My entry for November #memeMonday to @sqlrockstar on #sqlfamily:
What is a family? It consists of a group of people in which some are adults and some are children. What they do? They nurture each other, encourage, entertain and sometimes make each other angry as well. But they know that all family members are there for each other in thin or thick. Similarly #sqlfamily is a group of people who are passionate about SQL Server technology and they help each other through the problems and they learn from each other, they meet and greet each other at events and keep the connection after the meetings. There are some clashes of opinions also in this #sqlfamily like any other family, but they know that members of #sqlfamily are always there to cheer them up. They always find a common ground.
Today one of our application team requested to build new sql server 2008 R2. I asked them about the edition. They said only requirement is it should be able to handle 32 GB of RAM, other than that we are not using any high availability features. I installed sql 2008 R2 Standard. It supports up to 64 GB of memory. We moved the 6.5 TB database from the older machine having SQL2008 Developer Edition to new machine. This is how it was done. We first detached the existing database, shutdown sql server and moved the powervault containing data and log files to the new server. We brought the new server online. Sql server service was set to automatic start on the new server. Now we can see the database but cannot see it properties, cannot drop it or detach it either. Error said “The database is suspect. In SQL Server 2005 and later versions, a suspect database cannot be detached; before you can detach it, you must put it into emergency mode.” I checked the state of database. “Select state_desc from sys.databases where name = ‘mydatabase’ “. It showed “Recovery Pending”. Another error said something like this “This database uses compression and this version of sql server does not support compression. Need to Upgrade”. We got the point. We tried to put the database in emergency mode “Alter database mydatabase set emergency” but it complained “ it has to be in single user mode”.
So we put it in single user mode. “Alter database mydatabase set single_user”. Then we put it in emergency mode. Again I checked the state of database. “Select state_desc from sys.databases where name = ‘mydatabase’. It showed “Online”. Now I tried to detach the database and it complained “database is in single user mode, cannot detach”. Ok, we put it in multi_user mode and then detached successfully using GUI.
After this I upgraded using the maintenance option of setup GUI and upgraded it to Enterprise Edition. Then I attached the database using the GUI and 6.5 TB database came on line in less than 15 seconds. Altogether it took me 20 minutes. I like to give credit to Paul Randal’s (@PaulRandal) article http://www.sqlskills.com/blogs/paul/post/checkdb-from-every-angle-emergency-mode-repair-the-very-very-last-resort.aspx whithout which it would have taken us much longer.
Deadlock blocks lock. Optimize indexes and rock!.
I attended sqlsaturday67 and attended Brent Ozar and Tim Ford’s sessions. Bill is president of sql server user group in Chicago and I helped him on the registration desk on the day of the event. So I added them as my tags.