Posted by Erland Sommarskog on 02/11/06 20:14

xAvailx (bzamora.avastone@gmail.com) writes:
> I didn't find any documentation that notes save point names are case
> sensitive, but I guess they are...

As with all other identifier, they depend on the collation, more
precisely, the database collation.

This sample demonstrates:

CREATE DATABASE CS COLLATE Finnish_Swedish_CS_AS
go
USE CS
go
BEGIN TRANSACTION
SAVE transaction Nisse
PRINT 'rollback in case-sensitive database'
ROLLBACK TRANSACTION NISSE
rollback transaction
go
CREATE DATABASE CI COLLATE Finnish_Swedish_CI_AS
go
USE CI
go
BEGIN TRANSACTION
SAVE transaction Nisse
PRINT 'rollback in case-insensitive database'
ROLLBACK TRANSACTION NISSE
rollback transaction
go
use master
go
DROP DATABASE CS
DROP DATABASE CI

When you develop, you should also use a case-sensitive database,
since if you develop on case-insensitive collation, and then deploy
on case-sensitive (because the customer so requires), you will have a
nightmare.



--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]