Common Mistakes in SQL Server – Part 4
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)
928 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)
928 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
22 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)
966 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
15 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
15 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
41 reads
Security! This is the word that comes to mind of every concerned person when it comes to storing, accessing, and sharing the data and database or database server. At times when applications are run in geographically restricted areas, there...
2023-09-27 (first published: 2023-09-04)
403 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
72 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
13 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
490 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers