Viewing 15 posts - 18,406 through 18,420 (of 59,070 total)
stig.benning (2/13/2016)
Hi Jeff, Thanks for the links and your suggestion. And for solving my problem 🙂 Stig
You bet. Thank you very much for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2016 at 12:37 pm
J Livingston SQL (2/13/2016)
Jeff Moden (2/13/2016)
mw112009 (2/12/2016)
What we need is to be able to do via T-SQL and also we need to get the def for all tables (...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2016 at 10:25 am
mw112009 (2/12/2016)
What we need is to be able to do via T-SQL and also we need to get the def for all tables ( Not just picking one at...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2016 at 9:39 am
Darryl Wilson (2/12/2016)
I have huge backup files (18gb) but I am required to retrieve data from a certain date. so I have...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 9:15 pm
If you want to preserve the presence of leading zeros, don't import the data as any form of numeric. Import it as some form of string.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 9:02 pm
Having just been through a bit of a reindexing nightmare, I urge extreme caution. Non-clustered indexes are a bit of a pain in that they usually not in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 8:58 pm
stig.benning (2/12/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 8:34 pm
Hugo Kornelis (2/12/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 8:12 pm
rshukis10 (2/12/2016)
So now I'm trying to work with this:
UPDATE FGMULTI
JOIN
arinvt ar ON
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 8:08 pm
Ed Wagner (2/12/2016)
Lynn Pettis (2/12/2016)
Grumpy DBA (2/12/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 8:02 pm
SQL!$@w$0ME (2/12/2016)
Thanks, Please see the actual plan attached.
It would appear that you have no data in the leading table. The actual execution plan isn't going to indicate much.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 7:57 pm
Ironically and, perhaps shamefully, the really cool thing about 2005 is that you don't have to worry any longer about MS breaking something with a CU or SP. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 7:49 pm
rajemessage 14195 (2/12/2016)
which are overlaping with entered @pointfrom = 2 and @pointTo = 10[/font]
--requirement is "f" can > or = to previous "range's...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 7:14 pm
Phil Parkin (2/12/2016)
mw112009 (2/12/2016)
The answer is "YES" ( I mean I am able to modify the code )
Why do I need the code ?
I have...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 6:23 pm
Jacob Wilkins (2/12/2016)
Luis Cazares (2/12/2016)
Jacob Wilkins (2/12/2016)
SELECT [OrderNumber]=OrderID,
[User]=x.[User]
FROM ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2016 at 6:13 pm
Viewing 15 posts - 18,406 through 18,420 (of 59,070 total)