Viewing 9 posts - 16 through 24 (of 24 total)
My preference is to push as much logic as possible to stored procedures. In my experience, the actual code or logic tends to be the component of an SSIS...
September 23, 2009 at 3:16 pm
Ah, ok, you are correct. Depending on your permissions, another option might be an xp_cmdshell call such as xp_cmdshell 'systeminfo'. You might need to output that to a...
July 21, 2009 at 2:41 pm
I believe issuing a select @@version will provide you the information both the OS and SQL engine.
July 21, 2009 at 2:06 pm
Database mirroring is not available in SQL Server 2000. It is available in SQL Server 2005 and beyond. As for monitoring, I would recommend looking at the DMVs...
July 17, 2009 at 6:55 am
If you see a failed login attempt on the destination server, it is most likely a password issue. If you do not, then I suspect the package is never...
May 29, 2009 at 6:52 am
Greg --
This sounds like an issue in the way the package is being executed and the drivers being used. You may want to try something like below in your...
April 28, 2009 at 2:17 pm
Jose --
It would appear the login under which the package is running does not have permission to the database it is attempting to access. Adding a log file to...
April 28, 2009 at 12:51 pm
At this point, I would step through each step of the SSIS package manually (right-click the step, select Execute) one at a time to determine which step has an issue...
March 31, 2009 at 2:16 pm
I would recommend you add a log file to the SSIS package that will provide some more verbose error information. To do that, in the package, right-click in the...
March 30, 2009 at 2:53 pm
Viewing 9 posts - 16 through 24 (of 24 total)