SQL Server has the best client tools for a DBA of any RDBMS and SQL Server 2000 includes Query Analyzer, an amazing tool. There are a few places where this tool could use some improvement and Yakov Shlafman brings us a few ways that you make your work with Query Analyzer even smoother.
2005-09-29
16,268 reads
SQL Server 2000 has a great set of administrative and development tools, one of the most heavily used of which is Enterprise Manager. Sushila Iyer brings us a fantastic article with some tricks in using this tool to create and manipulate tables.
2005-09-26
16,251 reads
If you are working with SQL Server 2005, you really need Visual Studio 2005 as well. And since they are both in Beta, there are some interesting issues when installing both of these pre-products. New author David Russell brings us some technical notes he made while installing both of these many times in a corporate environment.
2005-09-14
52,706 reads
SQL Server 2000 has a fantastic subsystem for alerting the DBA and keeping him or her informed as to the state of the server. However the email subsystem introduces a dependency on Outlook for alerts that can be a problem for some environments. Author Roy Carlson brings us an ingenious method for reading logs and sending alerts without Exchange or Outlook.
2005-09-12
12,505 reads
Ensuring your SQL Server is performing well is a large part of any good DBA's job. It is not just writing good queries, but also monitoring your server and getting alerts on critical issues. Mike Metcalf has brought us a great article that shows how you can setup performance alerts and be notified via SMTP.
2005-08-31
13,145 reads
SQL Server 2000 has a great scheduler in SQL Agent, but it isn't integrated with anything else. And with lots of servers, having a centralized environment is essential to keeping yourself from being overworked. Author Sureshkumar Ramakrishnan brings us his technique for running SQL Server jobs from an external scheduler.
2005-08-24
14,509 reads
2005-08-15
1,715 reads
2005-07-26
1,365 reads
When Database Administrators manage multiple databases on multiple servers, it is difficult to keep track of and monitor the used percentage of data portion on every database. Though SQL Server has the capability of auto growth whenever the data portion reaches 100%, it is always advisable to increase the database size manually when it comes to VLDB. This article examines monitoring the percentage used on the data portion of every database and alerting the DBA using threshold settings. This article has been written for SQL Server 2000 server.
2005-07-18
1,765 reads
How many times have you run out of space in a database? What about on a file system? Andy Warren has had this happen a few times, especially when large imports take place. He brings us an article that describes some of the precautions he has taken to prevent this from happening.
2005-07-14
11,202 reads
By Vinay Thakur
I wrote about TempDB Internals and understand that Tempdb plays very important role on...
By Vinay Thakur
continuing from Day 1 where we covered the history of AI and GPT family,...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers