Kathi Kellenberger

Kathi Kellenberger is a Sr. Consultant with Pragmatic Works. She is an author, speaker and trainer.
  • Interests: Walking, running, grandchildren!

SQLServerCentral Article

Using Parameters with Stored Procedures

It seems that SQL Server developers avoid stored procedures whenever possible, especially if they are new to the product. Kathi Kellenberger brings us a basic article that you can give to developers that explains the basics of how you use parameters with ADO.NET, especially output parameters.

(28)

You rated this post out of 5. Change rating

2019-05-23 (first published: )

119,684 reads

SQLServerCentral Article

So Many Choices with SQL Server

There was a day when you didn’t have many decisions to make about a new SQL Server instance. You had to choose from a few editions and two licensing models: per proc or server cal. It wasn’t long ago that SQL Server would almost always be installed on a physical server on premises, and the […]

You rated this post out of 5. Change rating

2018-03-26

80 reads

SQLServerCentral Article

A Review of PDF-eXPLODE

Reporting is a huge part of any DBA's job with constant changes and new requests for data that non-technical people can use. And more
and more often the format of choice is PDF, which ensures the end result looks the same on many different platforms. Kathi Kellenberger takes a look at a product that can allow end-users to generate PDFs from a database and easily send them to other people.

(1)

You rated this post out of 5. Change rating

2008-02-07 (first published: )

8,101 reads

SQLServerCentral Article

Finding Primes

While it's not likely that many of you need to find prime numbers using T-SQL, it is an interesting programming exercise. SQL Server guru Kathi Kellenburger brings us one solution after taking a break over the holidays and reading some popular fiction.

(6)

You rated this post out of 5. Change rating

2008-01-01 (first published: )

7,381 reads

SQLServerCentral Article

Access to SQL Server: Linking Tables

SQL Server 2000 and Access databases can be configured to work closely together. If you find that the Access storage format is not handling your needs and an upgrade is needed, you need not through away all of your access development. Instead, you can link Access tables to underlying tables in SQL Server and improve your application by using SQL Server as the backend for your Access project. Author Kathi Kellenberger brings us her second articles in an Access series looking at Linking tables to

(1)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

45,449 reads

Blogs

Why Optimize CPU for RDS SQL Server is a game changer

By

One feature that I have been waiting for years! The new announcement around optimize...

Performance tuning KubeVirt for SQL Server

By

Following on from my last post about Getting Started With KubeVirt & SQL Server,...

T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future

By

I haven’t posted in a while (well, not here at least since I’ve been...

Read the latest Blogs

Forums

Refactoring SQL Code

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Refactoring SQL Code, which is...

The Read Committed Snapshot Isolation behaviour

By Alessandro Mortola

Comments posted to this topic are about the item The Read Committed Snapshot Isolation...

Working with JSON/JSONB Data in PostgreSQL using Python

By sabyda

Comments posted to this topic are about the item Working with JSON/JSONB Data in...

Visit the forum

Question of the Day

The Read Committed Snapshot Isolation behaviour

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;
go
Then, 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