Any solution for this thread ?  I've faced the same situation.  The only solution I found is to don't use table aliases.

Hi Jeff and Jeffrey,

The change from INT to numeric was for an example only.  You can try changing a varchar(10) to a varchar(9) and get the same error.  But you...

Hi Jeff,

Yes, the tablename are the same.  In the error message its the name of the table containing the column I want to ALTER.

I've asked to change the scope of the DOMAIN_B\GROUP_1.

According to this article, its supposed to be possible

https://technet.microsoft.com/en-us/library/cc755692(v=ws.10).aspx.

Thanks all 🙂

Thanks all! 😀

Hi,

Have you ever tried to call CopyDB.cmd from an SQL Job ?

I've created a job with a job step of cmdExec type and the command is like :

cmd.exe ...

Just to say thanks for this script. It's been a couple of months that I've been using it on our many productions DB for index, stats, DBCC maintenance and...