Thoughts about the Microsoft Data Amp Announcements
Microsoft conducted a live event called Microsoft Data Amp to announce a number of key features and releases for SQL...
2017-04-27 (first published: 2017-04-20)
1,593 reads
Microsoft conducted a live event called Microsoft Data Amp to announce a number of key features and releases for SQL...
2017-04-27 (first published: 2017-04-20)
1,593 reads
Apr 22nd I will be presenting “Re-Indexing – The quest of ultimate automation” & “Consolidated Essential Performance Health Check using PowerShell” @ SQLSaturday, Silicon...
2017-04-19
403 reads
So today I saw this tweet from Mathias in reply to Stefan and Amanda
That looks cool. Twitter in VS Code, one...
2017-04-28 (first published: 2017-04-19)
1,021 reads
It’s official: the next version of SQL Server, planned to be released this year, will be called SQL Server 2017....
2017-04-19
3,427 reads
I’ve been testing the SQL Server on Linux for a long time. After the recent Microsoft Data Amp event, I...
2017-04-19
874 reads
Taking a short break from the Database Fundamentals series of the last few weeks, I’d like to mention some upcoming...
2017-04-19
126 reads
In this brave, new world of Extended Events (XE, XEvents), I find myself with a mixture of scripts for troubleshooting...
2017-04-25 (first published: 2017-04-19)
3,326 reads
I recently was on a call where a technical unit indicated they did not receive any form of documentation around...
2017-04-24 (first published: 2017-04-19)
1,335 reads
A while back, I was building the database schema for a web application which had some reporting functionality and among other things, I had do implement logic in the...
2017-04-19
64 reads
A while back, I was building the database schema for a web application which had some reporting functionality and among...
2017-04-19
12,744 reads
By Steve Jones
I was experimenting with CHOOSE() recently after I was asked a question. In a...
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...
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