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 |
|
anupamk
Starting Member
8 Posts |
 Posted - 2015-03-31 : 04:47:06
|
| Hi,I have a table on which DML operation like Insert/Update/Delete is happening. In the same time users are trying to fetch data from that table(using Select). But it leads to performance issue and it get hang.Note:• It hangs even though 'No Wait/No Lock' is used.• DML operations are continuous process and cannot be stooped and at the same it should be available for usersEnvironment- SQL Server 2008 R2Please advise.Anupam |
|
|
bitsmed
Aged Yak Warrior
545 Posts |
Posted - 2015-03-31 : 12:04:34
|
| [url]https://msdn.microsoft.com/en-us/library/ms188929.aspx[/url] |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2015-04-01 : 05:04:17
|
| Don't use NOLOCK ever. The only time we use it is on queries used by DBAs to check values in tables with very high transaction rates. The DBA knows the data is not safe. That's very different to an end user seeing data in any application - they will ASSUME it is safe and take business critical decisions based on it.Consider setting the database to READ_COMMITTED_SNAPSHOT. Make sure you do a full QA test before rolling that out to Production! |
|
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2015-04-02 : 01:41:58
|
| have you analysed the SELECT queries and performed some optimisation exercise? Make sure the indexes and statistics are up to date.Have you analysed the workload placed on the server? Can you see where the bottleneck is occuring?Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
|
|
|
Table Performance and Locking issue