Info on VLDB (Very Large Database) scenarios?

So, the boss asked how Sql 2005 does with VLDBs (Very Large Database). Can someone, anyone, point me in the direction of some reliable, relevant information related to Sql 2005 and VLDBs?

I'm having a tough time finding anything with numbers, Gigs, Terabytes, stats... case studies, etc.

Thanks.

SQL Server 2005 is more robust for VLDB, it has a lot of enhancements:

Backup and Restore operations

Import/Export Operations

Case Studies:

http://www.microsoft.com/sql/prodinfo/casestudies/default.mspx

|||

I have a lot of experience in this area. My team , SQL Server Customer Advisory Team (SQLCAT), has helped many customers design, build and deploy some very large SQL Server implementations. The post before this had a good link to some case studies. You also want to check out the last WinterCorp study which records database sizes (Just search on WinterCorp) or go to www.wintercorp.com.

SQL Server has several production systems above 10TB today in production. One example is an internal application (around 20TB) where we load up to 1TB each day into the server daily and delete nearly as much. We are also working on a couple of projects that will be 5x-10x that size in the future but I can't elaborate too much. Feel free to contact me offline to discuss: mark.souza@.microsoft.com. Also check out our blog: http://blogs.msdn.com/sqlcat

|||

http://www.microsoft.com/sql/prodinfo/compare/wintercorp-survey.mspx

Info on VLDB (Very Large Database) scenarios?

So, the boss asked how Sql 2005 does with VLDBs (Very Large Database). Can someone, anyone, point me in the direction of some reliable, relevant information related to Sql 2005 and VLDBs?

I'm having a tough time finding anything with numbers, Gigs, Terabytes, stats... case studies, etc.

Thanks.

SQL Server 2005 is more robust for VLDB, it has a lot of enhancements:

Backup and Restore operations

Import/Export Operations

Case Studies:

http://www.microsoft.com/sql/prodinfo/casestudies/default.mspx

|||

I have a lot of experience in this area. My team , SQL Server Customer Advisory Team (SQLCAT), has helped many customers design, build and deploy some very large SQL Server implementations. The post before this had a good link to some case studies. You also want to check out the last WinterCorp study which records database sizes (Just search on WinterCorp) or go to www.wintercorp.com.

SQL Server has several production systems above 10TB today in production. One example is an internal application (around 20TB) where we load up to 1TB each day into the server daily and delete nearly as much. We are also working on a couple of projects that will be 5x-10x that size in the future but I can't elaborate too much. Feel free to contact me offline to discuss: mark.souza@.microsoft.com. Also check out our blog: http://blogs.msdn.com/sqlcat

|||

http://www.microsoft.com/sql/prodinfo/compare/wintercorp-survey.mspx

INF & IND errors

How do I update or delete a record with this floating point error in X
field? And, what the heck causes it?
Thanks!
Chris
Are you seeing 1.#inf values? That generally has something
to do with Microsoft's implementation of the IEEE standard
for floating point values - there are some values where the
representation of the value gets hosed out.
Are you trying to use column X in the where clause of your
delete or update statement?
-Sue
On Fri, 7 Oct 2005 10:43:54 -0400, "Chris Marsh"
<cmarsh@.synergy-intl.com> wrote:

>How do I update or delete a record with this floating point error in X
>field? And, what the heck causes it?
>Thanks!
>Chris
>

INF & IND errors

How do I update or delete a record with this floating point error in X
field? And, what the heck causes it?
Thanks!
ChrisAre you seeing 1.#inf values? That generally has something
to do with Microsoft's implementation of the IEEE standard
for floating point values - there are some values where the
representation of the value gets hosed out.
Are you trying to use column X in the where clause of your
delete or update statement?
-Sue
On Fri, 7 Oct 2005 10:43:54 -0400, "Chris Marsh"
<cmarsh@.synergy-intl.com> wrote:

>How do I update or delete a record with this floating point error in X
>field? And, what the heck causes it?
>Thanks!
>Chris
>