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.
New Author! Thom's first article discusses the difficulties you encounter when your database doesn't support cascading deletes (or you've opted not to use it) and you need to delete data in a child table based upon a value in the parent table. Not exactly your run of the mill delete query. Take a look and please rate/comment the article!
This article discusses various SQL Server Data Transformation Services (DTS) best practices. It is divided into sections like DTS naming conventions, DTS documentation, troubleshooting DTS packages, improving the performance of DTS packages, securing DTS packages, DTS resources.
Herve has done some work experimenting with max degree of parallelism (DOP) on some large multi processor blocks and based on that, has some recommendations for you if you're using more than 8 processors. Good reading!
David takes us through why he believes trying to run SQL and IIS on the same box is a bad idea. It's a common notion that it IS a bad thing to do, but you have real justification? Read this and you will!
Pedro Estrada has published a free tool that according to his site "This is a complete application to have an easier interface to work with BCP against MSSQL servers. Just specify a server, database, table user name and password to BCP out or IN." Worth a try, and he has some other free utilities (some SQL, some not) on the site.
UDF's are useful if somewhat tricky. Dinesh uses a common scenario where you have a self referencing table (the common example is an employees table where each employee has a managerid that links to another employee in the same table) to illustrate how a UDF can make querying easier, how to use it as the basis of a computed column, and how to index that column.
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