SQL Server Needs Incremental Updates
Although Brian likes that Microsoft delayed the next release of SQL Server for quality, he disagrees with the release strategy. See his opinion and argue your own!
Auditing Your SQL Server Part 4 - Selective Auditing
It's been some time and he apologizes. This next part of this series from Steve Jones looks at selective auditing changes to data on the server using a combination of methods presented in previous articles in the series. Read on if you have problems tracking changes to data on some tables, but don't want to implement a solution that tracks every change.
Capturing The Error Description In A Stored Procedure
Error handling is one of those things that is simple to do in SQL Server, but most people don't do it and it's not the most rebust thing. Here's another way that you can implement error handling in your stored procedures from a new author Amit Jethva.
Building Joins the Easy Way
Have you ever built a join graphically using Access or Visual Studio? Did you know that you can do this with the native SQL Server tools? And it's easy! Follow along as Dale Corey shows you how.
Reducing Round Trips Part 4
The fourth and final installment in this series, this week Andy discusses how using XML can reduce the load you put on your network and on your server. This is a high level article that discusses concepts. We think you'll find a good idea or two in this one!
Lumigent Technologies Delivers Data Auditing Solution for Microsoft SQ
Lumigent Technologies today announced that they are a recommended supplier to provide data auditing solutions for risk management to customers of Microsoft SQL Server 2000 through their Entegra product. Enterprises that depend on SQL Server databases can now rely on Entegra as a trusted auditing solution to enable compliance with regulatory requirements.
Be Prepared
The error handling in SQL Server leaves something to be desired, especially compared with other RDBMSes and languages. The standard method of testing for errors can leave your code bloated and hard to read. Stefan Popovski looks at another method of handling errors.
SQL Server Needs Revision
What's wrong with SQL Server? Lots of things to some people, but here's a look at where this product is positioned in the marketplace against the other RDBMSes.
Users From Hell
A little off topic (or is it?), David needed to vent a little - something we can all appreciate. Meant to be light hearted fun, please don't take too seriously.
Joins Clarified
Sometimes its good to get back to basics - or to make sure you really know all the basics. This is a very good intro to all the different join types.
Blogs
From Planning to Practice: Setting Up Your FinOps Framework
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Forums
Restoring On Top II
Comments posted to this topic are about the item Restoring On Top II
SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Breaking Down Your Work
Comments posted to this topic are about the item Breaking Down Your Work
Question of the Day
Restoring On Top II
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