5 Copy of production data
V něIn some cases, such as for testing or making some bulk changes to a large amount of data, it is necessary or appropriate to create a copy of production data and test the required functions or work in this copy.
Creating a copy of the accounting unit from production data is not complicated. It requires an SQL server administrator. The user themselves does not have permissions for this process 99% of the time. What is needed for this is outlined in this chapter.
What the program user - SUPERVISOR must do
Create a new accounting unit in the standard way
Enter this unit at least once and set in the module Manager - Global preferences
End work in this new unit
What the IT SQL Server administrator must do
Create a current backup of the SQL database of the production accounting unit (a .BAK file will be created)
Restore this backup to a new database. We will choose any name, for example, TestovaciDB, and during the restore, we will turn off "Tail-Log" in the Options section.
The database will be restored, creating a copy of the production data.
We have created a copy of the database; now we just need to adjust the settings of our test unit in Premiere.
It is necessary to set up this test unit just like the production one, with the only difference being that the field name "Sqldbname" will be written according to the name of the test DB.
We must also remember to set permissions for SQL users who will access this unit. Whether the option "Winaut" is set in the accounting unit or the user is authenticated using an account on the SQL server, it is necessary to grant this user or group access to the test database. This will also be done on the SQL server, see the image below.If it is necessary to transfer user preference settings from the production accounting unit, copy the three files named "LOKAL.." from the directory \premier\FAxx\ (where xx is the accounting unit number) to the directory of the test accounting unit.
FAxx