• Hi Chandon,

    Thanks for the Feedback.

    chandan_jha18 (10/9/2012)


    I have not gone through the script entirely but the part where you are generating an SQL command and then executing it.

    If I were you, I would have simply generated the T-SQL command and then execute that in small batches rather than as a whole.

    I was sort of hoping not to have to do too much typing, there are over 300 tables to add Primary Key Columns too for the Transactional Replication.....

    I could break this down into batches of tables however maybe by adding a where clause to the select statement that inserts into the temp table....

    Also, creating the new column is not that difficult but finding what it can break is. Do a search twice or even thrice to make sure it does not break anything.

    You don't have to search only for the objects inside that server but also for some adhoc processes

    outside that server because there wont be any DDL for those processes and they may break unless you know about it. Spread out the word to all the people directly and indirectly responsible for the application, collect suggests and feedbacks, go for the execution carefully and be ready with a rollback script(just in case).

    Thanks

    Chandan

    I totally agree with what you're saying about breaking any apps that attach to the DB, which is why I'll be testing this extensively on a Test System first, hence why I said that it should be used with extreme caution in a Production Environment.

    Great minds think alike I have also prepared a Roll-back script (one of the first things I did) just in case, all the testing in the world can't check for every eventuality.

    Thanks again for your feedback. 😉