Reading list for the week – 17/10/11

In this week’s edition, I have got quite a few good links lined up.

The big new first. SQL Server code-named “Denali” gets an Official Name. In the recently concluded PASS Summit 2011 it was announced that the next version of SQL Server will be called SQL Server 2012. Read more about this in this article.

Another big announcement that was made last week is that Microsoft SQL Server ODBC Driver  for Linux will be available along with SQL Server 2012! This is for sure a big step in the right direction.

We know that the Analysis Service cannot be added as a cluster instance. Amit Banerjee (b | t) explains how to add an Analysis Service as a failover cluster instance using the command line setup. This article is a very interesting read.

On clicking Fragmentation tab under the properties of an index in SSMS, the response time used to be very slow. This was because SSMS used to check the fragmentation of all the objects referenced by sys.dm_db_index_physical_stats DMV instead of the selected index. This hotfix resolves that bug.

Tibor Karaszi (b | t) in his article Who owns your jobs talks about the relationship between Active Directory users/groups and SQL Server Agent Job ownership.

Happy learning!

2 thoughts on “Reading list for the week – 17/10/11

  1. Pradeep Kumar Buddharam

    Hi Pradeep,

    Hope you are doing well. I facing a Sql server agent issue. I have installed Sql server 2008 R2 on Windows 2008r2 cluster. Once I have done with the sql installation I am not able to see the Sql server Agent in the resources list. I can sell Sql server(MSSQLserver). I am able to see the Sql agent in the services.msc and tried to restart the agent but I got the below error message
    The MSSQLSERVER service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service
    Can you please help me troubleshooting this issue.

    Thanks & Regards,
    Pradeep Buddharam

    1. PradeepAdiga Post author

      Hi Pradeep, the SQL Server Agent Error Log should contain more information regarding this


Leave a Reply