Just for good measure, I'll include the view creation statement:

create view dbo.iv_SystemTransactionCardFund

with schemabinding

as

select

SystemTransactionID = st.ID,

c.CardNumber,

...

I've checked the stats and they all seemed to be up to date (we have auto create and update stats on) But just to be sure, I forced an...

Here's the estimated execution plan for the view (sans index of course...)

It kind of reminds me of several systems I've looked at that try to protect their "IP" by naming tables and columns like tbl1.col12 and not using any declarative integrity....

Over the years I have evaluated many software systems for purchase and I have yet to recommend one that used encrypted procs. I assume that if they encrypt their...

Encrypting stored procedures is almost as annoying as it is pointless.

steve dassin (4/3/2009)

Now that's funny! 🙂 The sql community has ignored someone whose spent a lifetime trying to explain why there's nothing...

Chris Date's incoherency principle is in full force...

If you like cursors so much, why not use ORACLE instead, it works well with cursors. MS SQL Server was developed to work well using sets, and it works...

I can't be the only one who's seen this problem can I?

I'm sure this is more work than you want, but you could create staging tables for those tables (hopefully not the majority of them) and load into the staging tables...

Not to my knowledge...

Just curious why you can't do the explicit conversion using SQL? There may be another way to skin this cat...

Use the round function to explicitly control this behavior.

declare @Num decimal(6,3)

set @Num = 3.289

select round(@Num, 2, 1)

Nice article Andy, I never really understood what the data viewers were. I sure wish I'd had this information a year ago...

This is just one reason why change control is SO important. If you have a method of testing and documenting all changes made in your enviornment then it becomes...