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 |
|
dundealing
Starting Member
12 Posts |
 Posted - 2007-08-23 : 11:46:15
|
| Hi,in our development and testing environment we always use (nolock) on every table to minimize locks.I have found out that we can do the following:Go to Tools -> Options -> Query Execution -> SQL Server -> AdvancedSet the drop down box to READ UNCOMMITTED for SET TRANSACTION ISOLATION LEVELThis removes the need to have the NOLOCK hint on every table.However, I have some reservations about this. If I create a stored procedure in MS with these settings, will they apply on the production server when I deploy it? A window appeared when I changed the settings stating something like 'it would only affect the queries run on this instance of Management Studio, but I need to be sure.A colleague suggested that sometimes setting session defaults like this causes them to be written into coded scripts and installed procedures written in management studio and this is not obvious therefore you get inconsistent results across users apparantly running the very same script.Can anyone please advise me as to whether this setting is a good/bad idea in a development/testing/production environment? |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-08-23 : 23:16:35
|
| You should set those in code since people don't always run sp in ssms. |
 |
|
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2007-08-24 : 00:55:46
|
| Those settings are local to your machine.Dinakar Nethi************************Life is short. Enjoy it.************************http://weblogs.sqlteam.com/dinakar/ |
|
|
|
|
|
|
Customizing Management Studio