Infrastructure at your Service
I am currently managing at one of my customer a monitoring project that concerns SQL Server instances and SCOM (System Center Operation Manager). The project includes many instances, more or less 50, divided in two environment (Production and Test) and different versions of SQL Server as 2008, 2012 and 2014. The defined target was to create two groups of instances, respectively Production and Test, in order to manage differently the alert’s subscription. Let’s see how…
In my last blog post (here), I explained how to configure a host for Windows Container as well as how to use some Windows Container cmdlets. Finally I demonstrated how to create a container with a SQL Server 2014 instance. In this blog post, I will continue by explaining how to migrate the container I just created. First of all, let’s remind the context: I have a Container named Test that runs on the top…
Some weeks ago, I did a general presentation about Windows Server 2016 and the new Container feature (here). Today, I will go through the installation and utilization of Windows Containers. I will use a Virtual Machine, under Hyper-V, during this blog. First of all, I have to set the environment to be able to use Windows Containers as it requires the Container OS Base Images. Microsoft has prepared a script in order to configure a…
One of the new feature which will come with Windows Server 2016 is the Containers. Microsoft made available its fourth technical preview of his Windows Server 2016 platform some days ago. This new Technical Preview brings with it and for the first time Hyper-V Containers as the Technical Preview three came with the first release of Windows Server Containers. I will discuss about the difference of those two types of Container later in this blog….
Some months ago, my colleague Nathan explained you the bases of the new Stretch Database functionality via two blogs here and here. With the new SQL Server 2016 CTP 3.0, Stretch Database now includes new features and enhancements that I will sow you in this blog. In previous versions of SQL Server 2016 CTP 2.x, before to be allowed to Enable Stretch Database, you had to enable the “Remote Data Archive” option for the…
The new CTP 2.4 has been released some weeks ago by Microsoft. My colleagues and I have already blogged about some new functionalities. I will focus in this blog about the new possibility of Index Maintenance Tasks regarding Indexes. Until SQL Server 2016, DBAs didn’t use often the Maintenance Plan provided by SQL Server for indexes. In fact, those two tasks, Reorganize Index and Rebuild Index were not enough detailed and DBA’s preferred to create…
To be able to define which Tables or Stored Procedures will us the best performance gain after migration to In-Memory OLTP, SQL Server 2014 provided a tool called AMR (Analysis Migration and Reporting). This tool was really interesting but we should have, before to use it, to create a Management Data Warehouse and so on… (I wrote a blog here for this configuration and an article on SQL Magazine here) With SQL Server 2016, actually…
During the read of a blog of my colleague Nathan Courtine about Stretch database, I installed the version of SQL Server 2016 Upgrade Advisor and Oh surprise! it looks really NEW! “A new generation of advisor tool for SQL Server” aka Microsoft. To download and install it, click here. This new version has a dual role: Check the compatibility of old versions of SQL Server compared to SQL Server 2016 Help adoption of new SQL…
The CTP2.1 has been released for some weeks and it is time to check which interesting enhancements have been already deployed for the In-Memory OLTP feature. I will first have a look to the memory optimized table. Memory Optimized table I have a Memory Optimized table named command_queue_HK and I will add a column to this table. This table is saved on my disk in a XPT folder with its corresponding files: I execute the…
Some days ago, one of my customer claimed that searching for “Muller” doesn’t return “Mueller” and “Müller” as well! This is typically an issue due to the collation of the SQL Server database, but how to resolve this problem? The collation of the database is Latin1_General_CI_AS, so a case insensitive and accent sensitive collation. If a run the following query: Select name from Person where name like ‘muller’ I get only “Muller” which is normal…
