Tips
Dedicated Administrator Connection in SQL Server 2005
In years and versions of SQL Server gone by, at times it was impossible to gain access to SQL Server when the server had a spinloop, maxed out resources or severe corruption. With SQL Server 2005, Microsoft offers a new feature, the dedicated administrator connection. This configuration is intended to serve as a last means of defense to troubleshoot and kill the offending SQL Server processes as opposed to rebooting the server.
Digging into Microsoft Data Protection Manager V2
I have heard about Microsoft Data Protection Manager V2 as a portion of the System Center Data Protection Manager that Microsoft is supposed to be releasing shortly. I have heard this technology is backup or CDP related. What exactly is this technology? What does it mean to me as SQL Server DBA, Network Administrator or Backup Administrator? What benefits can I expect to yield from this technology?
Disaster Recovery Procedures in SQL Server 2005 Part 1
SQL Server 2005 has given us a lot of options on implementing high availability and disaster recovery. More than the technologies themselves, it is important to come up with the proper procedures as we manage different disaster recovery scenarios. How do we come up with procedures for various SQL Server disaster recovery scenarios?
Disaster Recovery Procedures in SQL Server 2005 Part 2 (Isolating Critical Objects)
In a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 1, we have seen how we can come up with a disaster recovery procedure in SQL Server 2005. There are other ways to increase availability of your highly critical database in SQL Server 2005. What are those other options?
Disaster Recovery Procedures in SQL Server 2005 Part 3 (Using Partitioned Tables with Multiple Filegroups for High Availability)
In a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 1, we have seen how we can come up with a disaster recovery procedure in SQL Server 2005. There are other ways to increase availability of your highly critical database in SQL Server 2005. What are those other options?
Migrating a SQL Server Instance
I need to migrate an instance of SQL Server 2000 due to a hardware issue that I am having. What are the steps that I should take before, during and after the process? What pit falls should I watch out for?
Rebuilding the SQL Server master database - Part 1
I recently found myself in a situation where I had to rebuild the master database on one of the nodes of our development SQL 2005 cluster. The process itself is quite simple, the proof is in the preparation however. The chances things will go wrong are low, but you still need to be prepared for the possibility that your quick rebuild is anything but. The need to prepare is critical because once you rebuild the master database you'll notice that there is a little issue involving NO LOGINS! The rebuild gives you a new master database fresh from the DVD. So, how do you prepare for a master rebuild and what do you do afterwards?
Rebuilding the SQL Server master database - Part 2
Previously in this series about how to rebuild the master database, we itemized the steps required to prepare for rebuilding the master database. In the third tip in the series will present how to restore your SQL instance back to the state it was in prior to the rebuild process. In this tip, it presents what is involved in destroying your instance which is really what a rebuild does, believe it or not. I know that is a fairly-severe description of what you're about to do, but this is what it feels like when you're just about to hit the F5 key that executes that first query that detaches all your user databases.
Rebuilding the SQL Server master database - Part 3
So far we have prepared for the rebuild of our master database and have gone through the surprisingly simple rebuild process. (One of those DBA things where you spend all of your time on the preparation for something to go wrong, but everything goes off without a hitch!) Now we find ourselves at the point where we need to recover all the data we have lost in the process: the logins, the jobs, oh those databases too. I guess those may be a tad bit important too! Let's get to work, shall we?
SQL Server Disaster Recovery Planning and Testing
One old adage that has stood the test of time is "you will never know until you try". I would have to say that is the case with a disaster recovery plan. I would be surprised to hear any company relying on IT does not have a disaster recovery plan. Some are probably more formal than others, but in the middle of many of those plans are SQL Servers and the need to recover them quickly to maintain the business operations. But have you put your plan to the test? What about when key people are out of town? Or when you do not have direct access to your SQL Servers or network? Does your DR Plan fall into place or does it fall like a house of cards?
SQL Server Log Shipping
There has been a lot written about SQL Server Log Shipping as well as several scripts and techniques for implementing this process. Basically Log Shipping is the process of backing up your database and restoring these backups to another server for failover. To keep the data current and to minimize risk of data loss the process involves using SQL Server transaction log backups. By using transaction log backups the size of the backups are much smaller than full backups and the restore process can be done on a continuous basis. So how do you implement Log Shipping?
Using Page Level Restore as a Disaster Recovery Procedure in SQL Server 2005
In a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 1, we have seen how we can come up with a disaster recovery procedure in SQL Server 2005. There are other ways to increase availability of your highly critical database in SQL Server 2005. What are those other options?
Who are the hosting companies that support SQL Server?
Finding a hosting company that will meet all of your needs can be a complex task. Knowing where to turn and trusting that the hosting company will take the same level of care as you do is a challenge. This is balanced with the notion that the hosting company has the needed expertise and will remove the burden of managing the infrastructure in order for you to focus on core business needs.
Top 10
Rebuilding the SQL Server master database - Part 1
I recently found myself in a situation where I had to rebuild the master database on one of the nodes of our development SQL 2005 cluster. The process itself is quite simple, the proof is in the preparation however. The chances things will go wrong are low, but you still need to be prepared for the possibility that your quick rebuild is anything but. The need to prepare is critical because once you rebuild the master database you'll notice that there is a little issue involving NO LOGINS! The rebuild gives you a new master database fresh from the DVD. So, how do you prepare for a master rebuild and what do you do afterwards?
SQL Server Log Shipping
There has been a lot written about SQL Server Log Shipping as well as several scripts and techniques for implementing this process. Basically Log Shipping is the process of backing up your database and restoring these backups to another server for failover. To keep the data current and to minimize risk of data loss the process involves using SQL Server transaction log backups. By using transaction log backups the size of the backups are much smaller than full backups and the restore process can be done on a continuous basis. So how do you implement Log Shipping?
Disaster Recovery Procedures in SQL Server 2005 Part 1
SQL Server 2005 has given us a lot of options on implementing high availability and disaster recovery. More than the technologies themselves, it is important to come up with the proper procedures as we manage different disaster recovery scenarios. How do we come up with procedures for various SQL Server disaster recovery scenarios?
Rebuilding the SQL Server master database - Part 2
Previously in this series about how to rebuild the master database, we itemized the steps required to prepare for rebuilding the master database. In the third tip in the series will present how to restore your SQL instance back to the state it was in prior to the rebuild process. In this tip, it presents what is involved in destroying your instance which is really what a rebuild does, believe it or not. I know that is a fairly-severe description of what you're about to do, but this is what it feels like when you're just about to hit the F5 key that executes that first query that detaches all your user databases.
Dedicated Administrator Connection in SQL Server 2005
In years and versions of SQL Server gone by, at times it was impossible to gain access to SQL Server when the server had a spinloop, maxed out resources or severe corruption. With SQL Server 2005, Microsoft offers a new feature, the dedicated administrator connection. This configuration is intended to serve as a last means of defense to troubleshoot and kill the offending SQL Server processes as opposed to rebooting the server.
Disaster Recovery Procedures in SQL Server 2005 Part 3 (Using Partitioned Tables with Multiple Filegroups for High Availability)
In a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 1, we have seen how we can come up with a disaster recovery procedure in SQL Server 2005. There are other ways to increase availability of your highly critical database in SQL Server 2005. What are those other options?
Rebuilding the SQL Server master database - Part 3
So far we have prepared for the rebuild of our master database and have gone through the surprisingly simple rebuild process. (One of those DBA things where you spend all of your time on the preparation for something to go wrong, but everything goes off without a hitch!) Now we find ourselves at the point where we need to recover all the data we have lost in the process: the logins, the jobs, oh those databases too. I guess those may be a tad bit important too! Let's get to work, shall we?
Migrating a SQL Server Instance
I need to migrate an instance of SQL Server 2000 due to a hardware issue that I am having. What are the steps that I should take before, during and after the process? What pit falls should I watch out for?
Disaster Recovery Procedures in SQL Server 2005 Part 2 (Isolating Critical Objects)
In a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 1, we have seen how we can come up with a disaster recovery procedure in SQL Server 2005. There are other ways to increase availability of your highly critical database in SQL Server 2005. What are those other options?
Using Page Level Restore as a Disaster Recovery Procedure in SQL Server 2005
In a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 1, we have seen how we can come up with a disaster recovery procedure in SQL Server 2005. There are other ways to increase availability of your highly critical database in SQL Server 2005. What are those other options?
Last 10
Using Page Level Restore as a Disaster Recovery Procedure in SQL Server 2005
In a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 1, we have seen how we can come up with a disaster recovery procedure in SQL Server 2005. There are other ways to increase availability of your highly critical database in SQL Server 2005. What are those other options?
Disaster Recovery Procedures in SQL Server 2005 Part 3 (Using Partitioned Tables with Multiple Filegroups for High Availability)
In a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 1, we have seen how we can come up with a disaster recovery procedure in SQL Server 2005. There are other ways to increase availability of your highly critical database in SQL Server 2005. What are those other options?
Disaster Recovery Procedures in SQL Server 2005 Part 2 (Isolating Critical Objects)
In a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 1, we have seen how we can come up with a disaster recovery procedure in SQL Server 2005. There are other ways to increase availability of your highly critical database in SQL Server 2005. What are those other options?
Disaster Recovery Procedures in SQL Server 2005 Part 1
SQL Server 2005 has given us a lot of options on implementing high availability and disaster recovery. More than the technologies themselves, it is important to come up with the proper procedures as we manage different disaster recovery scenarios. How do we come up with procedures for various SQL Server disaster recovery scenarios?
Rebuilding the SQL Server master database - Part 3
So far we have prepared for the rebuild of our master database and have gone through the surprisingly simple rebuild process. (One of those DBA things where you spend all of your time on the preparation for something to go wrong, but everything goes off without a hitch!) Now we find ourselves at the point where we need to recover all the data we have lost in the process: the logins, the jobs, oh those databases too. I guess those may be a tad bit important too! Let's get to work, shall we?
Rebuilding the SQL Server master database - Part 2
Previously in this series about how to rebuild the master database, we itemized the steps required to prepare for rebuilding the master database. In the third tip in the series will present how to restore your SQL instance back to the state it was in prior to the rebuild process. In this tip, it presents what is involved in destroying your instance which is really what a rebuild does, believe it or not. I know that is a fairly-severe description of what you're about to do, but this is what it feels like when you're just about to hit the F5 key that executes that first query that detaches all your user databases.
Rebuilding the SQL Server master database - Part 1
I recently found myself in a situation where I had to rebuild the master database on one of the nodes of our development SQL 2005 cluster. The process itself is quite simple, the proof is in the preparation however. The chances things will go wrong are low, but you still need to be prepared for the possibility that your quick rebuild is anything but. The need to prepare is critical because once you rebuild the master database you'll notice that there is a little issue involving NO LOGINS! The rebuild gives you a new master database fresh from the DVD. So, how do you prepare for a master rebuild and what do you do afterwards?
SQL Server Disaster Recovery Planning and Testing
One old adage that has stood the test of time is "you will never know until you try". I would have to say that is the case with a disaster recovery plan. I would be surprised to hear any company relying on IT does not have a disaster recovery plan. Some are probably more formal than others, but in the middle of many of those plans are SQL Servers and the need to recover them quickly to maintain the business operations. But have you put your plan to the test? What about when key people are out of town? Or when you do not have direct access to your SQL Servers or network? Does your DR Plan fall into place or does it fall like a house of cards?
Migrating a SQL Server Instance
I need to migrate an instance of SQL Server 2000 due to a hardware issue that I am having. What are the steps that I should take before, during and after the process? What pit falls should I watch out for?
Digging into Microsoft Data Protection Manager V2
I have heard about Microsoft Data Protection Manager V2 as a portion of the System Center Data Protection Manager that Microsoft is supposed to be releasing shortly. I have heard this technology is backup or CDP related. What exactly is this technology? What does it mean to me as SQL Server DBA, Network Administrator or Backup Administrator? What benefits can I expect to yield from this technology?
