Viewing 15 posts - 52,126 through 52,140 (of 59,091 total)
Ralph Curry (3/5/2008)
select
Widget,
DateValue
from (
select
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:51 am
Heh... at least you tried. Thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:49 am
The end of file marker is typically an ASCII 26 and SQL Server will not read it in. You don't have to prevent it from happening.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:46 am
I could be wrong, but this sounds like a "running total" problem with an additional SELECT to find the 2 million mark... please see the following...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:33 am
There's usually some merit and some future need for knowing the times. I think it's a huge loss of data to update datetimes that have the time to all...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:20 am
Can't help on the Reporting Services thing...
... But that's a cool avatar ...
... and my favorite NRA "saying" is "When they outlaw guns, only outlaws will have them."
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:16 am
Still, going the negative number route will likely only buy an addition year of time according to what was forecast by the OP. (18 months total... 6 months for +,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:12 am
Heh... even worse... all we really need now is for Joe Celko to jump in with his ISO standard mantra... 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:06 am
Ok... it's a fun exercise, but I've gotta know... why did you folks decide to do one in SQL? I mean, what do you actually use it for? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:04 am
I've seen all 3... but I think it's a mistake to do anything other than #1 and that's what we do at work. DBA does a backup just before...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 10:55 am
GregoryAJackson (3/5/2008)
Rishi,You're very welcome.
I never imagined this trivial little article would have generated so much interest and such a vigorous discussion thread.
I'm very glad that SQLServerCentral published the article now.
cheers,
Apprently,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 10:47 am
And thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 10:31 am
Heh... yeah... I know a really good one 😉
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 10:24 am
You bet, Rishi... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 10:21 am
That's pretty much true, Matt... I'm amazed at what people think a DBA is supposed to do... no wonder it's so hard to find that type of job in Michigan...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 10:07 am
Viewing 15 posts - 52,126 through 52,140 (of 59,091 total)