Home > Archive > MS SQL Server New Users > December 2005 > single vs multiple catalogs performance









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author single vs multiple catalogs performance
Tharon LeBlanc

2005-12-14, 8:25 pm

When designing a system we have used a single catalog for maintaining
clients data and differentiated by using a unique key.

Is it a better practice to map each user to a separate catalog or use a
single one in terms of performance on the server and clients? While I would
think this would make maintenance easier and reduce row numbers in the
tables, what impact does it have on the server and clients? Thanks very
much ahead of time.

Context:
* We are currently using MSSQL2000 and may switch to MSSQL2005.
* Most tables may be replicated on a backup DB server


Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com