The BestOf vol. 3 and Stumpers Vol. 2
New books from SQLServerCentral.com. The latest versions of our very popular SQL Server reference materials are now available.
2005-05-11
5,109 reads
New books from SQLServerCentral.com. The latest versions of our very popular SQL Server reference materials are now available.
2005-05-11
5,109 reads
The solution described below should probably not be considered a "best practice" but it works. It came to life as I was pondering the following conundrum: How can I pass a little bit of data from an internal Access application behind a firewall out to a public web site in real time?
2005-05-11
3,113 reads
Most of us have probably worked with some third party tool at some point in our SQL Server career. But how many tools have been written by a rocket scientist? Steve Jones had a chance to interview Red Gate Software's Simon Galbraith about a variety of topics. An interesting look at the software world through Simon's eyes.
2005-05-10
8,159 reads
Ongoing now, the SQL Server 2005 Roadshows in conjunction with PASS. Read Robert Pearl's notes from the show and if you are in Dallas or Houston or Europe, there is still time to attend on of these events.
2005-05-10
16,078 reads
In my article last month, I wrote about different methods you could use to identify the state of a SQL Server Agent job. One of the methods I discussed was using the undocumented extended stored procedure (XP) "xp_sqlagent_enum_jobs." In this article, I will show you how to use the "xp_sqlagent_enum_jobs" XP to help identify long running jobs.
2005-05-10
2,117 reads
The SQLAgent scheduler in SQL Server 2000 is an amazing tool that allows you to schedule many different kinds of jobs with a great deal of flexibility. However, it doesn't have great facilities for handling jobs that may take longer than expected. And about which you'd like to be notified. Leo Peysakhovich brings us his code and technique for detecting when a job step runs long.
2005-05-09
14,507 reads
It's now available!! Find out what's in there and where you can get it.
2005-05-09
22,057 reads
Backing up SQL Server data is like many of the things we do because we figure we need to. It is good for you, like eating a good diet and getting exercise. Unfortunately, folks are often about as successful with SQL Server backups as they are with diet and exercise.
This is the first in a series of articles covering SQL Server database backup. The series starts from the very basics of why database backup is important. The question of why to backup a database can inform many other decisions.
2005-05-09
2,411 reads
Query Analyzer is a great tool for developing SQL code. There are a number of little tricks that can greatly increase the amount of work you can do with very little effort. This article starts looking at some of the features of this tool.
2005-05-06 (first published: 2003-01-07)
70,340 reads
SQL Server Database administrators often copy(refer Fig 1.0) huge files, such as Full backup files and transaction log backup files from production to QA or from production to development environment and so on. Sometimes they need to copy source data files for importing. If they want to restore those Full backups or transaction log backup files or import those huge source files, they have to wait until the copy is complete.
2005-05-06
2,909 reads
By Steve Jones
This is timely, as I’m currently on a boat in the Adriatic taking a...
You can find the slides and SQL scripts for my session “Spice up your...
By SQLPals
How to Clear the SSMS Cache (SSMS 21 and Later) Updated...
Comments posted to this topic are about the item Risk Vs Reward, The never...
Hi, I have a trigger, that works fine elsewhere but is not working at...
In Azure SQL Database Hyperscale Edition, how many geo-replicas can be created?
See possible answers