October 17, 2002 at 10:07 am
Without providing a dissertation on what I'm doing...Our team has added functionality to our tools to "track" their usage. As a tool is used, we record 15-15k of data in local memory. When the user closes the tool, we connect to a SQL db and fire off a sp. The sp adds or updates the database with the row sent by the app. We have about 9,000 users of our tools and have 43 tools in production. I'm not so concerned with the connections to the database as we've limited that by holding the data in local memory. My concern is that we only have about 10% of our users with tools that are tracked and since May we have accumulated 1.2 million records. At what point do we need to consider a dedicated server? What about going to DB2 if performance begins to suffer? Please assume that we've set up everything in the app db and server as efficiently as possible.
October 17, 2002 at 1:23 pm
I think the max number of rows a table can have is only limited by how much hard drive space you have.
BOL says this about the max number of databases per server:
A maximum of 32,767 databases can be specified on a server.
Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
October 17, 2002 at 6:32 pm
Put it this way MS found it difficult to find a source of data that tested the limits of SQL server and came up with satellite pictures and thus terraserver, that was for SQL 7.
AS for dedicated server it all depends on what you are doing with your data, the volumns (Mb) cpu and memory usage.
Simon Sabin
Co-author of SQL Server 2000 XML Distilled
http://www.amazon.co.uk/exec/obidos/ASIN/1904347088
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
October 17, 2002 at 6:42 pm
Agree that I dont think max records will be an issue. Keep the columns small, index lightly, even consider inserting into a staging table during the day, do a batch insert into the indexed main table at night if you need the extra performance.
Andy
October 18, 2002 at 4:45 am
The only limits on a table you may run into is if you use an Identity column and it is limited to the max number that can be generated by the datatype itself. INT is standard and will go up to 2,147,483,647, in addition if you have SQL 2000 you can use BIGINT which goes to 9,223,372,036,854,775,807. If you can reach those numbers you can always look to the data itself to help handle. And terraserver is well into the terabyte size range.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply