DTS to SSIS Migration
Determining how you will upgrade your DTS packages to SQL Server Integration Services (SSIS) is the first step in creating a DTS-to-SSIS migration strategy.
Determining how you will upgrade your DTS packages to SQL Server Integration Services (SSIS) is the first step in creating a DTS-to-SSIS migration strategy.
Lots of packages exist that will import data files for you, even if you do not know the file name ahead of time. But most of them expect the files to be there. New author Andre Quitta brings us a technique he has for checking to see if the files are even there before importing them.
Some time ago, I worked on a team that was attempting to define an IT strategy for a large multinational company. Management incorrectly thought the company was unique in that it had a high number of failed IT projects. In fact, only one in four IT projects can be termed successful, if the benchmarks of success are adherence to scheduled completion time and budget, and realization of the project goal, whether that be saving money, growing the business, or what have you. I have to explain this because many of you may never have come across one.
An early adopter of SQL Server 2005 found some issues with Integration Services. And he shows how it was debugged and the issue solved. This is a great look at some of the helpful parts of Intration Services in solving problems as well as a few places it falls short.
SQL Server 2005 provides some new command line utilities. One such utility is "sqlcmd". The sqlcmd utility is used to run adhoc queries interactively from a command prompt window, or can be used to execute a script containing T-SQL statements. The sqlcmd utility is a great improvement over osql and isql of older releases of SQL Server. In this article, I will explain some of the features this new command line utility brings to administering SQL Server.
Use the relational query engine in SQL Server 2005 to make a single query plan for the SQL and XQuery parts of your queries, and make the implementation of XML queries fast and easy to predict and tune.
A new product has just been released in Beta to help you with source control for your SQL Server development. Beta testers are wanted, so if you're interested, read on.
Continuing with his series, Andy Warren looks at what it means for SQL Server 2000 to run as a service and some of the options you have for starting, stopping, and restarting your server.
Most SQL Server 2000 DBAs have heard of Notification Services, but are they aware of how it works and what it's capabilities are? This is a great platform on which to build any type of messaging/notification/subscription application. New author and PASS board member Joe Webb brings us a look at this add on for SQL Server.
This paper describes the new CLR integration features of SQL Server 2005 and how database application developers and architects can take advantage of them to write user-defined procedures, functions, and triggers, as well as define new types and aggregates
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