Viewing 15 posts - 40,951 through 40,965 (of 59,069 total)
That was my favorite, as well, and you highlighted the same words I would have especially in the current thread. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 9:12 pm
Well done, Seth! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 9:05 pm
See the following article...
http://www.sqlservercentral.com/articles/Crosstab/65048/
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 9:01 pm
Nah... too much work to do that way... can't you just ALTER the necessary columns in a table with the new collation? See ALTER TABLE in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 8:54 pm
Since this sounds a whole lot like homework, I'd imagine that you won't get very much help unless you also show what you've tried in code and explain why. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 8:38 pm
Lynn... the click link you posted is broken...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 8:35 pm
There's also several categorized articles in Books Online under "deadlocks [SQL Server]".
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 8:32 pm
Heh... just a "forum, survival tip"... I wouldn't make any such performance claims unless I had code to back it up. I've been burned without the code.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 8:30 pm
You'll need some reference as to when the job last ran in the data somewhere. If you can't add a "ProcessedOn" column to the actual tables, create a new...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 8:26 pm
Apologies for the delay... I was drawn aside by other duties. Here's the code... details are in the comments. You'll be totally amazed at how fast this "Quirky Update"...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 8:20 pm
mahesh.vsp (11/25/2009)
select a.slno,a.c1,a.c2,a.flag,
(select count(case when b.slno = 1 and b.c1-b.c2 = 0 then null -- for the first record if c1-c2 = 0
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 3:42 pm
dba_pkashyap (11/25/2009)
Use COALESCE to get rid of null values.
Why? Is it because you believe in the myth of portability? Unless I have more than 1 operand to check...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 3:15 pm
Keep it simple...
WHERE Time_Date between ISNULL(@startdate,0) and @enddate
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 3:10 pm
The amount of freespace in the table is pretty much consistent with the fact that the clustered index has a FILL FACTOR of 80. The only way to make...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 3:08 pm
dba_pkashyap (11/25/2009)
How about DDL triggers at database level!!!
I'm liking that but can't you just set the users up with "data reader" only?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2009 at 3:00 pm
Viewing 15 posts - 40,951 through 40,965 (of 59,069 total)