Administration

SQLServerCentral Article

Worst Practices - Making Databases Case Sensitive (Or Anything Else)

  • Article

Article number four in this popular series continues exposing Worst Practices! This week Andy continues his tirade by talking about why case sensitive databases should be BANNED from the planet. Is he right or just OUT OF CONTROL? Read the article and join the discussion - your comment may lead to an article, that's what generated this one!

4.5 (4)

You rated this post out of 5. Change rating

2005-07-08 (first published: )

29,107 reads

Blogs

A First Look at Redgate’s Subsetter

By

I have been a proponent of subsetting databases in dev/test for a long time....

Azure SQL MI License free?

By

A common setup when leveraging the cloud is to use the cloud for Disaster...

Foreign Keys in SQL Data Generator

By

A customer recently asked about using FKs in SQL Data Generator, and I decided...

Read the latest Blogs

Forums

Using AI for Security

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Using AI for Security

Writing to Clones

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Writing to Clones

Live webinar: How to excel at managing multiple database platforms

By Press Release

Comments posted to this topic are about the item Live webinar: How to excel...

Visit the forum

Question of the Day

Writing to Clones

I run this code on SQL Server 2019:

DBCC CLONEDATABASE(imdb, imdb_dev)
I then change to the cloned database, imdb_dev, and run some queries. I then run this code while testing:
INSERT dbo.Title (TitleID, Title, DateReleased) VALUES (3234, 'Maestro', '2023')
GO
What happens?

See possible answers