Viewing 15 posts - 42,526 through 42,540 (of 59,102 total)
Instead of using the [font="Arial Black"]-o filename [/font]option of OSQL, use [font="Arial Black"]>> filename [/font]instead
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2009 at 12:20 am
Swamy Magam (8/5/2009)
I have table like
tEmp
Empno EmpName Deptno
101 xyz ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2009 at 12:16 am
karthikeyan (8/5/2009)
My requirement is different.
Not according to what you posted. Capture the output in a temp table and apply a Tally table to get the dates.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2009 at 12:08 am
It's called a "Cross Tab"...
SELECT Product,
VersionNumber,
COUNT(*) AS Total,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2009 at 12:04 am
Estimated rows are just that... estimated. From what I've seen, they're rarely correct and there's not much you can do about it if your stats are actually up to...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 11:44 pm
Gianluca Sartori (8/5/2009)
1) You could send a mail to all users from a trigger.
2) Insert the rows into a message table from a trigger and...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 11:35 pm
AND you posted this on both the 2k and 2k5 forum! You know better than to double post! All it does is tick people off. Stop it....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 11:29 pm
Duplicate post... no responses here please. Goto http://www.sqlservercentral.com/Forums/Topic765935-8-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 11:26 pm
Duplicate post... no responses here please. Goto http://www.sqlservercentral.com/Forums/Topic765935-8-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 11:24 pm
Duplicate post... no responses here please. Goto http://www.sqlservercentral.com/Forums/Topic765935-8-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 11:21 pm
Gianluca Sartori (8/5/2009)
select
nameofmarket as "market",
sum(sales) as...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 11:05 pm
He's mine, please... all mine... pork chops in progress. I don't want to start a dog pile on him, but he's mine.
http://www.sqlservercentral.com/Forums/Topic765935-8-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 11:01 pm
AND you've been around long enough to know how to post data to get help. If not, please reread the article at the first link in my signature below....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 10:50 pm
...and the checksum algorithm is nothing more than a simple "Exclusive OR" at the byte level. It does NOT quarantee that two rows are different and it doesn't guarantee...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 10:46 pm
Heh... get busy Karthik... you know how to use a Tally table with an outer join. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2009 at 10:39 pm
Viewing 15 posts - 42,526 through 42,540 (of 59,102 total)