chris.shaw (5/21/2010)

---

Jonathan,

I must say that I found your article to have some really good information in it. I guess there was only a couple comments to it...

Gursoy Yerli (5/11/2010)

---

Fixed a bug;

Your generation sproc was ignoring the schema when using "EXEC sp_helptext @ProcedureName". Added below to fix the issue.

...

You can't update two tables in one SQL statement but you can wrap them in an transaction so from the outside it looks like they are.

BEGIN TRANSACTION

UPDATE A

SET Complete =...

I've written this trigger to record when DDL changes...

Grant Fritchey (5/7/2010)

---

Also, we make it a point of retaining the scripts that were generated for the final rollout to production, in case there's any question in the future what...

bill page-320204 (5/6/2010)

---

Am I missing something here?

We use SourceSafe. We keep each proc separate. When I need to change one, I check it out, modify it, paste it...

I didn't...

In the version of the procedure I have adds and additional call to another...

bphipps-931675 (5/6/2010)

---

True about the walking in late, for that issue but I would still want to logically arrange the various scripts into projects to make them easier to find and...

It is...

bphipps-931675 (5/6/2010)

---

That's certainly one way you can get a script started if you didn't save it from the start. We have a stored procedure template (that we access via...

bphipps-931675 (5/6/2010)

---

But SSMS inherently gives you a save option. All you have to do is save them like any other file to your hard drive. I really don't...

bphipps-931675 (5/6/2010)

---

This just seems silly overall. Why wouldn't you just create a project in SSMS and then save your scripts into the solution/project. The solution can then be...

Phil Factor (5/6/2010)

---

Right on the nail. If you can...

mike.renwick-894639 (5/6/2010)

---

I personally haven't found a great deal of info on how to script objects using SMO which is why I think people end up doing slightly scary things like...