kevriley (7/3/2008)

---

Plus be careful when calculating the number of bytes per row, as SQL will store some data off-row if the on-row limit is reached - so whilst the spec...

The capacity specs are listed in books online. to briefly summarise:

Rather create one database. The data volumes don't seem to be sufficient for the increase administrative complexity of multiple DBs

Thanks All

Jo'burg. Are you coming to Teched next...

Please don't cross post. It just wastes people's time and fragments replies. many of us read all the forums.

No replies to this thread please. Direct replies to:

http://www.sqlservercentral.com/Forums/Topic527823-338-1.aspx

Are you viewing this in management studio? There's a setting (Tools -> Options, expand out query results, SQL Server) that says how much data is displayed in text or grid...

Thanks

From what you've said I'd recommend that you use one database and ensure that your code is written properly and your indexes are useful

How much data are we talking...

Please don't coss post. It just wastes time and fragments replies. Many of us read all the forums

No replies to this thread please. Direct replies to:

http://www.sqlservercentral.com/Forums/Topic527770-149-1.aspx

I suggest that you don't shrink your databases at all. Databases tend...

Ouch. You have some nasty memory issues.

What's SQL's max and min memory set to?

Is there anything else running on that box?

2008-06-25 01:34:00.31 spid3 SQL Server is...

To the best of my knowledge, yes

Possibly. It depends on...

Don't shrink your databases.

Make sure that you have a good backup strategy

Make sure that you test your backups. A backup that you cannot restore is worse than no backup at...

Cuold you post all the code please. Including where @db coems from?

Not a bad idea....