{"id":2743,"date":"2012-09-06T01:58:00","date_gmt":"2012-09-05T23:58:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/snapmanager-for-sql-server-databases-limitation-policy-1\/"},"modified":"2012-09-06T01:58:00","modified_gmt":"2012-09-05T23:58:00","slug":"snapmanager-for-sql-server-databases-limitation-policy-1","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/snapmanager-for-sql-server-databases-limitation-policy-1\/","title":{"rendered":"SnapManager for SQL Server: databases limitation policy"},"content":{"rendered":"

I recently talked to a customer about SnapManager, its recommendation on the number of databases and about a way to prevent the creation of more than 35 databases.<\/p>\n

The NetApp recommendation is no more than 35 databases on a single volume. The reason is that SQL Server has to use 4-5 worker threads per database in order to manage the freezing and un-freezing I\/O for each database.<\/p>\n

Look at this note:<\/p>\n

\"\"<\/a><\/p>\n

More information on this issue may be found here<\/a><\/p>\n

To never ask about servers where each day new databases can appear created by other persons (IT group or Support) having rights who don’t know this limit, I proposed to create a policy in SQL Server to be alerted.<\/p>\n

What is a Policy-based Management?<\/h3>\n

It’s a new management feature introduced in SQL Server 2008.
\nHere is the definition on MSDN<\/a>:<\/p>\n

“Policy-Based Management allows DBAs to define a set of policies that can control many different aspects of SQL Server”.<\/p>\n

How to create a policy?<\/h3>\n

We need 4 steps for this:<\/p>\n