Viewing 15 posts - 30,241 through 30,255 (of 59,101 total)
dwain.c (4/30/2012)
The trick is to find something that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2012 at 5:59 am
Even the Latitude calculations can get a bit screwy on things like trans-Pacific flights because the actual flight path will usually follow the "Great Circle Path" which is hardly ever...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2012 at 5:48 am
capn.hector (4/27/2012)
;WITH e1(n) AS...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2012 at 5:39 am
GSquared (4/13/2012)
You could modify my version to use a table...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 6:06 pm
Teach the user how to use LIKE. It's easier.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 5:49 pm
Is the description all that important if it's not FKd? Probably not. So just do a MAX() on the description and call it a day. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 5:43 pm
andersg98 (4/20/2012)
This is a job for SSIS.
Oh, horse muffins! 😛 BULK INSERT with a format file makes this a simple T-SQL task.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 5:17 pm
jitendra.padhiyar (4/26/2012)
Okay, so evenuse msdb
SELECT backup_size/compressed_backup_size FROM backupset
Or
use msdb
SELECT backup_size/compressed_backup_size FROM dbo.backupset
are same as
use msdb
SELECT backup_size/compressed_backup_size FROM msdb..backupset
Am I correct ?
Yes... unless you log is as "Homer"...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 5:04 pm
People spend way to much time doing conversions that SQL Server will do on it's own. The following works just fine and will also work with a character based...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 5:01 pm
Thinky Night (4/27/2012)
declare @Table table (Doc_Nbr int,Ticket_Nbr int)
insert into @Table values
(12,907),
(12,908),
(12,909),
(12,913),
(12,915),
(14,1481),
(14,1484),
(14,1485),
(14,1486),
(14,1487),
(14,1489),
(14,1490);
WITH cteSequence ( number) as
(
SELECT 800
...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 4:54 pm
Oddly enough, I'll second that recommendation. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 4:51 pm
markpc2009 (4/27/2012)
Area|Date|Employee|Qty where Area|date|employee are the key
On "Sunday" someone will complete these for Monday. The probability is that the key fields will remain constant for the next...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 4:47 pm
dwain.c (4/26/2012)
CREATE TABLE #t (strings VARCHAR(100));
-- Count the unique...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 4:42 pm
ChrisM@Work (7/26/2011)
pdanes2 (7/26/2011)
ChrisM@Work (7/26/2011)
That's slick, and definitely going in my toolbox. I never would have guessed that could be done with set-based code.
Thanks! Must admit though, it's borrowed from the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 4:38 pm
Elliott Whitlow (4/26/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2012 at 4:29 pm
Viewing 15 posts - 30,241 through 30,255 (of 59,101 total)