Common Mistakes in SQL Server – Part 6
In SQL Server, there are various scenarios in which you may want to consider recompiling a query or a stored procedure to ensure optimal query performance. Recompilation generates a...
2023-10-23
51 reads
In SQL Server, there are various scenarios in which you may want to consider recompiling a query or a stored procedure to ensure optimal query performance. Recompilation generates a...
2023-10-23
51 reads
Last week, in the post Common Mistakes in SQL Server - Part 4 I explained about the Auto Growth configuration in SQL Server and how it can adversely impact....
2023-10-27 (first published: 2023-10-16)
1,269 reads
Last week, in the post Common Mistakes in SQL Server - Part 4 I explained about the Auto Growth configuration in SQL Server and how it can adversely impact....
2023-10-16
46 reads
Last week we have discussed how Null Values can cause a trouble in Common Mistakes in SQL Server – Part 3. This week I would like to draw your...
2023-10-23 (first published: 2023-10-09)
965 reads
Last week we have discussed how Null Values can cause a trouble in Common Mistakes in SQL Server – Part 3. This week I would like to draw your...
2023-10-09
48 reads
Last week we discussed advantages of recompilation in Common Mistakes in SQL Server – Part 2. This week in this article Common Mistakes in SQL Server - Part 3 I...
2023-10-18 (first published: 2023-10-02)
1,024 reads
Last week we discussed advantages of recompilation in Common Mistakes in SQL Server – Part 2. This week in this article Common Mistakes in SQL Server - Part 3 I...
2023-10-02
71 reads
The Identity property creates an incremental value for the specified column automatically, which is why it is widely used by developers when they designed the table and a primary...
2023-09-25
101 reads
The Identity property creates an incremental value for the specified column automatically, which is why it is widely used by developers when they designed the table and a primary...
2023-09-25
44 reads
In this series of articles I will be sharing the common mistakes in SQL Server. I am certain that this is going to be very interesting read, here is...
2023-09-18
517 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