j5 converts VARCHAR columns to NVARCHAR columns for Microsoft SQL Server when you upgrade to j5 version 30. This process can take a while if you have a big database, because the transaction logs can fill and cause j5 Setup to fail.
To avoid filling the transaction log, complete the following steps:
1. Make a full backup of your database
You should always have a database backup before making any changes. This is so you can restore your database if something goes wrong.
2. Ensure that your database recovery model is Simple
You can view and edit the recovery model in SQL Server Management Studio or using Transact-SQL.
-
Connect to the appropriate instance of the SQL Server Database Engine in Object Explorer.
-
Select the server name to expand the server tree.
-
Expand the Database node and select the user database you want.
-
Right-click the database and select Properties. The Database Properties dialog box appears.
-
In the Select a page pane, select Options. The current recovery model is displayed in the Recovery model list.
-
Ensure that the recovery model is set to Simple.
These steps were adapted from Microsoft - Use SQL Server Management Studio
-
Connect to the database engine.
-
Select New Query in the standard bar.
-
Copy and paste the following into the query window. This shows how to query the sys.databases catalog view to see the recovery model of the customer database.
SELECT name, recovery_model_desc
FROM sys.databases
WHERE name = 'customer';
GO
-
Select Execute. The recovery model setting is displayed.
-
To change the recovery model to Simple, copy and paste the following into the query window. This shows how to change the recovery model into the customer database to SIMPLE by using the SET RECOVERY option of the ALTER DATABASE statement.
USE [master];
GO
ALTER DATABASE [customer]
SET RECOVERY SIMPLE;
GO
-
Select Execute. The recovery model is changed to Simple.
These steps were adapted from Microsoft - Use Transact-SQL
3. Run j5 Setup
This might take a few hours to run through to completion, because various database updates need to be made.
4. Change the recovery model back to what it was before