Tag Info

New answers tagged

0

I've discovered what the issue was. 2 of the parameters were connection strings and if a connection string contained an Application Name then the value of the preceding parameter was not being stored. This worked fine from my machine so I'm assuming a difference in the version of SSMS client is to blame. For the time being I have simply removed the ...


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


0

The problem has something to do with permissions on the underlying server and not SSIS or the MSDB. We had the same problem. Temporarily adding the user's AD account to the local administrators group fixed this for us. Adding their AD account to PowerUsers or Users did not; however, I am certain that we could have found what was missing in the Local Security ...


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


-4

For tutorial you can watch the video series on youtube. https://www.youtube.com/watch?v=3cPq9FXk-RA&list=PLNIs-AWhQzcmPg_uV2BZi_KRG4LKs6cRs For query you have to union your queries into a single resultset.


0

There is a way to do this. Assume that, like the OP, you have two SQL Server instances, one of which has SSIS installed and one of which does not (probably cannot, e.g. if it is SQL Server Web Edition). Write a stored procedure which copies the user maintenance plan rows from the hobbled server to the non-hobbled one. The relevant rows are: SELECT name ...


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


0

I know that the post is old, but to make this work be sure that the user you set as Run As in the Job, has access to the proxy and is in the list of the proxy Principals. If the user is systemadmin in sql it will not get saved in the list and you will get the error.


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


0

@Fulproof: Based on what @RicardoBalda says (which all works as advertised), it seems clear that the vast majority of SSIS is installed and used by SQL Server Maintenance Plans, even if SSIS is not officially 'installed' as such, on a given server. (Which might sway someone's decision as to the perceived overhead of installing the rest of SSIS, to get at ...



Top 50 recent answers are included