Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Member Profile for Cadavre Expand / Collapse
Contact Information Personal Information
Username: Cadavre No photograph available.
Public Email: No information available.
  Send this member a private message...
  Send this member an email message...
  Add member to my buddy / ignore list!
MSN IM: No information available.
Yahoo IM: No information available.
AIM IM: No information available.
ICQ#: No information available.
Twitter Profile: No information available.
Facebook Profile: No information available.
Google+ Profile: No information available.
LinkedIn Profile: No information available.
Other social media: No information available.
Homepage: No information available.
Blog: No information available.
Birthday: 1/26/1985 (29 years old)
Location: UK
Occupation: Developer
Interests: View members interests...
Biography: No information available.
Tools: Show all posts by this member...
  Find all topics this member has participated within...
User Details Additional Information
User Status: (Offline)
Member Group: General Forum Members
Joined: 1/26/2010 5:35:15 AM (7,311 visits since)
Local Time: 4/17/2014 8:16:25 PM
Last Login: Today @ 7:06:23 AM
Total Points: 2,404 point out of 1,547,578 total points. (.16% of total)
Average Points: Averaging 1.56 points daily since registration
User Level: SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy
Avatar:
Post Signature:
Not a DBA, just trying to learn

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better, quicker answers on SQL Server performance related questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/



If you litter your database queries with nolock query hints, are you aware of the side effects?
Try reading a few of these links...

(*) Missing rows with nolock
(*) Allocation order scans with nolock
(*) Consistency issues with nolock
(*) Transient Corruption Errors in SQL Server error log caused by nolock
(*) Dirty reads, read errors, reading rows twice and missing rows with nolock


LinkedIn | Blog coming soon (for sufficiently large values of "soon" )!