@etheral1980,

Sorry about that... yes, in the example of the "equality" search, you would need an index on the encrypted column.

@mmartin1,

In the example I gave, the "sensitive date" has no meaning if not associated to the Customer (in this case); they are just dates, so they would not...

Hi @etheral1980,

There is no need for an index on the encrypted column. The index seek would be on Birthdate in the dbo.Customer_Birthdate table (yes, you'd want an index...

Nice breakdown of CTEs. I find them extremely useful for logically building queries and maintainability.

One thing I think is important to remember about CTEs is that they are syntactical simplifications...

A follow-up to my original post:

After some more testing, I was able to confirm the SQL optimizer is smart enough not to evaluate a function with static input parameters more...

Hi Grant,

I'm going to respectfully disagree. I have plenty of experience with programming languages that require trailing semi-colons, but I learned SQL a long time ago and never used semi-colons,...

Angeline,

I sure do wish I had updated this thread after. 🙁

I honestly can not recall if the restart solved the problem. I did manage to find some notes I still...

I had great hopes for this idea of yours, @scottpletcher.

Unfortunately, it doesn't seem to have affected index selection.  I tried increasing the values orders of magnitudes, to no...

• This reply was modified 4 years, 10 months ago by  David Lafayette.

There are a lot of indexes, but an example would be:

CREATE TABLE [dbo].[MyTable] (
[TaskID] INT NOT NULL IDENTITY(1,1) PRIMARY KEY,
[Active] BIT NOT NULL DEFAULT(1), 
[TaskTypeID] INT NOT...

This thread is old, but I'm trying to figure out if something like this is possible.

I have a table that somewhat large (80M rows, 104GB) and has 31 indexes totaling...

@SGT_squeequal, @jonathan-2 AC Roberts, @scottpletcher:

I'm sorry I wasn't clear. I've solved my problem. The solution is to use <> ("not equal to") instead of > ("greater-than")....

Hi Grant. Yes, you are correct about resizing any data type. 
When testing previously, I thought I had successfully resized a DATETIME to SMALLDATETIME and back without dropping indexes. Upon retesting,...

Since I didn't hear back from anyone on this, I did the testing myself.

Backstory

There are a lot of articles on...

I've enabled trace flag 1800 on all replicas now and I'm still receiving this error. I did not restart the SQL service though. I place the trace flag in the...

Good call, I hadn't enabled the trace flag. I've done this on the secondary (with no affect). I'll enable the trace flag on the primary during the next maintenance window...