Viewing 15 posts - 361 through 375 (of 476 total)
agerard (9/16/2015)
When the column is bigger, the index is bigger.
Yeah, but the data (in the key columns for the index) isn't any bigger so surely "no change" in that regard?
Longshot:
Memory...
September 16, 2015 at 8:05 pm
useful discussion Sean, thanks for your time 🙂
September 16, 2015 at 7:50 pm
Luis Cazares (9/16/2015)
There's a small CPU saving, but not tangible.
Thanks, as I assumed. I was pleasantly surprised how the plan turned out 🙂
I'm now going to have to spend...
September 16, 2015 at 6:59 pm
Sean Lange (9/16/2015)
Change the table and the CRUD stored procs
Probably not of any relevance to the discussion, but our CRUD are mechanically generated, so the chance of me missing a...
September 16, 2015 at 12:33 pm
P.S. On the day that that one ACTUALLY comes up I will be ROYALLY pissed off!!
September 16, 2015 at 12:28 pm
Sean Lange (9/16/2015)
But surely you aren't joining on these string values right???
Correct. Main thing I would be expecting to find would be an @MyColumn parameter to an SProc, or a...
September 16, 2015 at 12:27 pm
UNIQUE INDEX on the three columns
(UNIQUE CONSTRAINT comes to the same thing, I think??, in SQL Server)
September 16, 2015 at 12:13 pm
Sean Lange (9/16/2015)
This is where consistently using aliases has some advantages. Maybe Staff is st and Supplier is su. ... What I really don't like about prefixes is it adds...
September 16, 2015 at 12:07 pm
ScottPletcher (9/16/2015)
If you're trying to return a result set, not sure if that will work the same or not.
We do both ways and I can't say I've ever known a...
September 16, 2015 at 12:05 pm
Sean Lange (9/16/2015)
c.FirstName is obviously the Customer table but s.FirstName indicates the Staff table.
For me, that's where it starts to fall down. I don't know if S is Staff...
September 16, 2015 at 10:11 am
Luis Cazares (9/16/2015)
Here's a small test to prove it.
Interesting, thanks. I tried it without the CAST and got a query plan that looks like less work - its still using...
September 16, 2015 at 9:38 am
Sean Lange (9/16/2015)
ClientID is a great name. It can be named ClientID in every table and you shouldn't end up with a name collision.
I'm never sure where that approach starts-and-ends....
September 16, 2015 at 8:57 am
I think it is often easier to adjust the formula if it is in a view. For example if the calculation method for Quantity-on-Hand, taking into account "reserved stock", has...
September 16, 2015 at 8:21 am
andrew.mills 44498 (9/16/2015)
September 16, 2015 at 8:15 am
Sean Lange (9/16/2015)
Kristen-173977 (9/16/2015)
Did I do a better job of conveying what I meant this time?
Yup, got it! Totally missed it the first time around though, sorry.
So ID should...
September 16, 2015 at 8:03 am
Viewing 15 posts - 361 through 375 (of 476 total)