Why SQL Server 2005 Doesn't Permit Non-ANSI Style OUTER JOINs
As of SQL Server 2005, any database in 90 compatibility mode (settable by sp_dbcmptlevel) cannot support non-ANSI OUTER JOINs. Sometimes...
2007-11-01
2,172 reads
As of SQL Server 2005, any database in 90 compatibility mode (settable by sp_dbcmptlevel) cannot support non-ANSI OUTER JOINs. Sometimes...
2007-11-01
2,172 reads
Some time ago I was looking for a password vault and came across some recommendations for KeePass. KeePass is open...
2007-10-31
2,598 reads
SQL Server 2005 introduces Common Table Expressions (CTEs), which are great for recursive queries. Previously, in order to do recursion,...
2007-10-30
2,569 reads
A recent thread on SQLServerCentral.com had an individual what it took to be a successful DBA. Couple that with a...
2007-10-29
1,674 reads
For a variety reasons, including personal/family concerns and workload, I've not been able to write as often as I'd like....
2007-10-28
1,466 reads
Noted SQL Server security expert, Chip Andrews, has released an alpha version of a command-line version of SQLPing3. You can...
2007-10-25
2,307 reads
How to Cheat at Securing SQL Server 2005
I recently had the opportunity to contribute a couple of chapters to this...
2007-10-04
547 reads
Brian Kelley continues his series on getting the most out of SQL Server 2000's Query Analyzer. In this article he looks at the Object Browser and the Transact-SQL Debugger, new features in the 2000 Edition which can reduce development and troubleshooting time for DBAs and database developers.
2007-10-03 (first published: 2002-03-05)
40,165 reads
Taya Blanchard to speak on A
Practical Guide to Making Sense of Your SQL Server Application
Performance
Midlands PASS Chapter - October...
2007-10-03
576 reads
SQL Server includes a great auditing tool: Profiler. It's not the easiest tool to use, however, and it's one that takes some getting used to. Our resident security export, Brian Kelley looks at a simple example of using this tool to audit logins.
2007-10-02 (first published: 2004-09-01)
35,412 reads
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