Cycling related:

Congrats to the trio of ladies from Austin, TX that were in the top 10 at the Women's National Crits this weekend!

2005 Log Shipping

ok...I'm behind the times and just started working with SQL Server Log Shipping instead of writing my own custom scripts (Backup, Copy, Restore...just ain't that hard...)

Messing with a dead LS database this weekend, I tried to script out the existing configuration from the Log Shipping GUI. Has anyone else seen this thing drop all of the information on the destination server when it created the script?

I didn't bother to Google it and just re-created from scratch.

It bothers me that you have to drop and re-create to "re-initialize" a log shipped database.

No fries for me :(


LazyWriter: warning, no free buffers found.

SQL 2005, 9.0.3042

Got this in my ERRORLOG, along with a ton a memory messages not worth repeating here.

8GB RAM in the box, SQL Server set to dynamically allocate, and using 6.3 gb.

SQL was not allowing connections, giving the misleading "remote connections are not allowed/TCP" messages (translated: "something bad happened")

Solution (as seen in other places, but not many)...hard reboot of the server, bring up SQL, configure max memory to 6GB (anything other than dynamic, but leave some for the O/S).

No fries...took 30 minutes to get to the resolution. Dessert maybe :)