Skip to Content
Business Trends
Author's profile photo Rui Fontinha

SQL Server – System Copy Schema Conversion Script Old Versions

This webpage was moved to:

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Matt Fraser
      Matt Fraser

      I recently brought it up to the team that manages SWPM that the old "SAP Tools for SQL Server" had a refresh option (using sapinst), which surprised them -- they thought this could only be done with newer versions of NetWeaver. I pointed out that SQL Server Basis admins had been doing this for many years, and it was a disappointment to see the functionality be removed for all NW versions less than 7.1. Anyway, as a result of that conversation, they are investigating adding it back in (SWPM for 7.1+ already has a "refresh" option, but this is lacking in 70SWPM).

      Anyway, that aside, the one thing I would add here is that in most cases -- for me, at least -- it is a production system being copied, and taking it down to detach the database is simply not an option. However, it's easy enough to copy a database by restoring from a backup, and this turns out to additionally have the advantage of only copying the backup file(s) over the network. That's typically much faster, as the backup file is usually much smaller than the original database, especially with backup compression enabled.

      The other advantage of using backup/restore instead of detach/attach is the ability to copy a point-in-time snapshot, where the point in time may not be known precisely until after it has passed. We use this regularly for running parallel tests of payroll, where we want to capture a snapshot of production in the moment just prior to payroll exit.



      Author's profile photo Matt Fraser
      Matt Fraser

      Never a waste of time.

      Author's profile photo Former Member
      Former Member

      Very informative. Thanks.