Use a Table Variable for Logging Entries that Need to Survive Rollbacks.
This article shows how a table variable can be used to capture error information and log it when your code doesn't work as expected.
2024-02-09
2,659 reads
This article shows how a table variable can be used to capture error information and log it when your code doesn't work as expected.
2024-02-09
2,659 reads
Learn how a C# script can easily load data from Excel into SQL Server.
2024-01-15
6,796 reads
The ForEach loop works with only one file type at a time by default. Learn how you can add code to your packages to work with multiple types of files.
2023-12-18
3,474 reads
I created this stored procedure to be able to run SSRS subscriptions using T-SQL code instead of adding a component in the SSIS package with the subscription id. Let's say we have a set of report subscriptions named like this: ClientReport1, ClientReport2, ClientReport3. To run them using the stored procedure, all we need is this […]
2023-11-29 (first published: 2023-11-21)
1,250 reads
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
One feature that I have been waiting for years! The new announcement around optimize...
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
hi, i noticed the sqlhealth extended event is on by default , and it...
Using New-AzSqlInstanceServerTrustCertificate to import a certificate and get the message New-AzSqlInstanceServerTrustCertificate: Long running operation...
Comments posted to this topic are about the item Refactoring SQL Code, which is...
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers