Viewing 15 posts - 44,671 through 44,685 (of 59,101 total)
tvanharp (3/10/2009)
It would be nice if I could make better use of the error handling, logging, and auditing that we've already buillt into SSIS...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 9:27 pm
LoveSQL (3/10/2009)
Well the back end is SQL 2000 not SQL 2005thanks!
Heh... understood. And I agree with Micheal, it would have been better if you posted your question in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 9:20 pm
Giovanni (3/10/2009)
We have a table named SYS_BusinessObjects wich contains some information that is common to all tables in db and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 9:15 pm
Ya gotta trust me on this... perfectly up to date stats and indexes just aren't gonna help this one. Try the pre-aggregation I spoke of... you'll be amazed.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 8:47 pm
Mike Levan (3/10/2009)
please see the query attached.thanks
Heh... if you want more people to look at it, post it in a format more people have. I sure haven't spent the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 8:42 pm
adams.squared (3/10/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 8:40 pm
Heh... ya just gotta know what the next question on this will be... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 8:28 pm
LoveSQL (3/10/2009)
Can some one help me writing the following query?
Update the Seq numbers in the table below. Seq numbers must be ordered by their CreateDate and reset for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 8:24 pm
asita (3/10/2009)
Hello GSquared,i applied SUBSTRING([DateString], 1, 6) + SUBSTRING([DateString], 9, 2) it is working fine, given by Todd
thank you for your valuable response
Best regards
bujji.
That also means that you've learned...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 8:20 pm
But, again, and as Flo suggested... SQL Server is NOT the place to do such formatting unless it's for direct output to a file sans any trip through a GUI...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 8:15 pm
scorpio_zz19 (3/10/2009)
i searched how to split the date from datetime data type and i came up with this code(below), the problem is that i dont know where to put it.
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 7:52 pm
I just got done doing one like this a coupe of weeks ago. The problem is the aggregation... you're trying to aggregate in the presence of way too many...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 7:48 pm
As Flo implied, variable length columns in SQL Server 2005 are handled quite a bit differently than they were in SQL Server 2000. For example, the following would cause...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 7:32 pm
Chris Morris (3/10/2009)
Wayne (3/9/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 4:25 pm
GSquared (3/10/2009)
Jeff Moden (3/10/2009)
I'll have to look for it, but...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2009 at 2:02 pm
Viewing 15 posts - 44,671 through 44,685 (of 59,101 total)