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 |
|
layziee
Starting Member
1 Post |
Posted - 2012-01-26 : 16:51:49
|
| My company's accounting department works with excel files that are connected to database tables to pull data from on occasion. They have been using this for some time now, but recently we ran into an issue where a spreadsheet was left open for an extended period of time, which somehow locked up key tables, which prevented users from accessing the application tied to this database. What is an effective way to prevent this from happening? One co-worker advised that I should create a procedure to copy the tables used queried within the spreadsheet and insert it into another virtually empty database, point the spreadsheet's query to this new DB, and schedule the procedure to run every 10 minutes. But I'm not sure if this is the best way to approach this, as some of the tables are rather large. Any suggestions would be appreciated! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|