As a DBA you might be aware that since SQL Server 2005 database maintenace plans have given flexibility in deploying the workflow of tasks required to make sure that your database is optimized, is regularly backed up, and is free of inconsistencies in addition to the avoiding the fragmentation on indexes...
You may be aware that Database Mirroring is an important High Availability [HA] option available within SQL Server 2005 version. Having this HA option within your Sharepoint farm where the databases are associated to failover, then you must note few issues that might crop up in this case. Also you should...
Until last month I was not aware about Volume Shadow Copy and what is the relation between that service & SQL Server services, so here I would like to give the information in this regard that will discuss SQL Server connection issues that you may encounter when you use Volume Shadow Copy Service...
Upgrading a SQL Server database should be straight-forward, when you haven't got much of constraints on the application code. In this regard we have blogged previously such as UpgrageTags posts. Here in this post I would like to go with few FAQs that are related to Upgrade process & procedure...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
01-22-2008
Filed under: sql server, database, upgrade, best practices, sa, clustering, database mail, data files, FAQ, gotchas, sqlmail
How can you calculate size of an index in a database whenever a capacity planning exercise if performed? By default the size allocated for each user objects depends on the user application and on the amount of space that is created by the application for user-defined tables, global and local temporary...