Almost every DBA will be asked to change data in production at some point. Too often we don't have the tools to allow users to correct errors, but when you make changes, Steve Jones reminds you that you need to be careful and still have a process.
As a DBA, you'll encounter elusive performance, connectivity and locking problems that you'll need to troubleshoot. There are many tools that you can use such as Profiler. In addition to these tools, SQL Server 2008 offers extended events ("XEvents"), which you can use as a powerful tracing system. By default, the "system_health" extended events session is always on, and can provide you help to locate the source of trouble much faster.
Can one generalize from agile techniques of application testing to database testing. Phil isn't entirely convinced that it can do any more that remove the distracting trivial bugs in order to allow testers to concentrate on the important issues
SQL 2008 has some key improvements over SQL 2005. This article deals with backup compression and faster backups in SQL 2008
Your job is to scan the trades data and identify combination of trades that match a given rollup data.
An open call to the amatuers that might want to pen some database related cartoons for Simple Talk Publishing.
Should we really avoid cursors? See how to rewrite code to avoid cursors and also analyze the implications.
Today Steve Jones asks how you handle those passwords across time for backups in this week's Friday poll.
By Steve Jones
A customer was trying to compare two tables and capture a state as a...
By Zikato
When I'm looking at a query, I bet it's bad if I see... a...
By Steve Jones
This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...
Wa:0821-4447-7715 Jl. A. R. Hakim No.2, Mangkukusuman, Kec. Tegal Tim., Kota Tegal, Jawa Tengah...
Wa:0821-4447-7715 Jl. Jend. Sudirman No.49-51, Terban, Kec. Gondokusuman, Kota Yogyakarta, Daerah Istimewa Yogyakarta 55223
Comments posted to this topic are about the item A Quick Second Opinion
On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?
See possible answers