Viewing 15 posts - 3,046 through 3,060 (of 10,144 total)
gstarsaini (8/7/2014)
Thanks for the reply.This means there is no effect on the queries?
Each reply posted to your question implies "maybe", "probably" or "definitely". The average of these isn't "definitely not"!
August 7, 2014 at 8:47 am
pwalter83 (8/7/2014)
ChrisM@Work (8/7/2014)
SELECT *
INTO #Offices
FROM (VALUES
('KBE ANR','BELGIUM'),('KBE ZEE','BELGIUM'),('KEU ANR','BELGIUM'),
('KDE VIE','AUSTRIA'),
('KDE BRE','GERMANY'),('KDE BRV','GERMANY'),('KDE DUS','GERMANY'),('KDE FRA','GERMANY'),('KDE HAM','GERMANY'),('KDE MUC','GERMANY'),('KDE STR','GERMANY'),
('KFR BOD','FRANCE'),('KFR DKK','FRANCE'),('KFR FOS','FRANCE'),('KFR LEH','FRANCE'),('KFR...
August 7, 2014 at 8:15 am
Shadab Shah (8/7/2014)
ChrisM@Work (8/7/2014)
August 7, 2014 at 8:13 am
This should get you started with Jeff's suggestion:
SELECT *
INTO #Offices
FROM (VALUES
('KBE ANR','BELGIUM'),('KBE ZEE','BELGIUM'),('KEU ANR','BELGIUM'),
('KDE VIE','AUSTRIA'),
('KDE BRE','GERMANY'),('KDE BRV','GERMANY'),('KDE DUS','GERMANY'),('KDE FRA','GERMANY'),('KDE HAM','GERMANY'),('KDE MUC','GERMANY'),('KDE STR','GERMANY'),
('KFR BOD','FRANCE'),('KFR DKK','FRANCE'),('KFR FOS','FRANCE'),('KFR LEH','FRANCE'),('KFR LIO','FRANCE'),('KFR MRS','FRANCE'),
('KFR...
August 7, 2014 at 6:21 am
If you set up your sample data as CREATE TABLE ... followed by INSERT to populate it, I'm sure your problem will be solved in minutes.
August 7, 2014 at 4:40 am
Should be easy enough - but as Lutz pointed out, which column will you use for the sequence? Without one, there's no concept of "earlier" or "later". Did you miss...
August 7, 2014 at 1:41 am
A good friend of mine lived with colitis for 20 years and endured enough colonoscopies to feel like an inside-out Kate Moss, along with an assortment of drugs - many...
August 6, 2014 at 9:57 am
You can read about per-row and per-index updates in this article by Paul White.
I'll take a wild-ish guess and suggest that if you refresh statistics on tblPersonOtherAttribute, the plans for...
August 6, 2014 at 7:56 am
;WITH SequencedData AS (SELECT Seq = ROW_NUMBER() OVER(ORDER BY (SELECT NULL)), * FROM #TEMP)
SELECT t.PlayerName, t.DismissFormat, x.StrickRate
FROM SequencedData t
OUTER APPLY (
SELECT TOP 1 StrickRate
FROM SequencedData ti
WHERE ti.PlayerName...
August 6, 2014 at 5:55 am
Kwisatz78 (8/6/2014)
August 6, 2014 at 3:57 am
With so much repetition of columns in the output, isn't index refactoring a little "cart before the horse"? I'd recommend you eliminate duplicated data from the output before considering indexing....
August 6, 2014 at 2:18 am
-- The plan doesn't seem to work at all well with the actual rowcounts, probably due to out-of-date stats as others have suggested.
-- You can probably eliminate the 500million row...
August 4, 2014 at 9:09 am
MMartin1 (8/1/2014)
.
.
.
Its quite clear that a csv column is not only not normalised, but given the leading % in the search condition (doing a LIKE '%someTerm%' search) will create a...
August 4, 2014 at 1:55 am
ScottPletcher (8/1/2014)
Try code below instead.
--temporarily add "TOP (100)" to the query for testing purposes
SET @tsql = STUFF(@tsql, CHARINDEX('SELECT', @tsql) + 6, 0, '...
August 4, 2014 at 1:50 am
Use the one which is working.
If this answer is insufficient, please make your question more clear. What are you trying to do? What are you trying to ask?
August 1, 2014 at 8:59 am
Viewing 15 posts - 3,046 through 3,060 (of 10,144 total)