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 |
|
debicool98
Starting Member
1 Post |
 Posted - 2006-01-09 : 18:16:14
|
| I wrote a VB program which reads from a MS SQL database via Select statements Goldmine information and writes them to a different MS SQL Server/database.Goldmine Users are complaining that when i run my program that Goldmine locks up on them when they do changes to the data and Goldmine tries to write the data to the Server.I don't understand why that would be happening.I'm only "reading" the information.Can someone tell me what the reason is for this?If you need any additional info please let me know.I don't know what else to provide.Any help as always is appreciated. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-01-09 : 18:33:34
|
| You can use nolock in your SELECT statements to prevent this behavior. Even though you are just reading the data doesn't mean that you aren't locking data. Take a look at shared locks in SQL Server Books Online for more information, also nolock. This is the main reason why we have a separate reporting database. You might want to consider moving the data that you require to another database, then reading from there.Tara Kizeraka tduggan |
 |
|
|
|
|
|
Select statement locks Goldmine