Viewing 15 posts - 8,446 through 8,460 (of 9,725 total)
Bob Hovious (3/9/2009)
I have colleagues who use GROUP BY clauses without aggregation in place of a SELECT DISTINCT. The results appear to be the same. I've always used a DISTINCT...
March 9, 2009 at 8:25 am
sotn (3/9/2009)
March 9, 2009 at 8:22 am
I'd agree with the temp mapping table approach because a CASE statement can inadvertantly overwrite an "earlier" conversion if you're not careful. Also, you can use the IN for the...
March 9, 2009 at 8:12 am
One thing not previously mentioned, which happens in our environment all the time. If you have procs constantly added to the database which the client needs to use and this...
March 9, 2009 at 8:07 am
Have you tried the following yet?
Select * from tbldeals
where trade_date = '03/06/2009';
Depending on your database collation, this might make all the difference.
March 9, 2009 at 7:59 am
Nelson,
Do you understand the difference between GROUP BY & ORDER BY? GROUP BY is like taking a bowl of fruit and putting the grapes with the grapes and the apples...
March 9, 2009 at 7:54 am
Did any of the other information help?
March 9, 2009 at 7:33 am
Have you looked at DDL triggers yet? They can help you log the information to the table. Then all you have to do is schedule a job that checks for...
March 9, 2009 at 6:54 am
A little more detail on what you're trying to accomplish would help us help you better. @=)
March 9, 2009 at 6:52 am
From what I understand, SQL 2008 has more Administrator tools than 2005, but most of the developer tools have remained the same. Therefore, it would behoove your company to upgrade...
March 9, 2009 at 6:51 am
The biggest issue will be performance. SSIS is a memory hog and each instance of the package (if it even allows you to kick off the package multiple times at...
March 9, 2009 at 6:42 am
Just add a flat file connection manager for each different file. Then, in your data flow, use them as multiple sources, join them with a UNION (works faster than a...
March 9, 2009 at 6:39 am
Timestamp is a really poor data type to use for any sort of date comparison. It isn't really a date, but an incrementing number that mimics an approximate date/time. It...
March 9, 2009 at 6:36 am
I had a similar problem a few times in the past when I was on SP1 for SQL 2005. I had to write out a T-SQL Statement instead of using...
March 9, 2009 at 6:32 am
Viewing 15 posts - 8,446 through 8,460 (of 9,725 total)