Aaron Bertrand [SQL Server MVP] (ten.xoc (AT) dnartreb (DOT) noraa) writes:
Maybe Chris wanted some special tweak fit the local standards where he
work.

While it takes Chris some time to develop his tool, it's not that tricky
to do, and it is a good exercise in using the catalog views.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

It's great that you're speaking for him, but I'm still curious what it is
exactly. If there's something the free tools and 3rd party utilities aren't
doing, even if Chris *wants* the exercise of using the catalog views to
achieve it, it still might be beneficial to others who don't.




On 8/5/09 5:21 PM, in article Xns9C5EEC5BE5AB5Yazorman (AT) 127 (DOT) 0.0.1, "Erland
Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote:

It's as Erland says... it's not that there were any problems with 3rd party
tools so to speak it's just I thought for the effort of an hours work or so
I would create my own routine to create a stored procedure generator. This
allowed me to customise it to our needs including:- having the option to
output the identity, format the query with the spacing we like in our
company, on update stored procedures automatically exclude out datecreated
columns etc. I simply created a query that looked in sys.objects and
sys.columns to achieve this. It's not perfect but does the job.

Chris



"Aaron Bertrand [SQL Server MVP]" <ten.xoc (AT) dnartreb (DOT) noraa> wrote