January 27, 2009 at 8:46 am
I'm looking for anyone with any good ideas as to what's happening here. We have a server that is reporting itself as MSDE. A properties on the Registration in Enterprise Manager claims to be SQL Server Desktop Engine Build 8.00.2050(SP4), and the SQL Server H2 Tool from Microsoft sees it as MSDE.
Running a select @@version gives the following output:
Microsoft SQL Server 2000 - 8.00.2050 (Intel X86) Mar 7 2008 21:29:56 Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
However this server is happily running a database that has a 5,384.32MB mdf file (with 2,263.66MB of free space). This shouldn't be possible if the server is running MSDE as it claims. Has anyone else ever seen this? And does anyone know of a way we can find out what this server is actually running (since it can't be MSDE).
February 3, 2009 at 6:56 am
What do you see when you run select * from spt_server_info?
MJ
February 3, 2009 at 7:08 am
Hi
This page http://support.microsoft.com/kb/321185
gives you this bit of code:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
which will show you the edition and service pack for your SQL boxes
Seth
February 3, 2009 at 7:45 am
I'm off work ill at the moment, but I'll post the info as soon as I get into the office again.
February 4, 2009 at 6:36 am
Thanks to both Seth and MJ for excellent suggestions, and both of these report SQL Server 2000 Desktop Edition.
The mystery deepens, as it is still managing to run a 5GB database :crazy:
February 4, 2009 at 7:07 am
Can you plz post the output of
USE Databasename
sp_spaceused @updateusage = 'TRUE'
MJ
February 17, 2009 at 4:43 am
Hi MJ,
Sorry for the massive delay getting back to you, but things went a bit mad here for a while. Anyhooo, in answer to your question here's the output:
DBName db_size unallocated
PcDocsLib18423.00 MB2205.42 MB
Reserved data index_size unused
3202768 KB1910488 KB1258448 KB33832 KB
Interesting, despit the db_size being over 8GB, it would seem that only about 1.9GB is data. I guess this might be how MSDE is managing to still run an 8GB database
Andy
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply