SSDT DevPack - Highlight expensive queries
When developing stored procedures in SSDT it is important to know when you have written a query that is potentially...
2015-11-27 (first published: 2015-11-22)
1,736 reads
When developing stored procedures in SSDT it is important to know when you have written a query that is potentially...
2015-11-27 (first published: 2015-11-22)
1,736 reads
When developing stored procedures in SSDT it is important to know when you have written a query that is potentially slow or has a high IO or CPU cost...
2015-11-22
11 reads
When developing stored procedures in SSDT it is important to know when you have written a query that is potentially...
2015-11-22
19 reads
When developing stored procedures in SSDT it is important to know when you have written a query that is potentially...
2015-11-22
28 reads
When developing stored procedures in SSDT it is important to know when you have written a query that is potentially...
2015-11-22
79 reads
A few days ago I returned from PASS Summit 2015 (and a vacation I took afterwards). Here’s my recap: I...
2015-11-22
684 reads
One of the projects that’s been on my list lately is to programmatically access Twitter for a few ideas I...
2015-11-20
833 reads
As a DBA, I have a collection of scripts that I use for anything from auto-fixing logins to seeing who...
2015-11-20
981 reads
SQL Server Reporting Services (SSRS) is getting quite the overhaul in SQL Server 2016. Lot’s of things are changing:
new look...
2015-11-24 (first published: 2015-11-20)
4,140 reads
I was always challenged when my customers asked me what tables and columns are referenced by a stored procedure which was written many years ago by the guy who...
2015-11-19
29 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