Ahhh ... yes that'd be the exception. If you're using global temp tables,
you will be in trouble.



Thanks
Phillip Carter
Ph: +61 3 9235 1691


-----Original Message-----
From: Daniel Morphett
[mailto:mssqldba-ezmlmshield-x5702011.[Email address protected]
Sent: Thursday, 29 July 2004 5:17 PM
To: LazyDBA Discussion
Subject: RE: same temporary table and cursor names running on different DBs
and same server

This is off the top of my head, so check it.

If you use global temp tables i.e. ##temp, I think you might run into
trouble, because the double hash sign means it can be read by more than one
connection. So I would restrict your procs to using a local temp table (one
hash in name: #temp). However, you won't be able to use this if your proc
calls another proc that also needs to refer to the temp table, because it
will then be out of scope.

Best thing to do is to try creating the temp table from one db, and then try
reading it from the other (or read BOL on subject)

Daniel Morphett
DBA
Brilliant Digital Entertainment
02 9281 9272


-----Original Message-----
From: Entena Raymond
[mailto:mssqldba-ezmlmshield-x63384665.[Email address protected]
Sent: Thursday, July 29, 2004 5:09 PM
To: LazyDBA Discussion
Subject: FW: same temporary table and cursor names running on different
DBs and same server

Hi,

Any thoughts on my concern below?

Thanks,
Ray

-----Original Message-----
From: Entena, Raymond
Sent: Thursday, July 29, 2004 10:43 AM
To: '[Email address protected]
Subject: same temporary table and cursor names running on different DBs
and same server


Hi Guys,

I have the same set of stored procedure running on different DBs on the
same server. This stored procedure is using temp tables and cursors.
The stored procedure will be scheduled to run everyday, synchronously.

Would this cause data and stored procedure inconsistencies considering
it's declaring the same set of temp tables and cursors?

Thanks in advance.
Ray






---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]




---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]


IMPORTANT DISCLAIMER - THIS MAY AFFECT YOUR LEGAL RIGHTS:

Because this document has been prepared without consideration of any
specific clients investment objectives, financial situation or needs,
a Bell Potter Securities Limited investment adviser should be
consulted before any investment decision is made.

While this document is based on the information from sources which
are considered reliable, Bell Potter Securities Limited, its directors,
employees and consultants do not represent, warrant or guarantee,
expressly or impliedly, that the information contained in this document
is complete or accurate.

Nor does Bell Potter Securities Limited accept any responsibility to
inform you of any matter that subsequently comes to its notice, which
may affect any of the information contained in this document.

This document is a private communication to clients and is not intended
for public circulation or for the use of any third party, without the
prior approval of Bell Potter Securities.


Disclosure of Interest: Bell Potter Securities Limited receives commission
from dealing in securities and its authorised representatives, or introducers
of business, may directly share in this commission. Bell Potter Securities
and its associates may hold shares in the companies recommended.

Bell Potter Securities Limited ABN 25 006 390 772 AFS Licence No. 243480

MS Sql Server LazyDBA home page