Viewing 15 posts - 34,456 through 34,470 (of 59,099 total)
jeedee (3/28/2011)
You should use table variables instead of temporary...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 4:53 pm
Tim-24860 (3/28/2011)
I'd like the output to be like this.
Name | Oct 2010 | Nov 2010 | Dec 2010 | 2010 Total | Jan 2011 | Feb 2011 |...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 2:36 pm
In fact, I'll state that I normally avoid Table Variables because they don't persist during troubleshooting and they don't act like Temp Tables would. Here's an example I recently...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 2:34 pm
jeedee (3/28/2011)
Almost all the books I have read about SQL Server state that it's better to use table variables than...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 2:28 pm
Either way, I still think it's a really bad idea to have such sequences write directly into the table.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 2:20 pm
srdjan.katic (3/28/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 2:16 pm
DMS11X (3/28/2011)
USE [msdb]
GO
/****** Object: Job [CYCLE NUMBER] Script Date: 03/28/2011 08:01:05 ******/
BEGIN TRANSACTION
DECLARE @ReturnCode INT
SELECT @ReturnCode = 0
/****** Object: JobCategory [[Uncategorized...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 10:46 am
DMS11X (3/28/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 8:31 am
David Benoit (3/28/2011)
srdjan.katic (3/28/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 8:24 am
chetanr.jain (3/28/2011)
@jeff,SAN replication always has edge over Log shipping if cost is not a factor.
I hope my statement is correct.
You're correct. I was just making sure that people know...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 8:20 am
Gianluca Sartori (3/28/2011)
Jeff Moden (3/28/2011)
Gianluca Sartori (3/28/2011)
GilaMonster (3/28/2011)
Not trying to start any bashing or pile-ons, but this has to rate high on the list of most useless replies: http://www.sqlservercentral.com/Forums/FindPost1084783.aspx
Sounds like...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 8:01 am
GilaMonster (3/27/2011)
Jeff Moden (3/27/2011)
GilaMonster (3/27/2011)
Jeff Moden (3/27/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 7:42 am
Craig Farrell (3/28/2011)
GSquared (3/28/2011)
Stefan Krzywicki (3/26/2011)
Jeff Moden (3/26/2011)
Gianluca Sartori (3/25/2011)
GilaMonster (3/25/2011)
Koen Verbeeck (3/25/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 7:27 am
Gianluca Sartori (3/28/2011)
GilaMonster (3/28/2011)
Not trying to start any bashing or pile-ons, but this has to rate high on the list of most useless replies: http://www.sqlservercentral.com/Forums/FindPost1084783.aspx
Sounds like "OK, just do it"....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 7:23 am
DMS11X (3/28/2011)
I need to reset a sequence number every 0000hrs daily...I have searched and searched and tested different ways, and have found no viable solution.
Anyone know how to do this?
There...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2011 at 7:18 am
Viewing 15 posts - 34,456 through 34,470 (of 59,099 total)