Tag Info

Hot answers tagged

4

That is correct. Forward compatibility is guaranteed. Backwards compatibility does not exist*. Having 4 different BIDS/SSDT instances on a machine is a pain I've known all too well but there's not much you can do. There are ways of constructing SSIS packages such that your solution can target whatever version of SQL Server will be hosting them but that's ...


2

Make this your SQL Statement. select * from tbldatasets where dataset = 104 and ADDEDTIMESTAMP BETWEEN Convert(datetime, DateAdd(month, -2, Convert(date, GETUTCDATE()))) AND GETUTCDATE() UNION ALL select * from tbldatasets where dataset = 106 and ADDEDTIMESTAMP BETWEEN Convert(datetime, DateAdd(DAY, -10, Convert(date, GETUTCDATE()))) AND GETUTCDATE() ...


2

You can connect to Oracle from SSIS. You have to install Oracle client on your development and also on your production environments. After doing proper tnsnames configurations you can use odbc source or ado.net source.


1

Change tracking offers the functionality you're looking for. When switched on, SQL Server creates additional internal tables. Changes to your data tables are noted in these internal tables. System functions allow you to pull changes out of these internal tables and transfer only changed rows. A related technology - Change Data Capture - allows you to see ...


1

I have used 2 tools to perform Oracle to SQL data migrations: The first is the Oracle to SQL Server Migration Assistant (SSMA). It is a fairly basic tool and if you don't have any binary objects to migrate it is ok. It allows you to create the schema and migrate the data, but it isn't the fastest tool in the world and the OLE drivers wont work with binary ...


1

Throw Execute SQL tasks into the control flow and don't link them to each other. Any task without a preceeding task will run asychronously. Executing 20 - 30 Stored procedures in parallel would bring you a lot of workload. I say think twice about it. I have a developer who did that with a custom written windows service, i am facing resorce_semaphore wait ...


1

Instead of SSIS I think you might want to look into SQL Server Service Broker. This lets you send messages asynchronously. See here or here for a start. MSMQ or RabbitMQ may also be options you should consider.


1

My first inclination would be to use a script component (e.g. C#) as source in a Data Flow Task. The script would just read the column contents, parse the individual records and fields, and send records down the pipeline. The individual fields (perhaps strongly-typed) can be defined in the output record definition of the designer. ...


1

I know this was asked a while ago, but maybe someone else will stumble across this answer and not spend the multiple hours that I've been bashing my head against this. Turns out that you need to use the SQL_WVARCHAR type for Variables. The following is my evidence, showing the SQL_WVARCHAR works. OLEDB command from SQL Profiler: exec sp_executesql N'exec ...



Only top voted, non community-wiki answers of a minimum length are eligible