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-01-14 : 07:54:49
|
| Pallavi writes "I have a two similar processes (cannot be merged), that will be run around the same time everyday (no, the time cannot be changed either :-). I need to know if it is OK to have one single database that is queried (with similar queries), at the same time. The only difference in the queries would be the location. For example:Select * form agents where location = 'J' would be one query and Select * from agents where location = 'L' would be the other one. Now the queries are not this simple, there are multiple joins in the queries, and ofcourse there are several update, insert statements. Would it be advisible to have two different databases, one per location? How would the performance be affected if I keep everything in a single database. Hope this question is clear enough. If not, I can explain further. Thanks" |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-01-14 : 08:20:01
|
| If you are just slecting data then they will take shared locks so will be OK together apart from the disk access.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
Querying a database simultaneously from two different processes