Viewing 15 posts - 30,916 through 30,930 (of 59,101 total)
okbangas (3/2/2012)
Jeff Moden (3/2/2012)
Now that you've found out what the massive overhead is, can't you just bypass it and build a report of your own?
You mean create a web solution...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2012 at 10:55 am
R.P.Rozema (3/2/2012)
SELECT LEFT(t2.TEXTFIELD...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2012 at 10:50 am
Elliott Whitlow (3/2/2012)
Mutual Admiration Society?CEWII
BWAA-HAAA!!! Well thank you Elliott. You are DA MAN! :-):-D:-P
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2012 at 10:45 am
R.P.Rozema (3/1/2012)
Jeff Moden (3/1/2012)
It sounds like the OP has unknown length data and wants to size the output based soley on the max width of the unknown data.
That's not what...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2012 at 6:44 am
Henrico,
Heh... you've been around long enough... Post some data for folks to use. 😉 See the first link in my signature for how to make it easy for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2012 at 6:38 am
MysteryJimbo (3/2/2012)
It is possible to get a hung spid in this state which will never end. The only way to get rid of it is to restart the service.
That's...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2012 at 6:34 am
Now that you've found out what the massive overhead is, can't you just bypass it and build a report of your own?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2012 at 6:32 am
Remember the "old" ways... one less SORT and no 3 scan worktable behind the scenes. 😉
SELECT ID, Name, SomeDate,
Flag = (ROW_NUMBER()...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2012 at 8:39 pm
For all of the reasons in Jacob's article, I'll copy the definition and use it to create a newly named stored procedure and then drop the old one. Saves...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2012 at 8:14 pm
ColdCoffee (3/1/2012)
I must also ask a question here. What should happen if there are 2 LocationIDs with same number of appearances for a particular OrgID ?
Hey there folks. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2012 at 8:09 pm
agustingarzon (2/29/2012)
Both databases would be on the same SQL Server instance, in case I forgot to mention :unsure:
Then, no need for a linked server. Create a wad of SYNONYMs...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2012 at 8:01 pm
Elliott Whitlow (3/1/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2012 at 7:32 pm
donbuz (3/1/2012)
CTE are of great interest - I suspected that someone answering me...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2012 at 7:27 pm
Red Gate's SQL Compare product would pretty much do it all for you. If data is also involved, the use of Red Gate's Data Compare product would do that....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2012 at 7:08 pm
ram_kamboz2k7 (3/1/2012)
However this is a code that was assigned to me for a specific task...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2012 at 7:06 pm
Viewing 15 posts - 30,916 through 30,930 (of 59,101 total)