The book is almost here! We've been working on it for months, now you can find out what it's going to look like, who the authors are, and how much it costs. It's been a lot of work but we think it's been worth it. Read the article to see how to save $3 off an already low price.
The big day is Monday. The day you get to show off what you know about SQL Server 2000. The problem is, you're not really up to speed. Maybe it's been a while since you worked with SQL Server. Or maybe you just like a challenge. Open the book Friday evening and by Sunday afternoon, after completing 30 fast, focused sessions, you'll be able to get right to work on a SQL Server 2000 databases.(Not Reviewed)
This article from Robbe Morris at EggheadCafe.com looks at how to generate a script for a stored procedure that includes all it's dependencies.
Chris does a lot of work with IIS and based on that he put together this nice map showing how all the bits and pieces go together. No SQL here, but most of us deal with IIS so we thought it might be of interest.
David writes about the system he put together to handle addresses and the pros and cons of various techiques. Familiar with Soundex? He uses that too! Even though some of the info is specific to Great Britain, it's good reading. Addresses are one of the hardest pieces of information to handle!
This article, Part 2 – SQL Server 6.5 to 2000 Critical Upgrade Decisions and Redundant Upgrade Architecture, will begin to detail the technical components faced by the DBAs and Developers during the Upgrade process. The technical components detail the Critical Upgrade Decisions related to ANSI NULLS, Quoted Identifiers and other items.
As we mentioned before, Brian will be writing a column covering all facets of security. Turns out that there is so much to cover, he has agreed to write two columns per month! This article talks about the principle least privilege, why it doesn't always work, and some good info about removing the Builtin\Admin account.
Should your stored procedure continue when it hits an error? Or keep executing? What errors will cause a stored procedure to quit executing auotmatically? Regular columnist Robert Marda has at least some of the answers, we think you'll find this interesting.
This article from Veritas does a good overview of the complexities involved in managing a SAN. SAN's are here to stay, even if you don't have one, you should be reading about them.
Andy has been busy lately on a project you'll be hearing more about soon (!), but he did manage to get part four of his managing jobs series done. This article discusses ideas for patterns to follow when building jobs, including writing to the console, setting errorlevels, and how to get them installed on the server. DBA's, if you're not developers, look at this article - this is stuff you can take to your development team and get better/more manageable jobs.
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Hi everyone I am looking at building a query to determine how much time...
Comments posted to this topic are about the item SQL Server Transactional Replication from...
Comments posted to this topic are about the item Hidden Heroes
When thinking of the Identity property for auto incrementing columns and sequences for the same action, which are explicitly linked to increment a number in a table when a new row is added?
See possible answers