In general it is not a best practice to perform SHRINK database operation on a production server, atleast regularly! Sometimes it may be compulsory to keep them sized in order to ensure the disk storage is not compromised for any sudden changes to databases ETL processes, coming to the point by design...
When do you need data partitioning? The data you see in relational database may need such a strategy if the volume is huge, for instance the data to store event-log information having the schema such as: [Id] INT (make this primary key clustered), [Unit_Id] UNIQUEIDENTIFIER, [EventType_Id] UNIQUEIDENTIFIER...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
03-12-2008
Filed under: sql server, performance, indexes, data, backup, bi, database, statistics, partition, monitoring, strategy, data warehouse
Though it is not a best practice to perform a CREATE INDEX on large tables during the online hours where you have number of users accessing the metadata of SQL Server database. Within SQL Server 2005 Enterprise Edition you can perform ONLINE indexes operation, in this regard review the blogs by SQLQuery...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
01-25-2008
Filed under: sql server, performance, indexes, cache, users, tsql, best practice, backups, create, online, monitoring, operating system, busy, creation
As a DBA you should now how locking works with tables and how best you can make use of indexing enhancements within SQL Server 2005 version. Until SQL 2000 there was a limited availability of documentation on the guidelines even in the Books online and most of the times we have to depend upon the web...