Viewing 15 posts - 226 through 240 (of 474 total)
I agree, depending on the circumstances I think one could make an argument that Database Mirroring and Log Shipping both require little administrative effort once they are set up. ...
March 9, 2009 at 7:48 am
Just a batch file with the following line before we do the file copies:
net use
I'm sure it's not the most secure thing in the world, but it will...
March 3, 2009 at 1:46 pm
We ended up deciding to just do this outside of SQL.
March 3, 2009 at 1:06 pm
Finally figured it out. There was a database trigger involved that was causing it.
March 3, 2009 at 10:12 am
I've got a SQL server box outside our domain, and I need to be able to use xp_cmdshell on it to access a filesystem that is on our domain.
Anyone...
March 3, 2009 at 10:11 am
You shrink a mirrored databases's log file just like any other. Mirroring has no effect on your log file backups/truncating.
February 12, 2009 at 8:23 pm
You don't need to kill your mirroring session to truncate your transaction log file.
February 11, 2009 at 2:07 pm
Glad you got it working. Just keep in mind two things about mirroring from a 2005 principal to a 2008 mirror:
1) You can't do snapshots
2) If for some reason...
February 1, 2009 at 11:04 am
If by manually you mean by scripting it instead of using the GUI setup in SSMS, then yes, I did it manually.
I haven't ever played with the GUI, so...
January 30, 2009 at 10:23 am
Jeff Moden (1/30/2009)
January 30, 2009 at 9:41 am
Hey! Now that's what we need. A hall of fame for stupid posts, (and another one for the most creative replies to these posts).
January 30, 2009 at 8:38 am
I'd reccomend running thru the upgrade process a couple of times on a dev/test server before doing your production server.
We just did an upgrade of about 8 dev boxes and...
January 22, 2009 at 7:21 am
Steven Cameron (1/21/2009)
January 21, 2009 at 7:16 am
Viewing 15 posts - 226 through 240 (of 474 total)