#sqlchamp

#New Database scoped Configurations #SQL #Azure #SQLAzure @SQLChamp MS introduced new Database scoped configurations in SQL Azure (V12) and SQL Server 2016; Need for new Database Scoped Configurations Have you ever faced a situation where one of the database requirements are totally different from other like MAXDOP settings and you wanted to set a different MAXDOP for a single DB; or you wanted a feature which can keep such Primary and secondary database configurations in sync. MS is listening and they introduced Database Scoped Configurations and you can change them with this DDL statement: Alter Database Scoped Configuration. This was a much needed enhancement. Here's a list of Database scoped configurations which are now available on DB level. These are not new configurations, but now you can also configure these options at the database level rather than the server level. So imagine you are planning to consolidate servers on a single instance, but earlier you were not able to do it because of different needs of such configurations, http://www.sqlchamp.com/2016/06/database-scoped-configurations/230 http://www.sqlchamp.com/2016/06/database-scoped-configurations/230

Know these restrictions #limitations before moving to #SQLAzure #SqlChamp As we already discussed SQLAzure is an offering under Microsoft Azure umbrella as PaaS (Platform as a service) & there are limitations of using SQLAzure (SQLDatabase) over SQLServer in Azure VM (or on-premise SQLServer) I am listing down all the limitations under specific headings which will help you prepare accordingly and decide before shooting the arrow (Making the switch). Make sure you read the detailed difference between both offerings so that you understand it better. The Limitations of SQLAzure are as follows: Troubleshooting & Audit related Limitations Eventing: events, event notifications, query notifications Read More at http://www.sqlchamp.com/2016/04/sqlazure-limitations/166 http://www.sqlchamp.com/2016/04/sqlazure-limitations/166