This article uses XML to deal with optional parameters along with multiple parameter passed into a stored procedure. (Note: We are re-running this as we had a newsletter issue last week)
2013-12-28 (first published: 2013-12-10)
7,530 reads
T-SQL has some well known limitations when working with parameters for a stored procedure, not the least of which is a variable number of parameters. While there are some solutions, they can be cumbersome to work with. Sloan Holliday brings us a creative solution using XML that can solve many issues.
2006-02-28
12,063 reads
DTS is a fantastic ETL tool and it is often used to import Excel documents. However this can be a manual process in many cases in setting up the package. New author Sloan Holliday brings us a way that you can leverage Office XP's automation facilities and XML to import data into SQL Server.
2005-11-22
11,006 reads
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
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...
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