Review of Review of SQL Server 2000 Administrators' Companion
Nice write up on the Admin Companion. Should you add it to your bookshelf? Frank offers his frank opinion.
Nice write up on the Admin Companion. Should you add it to your bookshelf? Frank offers his frank opinion.
It's not often you'll need to access the registry from SQL, but when you do - these functions make it happen!
A week ago, we solicited readers to let Microsoft know which of the SQL Server 2005 announced features mattered most to them. We had a great response, with 890 of you answering the survey in three days. The answers were pretty interesting. The full results can be seen at the bottom of this article.
Some good info on password changes in Yukon (SQL 2005). Based on the beta, but worth taking a look at.
Dinesh did a little research on nulls and was kind enough to package it up for us. How many of you know or use NULLIF? Or COALESCE? Handy stuff!
We saw a note from Chad about a tool he wrote in the forums and asked him to write up some notes. Not only did we get notes, we got the source code! See what a DBA can do with some DMO.
We get books in occasionally for review and have started making them available to our existing authors. Jim was interested in this one - turns out he didn't find much to like. If you're a beginner it might be a better fit. Or maybe you've read the book and disagree?
A very short article that discusses how nulls can ruin your day if you don't understand how they behave when you concatenate.
We had Mike take a look at this product recently and he found a lot to like. He also had some suggestions about ways the product could be improved - interesting since you get free upgrades for life with this product. This is a very good walk through of the product.
Microsoft confirmed today that it has delayed Yukon yet again. It also announced that Yukon has an official name and will have another beta added to the development cycle. Get all the info here and share with Microsoft your thoughts about what features are important to you.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers