Viewing 15 posts - 52,396 through 52,410 (of 59,091 total)
Thanks for the feedback guys...
Ryan and Mike C... thanks for the performance comparisons. That's good stuff. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 8:19 pm
Heh... sorry about that, Matt. Thanks for the help...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 7:19 pm
Understood... but this doesn't even have anything to do with indexing... changing a constant to a variable causes a massively detrimental change in the execution plan. This is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 3:25 pm
Well, good! At least it's not just me! 😀 Thanks for the help, Matt and Michael.
I also ran into this the other night on something totally different...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 1:29 pm
Oh yeah... and, of course, it works just fine. But, any idea on how to make it work without being dynamic though? Seems the optimizer is making a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 12:36 pm
Edward (2/22/2008)
have a look at thishttp://ryanfarley.com/blog/archive/2004/03/01/390.aspx
Hope it helps
Pretty good explanation of SET vs SELECT... horrible method of creating a split function. Use a Tally table, instead.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 6:36 am
1. I just have modified my select statement a bit like iam just taking all now
means...
bcp "Select * from CurveTempDB.dbo.tLoanVectors where cusip='86359B6G1' " queryout C:\Sample.txt -T -c
for which am still...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 6:31 am
VALEK (2/21/2008)
It would be great if...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 5:44 am
Muhammad Furqan (2/21/2008)
i know about that simple query that you hace written, but problem with me is that the "table_name" and "column_name" are...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 5:40 am
Ok... first, we have to determine precisely what the problem is... correct identification of the problem will be 90% of the solution....
1. Are you still using this exact syntax?...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2008 at 5:35 am
It was easy for us... we had a great junk yard dog for a DBA who said "Sure... I can keep anything out that doesn't have a signed off ticket"....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2008 at 8:49 pm
I'd recommend that you post the code that doesn't work along with any error messages you may receive...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2008 at 7:56 pm
One more thing... the ticketing system should have the concept of "Parent Tickets" and "Projects" associated with it. Seriously, this is the only way to keep a handle on...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2008 at 7:12 pm
Eric Peterson (2/21/2008)
We need to better document user requests comming into the system and a good...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2008 at 7:10 pm
Gosh... can't you just make a linked server and write a proc that would maybe use a little dynamic SQL to just copy everything it sees on the linked server...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2008 at 7:02 pm
Viewing 15 posts - 52,396 through 52,410 (of 59,091 total)