SQL Server - Challenge converting DTS Lookups to SSIS Package

Asked By Fraz
17-Nov-09 05:28 PM
I have already migrated a SQL 2000 DTS package to SQL 2005 DTS Legacy and it
is working fine. Now I am trying to convert it to SSIS package. It is a SQL
2005 64-bit environment and I am having issues like failed to load "Execute
DTS 2000 Package Task". I think "Execute DTS 2000 Package Task" is not
supported in SQL 2005 64-bit so I have decided to create the package from
scratch. The flow in the SQL 2000 DTS package is:
1. Source OLE DB connection
2. Destination OLE DB Connection
Transform Database Task Properties:
3. Source: SQL Query
4. Destination :  TableName
5. Transformation : Source-Destination Field mapping
6. Lookups: There are two lookups:
(a) Get RefNo from destination table e.g.
(Select RefNo from dbo.TableName where status is NULL)
(b) Update Destination Table using Source SQL Query and (a) Lookup e.g.
UPDATE dbo.TableName
SET Field1 = ?, Field2 = ?, Field3 = ?, Status = ?
WHERE  (RefNo = ?)

In the SQL 2005 BIDS, I have created OLE DB Source and Destination
connection but for Lookup for Update Statement I am having issue. How to use
the parameterized Lookup in SQL 2005. Your assistance is appreciated.
Thanks,
Fraz
Bit
(1)
TableName
(1)
RefNo
(1)
Database
(1)
Arun
(1)
Goto
(1)
OLE
(1)
  ArunKumar replied to Fraz
01-Dec-09 06:41 AM
Hi Fraz,

Hope this is not too late to reply to your question..

Here is what you need to do:
1) Goto "Advanced" tab and click "Enable Memory Restrictions"
2) Click the Modify the SQL Statement
3) Click the parameters button


You should able to see the parameters here, set the value for your parameter
accordingly..

Thanks,
Arun
Create New Account
help
SQL server 2008 64 bit SQL Server Hi, Does anyone know the diff between SQL2008 32 bit adn 64 bit. What kind of situation the we need to have WIN 64 bit + sql server 64 bit? Thanks, SQL Server Discussions SQL Server 2008 (1) Disk (1 Bit (1) DB (1) SQL server 2008 64 bit (1) Database (1) ODBC (1) Online (1) Mecn (mecn@yahoo.com) writes: The difference is that with 64-bit SQL Server works against a completely uniform memory space. With 32-bit, there is a
is in integer SQL Server I have an integer which is the summation of several bit-values. For example: bit(0) = 1 bit(1) = 2 bit(2) = 4 bit(3) = 8 If the integer field is 15, I know that is has bit(0)-bit(3) in them. If the integer field is 3, It contains bit(0) and bit(1) If the integer field is 10, It contains bit(1) and
MSSQL equivalent / explanation of Access TableName, TableName SQL Server Hi , I have a query below which I have ported across from Access Ratchev http: / / www.SQLStudio.com YPE EB Thanks :) Mike keywords: MSSQL, equivalent, / , explanation, of, Access, TableName, , TableName description: Hi , I have a query below which I have ported across from Access in
8) NULL, [ShipToNum] [nvarchar](14) NULL, [TermsCode] [nvarchar](4) NULL, [ShipViaCode] [nvarchar](4) NULL, [PrintStatements] [bit] NULL, [PrintLabels] [bit] NULL, [PrintAck] [bit] NULL, [FinCharges] [bit] NULL, [CreditHold] [bit] NULL, [GroupCode] [nvarchar](4) NULL, [DiscountPercent] [decimal](6, 2) NULL, [PrimPCon] [int] NULL, [PrimBCon] [int nvarchar](20) NULL, [TaxExempt] [nvarchar](3) NULL, [MarkUpID] [nvarchar](4) NULL, [BillDay] [int] NULL, [OneInvPerPS] [bit] NULL, [DefaultFOB] [nvarchar](15) NULL, [CreditIncludeOrders] [bit] NULL, [CreditReviewDate] [datetime] NULL, [CreditHoldDate] [datetime] NULL, [CreditHoldSource] [nvarchar](8) NULL, [CreditClearUserID] [nvarchar](20) NULL nvarchar](20) NULL, [BTFormatStr] [nvarchar](50) NULL, [ParentCustNum] [int] NULL, [TaxRegionCode] [nvarchar](4) NULL, [ICCust] [bit] NULL, [ContBillDay] [int] NULL, [EMailAddress] [nvarchar](50) NULL, [ShippingQualifier] [nvarchar](1) NULL, [AllocPriorityCode] [nvarchar](6