By Saleem Hakani (Microsoft Corporation) on 6/7/2011 12:29 PM
Ever wanted to find out what was happening when SQL Server crashed? Your investigation should also include reviewing the SQL Server activities much like what profiler would do. SQL Server 2008 (Including SQL2K5) out of the box comes with a default trace enabled. This trace keeps track of configuration changes, process level information and other information that can be very helpful for troubleshooting SQL Server related issues. |
By Saleem Hakani (Microsoft Corporation) on 2/1/2011 9:46 PM
What if you have 100's of SQL Server 2005 in your company and you would like to configure all the servers based on some standards (Example: Surface Area Configuration Properties). Take an example you have just installed a SQL Server and also have configured the surface area configuration (SAC) for that SQL Server based on your standards and now you would like to replicate this configuration to 100's and 1000's of other SQL Servers in your company. How would you do that? |
By Bellevue College Student on 2/1/2011 8:31 PM
Posted by: Chun-Ming Chen (Bellevue College Student, WA)
Concurrency is an ability that allows multiple users to access the same data at the same time. However as more users access the data at the same time, the greater the chance for users to change the same set of data at the same time and overwrite each other’s input. The integrity of the data is compromised without the users initiating the operations knowing it. There are four types of concurrency problems:
· Lost updates
· Dirty reads (uncommitted dependencies) · Nonrepeatable reads (inconsistent analysis) · Phantom reads |
By Saleem Hakani (Microsoft Corporation) on 1/29/2011 12:19 AM
There are times when you may want to create indexes on large tables which may take huge amount of time (sometimes several hours) and yet you want to make the data available during the creation of Index as your database is being used by thousands of users in the production environment. |
By Saleem Hakani (Microsoft Corporation) on 1/29/2011 12:16 AM
Starting with SQL Server 2005, putting user database in EMERGENCY mode is now a supported and documented feature (unlike SQL Server 2000 and SQL Server 7.0 where you had to change the status of SYSDATABASES) |
By Saleem Hakani (Microsoft Corporation) on 1/29/2011 12:11 AM
One of the best features of SQL Server 2005 & 2008 that I like is that it lets you perform restore on portions of the database which is damaged and yet keep the database ONLINE. This was not possible with earlier versions of SQL Server. In SQL Server 2005/2008, you no longer have to take the database offline to perform a restore on a small portion of a database. Once you have identified the pages that need to be restored you have two options:
1) You can perform a PAGE level restore (My recommendation is to do this when you have small number of pages)
2) You can perform a FILE level restore (My recommendation is to do this when you have large number of pages) |
By Saleem Hakani (Microsoft Corporation) on 1/29/2011 12:06 AM
Did you know that prior to SQL Server 2005, Microsoft used to ship an executable called "REBUILDM.EXE" that would help you rebuild the Master database? The world has changed and so has SQL Server and REBUILDM.EXE tool. |
By Saleem Hakani (Microsoft Corporation) on 12/29/2010 2:46 AM
There are times when you may want to change the date to a specific format at the server level instead of making changes to individual procedures/objects. It would be very tough to perform this change at every object level. However, below commands will help you identify the current date format at the server level and how to change that format. |