Viewing 15 posts - 361 through 375 (of 4,081 total)
If your application can handle getting two result sets, I'd go that way.
You do have a column that can associate the perms with their users?
August 21, 2016 at 12:49 pm
Don't be afraid to read through the input data three times. Reading through a table is very fast compared to the cost of doing individual inserts.
Also, you might...
August 21, 2016 at 12:14 pm
=([TotalStaffedTime] - [IdleTime]) - ([ContactTalkTime]+[PostCallProcessingTime]+[DNOutExtTalkTime]) / [TotalStaffedTime] - [IdleTime]
You're dividing by TotalStaffedTime. Apparently you have cases where TotalStaffedTime = 0. What do you...
August 19, 2016 at 4:34 pm
Jeff Moden (8/18/2016)
I guess it's my turn in the proverbial barrel.
For this, you wear the HAT OF SHAME.
August 18, 2016 at 6:29 pm
Jeff, why are you quoting yourself now?
Guys, I agree that minimizing the logical reads is always a good idea. My point was that the article espoused accepting more...
August 18, 2016 at 11:06 am
George, I read and understand what you are saying, but I have run the queries multiple times with ANSI_NULLs OFF and ANSI_NULLS on.
* Query 1...
August 18, 2016 at 9:47 am
Christian, just in case you're still following this thread. The answer that we all agree on is that the correct index choice depends on the particular usage of...
August 17, 2016 at 3:17 pm
christiandreyer (8/17/2016)
Hello all,1) Should every primary key in a table be a clustered index so that data is organised?
As a general rule, yes. There may be...
August 17, 2016 at 1:45 pm
Stephen Randolph (6/29/2015)
When it comes to views, I never join views to views.
Amen
August 16, 2016 at 1:12 pm
ThomasRushton (8/16/2016)
whereisSQL? (8/16/2016)
Grumpy DBA (8/16/2016)
djj (8/16/2016)
RocketRichard
Canada
Dry
Martini
August 16, 2016 at 9:15 am
Interesting discussion, but I am concerned about the casual dismissal of the number of logical reads. A consequence of more logical reads is that, in a busy system,...
August 16, 2016 at 9:03 am
Thank you for setting the problem up so nicely.
The problem is that something about the REPLACEs below is limiting your result below to NVarchar(4000).
When your outer replace goes over that...
August 15, 2016 at 11:03 pm
Steve Jones - SSC Editor (8/15/2016)
ChrisM@Work (8/15/2016)
Steve Jones - SSC Editor (8/15/2016)
ChrisM@Work (8/15/2016)
August 15, 2016 at 10:03 pm
Ed Wagner (8/15/2016)
whereisSQL? (8/15/2016)
Y.B. (8/15/2016)
Manic Star (8/15/2016)
HappyGeek (8/15/2016)
Luis Cazares (8/15/2016)
whereisSQL? (8/15/2016)
Revenant (8/15/2016)
Ray K (8/15/2016)
Ed Wagner (8/15/2016)
djj (8/15/2016)
Grumpy DBA (8/15/2016)
djj (8/15/2016)
Ed Wagner (8/15/2016)
SweetTreat
Trick
Joke
Puzzle
Jigsaw
Tools
Power
Unlimited
Opportunities
Scam
Spam
Eggs
Ham
Pork
August 15, 2016 at 9:56 pm
Hey Lynn,
A quick example follows. It needs a lot of polish, but I just wanted to illustrate the concept.
Like other SQL splitters, this shouldn't be used for strings...
August 12, 2016 at 2:41 pm
Viewing 15 posts - 361 through 375 (of 4,081 total)