Do you have to refresh a test or QA server from the production system? Do you have a good process or is it a spur of the moment, let's get it done thing? Here's a look at Steve Jones' process, which was used weekly for well over a year.
What happens when you have a day job, a web site, a new job at work, and a baby? Chaos! See what Andy's been up to the past few months. It's off topic from SQL of course, but it contains an interested bit or two.
Do you run an anti-virus product on your SQL Servers? After all, it's recommended, more and more, that you run anti-virus on ALL machines you have. There's just too much stuff running around out there. But putting this on a SQL Server creates some interesting issues. Our resident security guru, Brian Kelley, looks at some of the things you need to consider when deploying anti-virus products on your servers.
How can you tell if your code if performing well? Do you know what you want to look for when starting to analyze code? Here's an article from Leo Peysakhovich that looks at some of the things that you can use at a high level to improve the performance of your code.
Here's a little replacement for Query Analyzer that appears to provide most of the functions, plus a few more. While we haven't given it a full review, at first glance it appears to do the job. Plus there's NO INSTALL!!!! Always a plus for me.
How many of you register a server in Enterprise Manager? Now how many of you click the "save password" box? Probably most of you. Are you aware of the security risks associated with this? James Travis looks at one of potential problems here and other security issues relating to SQL-DMO.
Another look at how the next version of SQL Server will integrate and work with .NET technologies.
Although Brian likes that Microsoft delayed the next release of SQL Server for quality, he disagrees with the release strategy. See his opinion and argue your own!
It's been some time and he apologizes. This next part of this series from Steve Jones looks at selective auditing changes to data on the server using a combination of methods presented in previous articles in the series. Read on if you have problems tracking changes to data on some tables, but don't want to implement a solution that tracks every change.
Error handling is one of those things that is simple to do in SQL Server, but most people don't do it and it's not the most rebust thing. Here's another way that you can implement error handling in your stored procedures from a new author Amit Jethva.
By Steve Jones
vicarous – adj. curious to know what someone else would do if they were...
Say we have a database that we want to migrate a copy of into...
We are trying to get apps and users off of using SQL accounts to...
Hi I have this view to check if a job is running: SELECT...
All, if you are like me and do not care for the built-in color...
Certain internal SQL Server actions cause internal checkpoints. Which of these actions does not cause an internal checkpoint?
See possible answers