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)

You rated this post out of 5. Change rating

2005-07-08 (first published: )

29,264 reads

Blogs

A New Chapter: Why I Made the Move from Dayforce to ESO

By

A New Chapter: Why I Made the Move from Dayforce to ESO Over the...

Lean Six Sigma – Brief

By

When you have a project or system, it has to be optimized, tuned, and...

T-SQL Tuesday #200: Bad Query signals

By

NO AI was used to generate this content. Grammarly was used to check and...

Read the latest Blogs

Forums

Reading Parquet using openrowset

By saum70

Hi, We are looking out to read parquet file directly from on premise shared...

Impact of Single-Threaded PVS Cleanup on ADR in SQL Server 2019

By abdalah.mehdoini

We want to enable ADR on our SQL Server 2019 instances. I’ve heard that...

Forward Deployed Engineers

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Forward Deployed Engineers

Visit the forum

Question of the Day

DBCC CHECKDB Limits II

I have a SQL Server 2025 database that I want to check for corruption every night. One of the things we do is disable indexes used for ETL loads during the weekend and re-enable them on Monday morning. If we run DBCC over the weekend, are our disabled indexes checked for consistency?

See possible answers