2010-10-14
2,954 reads
T-SQL
2010-10-12
2,967 reads
2010-10-11
2,803 reads
Working with the INSERT statement in SQL Server
The INSERT statement in SQL Server is versatile. It now allows the insertion of multiple rows of literal values. It also provides the output clause that solves a number of common problems such as ascertaining the value of identity fields, and other calculated fields in tables, or for auditing the rows that are added to tables. Robert, once again, gives a clear introduction.
2010-10-11
5,220 reads
2010-10-07
3,031 reads
2010-10-04
3,033 reads
2010-09-28
2,832 reads
2010-09-27
3,588 reads
Eliminating Duplicate Rows using The PARTITION BY clause
The Partition clause in the Row_Number() Over() function is a quick tool for eliminating duplicate rows.
2012-03-02 (first published: 2010-09-22)
143,687 reads
2010-09-17
3,086 reads
Blogs
T-SQL Tuesday #192: What career risks have you taken?
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
AI: Blog a Day – Day 3: LLM Models – Open Source vs Closed Source
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
How to Parameterize Fabric Linked Services in Azure Data Factory for Azure Devops Deployment
Quite the title, so let me set the stage first. You have an Azure...
Forums
A Quick Restore
Comments posted to this topic are about the item A Quick Restore
Guarding Against SQL Injection at the Database Layer (SQL Server)
Comments posted to this topic are about the item Guarding Against SQL Injection at...
Ola Hallengren Index Optimize Maintenance can we have data compression = page
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
Question of the Day
A Quick Restore
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers