Tag Info

Hot answers tagged


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 ...


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.


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.


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. ...


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 ...


Amusingly enough, you have the answer in your question, specifically, run as. RunAs and in case MS butchers links again, RunAs RunAs allows you to run a program as another user. You can't automate the entry of credentials, which is a pain and you won't be able to see your password but it does work. It also fails in situations like SSRS development when you ...


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