Database cloning – CLONEDATABASE
Database cloning is a new feature supported in SQL Server. Only SQL Server 2014 SP2 and SQL Server 2016 SP1 support cloning. The command syntax is very simple [crayon-5e81b52ed8fb5359335187/]...
2017-02-27
45 reads
Database cloning is a new feature supported in SQL Server. Only SQL Server 2014 SP2 and SQL Server 2016 SP1 support cloning. The command syntax is very simple [crayon-5e81b52ed8fb5359335187/]...
2017-02-27
45 reads
Database cloning is a new feature supported in SQL Server. Only SQL Server 2014 SP2 and SQL Server 2016 SP1...
2017-02-27
726 reads
These are those queries where you are pulling for, let’s say, a first name, a last name, a state, and/or...
2017-03-06 (first published: 2017-02-27)
3,563 reads
This weekend I set up some SQL vNext virtual machines, two on Windows and one on Linux so that I...
2017-03-07 (first published: 2017-02-27)
2,115 reads
I am resuming technical blogging after a gap of nearly a month. I will continue to blog my re learning...
2017-03-02 (first published: 2017-02-27)
2,583 reads
Today is the launch of SQL Clone, a great new tool that helps you quickly and easily provision SQL Server...
2017-03-06 (first published: 2017-02-27)
2,155 reads
Ergh, not a fun weekend rugby wise. But anyway…
Last week Microsoft released an image for SQL Server 2016 SP1 Developer...
2017-02-27
595 reads
Hey guys! So here's my adventure in deploying Windows Server 2016 Nano on a physical server. It was a hard...
2017-02-27
896 reads
Note this was during earlier beta usage, so some of the UI and other features will have been updated more....
2017-02-27
726 reads
Continuation from the previous 98 parts, the whole series can be found at http://www.nikoport.com/columnstore/.
This blog post is focused on the...
2017-02-26
844 reads
By DesertDBA
I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it...
Should you adopt an off-the-shelf AI tool, partner with a specialist, build in-house, or...
By ReviewMyDB
Part 1 of my What's New in SQL Server for the Developer series. IIF,...
Comments posted to this topic are about the item Switching Schema II
Comments posted to this topic are about the item A Practical Approach to Automating...
Comments posted to this topic are about the item Data Lost in the Cloud
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get two rows back for the objects, named dbo.beer and etl.beer. Both the tables have identical schemas and are not partitioned. There are 25 rows in dbo.beer and 0 rows in etl.beer. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers