Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-09-20 : 08:27:14
|
| Anya writes "Hi, I have a stored procedure that processes some information. To utilize several CPUs, I create SQL jobs for each available CPU and each job calls that stored procedure. Inside the stored procedure I declare several cursors and their names start with ‘#’. I thought it was visible only to the current session of the SQL Server and it is exactly how you describe it in some of your replies. When I use only one CPU and therefore only one job calls my stored procedure, everything works. If I use several CPUs and call my stored procedure from simultaneously from several jobs, at some point jobs fail. It seems to me that there is a conflict between the cursor names or something similar to it. Can you please tell me if I can use cursors that start with ‘#’ to create local cursors or how can I find out what exactly is the problem.Thank You" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-09-20 : 14:21:49
|
| Why do you need cursors? Please post your code.Tara |
 |
|
|
|
|
|
Defining temporary cursors that do not conflict between different connections