October 10, 2008 at 12:21 am
Comments posted to this topic are about the item Creating Functions for Stored Procedures
October 10, 2008 at 3:14 am
the C# link is broken ... however ... I was able to download the VB code
October 10, 2008 at 3:16 am
I wanted to know how it was done in c# but the link is broken.
October 10, 2008 at 4:30 am
I have script that generate DML stored procs for all tables. This will help me generate even more code, if only the C# script is available. Please fix the link
October 10, 2008 at 5:08 am
The link for C# TSQL script is http://www.sqlservercentral.com/Files/CreateADO_Call_BySPName_Cs_GetFile.sql/1788.sql.
October 10, 2008 at 5:09 am
I am getting the following error while accessing the C# code:
The resource could not be found
Sorry, we could not find the resource at http://www.sqlservercentral.com:80/Files/CreateADO_Call_BySPName_C
If problems persist, please contact us to let us know.
October 10, 2008 at 5:10 am
Just curious, if you are working in an environment where DBA's DON'T know not to use sp_, is there another way to filter out the system procs and keep the rest? SQL Server doesn't hold onto a createid, does it?
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
October 10, 2008 at 5:11 am
Marcelo Luiz Soares de Souza (10/10/2008)
Thanks I got the code. I didn't saw this link while posting the earlier message. Please rectify this in the article also. π
October 10, 2008 at 6:07 am
Alex,
This is AWESOME. This is going to save me a heap of time. Thanks a million for sharing.
-Barry
October 10, 2008 at 6:18 am
Believe it on not β I did. This is was while ago, but when I joined to project, all sprocs named as SP_. It took about a month to convince managers to stay out of prefix SP_.
October 10, 2008 at 6:20 am
jcrawf02 (10/10/2008)
Just curious, if you are working in an environment where DBA's DON'T know not to use sp_, is there another way to filter out the system procs and keep the rest?
Yes...
If you use Information_Schema.Routines as the source of information, only user objects are listed. You can also brute force things using one of the following...
WHERE OBJECTPROPERTY(id , 'IsMsShipped') = 0
WHERE OBJECTPROPERTY(OBJECT_ID(tablenamecolumn) , 'IsMsShipped') = 0
WHERE OBJECTPROPERTY(OBJECT_ID(schemanamecolumn+'.'+tablenamecolumn) , 'IsMsShipped') = 0
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 6:22 am
Thanks to everyone for good response (and bad as well). Sorry for broken C# link, but itβs nothing to do with the article.
October 10, 2008 at 6:25 am
You could use select * from sys.objects where is_ms_shipped = 0 as well. I am not INFORMATION_SCHEMA fan. This is personal preference.:D
October 10, 2008 at 8:23 am
The link has been corrected in the article.
October 10, 2008 at 7:24 pm
Alex Grinberg (10/10/2008)
You could use select * from sys.objects where is_ms_shipped = 0 as well. I am not INFORMATION_SCHEMA fan. This is personal preference.:D
Heh... I forgot about that. I'm still a bit stuck in the world of 2k. Thanks for the reminder. π
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply