You need to check the windows and server logs to see what is the exact error.  You're basically asking I ahve the blue screen of Death, what is the problem. ...

Humm, this should work.  Unless, the new column is saved as -1 on the server.  What error are you getting?  Could you also post some sample data and the required...

Are you talking about a problem you are having internally or a problem that the sqlservercentral.com site is having??

That explains it... I never had any problems with the columns order, but then again I never (except for Exists) use the Select * combinaison

Why couldn't you just use the alter table statement in 2000?  I never add any problems doing that in production (or maybe I was just lucky)

Try restarting the services (server and maybe agent too).  That will solve this 99% of the time.

I think you are pretty much forced to use the user interface.  Manually coding this stuff is just too time comsuming and error prone (been there, didn't quite do that...

You can simply move (create new + drop existing) the non clustered indexes to another filegroup using on [file groupname here].

You may also do the same thing with the data by moving...

Well most of what you said was accurate .

Thanks for helping out.

Never seen this.

Are you sure about this one?

"JOIN by itself is a LEFT JOIN which pulls all records from the left table (HOLDING in your case) and only the records from the...

Can't help you there.  I'm not an ssis expert... not a ssis user for that matter.  I'll let the other DBAs figure this one out.  Good luck with this project. ...

Best practices dictates that all ddl should be grouped in one point (the earlier in the proc the better).

Without seing the code and requirements, it's hard for me to say...

Union ALL returns ALL rows.

Union returns distinct rows only.

Hope this helps.

Thanks for sharing this.  However from now on I'll simply add more than 1 schedule for the job.  Just to try something new .