Monday, July 1, 2013

[SQL Server] Performance Tuning on Very Small Databases - When is it worth it

[SQL Server] Performance Tuning on Very Small Databases - When is it worth it

Performance Tuning on Very Small Databases - When is it worth it

Posted: 01 Jul 2013 03:06 AM PDT

When does rebuilding an index make sense? When does Shrink Database make sense on a Very Small Database? Some say that on a Very Small Database, the indexing overhead can be larger than a disk cache. So, on a table of 10,000 records, less indexing might be better.The user forms and user look-ups seem to be very fast. The difference in indexing doesn't seem to make any difference so far.The front-end application is MS Access using DSN-Less linked tables with the SQL Server Native Client 11.0.The Citrix server resides in a rack and host the MS Access application in the same rack as the SQL Server 2008.The SQL Server 2008 has 6 small databases. The largest Database is 150 MB.All are new servers with plenty of RAM and processor, typically well under 20% system resource usage (processor, RAM, ...).Number of concurrent users is 5 to 25.There are no large imports and no batch jobs to transact. In a Compliance Database, most existing records have existing fields updated.When rebuilding indexes on the largest tables (between 20,000 rows to 300,000 rows in a big table) the percent fragmentation is 5% to 35%.The Database(s) will not grow 100% per year in size.

Replicating tables (temp) on another server

Posted: 30 Jun 2013 11:43 PM PDT

Hello all.I am in a situtation where I need to take data from a few of tables from our internal SQL Server (secured), create a few temp tables, and throw them out on a public web server every morning. Not having done this before, I am asking for some advice from anyone who has done this before. Generally speaking, what would be the best method of doing this?
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Search This Blog