Re: sqlAdapter
- From: "Analizer1" <vettes_n_jets@xxxxxxxxx>
- Date: Sun, 28 Oct 2007 21:08:39 GMT
one of them long Proc names i had a incorrect letter
this servers talks more than one databases in a multi type and multitheaded
service
1st proc is a call to main database to get work to do on 2nd database
got it all working
thank you very much
"Marc Gravell" <marc.gravell@xxxxxxxxx> wrote in message
news:1193602543.057443.244840@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Opening a connection to database A and then immediately changing to B?
Why not just open a connection to B in the first place? 2 connection
will work just fine... Of course, within SQL you could use the longer
database.owner.object syntax to cross-call, but I don't advise it, as
I prefer a database to be able to stand by itself (so that I can
relocate databases between servers without issues, or take one
offline, etc). Another option (depending on the context) may be to
place the SP in "master", which should make it more-or-less visible to
all databases.
Marc
.
- References:
- sqlAdapter
- From: MikeJ
- Re: sqlAdapter
- From: Marc Gravell
- sqlAdapter
- Prev by Date: Re: sliced find in Linq
- Next by Date: Re: exec stored proc from c#
- Previous by thread: Re: sqlAdapter
- Next by thread: exec stored proc from c#
- Index(es):
Relevant Pages
|
