Re: Identical database w/ identical stored procedures?
- From: "Stu" <stuart.ainsworth@xxxxxxxxx>
- Date: 25 Oct 2005 08:34:05 -0700
Better in terms of what?
I mean, there are risks with using sp_executesql, and you've already
made the decision to split your data (thus minimizing contamination
and/or infiltration) so it seems a bit odd to allow users to jump into
a common database (but there are ways to do this without
sp_executeSQL)...
What's your criteria for defining "better"?
Stu
.
- Follow-Ups:
- Re: Identical database w/ identical stored procedures?
- From: HeadScratcher
- Re: Identical database w/ identical stored procedures?
- References:
- Identical database w/ identical stored procedures?
- From: HeadScratcher
- Identical database w/ identical stored procedures?
- Prev by Date: Re: Problem with simple cursor
- Next by Date: Server Listing for TCP connection
- Previous by thread: Identical database w/ identical stored procedures?
- Next by thread: Re: Identical database w/ identical stored procedures?
- Index(es):
Relevant Pages
|