Re: Frustrated :(

From: Steven Burns (royalstream@hotmail.com)
Date: 11/22/02


From: "Steven Burns" <royalstream@hotmail.com>
Date: Thu, 21 Nov 2002 17:01:11 -0600


you know...that sounds like a good idea.
The only problem I got is that global sps die when the connection that
created them closes, but I guess I'll get around that somehow.

Thanks.

"Eric" <ega@cenosis.com> wrote in message
news:ePDp1NXkCHA.1392@tkmsftngp12...
>
> Just a suggestion:
>
> 1. have a SP executed when the server is started
> 2. this SP can execute a COM (using SP_OA* procedures)
> 3. The com creates Global Stored Procedures (Create Proc
> ##My_Stored_Proc...)
>
> This way:
>
> - all sp all re-create when the server is started
> - you can distributed a new version of the package to update all sp
> - easier to track changes or roll them back
>
> It could be an encrypted script instead of a COM. Anybody see a downside
to
> using global stored procedures?
>
> Eric
>
>
>
>
> "Steven Burns" <royalstream@hotmail.com> wrote in message
> news:O4aIX6$jCHA.1572@tkmsftngp09...
> > I just found out that the stored procedure encryption used in sql 2000
can
> > be easily cracked.
> > Maybe that will be fixed in yukon....but in the meantime....
> > Is there any alternative to stored procedures?, third party products
(like
> > extrensions to sqlserver)?
> > Any kind of advice will be appreciated.
> >
> > Best regards
> >
> > Steven Burns.
> >
> >
>
>