Viewing 15 posts - 34,831 through 34,845 (of 59,099 total)
drew.allen (3/2/2011)
SELECT *
FROM TableA
INNER JOIN TableB
ON TableA.ID LIKE Cast(TableB.ID as varchar(11)) + '%'
This assumes that...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2011 at 12:14 pm
Can't you just add OPTION(RECOMPILE) to the end of the query?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2011 at 12:11 pm
Michael T2 (2/17/2011)
is i run the the 2 cte queries alone they are fast, less then a second...
I went to the doctor, held my arm over my head in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2011 at 11:47 am
gupta.sreekanth (3/2/2011)
thanks a ton......................
You bet... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2011 at 10:33 am
Koen Verbeeck (3/2/2011)
That is a very interesting method. (I had never heard of the PARSENAME function before).Another one for my knowledge base 🙂
grahamc (3/2/2011)
Just having a play with...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2011 at 10:31 am
If the expected format of the source data is always the same, this is a simple way to do it...
DECLARE @SplitString VARCHAR(100)
SELECT @SplitString = 'bas-06-12586'
SELECT Col1 = PARSENAME(REPLACE(@SplitString,'-','.'),3),
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2011 at 6:59 am
NewBeeSQL (3/2/2011)
Mark-101232 .. You rock...I was struggling with pivot..and you gave a solution by not using PIVOT..Thanks a lot mark....
As a suggestion, take the time to read the article about...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2011 at 6:49 am
Lookup sp_spaceused in Books Online. I "leverage" code from it frequently.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2011 at 6:45 am
pharmboy4u (3/2/2011)
I hope to someday get a good...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2011 at 6:06 am
So did that help at all? Heh... "Enquiring minds want to know." 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2011 at 10:41 pm
coder_t2 (2/22/2011)
At times, my server is hitting memory and I/O bottlenecks, and I was thinking about managing the database to fit entirely in memory to overcome those bottlenecks.
That usually turns...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2011 at 7:34 am
Three hints...
CTE
ROW_NUMBER() OVER (PARITION BY ________ ORDER BY ________)
OUTER JOIN
Look those up in Books Online (the "Help" system that comes with SQL Server)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2011 at 7:28 am
Saravanan M (3/1/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2011 at 6:56 am
Heh... thanks for the feedback, Koen. I may just have to teach myself C# so I can write a conditional splitter that would make it all a whole lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2011 at 6:50 am
Understood and thanks for the feedback.
Does the original DB have a PK or unique index on the data? If so, you could always target that column or columns as...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2011 at 6:41 am
Viewing 15 posts - 34,831 through 34,845 (of 59,099 total)