Viewing 15 posts - 10,186 through 10,200 (of 13,879 total)
iamsql1 (2/4/2013)
I am newbie to SSIS, i tried every effort to change the variable in olde db...
February 4, 2013 at 6:31 am
iamsql1 (2/4/2013)
i have an idea. can i use a stored procedure and get it executed in EXECUTE SQL TASK
instead...
February 4, 2013 at 2:10 am
Thanks, I failed at Google and hoped everyone would just take my word for it.
Not in this forum! 😉
February 1, 2013 at 3:48 am
It it just another general purpose tool.
Anyone else picturing a man with a big hammer? 🙂
January 31, 2013 at 5:57 am
Excel 2003 has a maximum number of rows of 65,535 - maybe that is the cause of your error.
Try exporting to CSV instead to see whether that is the reason.
January 31, 2013 at 2:43 am
Two options:
1) Remove the IDENTITY definition on the destination table and insert as usual.
2) Set identity insert on during the import and insert as usual.
January 31, 2013 at 2:40 am
johnnycash (1/30/2013)
January 31, 2013 at 2:38 am
cafescott (1/29/2013)
http://sqlserverdownanddirty.blogspot.com/2011/07/ssis-execute-process-task-hangs-when.html
I added the SEE_MASK_NOZONECHECKS environment variable to the server that houses the SQL installation where my package resides. It now works as a job! ...
January 29, 2013 at 12:55 pm
Use the Advanced Editor on your data sources to have a look at all the datatypes involved & see whether that gives you any clues.
It's difficult to provide more advice...
January 29, 2013 at 12:02 pm
It's probably not relevant, but I thought I'd post just in case. Did you know that if you copy a batch file to another server and then run it, it...
January 29, 2013 at 8:34 am
You could try a MERGE JOIN from t1.name to t2.city, join type = FULL.
January 29, 2013 at 4:53 am
cafescott (1/29/2013)
Are you able to add something to your .bat file to at least work out where it is hanging? Possibly writing to a text file or something similar?
Your initial...
January 29, 2013 at 4:48 am
cafescott (1/29/2013)
Phil Parkin (1/29/2013)
This user may not have permissions to the various files involved - I suggest that...
January 29, 2013 at 4:21 am
The job is probably running under the credentials of the SQL Agent user.
This user may not have permissions to the various files involved - I suggest that you investigate this...
January 29, 2013 at 1:48 am
I second Eugene (whose middle name may well be ssCrazy 🙂 ) - best practice is to use YYYY-MM-DD format when specifying dates in T-SQL:
WHERE orderdate >= '2010-10-31'
January 28, 2013 at 8:32 am
Viewing 15 posts - 10,186 through 10,200 (of 13,879 total)