How you use a synonym can be a huge asset or it can be a significant dampener to performance. There are benefits and uses for these nifty little things. Check them out and let us know how you have been able to put synonyms to use to benefit you.
1 DBA's Professional Blog
How you use a synonym can be a huge asset or it can be a significant dampener to performance. There are benefits and uses for these nifty little things. Check them out and let us know how you have been able to put synonyms to use to benefit you.
Have you ever taken over a server that had several maintenance plans on it? Have you ever really checked who the owner of those plans is? Or, maybe you had a failing job relating to one of these maintenance plans and you changed the job owner, but did you really fix the root cause? That could be one of those things that you inherited that could be annoying but you just don’t know it yet.
Yes Virginia, there are ghosts in your database. More specifically, there are ghosts in your SQL Server database. They are not there to haunt you. They are not there just for this holiday season (speaking of Halloween Month).
How can there be ghosts in the database?
Why would there be ghosts in the database?
Do they happen because somebody issued a KILL statement?
As is true in most facets of life, things tend to get stale and old. Sometimes this staleness can be visibly represented as the wrinkles on your face. Other times, as with SQL Server, it may mean that a stored procedure or view stops working.
Cannot use the special principal ‘dbo’. This error message can be misleading. This article will take you on a journey of common mis-steps along with the appropriate fix for this error.
It is not unusual to find a server where some random user created a bunch of jobs to be run by SQL Agent. Sometimes, the user creating the job(s) sets themself as the owner of the job. Learn how to efficiently manage the proper change of such job owners.
Runas should be a very common tool in the toolbox of all IT professionals – not just Data Professionals. Learning how to test different accounts is essential to being an effective and efficient professional that can provide solid results.
Starting SQL Server in single-user mode should be a tool every data professional holds in the bag. This is an essential tool that can be used in multiple scenarios and ensure you are able to fully maintain and control your server. This article will show how to start in single-user mode via two methods.
Losing access to a SQL instance is never a desirable situation – for the DBA. When the people that are supposed to have access, lose that access, all hope is not lost. There are plenty of methods available to regain the requisite access to manage the server. Today, I shared one such method that I view as being extremely easy. If you lose access, I would recommend taking the steps shown in this article to regain that access.
Every now and again we have to deal with a sudden requirements change. When that happens, we sometimes just need to take a step back and evaluate the entire situation to ensure we are proceeding down the right path. It is better to be pensive about the course of action rather than to knee jerk into the course of action. Do you want to spend 5 minutes on the solution or 30-40 minutes doing the same thing? Changing collation can be an easy change, or it can be one met with a bit of pain doing a reinstall (more painful if more user databases are present). Keep that in mind and keep cool when you need to make a sudden change.