SQLCover v 0.2 - Bug fixes and Azure V12 Support
I have released a new version of SQLCover which is a code coverage tool for T-SQL (let's you identify where you need to focus when writing tests).
This includes a...
2016-05-05
11 reads
I have released a new version of SQLCover which is a code coverage tool for T-SQL (let's you identify where you need to focus when writing tests).
This includes a...
2016-05-05
11 reads
The code optimization is a mandatory task for the programmable objects in SQL Server. During time some code can start working “badly” i.e. become slow. In that case a...
2016-05-05
14 reads
The code optimization is a mandatory task for the programmable objects in SQL Server. During time some code can start working “badly” i.e. become slow. In that case a...
2016-05-05
14 reads
The code optimization is a mandatory task for the programmable objects in SQL Server. During the time some code can...
2016-05-05
235 reads
The code optimization is a mandatory task for the programmable objects in SQL Server. During time some code can start...
2016-05-05
91 reads
There seems to be two trains of thought and I think this is mainly down to who and where your...
2016-05-13 (first published: 2016-05-05)
4,356 reads
There seems to be two trains of thought and I think this is mainly down to who and where your...
2016-05-05
47 reads
There seems to be two trains of thought and I think this is mainly down to who and where your...
2016-05-05
42 reads
One June 5, I’ll be back in Pensacola, FL for SQL Saturday #491. It’s been a few years since there...
2016-05-05
522 reads
There seems to be two trains of thought and I think this is mainly down to who and where your developers are. The first is that a stored procedure...
2016-05-05
21 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...
Has anyone ever seen this before? I have sysadmin permission on a server. I...
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...
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