Viewing 15 posts - 91 through 105 (of 194 total)
Maybe have the two destinations set up in connection manager.
You can then run a count in a SQL task that in turn populates a variable. You then have two...
'Only he who wanders finds new paths'
June 10, 2013 at 10:42 am
Thanks for the reply Steve and yes we did go through the 'if only we had 2012' process!
'Only he who wanders finds new paths'
June 9, 2013 at 1:46 pm
These are not my scripts but I have tested and they might give you a start..
This script will give you the last status of a job, whether success or failure...
'Only he who wanders finds new paths'
May 24, 2013 at 12:50 pm
Not in T-SQL I am afraid but we have recently utilised WINSCP via the command line to SFTP to a client site inside an SSIS package and that was pretty...
'Only he who wanders finds new paths'
May 24, 2013 at 12:34 pm
Stop SQL service
Start SQL in single user mode via command prompt with -m, essentially this allows any member of the local admins group to connect as a member of the...
'Only he who wanders finds new paths'
April 26, 2013 at 9:54 am
I would be tempted to load both spreadsheets into two sql tables then output matches to a new spreadsheet based on a join but that is because I am much...
'Only he who wanders finds new paths'
April 17, 2013 at 10:02 am
Yup, just had a play...
DECLARE @TestClient varchar(11);
DECLARE @SQLString nvarchar(500);
DECLARE @ParmDefinition nvarchar(500);
SET @TestClient = 'somevalue';
SET @SQLString = N'EXEC [database].dbo.Test @Client'
SET @ParmDefinition = N'@Client varchar(10)';
EXECUTE sp_executesql @SQLString, @ParmDefinition, @Client = @TestClient;
'Only he who wanders finds new paths'
April 17, 2013 at 9:47 am
Sorry Jeff, misunderstood!
Just to run a sproc you can of course edit it to look like:
SET @Param1 = 'somevalue';
SET @SQLString = N'EXEC [db].dbo. ' + @Param1
EXECUTE sp_executesql @SQLString
But...
'Only he who wanders finds new paths'
April 17, 2013 at 9:02 am
slightly edited the query from msdn, hopefully will help you out:
DECLARE @IntVariable varchar(10);
DECLARE @SQLString nvarchar(500);
DECLARE @ParmDefinition nvarchar(500);
SET @IntVariable = 'somevalue';
SET @SQLString = N'SELECT *
FROM [database].dbo.
...
'Only he who wanders finds new paths'
April 17, 2013 at 8:32 am
Am I right in thinking that the optimise for ad hoc workloads option is preferred for high usage of non-parameterised queries?
'Only he who wanders finds new paths'
April 17, 2013 at 6:58 am
http://technet.microsoft.com/en-us/library/ms143506(v=sql.100).aspx
'Only he who wanders finds new paths'
April 16, 2013 at 9:58 am
If you are looping through a folder using a for each container you could use a script task to check for the substring and set an appropriate condition for whether...
'Only he who wanders finds new paths'
April 16, 2013 at 9:55 am
I have ran into this problem when using SSIS to insert delimited columns into a table. Didn#t need to free cache space.
The issue was an incorrect file structure, it...
'Only he who wanders finds new paths'
March 28, 2013 at 12:25 am
Jeff Moden (3/21/2013)
david.alcock (3/21/2013)
SSIS is normally utilised when the copy/move is complex, if it involves data transformations, validations etc.
I'll go ahead an disagree with that. I've built some killed...
'Only he who wanders finds new paths'
March 22, 2013 at 10:50 am
SSIS is normally utilised when the copy/move is complex, if it involves data transformations, validations etc.
'Only he who wanders finds new paths'
March 21, 2013 at 3:51 am
Viewing 15 posts - 91 through 105 (of 194 total)