I think I posted my Error on creating the SQL 7.0 DB in the worng place - My apologies, if this a duplicate entry -

I have used ISQL to create the DB.

I resolved the COLLATE problem and now only one remains, as follows -

Server: Msg 195, Level 15, State 10, Procedure wwfSpDBinfo, Line 33
'ServerProperty' is not a recognized function name.

I have editied out all the COLLATE statements, and this one remains- any advice on this one please ?

Jon (spartanx15) email: mailto:jonux@ixtech.net - jonux@ixtech.net

The error occurs within the following lines -

---Creating Output Table
select  @dbsize Databasesize, @dbpath DataLocation , @logpath LogLocation,
 @dbfilesize DatabaseFileSize, @logfilesize Logfilesize,
 @maxdbfilesize MaxDBSize, @maxlogfilesize MazLogSize,
 ServerProperty('edition') Edition,
 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

SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO

-boRg- wrote: Use the MSSQL_server_setup.asp file to seyup the database. Please read the documentation.

Hi boRg

There was another thread on this as well, and the person mentioned that he had previously used the setup script ... and it was failing.

Your setup script uses code which will not work with MSSQL7, specifically setting up the DBinfo proc, and specifically

ServerProperty

Someone might want to mention to ignore this in the install instructions.

Jon Spartan

THe adjusted script that was posted will allow SQL7 and the admin page to still work.

Having a page "not work", I would believe, will just create more of a support headache.

Welp, we use enterprise versions. The cost of another SQL Server Enterpise would be about $ 11,000.00 USD.

Sometimes we have to balance the costs of upgrades to new servers versus the rewards and conversion costs. Admitidly there are many reasons to go to SQL Server 2003, however for us it would also entail moving to Win 2003 Advanced Server so another 5K plus CALs. Oh, yes, I really would like to deploy a replacement to our SQL 7.0 ( we are using SQL 2000 but not for web work ).

For many companies it many not be worth the price. However short note in the ASP script to disregard the error and a "why" might be of assistance to others ? Would you not agree ?

BTW I, for one, think this is a good thing we are discussing here, provided no one takes offense, because it sounds like a few of us have been around this block many times and maybe we might add something of benefit to our less experienced collegues. After all it is what Forums are for, no ? And I learn some things along the way also. After 30 years in the compuiting business, right back to the days where we were a cabal of mysterious programmers working in assembly, there are many things yet for me to learn. Thus discussions here and everywhere, allow myself to learn many new things and new ways of thinking, working on systems, and wokring throughout the world. I am hoping all will agree ?

Jon Spartan.