http://www2.sqlblog.com/blogs/merrill_aldrich/archive/tags/logshipping/default.aspxTags: logshippingenCommunityServer 2.1 SP2 (Build: 61129.1)http://www2.sqlblog.com/blogs/merrill_aldrich/archive/2013/03/15/ssms-2012-restore-gui-gotcha.aspxFri, 15 Mar 2013 16:30:07 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:48261merrillaldrich2http://www2.sqlblog.com/blogs/merrill_aldrich/comments/48261.aspxhttp://www2.sqlblog.com/blogs/merrill_aldrich/commentrss.aspx?PostID=48261Today I want to bring to your attention an issue in the SQL Server Management Studio 2012 restore GUI. In many ways the new restore dialog is nicer than the old one, with new features and added convenience – but, as is always the Achilles heel of GUI...(<a href="http://www2.sqlblog.com/blogs/merrill_aldrich/archive/2013/03/15/ssms-2012-restore-gui-gotcha.aspx">read more</a>)<img src="http://www2.sqlblog.com/aggbug.aspx?PostID=48261" width="1" height="1">management studiobackupdisaster recoverylogshippinghttp://www2.sqlblog.com/blogs/merrill_aldrich/archive/2011/05/19/case-study-secure-log-shipping-via-ssl-ftp.aspxFri, 20 May 2011 00:12:21 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:35754merrillaldrich1http://www2.sqlblog.com/blogs/merrill_aldrich/comments/35754.aspxhttp://www2.sqlblog.com/blogs/merrill_aldrich/commentrss.aspx?PostID=35754Today I’m putting up sort of an oddball solution I build a couple of months ago. We had the need to provide a reporting copy of some production databases for analysts to do ad-hoc reporting. The trick was that we needed to move the databases from a less...(<a href="http://www2.sqlblog.com/blogs/merrill_aldrich/archive/2011/05/19/case-study-secure-log-shipping-via-ssl-ftp.aspx">read more</a>)<img src="http://www2.sqlblog.com/aggbug.aspx?PostID=35754" width="1" height="1">securitypowershelllogshipping