Only a day left to register…
Webcast: Learn about managing your SQL Server data recovery vulnerabilities
In this session we’ll look into the different options you have available to protect your SQL Server investment. Learn about backup and restore, log shipping, replication and other tools you can use to help reduce risk. Find out what is involved, the pros and cons and where you can go to learn more about each option.
> Register Now
> Live date: 2/25/2009
Featured Article(s)
BCP from the Ground Up (Part 1)
Your boss comes to you and says that a vendor is going to massage your data for you and they will be sending you a file that will replace the data that you have in your table. This has to happen quickly and you will be getting this file every month. This could be a job for SSIS but you dont feel comfortable using it. BCP just may be your answer.
Let Site Administrators Recover Their Own Documents
Did you know that it’s possible to set up your SharePoint installation so your site administrators can do their own recovery? You can with Idera’s Point backup. This is a great option to both reduce administrator workload at the system level and also let your end-users begin to have a bit more control over their sites and site collections. Saving time, increasing end-user independence with controls – you can’t lose! Get more information here and see how Idera’s new Point backup takes care of things for you with SharePoint sites.
Do You Have a Plan?
I was talking with Kevin Kline today, he was in town for his sessions for the conference. He was talking what amounts to being a somewhat standardized approach to troubleshooting SQL Server (there’s even a session on it at the vConference). I’m not plugging the session or the conference (honest), but it had me wondering whether this should be standard for most SQL Server tool arsenals.
I know we’ve talked about "how to troubleshoot" stuff before, but the idea of a fairly well-tested set of steps that will help you get started investigating a specific issue is really appealing. When the chips are down and you’re chasing an issue with your system, having a checklist or other pre-built plan of attack to investigate an unknown-origin issue would be priceless and save your sanity.
Do you have a list? Have you established a plan? Now is the time, not later, that’s for certain.
A bit of advise for your list – start with the very, very simple items you need to consider. Always start there. Don’t assume you have a massive problem until you’ve eliminated all of the smaller, common things that could be happening. Sometimes, the best way to approach unknown issues is to assume the most simple causes, then set out to prove that it can’t be that. Only escalate severity and response when you know that the more straightforward possible causes are not in play with whatever issues you’re seeing.
Featured White Paper(s)
Real-Time Data Integration for the SQL Server Data Warehouse
The Microsoft SQL Server database is becoming an increasingly popular platform for hosting data warehouse and operational rep… (read more)