Generally, sodium hydrogen sulfite and sodium hydrogen sulfate are not interchangeable.

Sodium hydrogen sulfite or “sodium bisulfite” (NaHSO3) is used in food processing as sanitising agent for food containers and fermentation equipment, preservative to reduce or prevent microbial spoilage, selective inhibitor of undesirable microorganisms
in the fermentation industries, and as an antioxidant and inhibitor of enzyme-catalysed
oxidative discoloration and non-enzymic browning. The food additive code (the E number, which is commonly found on food labels) of sodium hydrogen sulfite is E 222.

Sodium hydrogen sulfate or “sodium bisulfate” (NaHSO4) is used as acidity regulator. The food additive code of sodium hydrogen sulfate is E 514.

Sodium Bisulfate vs Sodium Bisulfite
I'm given the task to export the content of a huge table from a production database and to import the data into a database at a remote location.

The Table has about 45,000,000 rows. using about 4 GB space in the database.

Its 10 Columns are of type int, datetime and varchar(n) &lt;= 255, but some of the varchar fields contain newlines and the usual field separators used by bulkcopy.

I guess export to Excel is no option due to the number of rows.
Export with SSIS to Flatfile is possible (took about 30 minutes), but reimport is not automatic, since some fields where spitted.

My current idea is


create a new database on the production server (using same
collations as the production database)
Set its recovery mode to simple
copy the data with
Select * into copy_of_table from prod_db..big_table
Detach mdf file from this new database and ship it to the other
location
Drop adhoc database


I assume that inserting into a database with simple recovery model generates only minimal logging on the new database and this way is one of the fastest possible to export the data and the impact to the production database is the least possible.
