Viewing 11 posts - 1 through 11 (of 11 total)
The packages mainly read data from SQL Server and copies it to Ingres. The login has permissions to select this data and run the cmd file so it uses windows...
July 20, 2012 at 7:47 am
Charmer
The contents of the cmd file are fairly simple
dtexec /sql "Dataload" >i:\xx\xxx\dataload\logfiles\dataload.log
call e:\\dba\common\BATCHscripts\datestamp_file i:\xx\xxx\dataload\logfiles\dataload.log
The package Dataload is run from the server dataload.log is to capture the output from the...
July 20, 2012 at 6:34 am
I had the same problem with packages that use an ADO.NET connection to an Ingres server. The connection login for Ingres is different to my local SQL server login....
July 20, 2012 at 5:41 am
No clash. No other scheduled task running at the same time.
July 6, 2012 at 5:52 am
I know it has been a while since I responded but I thought that you may like to know that I eventually found a cure for the slow running but...
July 5, 2012 at 8:18 am
There have been no changes to either system of any form. There have been no changes to either database on SQL Server or Ingres, nor has there been any change...
June 8, 2012 at 3:21 am
The data source is SQL Server. All server and event logs have been checked on both systems - no hint of any problem anywhere. Ingres gives little or no information...
June 7, 2012 at 9:18 am
i have altered the procedure so that it builds the sql query at run time and executes it dynamically. The query now executes as a parallel query.
April 11, 2012 at 5:27 am
Updated proc and plan attached. Using parameter sniffing is now causing the test with forename ='%' to not use a parallel query.
April 11, 2012 at 2:17 am
Tried to fix as parameter sniffing but still getting the problem
April 10, 2012 at 9:14 am
Viewing 11 posts - 1 through 11 (of 11 total)