Our first run trying to copy a database using SQL Packager has not been so successful.
After having disk space issues and no key errors, I finally got the process running against a 90 gb database only to get a System.OutOfMemoryException. Considering this workstation has 2 gb RAM and nothing else is running on it, I'd like to see how this software is actually usable.
Operating system: WinXP pro ( 5.1.2600 )
Sql Packager: 18.104.22.168
Database: Sql Server Enterprise 2005 ( on Windows 2003 Server )
To solve the first two errors, I created variable pointing to a network drive ( gig card ) and excluded the table with the missing key ( proprietary database ). Oh, and there was a permission snafu for creating a assembly object that I fixed.
If I could get past this memory problem, this software might actually have value. Thanks for your time.
Also, is there a setting to enable the job to bypass and report errors, while continuing to do the job of moving schema and data?