Conor vs. SQL Saturday Austin

I’ll be talking about one of the new things our team has been develping this Saturday at the SQL Saturday event in Austin (http://www.sqlsaturday.com/97/eventhome.aspx) on the new ColumnStore index being added in the upcoming release of SQL Server.  It will have a little something for everyone, so I hope to see some of you there.  The…

0

Conor vs. Views/Tables

I received an email from a reader this weekend that has a lot of different questions, but one of the main questions related to the difference between views and base tables in SQL Server’s plan generation process.  ie if I have a view “select * from table” vs. a table “table”, does the optimizer treat…

2

Conor vs. UNIQUE in Index Definitions

I gave a talk to the Austin-area PASS group last night on B-Tree indexing in SQL Server, and I received a question about whether to make clustered indexes UNIQUE or not (assuming the data is unique on the key columns).  The expectation was that this should perform better when the index was UNIQUE. Let’s back…

1

Conor vs. Isolation Level Upgrade on UPDATE/DELETE Cascading RI

A customer recently asked our support organization about an unexplained series of range locks that they were seeing on a DELETE to a table with a foreign key. Here is the repro:   1: create table Foo (FooId int not null primary key) 2: create table Bar (FooId int not null, BarId int not null)…

4

Conor vs. Non-ANSI NULLs, part 1

I was thinking about indexed views.  Well, more specifically, I was thinking about why indexed views are hard to use.  One of the reasons that they are hard is that there are just so many restrictions.  Anyways, one of the things I’d like to better understand is how many customers actually use ANSI NULLs OFF…

1

Conor vs. MERGE and PRIMARY KEY collisions

MERGE is a new operation added in SQL Server 2008. It has all sorts of knobs, bells, and whistles. The primary value of this feature is to collapse multiple query statements into one query statement. Overall, this avoids the “overhead” necessary to run a query a few times and can be a big benefit, especially…

1

OPTIMIZE FOR UNKNOWN - How could that possibly make any sense???

Yes, I’m alive. I have been chatting with my wife about the times I need to “go dark” – in this case, I am working on features that I can’t discuss yet, other than to say that I am *very* excited to go to work every day.. (well, since I work out of my house,…

3

The vote is in! (CHECK CONSTRAINTS vs. TRIGGERS vs. STORED PROCEDURE business logic)

Thank you for everyone who “voted” – a great day to talk about the issues of the day :). After much research, I’ve found that we live in a divided country.  Some of us like triggers.  Others wouldn’t be caught dead with a trigger and do lots of business logic validation within stored procedures.  Some…

2

More Business Logic Validation

I’ve gotten a few data points, but I don’t think I’ve had enough yet to complete my sample.  I’m still looking for people willing to describe how and where they implement business logic in their database applications. 1. CHECK CONSTRAINTS 2. TRIGGERS 3. Mid-Tier 4. what’s business logic?? Please send me some details of why…

1

CHECK Constraints vs. TRIGGERS

I’ve been having a conversation with a customer about CHECK constraints and TRIGGERs, and I thought it would be good to survey some of our customers about how people use these features. I’m curious how many people encode business logic validation in CHECK constraints.  I’m also curious about what you would LIKE to encode in…

1