After the installation of Print&Share CQ the default database is LocalDB. This database doesn't require you to configure anything special and runs out of the box.
However it is possible to change the underlaying database to Microsoft SQL Server.
Note: In case you are planning to use MS SQL Server it is recommended to do this right after the installation of Print&Share CQ. The reason is that you will lose your configurations and settings. In case you do this at a later stage it is recommended to take a backup first and export your configured profiles.
Switching from LocalDB to Microsoft SQL Server
We assume that you have Microsoft SQL Server Management Studio (MS SSMS) installed, which lets you manage the SQL Server.
We demonstrate two options:
- Let Print&Share CQ create the SQL database
- You create an empty SQL database first
1. Let Print&Share CQ create the SQL database
In this case you will create a dedicated SQL user in SSMS. During configuration of Print&Share CQ you fill in the database name and the dedicated user. Print&Share CQ will create a database with the given name for that user and create all tables.
We will use SQLExpress in this article.
- Open MS SSMS and connect to your SQL Server instance. (e.g.
MYSERVER\SQLEXPRESS
) - Navigate to
MYSERVER\SQLEXPRESS > Security > Logins
and right-click on Logins and select New Login... - In the page General:
Use For the Login name usewinkingpscq
.
Select SQL Server authentication and fill in a password.
(Depending on your policy uncheck Enforce password policy, uncheck Enforce password expiration and uncheck User must change password at next login)
In the page Server Roles give the user also thedbcreator
permission to allow creating a new database. (Other permission could be needed depending on your environment.)
Click OK to close the dialog in MS SSMS. - In Print&Share CQ navigate to
Manage > System Setup > System settings
and edit the Database connection: settings. - Change the Selected provider: from LocalDB to
Microsoft SQL Server
. - Use the settings:
Server:MYSERVER\SQLEXPRESS
Username:winkingpscq
Password:<thepassword>
Initial catalog:PSCQ
(=this is the name of the new database that we will create in Sql Server). - Click OK to close the database settings dialog.
- Click Save on the System settings page.
If all went fine, Print&Share CQ is now using SQL Server as underlaying database.
2. You create an empty SQL database first
In this case we will create an empty database first (and dedicated user) in our SQL Server instance and only connect to it using Print&Share CQ. Print&Share CQ will connect to that empty database and create all tables.
- Open MS SSMS and connect to your SQL Server instance. (e.g.
MYSERVER\SQLEXPRESS
) - Navigate to
MYSERVER\SQLEXPRESS > Security > Logins
and right-click on Logins and select New Login... - In the page General:
Use For the Login name usewinkingpscq
.
Select SQL Server authentication and fill in a password.
(Depending on your policy uncheck Enforce password policy, uncheck Enforce password expiration and uncheck User must change password at next login)
In the page Server Roles give the user also thedbcreator
permission to allow creating a new database. (Other permission could be needed depending on your environment.)
Click OK to close the dialog in MS SSMS. - in MS SSMS navigate to
MYSERVER\SQLEXPRESS > Databases
and right-click on Database and select New Database... - In the New Database dialog on the General page, fill in the Database name:
PSCQ
Change the Owner: to our newly createdwinkingpscq
.
Click OK to close the dialog in MS SSMS. - In Print&Share CQ navigate to
Manage > System Setup > System settings
and edit the Database connection: settings. - Change the Selected provider: from LocalDB to
Microsoft SQL Server
. - Use the settings:
Server:MYSERVER\SQLEXPRESS
Username:winkingpscq
Password:<thepassword>
Initial catalog: and choose from the dropdown our newly createdPSCQ
database. - Click OK to close the database settings dialog.
- Click Save on the System settings page.
If all went fine, Print&Share CQ is now using SQL Server as underlaying database.