SQL Server Script Issues...

Yup ... my apologies ... there does appear to be a "ServerProperty" call in the setup script of the stored procedure wwfSPDBinfo. This would suggest it would never work under SQL7, contrary to the Requirements on this site?

Looking at the script Id say it should carry on and correctly setup the remainder of your database ....

Try this in Query Analyser

CREATE PROCEDURE [dbo].[wwfSpDBinfo] As
Declare @low int
Declare @dbsize dec(10,2)
Declare @dbpath nvarchar(100)
Declare @logpath nvarchar(100)
Declare @dbfilesize dec(10,2)
Declare @logfilesize dec(10,2)
Declare @maxdbfilesize dec(10,2)
Declare @maxlogfilesize dec(10,2)
 
--Minimum Database Size
select @low = low from master.dbo.spt_values
   where type = N'E' and number = 1
--Calculation of current Database Size in MB
select @dbsize = (convert(dec(15),sum(size)) *  @low  / 1048576)
from [sysfiles]
--Actual File Size of Log and Data File
Select TOP 1 @dbpath = [filename] from [sysfiles] where groupid = 1
Select TOP 1 @logpath = [filename] from [sysfiles] where groupid = 0
Select @dbfilesize =  convert(dec(10,2),sum([size]))/128 from [sysfiles] where [filename] = @dbpath     --in MB
Select @logfilesize = convert(dec(10,2),sum([size]))/128 from [sysfiles] where [filename] = @logpath   --in MB
Select TOP 1 @maxdbfilesize = convert(dec(10,2),[maxsize])/128 from [sysfiles] where [filename] = @dbpath
Select TOP 1 @maxlogfilesize = convert(dec(10,2),[maxsize])/128 from [sysfiles] where [filename] = @logpath
If @maxdbfilesize = (-.01) Set @maxdbfilesize = -1
If @maxlogfilesize = (-.01) Set @maxlogfilesize = -1
 
---Creating Output Table
select  @dbsize Databasesize, @dbpath DataLocation , @logpath LogLocation,
 @dbfilesize DatabaseFileSize, @logfilesize Logfilesize,
 @maxdbfilesize MaxDBSize, @maxlogfilesize MazLogSize, "" Edition, "" Cluster, "" Licensing, "" PLevel
 --ServerProperty('edition') Edition2
 --CASE ServerProperty('IsCluster')
  --WHEN 0 THEN 'No Cluster'
  --WHEN 1 THEN 'Cluster'
   --ELSE  'No Cluster/Unknown'
 --END Cluster,
 --CASE ServerProperty('License_Type')
  --WHEN 'PER_SEAT' THEN 'Seat Licensing (' + Convert(nvarchar(5),ServerProperty('NumLicenses')) + ')'
  --WHEN 'Per_Processor' THEN 'Processor Licensing (' + Convert(nvarchar(5),ServerProperty('NumLicenses')) + ')'
  --ELSE 'Licensing Disabled / Unknown'
 --END Licensing,
 --ServerProperty('ProductLevel') PLevel
GO

Worked fine, of course. Now we shall see if it affects/effects the Forum at all.

Many thanks. I hope the ASP script gets changed for other SQL 7.0 users.