Viewing 15 posts - 1,576 through 1,590 (of 2,436 total)
It makes a difference in how you can recover. If recovery mode is 'simple' than a backup before the truncate is not needed at all, just after the truncation to...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 27, 2005 at 9:18 am
opinions are like a$$holes in a number of ways ... first everyone has one, second some are bigger than than others ... need I say more based on the source of...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 26, 2005 at 10:33 am
We've had a couple of IBM E-Series 445 clusters with RAID and SAN storage. You might want to check the driver levels on your servers. DO NOT USE Windows Update....
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 26, 2005 at 10:21 am
Prior to SQL Server 2005 (v4.21, v6.0, v6.5, v7.0 & SQL2000) there were no imposed limitations on the length and complexity of 'standard' security regarding SQL Server login passwords. However...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 26, 2005 at 10:15 am
If it were my database I'd go through and change the names of all of the offending columns. One never knows when SQL will serve up an 'undocumented feature' (bug)...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 26, 2005 at 9:48 am
No one mentioned anything about 'recovery mode' ...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 26, 2005 at 9:36 am
It sounds like a corrupt file to me ...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 22, 2005 at 10:43 am
Based on 2 points in your initial problem:
"... the snapshot file of 970 MB. it will take 5 to 6 hrs ..."
I'd also look into the network performance and throughput....
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 21, 2005 at 11:42 am
If you did not get an error message within SQL Server then your next step would be to contact your email admin. depending on your email system there are various...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 20, 2005 at 2:10 pm
Could you post the error message ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 20, 2005 at 11:41 am
You may want to take a look at the application that uses the databas. Maybe there are administrative functions within the application (we just found one that did DBREINDEX and...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 20, 2005 at 11:22 am
The 'paranoid' DBA in me now comes to light ... To be on the safe side I always perform a full backup every time I switch recovery modes ... Backup...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 20, 2005 at 10:33 am
Now I see said the blind man ...
My response to STFU is BFD ...
big furry dog ...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 19, 2005 at 12:25 pm
"STFU" ??? Please translate ...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 19, 2005 at 11:14 am
I believe that the answer to this question lies in your own 'perspective'. Have I ever failed on a project - NO. Have I been a part of projects that...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 16, 2005 at 11:33 am
Viewing 15 posts - 1,576 through 1,590 (of 2,436 total)