12 May 2010 14:45
Strangely enough for a predominantly SSIS blog, this post is all about how to perform data profiling without using SSIS. Whilst the Data Profiling Task is a worthy addition, there are a couple of limitations I’ve encountered of late. The first is that it requires SQL Server 2008, and not everyone is there yet. The second is that it can only target SQL Server 2000 and above. What about older systems, which are the ones that we probably need to investigate the most, or other vendor databases such as Oracle?
With these limitations in mind I did some searching to find a quick and easy alter... [More]
27 Aug 2007 14:00
We see this coming up quite a bit on newsgroups and even have people eMailing about it so we though we would put up an article explaining where to find packages when saved to SQL Server.
If you want to view them visually in SQL Server Management Studio then you will need to connect to the Integration Services Service for the Server on which you have stored the packages.
Below is an example of us connecting to the service by first opening up Object Explorer and then connecting to the Service by choosing it from the dropdown menu and then using Integrated security (no choice here) to... [More]
6 Dec 2004 14:00
Package configurations are now the prescribed way of being able to set values within your package from an outside source. One of the options for the source is Parent Package Variable. The name is perhaps a little misleading so this article is meant to guide you through this slight confusion and into using them. It also helps to explain a key concept in SQL Server Integration Services Setting Up Your Packages This example is very simple. We have two packages. One is called Caller and the other is named Called. In the Caller package we have an Execute Package task which calls the other packag... [More]
30 Nov 2004 14:00
(By Jamie Thomson) One of the age old problems in DTS is moving packages between your development, test and production environments. Typically a series of manual edits needs to be done to all the packages to make sure that all the connection objects are pointing to the correct physical servers. This is time consuming and gives rise to the possibility of human error, particularly if the solution incorporates many DTS packages. Many companies have provided their own custom solutions for managing this problem but these are still workarounds for a problem that was inherent in DTS. Happily, Inte... [More]
1 Sep 2004 14:00
(By Jamie Thomson)
A common requirement when building a data warehouse is to be able to get all rows from a staging table where the business key is not in the dimension table. For example, I may want to get all rows from my STG_DATE table where the DateID is not in DIM_DATE.DateID.
There are 2 ways to do this in conventional SQL.
-- Method #1
FROM STG_DATE s
LEFT OUTER JOIN DIM_DATE d
ON s.DateID = d.DateID
WHERE d.DateID IS NULL
-- Method #2
FROM STG_DATE s
WHERE D... [More]
2 Aug 2004 14:00
In this article we are going to assume a few things about the reader as we want to concentrate as much as possible on the Script Component itself and not the peripheral stuff
The things we will assume are:
You are happy with adding a Data Flow task to the designer in Workflow
You are happy to configure an OLE-DB Source adapter
You are comfortable with configuring mappings in the Destination adapter
As usual we will show you a graphic of the Data Flow once it is completed so we know that if yours resembles ours at the end then chances are we are at the same place. ... [More]