Viewing 15 posts - 28,081 through 28,095 (of 59,101 total)
Steve Jones - SSC Editor (11/24/2012)
... and Jeff's attempt to get the thread into a serious discussion :w00t:
Heh... yeah. Totally misplaced attempt. Wrong place. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2012 at 7:41 am
FusionIO has listed 2 million hours and 6 years write endurance for their cards, ...
Perhaps I'm reading something wrong but 6 years is only about 52,596 hours. 2 Million...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2012 at 7:27 am
Michael Valentine Jones (11/24/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2012 at 7:20 am
opc.three (11/24/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2012 at 7:04 am
Vedran Kesegic (11/24/2012)
It has much better performance than a procedure, but if you must use a procedure you can use the same expression used in a vew.
You know, of course,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2012 at 6:51 am
SpringTownDBA (11/24/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2012 at 4:51 pm
Wouldn't it just be easier and safer to set the FILL FACTOR appropriately and make sure that reindexing was occuring on a regular basis? That would't require any code...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2012 at 4:32 pm
Sqlsavy (11/23/2012)
We use Litespeed to backup our databases. One particular database grows 330MB/day there is enough space on the data and log drives but I think backup drive will...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2012 at 4:25 pm
This is a duplicate post. Please, no answers here. Instead, please see http://www.sqlservercentral.com/Forums/Topic1388300-391-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2012 at 4:17 pm
sanjay.dakolia (11/24/2012)
i want to write a stored procedure tat will take email as a input from...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2012 at 3:08 pm
jameslester78 (11/24/2012)
GO
USE example
GO
Create table tbl_a (email varchar (20),membershipexpiry date)
insert into tbl_a VALUES
('a@a.com','01-Jan-2012'),('b@a.com','01-Jan-2013')
GO
Create proc proc_a
@email varchar(20)
as
declare @v-2 date =
(select membershipexpiry from tbl_a where email = @email)
if @v-2<GETDATE() select 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2012 at 2:58 pm
sanjay.dakolia (11/24/2012)
i want to write a stored procedure tat will take email as a input from...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2012 at 2:47 pm
Even easier... use MERGE and migrate everything from the old table to the new table so you do't have to do this check for future inserts, etc.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2012 at 2:37 pm
We store the SSIS stuff on the SSIS box and the entire box gets replicated to the DR site through SAN replication. Makes life real easy and the DR...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2012 at 2:35 pm
opc.three (11/24/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2012 at 2:30 pm
Viewing 15 posts - 28,081 through 28,095 (of 59,101 total)