|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 7:18 AM
Points: 33,112,
Visits: 27,038
|
|
AndyD (6/12/2008)
Jeff Moden (6/12/2008)
I remember seeing an article on the difference between 0% and 100% fill factors... Dunno if I can find it, again, but I'll look...I was only regurgitating what is stated in BOL... from my point of view it seems strange that 0% and 100% mean the same thing 
Oh no... sorry. It wasn't a challenge... I agree that's what BOL says... dang, I gotta find that article.
--Jeff Moden "RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 7:18 AM
Points: 33,112,
Visits: 27,038
|
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Friday, June 07, 2013 1:40 AM
Points: 893,
Visits: 880
|
|
| Perhaps the esteemed Mr Phil Factor would like to get involved in the discussion?
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Tuesday, January 25, 2011 9:59 AM
Points: 30,
Visits: 120
|
|
I set up the alerts on a test system and have database mail enabled with a valid profile (that I can send a test email from). I added the notification to the alerts to use a operator that used this DBMail profile. I generate a test deadlock but the alert never fires and yes the deadlock does happen: Msg 1205, Level 13, State 45, Line 4 Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
What am I missing here? Alert set up, dbmail set up, operator set up. Alert setup for deadlock as recommended to use the operator that uses dbmail.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Yesterday @ 9:00 AM
Points: 1,397,
Visits: 2,748
|
|
Check checking did you enable the profile you created as per the article? Did the alert fire into the event log? do any of the other events fire?
Facts are stubborn things, but statistics are more pliable - Mark Twain Carolyn SQLServerSpecialists
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Tuesday, January 25, 2011 9:59 AM
Points: 30,
Visits: 120
|
|
I double checked and the profile is enabled. The script to set the jobs to write to the event log worked (one of the dummy job now is set to write to teh application log) but I am still not seeing the deadlock in the logs though.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Thursday, May 02, 2013 10:44 AM
Points: 1,079,
Visits: 513
|
|
Nice article. We are going through an upgrade to 2005 and it's nice to see what your doing being confirmed by your peers.
I would also add some more notes on hardware set-up. I'm a little weak in this area and like to see more on the initial set-up so I know I'm going to get the most out of the server.
For instance, I didn't know about volume alignment and found the following article very helpful:
http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/pdpliobp.mspx
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, September 01, 2010 9:01 AM
Points: 3,
Visits: 37
|
|
Great article! I may have missed these but, a couple other items that come to mind:
- Security, who has access and who should or shouldn't have access? - Service accounts being used. - Auditing of schema changes. - Do any tables need to have auditing setup? - Under backups, are transaction log backups not being done that should be? - Linked Servers. - Index usage statistics
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Yesterday @ 9:00 AM
Points: 1,397,
Visits: 2,748
|
|
Try a different alert, I'll be honest I have been lucky enough not to come across any deadlocks in SQL Server 2005 databases I've supported - things have been looking up, the deadlock event was set up and taken from a SQL Server 2000 script.
USE [msdb] GO /****** Object: Alert [Deadlock] Script Date: 06/12/2008 17:46:22 ******/ EXEC msdb.dbo.sp_add_alert @name=N'Deadlock', @message_id=0, @severity=0, @enabled=1, @delay_between_responses=0, @include_event_description_in=1, @category_name=N'[Uncategorized]', @performance_condition=N'SQLServer:Locks|Number of Deadlocks/sec|Database|>|1', @job_id=N'00000000-0000-0000-0000-000000000000'
Facts are stubborn things, but statistics are more pliable - Mark Twain Carolyn SQLServerSpecialists
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Thursday, May 02, 2013 10:44 AM
Points: 1,079,
Visits: 513
|
|
Carlo Mitchell (6/12/2008) Great article! I may have missed these but, a couple other items that come to mind:
- Security, who has access and who should or shouldn't have access? -
Ack! Security! Another one of those areas I have to read articles on....
|
|
|
|