This is just a little blog posting to announce that the first fix for SQL Server 2012 came out last week during Easter Break.

Since the commercial version of SQL Server 2012 is due to be released in April, a little posting about the changed licensing costs seems appropriate.

Recently, during one of my missions, a client asked me to give him access rights to the SQL Server logs from SSMS to his application managers. As you know, you must grant the role “securityadmin” to have such rights. However, with this role you can also manage logins, CREATE DATABASEs and change passwords.

These are “too many rights” for an IT manager, but there seems to be no other way ... or is there?

I have seen at a customer that SQL Server's policy doesn't follow Microsoft's recommendations about antivirus and databases (kb 309422), such as excluding *.mdf,*.ndf and *.ldf files. In addition, there is no Oracle policy in case of Forefront Endpoint Protection 2010 (known as FEP 2010).

I have decided to create generic databases policies for FEP (optimized by dbi services) adapted for all SQL Server and Oracle environments.

Since a few days, Microsoft® SQL Server® 2012 Express LocalDB Release Candidate 0 is online.

We were looking forward to it and it has finally arrived...

Since Friday, 18 November, Microsoft® SQL Server® 2012 Release Candidate 0 is online.

For a few months, I have been testing the new  SQL Server 2012 (codename Denali) and I was very surprised from the DMVs of this version. Dynamic management views (DMVs) return server state information that can be used to monitor the health of a server instance, diagnose problems and tune performance. I will focus on some DMVs which are very interesting for a DBA.

Last week, I attended the Microsoft TechDays for the first time. The Swiss 2011 "edition" took place in Bern. For me this is really a new challenge because I have never worked deeply with the Microsoft database platform "SQL Server".