Viewing 15 posts - 136 through 150 (of 172 total)
yep...thanks for the add on...I did everything u told...actually the problem is with the temporary packages it creates during run time ...when u check the option optimize for many tables,...
July 14, 2008 at 4:55 pm
hey, Thanks for ur reply...other ssis packages are not import and export wizard...they r different..I create the packages on my development server and test all the packages by changing the...
July 14, 2008 at 3:05 pm
well, u said like that package is executing with no errors on other systems. so, The problem might be u may not have exclusive access to the database. check the...
July 14, 2008 at 3:03 pm
Actually I did nt move it to production...but I was just testing by changing the configuration value in xml file...i mean I m changing the server names and testing...it worked...
July 14, 2008 at 2:32 pm
Thanks for the reply....but we r gonna schedule the package to run everyday... from ur post, It looks like everyday we have to give the new logfile name in .dtsconfig...
July 9, 2008 at 1:34 pm
Thanks for the reply....but wher can I find that?? u mean in the logging window ?? In logging window I don't find anything like that....
July 9, 2008 at 1:15 pm
yep...the table which u r trying to export is having some duplicate records...in columns with the primary key constraint, they can not insert the duplicate records...so u need to drop...
July 9, 2008 at 11:44 am
with my minimum knowledge I can suggest you to use import and export wizard if you have more than 100 tables to transfer..or else if u wanted to tranfer 1...
July 9, 2008 at 10:59 am
you can use dataflow task in ssis...you just need to map the source columns to appropriate columns in Destination provided the datatypes should be same...
July 9, 2008 at 9:12 am
Thanks a lot for the replies...we solved the issue....we have 1 more job on the same data....so we changed the times...
June 25, 2008 at 3:55 am
That error looks like you have not installed the full version of integration services. only few components of SSIS might have been installed on your box.
June 18, 2008 at 8:56 am
you may find the solution in the link given below...I have the similar error..
June 16, 2008 at 11:50 am
Viewing 15 posts - 136 through 150 (of 172 total)