Viewing 15 posts - 42,436 through 42,450 (of 59,067 total)
jrw39,
Since you're a newbie, I have to ask... Do you know what "Books Online" is? It's the "help" system that comes with SQL Server. It's one of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 6:26 pm
jrw39 (8/7/2009)
I have one additional question on the joins
this query is similar to the last I used your example but I'm still getting an error
before
UPDATE [tblShipments] LEFT OUTER ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 6:01 pm
Adam Gojdas (8/7/2009)
Closer to being perfect is the LUN 10 checksum (sanity check on credit card numbers)... but even that can have a failure.
Just in case anyone else is interested...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 5:53 pm
p.s. Pork chops to the "designer" of the table that put you in this pickle to begin with. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 5:50 pm
saivko (8/7/2009)
The description above explains what I'm thinking:
000021 + 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 5:49 pm
tjm (8/7/2009)
Jeff,Just wanted to thank you again. That procedure has really come in handy in multiple scenarios.
-tjm
That's absolutlely awesome. Thanks for the feedback! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 1:09 pm
Michael Valentine Jones (7/22/2009)
declare @files table (cmdout nvarchar(100) )
insert into @files ( cmdout )
-- Get filenames excluding directories
exec master.dbo.xp_cmdshell 'dir C:\ /b /a:-d'
select cmdout from...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 1:08 pm
VERY well done on the setup but that brings up another question... why do you need help? I've not run the code but it appears that you've already solved...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 9:05 am
Mohan Kumar (8/7/2009)
UseSELECT CONVERT(VARCHAR,GETDATE(),109) or
SELECT CONVERT(VARCHAR,GETDATE(),100) or
SELECT CONVERT(VARCHAR,GETDATE(),9)
None of those produce what was asked for.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 8:42 am
Jeff Moden (8/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 8:41 am
No! The recursive CTE method is the wrong method for this! Do you have the link back to the original problem? Recursive CTE's are just too damned...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 8:39 am
Ok... I need a pry bar or at least a sturdy sword to get the tennis shoe out of my mouth. It was a different guy and not the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 6:44 am
Ah... my very bad then... you are a different Karthik than the one I'm used to working with. Someone showed me that there are two people with the same...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 6:42 am
Heh... but I know how this works... 99% of the time, if you don't get your answer up front, the OP becomes a check valve as soon as he gets...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2009 at 6:37 am
Darned sorry about that, Goldie. I answered too quickly.
You would think that Microsoft would allow you to return data from the "from_table_name" on an insert like they do on...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2009 at 9:52 pm
Viewing 15 posts - 42,436 through 42,450 (of 59,067 total)