SQL Server STUFF
The STUFF function in SQL Server is one of those little gems that is very under-used but when needed can be a real handy utility – at least that’s...
2022-01-10
24 reads
The STUFF function in SQL Server is one of those little gems that is very under-used but when needed can be a real handy utility – at least that’s...
2022-01-10
24 reads
I blogged the other about have some issues translating Oracle date formats to SQL Server date data types I find the way SQL Server handles dates with a defined...
2021-12-06
10 reads
I was doing some conversion of Oracle code (PL/SQL) to SQL Server code (T-SQL) – which had some quirks. I just thought that I’d share a quick tip that...
2021-12-02
16 reads
G’day, I was asked recently what a modern data warehouse is – and that’s a vey thought provoking question. First, there’s the tag “Modern” – I think what’s modern...
2020-12-14
19 reads
OPENJSON is pretty central to manipulating JSON documents in T-SQL. As we’ve seen, we can use a default schema that will return metadata about the JSON document or we...
2020-06-24 (first published: 2020-06-09)
6,852 reads
OPENJSON is pretty central to manipulating JSON documents in T-SQL. As we’ve seen, we can use a default schema that will return metadata about the JSON document or we...
2020-06-09
16 reads
Using Aliases in T-SQL is very common. We can alias both Tables (FROM clause) and Columns (SELECT clause) and some other things too. It’s all pretty fundamental to writing...
2020-06-08
285 reads
Using Aliases in T-SQL is very common. We can alias both Tables (FROM clause) and Columns (SELECT clause) and some other things too. It’s all pretty fundamental to writing...
2020-06-08
13 reads
We’ve looked at getting pulling data from a JSON document into relational table format using an explicit schema that was defined in the WITH clause of the OPENJSON table...
2020-06-07
25 reads
We’ve looked at getting pulling data from a JSON document into relational table format using an explicit schema that was defined in the WITH clause of the OPENJSON table...
2020-06-07
5 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