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,207 reads

Blogs

AI Step 1

By

As this is an Artificial Intelligence (AI) World, things are changing. We can see that...

Beginner’s Guide: Building a Dockerized Todo App with React, Chakra UI, and Rust for Backend

By

In a containerized app, React and Chakra UI provide a robust and accessible user...

A New Word: Nachlophobia

By

nachlophobia – n. the fear that your deepest connections with people are ultimately pretty...

Read the latest Blogs

Forums

SSIS package works in VS but failed in SSMS

By HL

Please help and thanks. Package:Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has...

Need a list of stored procedures that execute multiple stored procedures

By Lord Slaagh

Hello SSC! I hope you all had a happy and safe holiday! Apologies if...

sql query to check status change of an item

By SQL Bee

I have a table dbo.tblPresentationStatus (sql script attached - table script.txt) I have to...

Visit the forum

Question of the Day

The Funny SELECTs

What is returned from this query?

SELECT
  ( SELECT COUNT (*) FROM Sales.SalesOrderHeader AS soh
    WHERE soh.OrderDate > '01/01/2011' AND soh.OrderDate < '01/01/2012') AS OrdersIn2000
, ( SELECT COUNT (*) FROM Sales.SalesOrderHeader AS soh
    WHERE soh.OrderDate > '01/01/2012' AND soh.OrderDate < '01/01/2013') AS OrdersIn2001
, ( SELECT COUNT (*) FROM Sales.SalesOrderHeader AS soh
    WHERE soh.OrderDate > '01/01/2013' AND soh.OrderDate < '01/01/2014') AS OrdersIn2002;

See possible answers