Oops, we have a 1.3 TB Database
-
As the title of this thread indicates, we do have a Geospatial DB file in excess of 1 Terabyte in size. The books, and Microsoft site says for SQL Server 2000 (and we have SP3a), the size should not exceed 1024 GB (1 TB).
If we broke this up into 2 x 512 GB databases might we see a noticable difference in performance and would it just be darn safer to do this?
Thanks,
Chris
-
Are you sure you're reading that right? Books Online says
Database size 1,048,516 TB3 Databases per instance of SQL Server 32,767 Filegroups per database 256 Files per database 32,767 File size (data) 32 TB File size (log) 32 TB Which would indicate that you're way under the limits
If you're not already doing it, I would suggest you break the database up into filegroups though.
--------------------
Colt 45 - the original point and click interface
-
Well, as you know, you're right! I don't know how I "saw" that in that way.
Now that I'm "really" awake this morning I see what you mean.
Thanks for the double check.
-
Here are some more to read:
http://www.microsoft.com/sql/techinfo/administration/2000/rosetta.asp
http://www.microsoft.com/technet/prodtechnol/sql/2000/plan/ssmsam.mspx
http://www.microsoft.com/sql/techinfo/administration/2000/scalability.asp
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url] -
Thanks Frank, these look VERY informative. I appreciate the advice.
Cheers,
Chris
-
Thanks Frank, these look VERY informative. I appreciate the advice.
Cheers,
Chris
-
Thanks Frank, these look VERY informative. I appreciate the advice.
Cheers,
Chris
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply