I have created an article sometime back about filetables but I have covered how to work with it. It’s now time for writing this article. In my earlier article you came to know what’s filetable and how it’s useful. Let’s now jump in to create and work with filetables. You need to satisfy all the pre-requisites which we have taken care in the earlier article. Continue reading Working with Filetables
SQL Server 2012 has been released with so many new features. Microsoft has changed SSMS 2012 core to integrate with Visual studio 2010 shell. This revamp is not only for features they also changed certification path for SQL Server 2012. Below are the new certification titles that comes with SQL Server 2012
I was working in a project where we are using database mirroring as high availability solution. In the same instance we have multiple databases in which only critical databases are configured for database mirroring. As you know database mirroring scope is limited to database only which means dependent database are not failed over (which is now possible in SQL Server 2012 as Availability groups). In my case the dependent database is not even configured for mirroring. They have some procedures \ views which will pull the data from dependent database. Assume if the mirrored database is failed over to next node they won’t be able to pull the data from dependent database which means they are screwed and application will be down till we go back to principal node.
This might be a simple article for the intermediate folks, however I would like to show you the screen’s in SQL Server 2012 installation. As far as I know the setup is similar to the one which we did for SQL Server 2008 R2, there are some additions to the installation part. Before jumping into the installation lets see the add-ons related to installation.
As you know there are so many security measures are taken during every release of SQL Server. This version of SQL Server will be using Managed Service account to run SQL server related services. In other terms earlier versions we used Local system account as service account for all SQL Server related services however in this version we be will using individual local accounts for all SQL server related services. In this case whatever application runs on local system are allowed to access SQL Server. So to overcome this MS team has started using managed service accounts in SQL Server.