Viewing 15 posts - 41,206 through 41,220 (of 59,069 total)
Phil Parkin (11/8/2009)
Nice solution Jeff.
Thanks, Phil. A lot of folks have asked why I haven't taken the time to learn SSIS. It's because of things like this...:-)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 8, 2009 at 4:49 pm
UnionAll (11/8/2009)
Jeff Moden (11/7/2009)
Jeff Moden (11/7/2009)
Let me ask this... does it have to be done in SSIS?
Yes, because my situation is more complex than what i have showed...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 8, 2009 at 4:47 pm
As a bit of a side bar... if you're using the 32 bit version of SQL Server 2005, doing such a thing as importing a file with an unknown number...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 10:40 pm
Jeff Moden (11/7/2009)
Let me ask this... does it have to be done in SSIS? The reason I ask is because this is a trivial task in T-SQL.
Heh... see what...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 10:14 pm
Let me ask this... does it have to be done in SSIS? The reason I ask is because this is a trivial task in T-SQL.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 9:39 pm
I agree... some readily consumable sample data and a CREATE TABLE statement would be nice.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 9:01 pm
rshm35 (11/6/2009)
Hi,I have a view which selects the data with 12 joins in it...
can you give me suggestions how can i optimize this view....
Thanks
Yes...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 8:55 pm
Thanks, Paul.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 8:54 pm
Ken McKelvey (11/6/2009)
designing applications and databases is an art which requires experience
Heh... would someone please tell that to the folks that I've worked for? 😀 The term "GUI...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 8:32 pm
Double post... no discussion here, please. Keep it all together at the following URL... thanks.
http://www.sqlservercentral.com/Forums/Topic815495-338-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 8:30 pm
See the following articles and keep in mind that the MAX of a single row will always be the value of that row.;-)
http://www.sqlservercentral.com/articles/T-SQL/63681/
http://www.sqlservercentral.com/articles/Crosstab/65048/
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 8:25 pm
Heh... I can't speak of Linq because I've not had to clean up any messes from it, yet, but Hibernate and NHibernate are both 4 letter words to me. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 8:20 pm
Before you trot off, answer a question for me, please. Why did you need to format data in this manner?
I also noticed that you didn't get your dynamic date...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 7:54 pm
I agree... it's a very bad Litmus test. It's more like a ring-knockers club and it shows a very narrow mind.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 7:47 pm
David Portas (11/7/2009)
In either SQL or Oracle you can use COALESCE, which is the Standard SQL function instead of ISNULL and NVL which are non-standard.
Why do you think that's so...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2009 at 7:22 pm
Viewing 15 posts - 41,206 through 41,220 (of 59,069 total)