6.8 KiB
BKKSQL2017Test
Dienstag, 26. März 2019
09:32
Admin Passwort: Tausend2003#
CPU 4
RAM 16
Festplatte C 127 GB
IP Adresse 10.96.73.108
SQL Instanzen :
BKKSQL2017Test\SPTEST2019
BKKSQL2017Test\SQL2017
BKKSQL2017Test\sqlsharepointP
BKKSQL2017Test\SPTEST2019
Installed Features :
{width="4.1875in" height="4.541666666666667in"}
Erfasster Bildschirmausschnitt: 25.04.2019 15:18
BKKSQL2017Test\sqlsharepointP
Installed Features :
{width="4.1875in" height="4.541666666666667in"}
Moving the (Control Manager/Apex Central™) database from SQL Express to SQL (Full version)
-
Updated:
-
18 Mar 2019
-
Product/Version:
-
Apex Central All.All
-
Platform:
-
Windows 2008 Server R2
Summary
In this article you will find the steps how to move the Control Manager/Apex Central™ Database from the SQL Server Express to a SQL Server Standard or SQL Server Enterprise.
Details
-
Stop the following Control Manager Services:
-
Trend Micro Control Manager/Apex Central™
-
Trend Micro Management Infrastructure
-
-
Open Microsoft SQL Server Management Studio and connect to the SQL Express Instance.
-
Right click on "db_ControlManager" or "db_ApexCentral" (it can differ if you chose a different name)
-
Click on Tasks > Detach.
- Tick Drop Connections and Update Statistics. All existing Connections will be dropped.
-
Copy the following database files to the new SQL Server:
-
For Control Manager:
-
db_ControlManager.mdf
-
db_ControlManager_log.ldf
-
-
For Apex Central™:
-
db_ApexCentral.mdf
-
db_ApexCentral_log.ldf\
The default file location of the SQL Server is \Program Files\ Microsoft SQL Server\MSSQL<Version>.<InstanceID>\MSSQL\DATA
-
-
-
Open Microsoft SQL Server Management Studio and connect to the new SQL Server Instance.
-
On the left pane, right-click on Databases, then select Attach...
- Click on Add.
- Choose which Database you want to attach.
-
Once the Database is successfully attached, configure TMCM to connect to the new Database. Do the following:
-
Go to the TMCM Server and open Command Prompt.
-
Navigate to C:\Program Files (x86)\Trend Micro\Control Manager\DBConfig.
-
Use the following command:\
DBConfig.exe -DBName="<DBname>" -DBAccount="<DBaccount>" -DBPassword="<password>" -Mode=">WA or SQL>" -DBHost="<IP address or FQDN of SQL server>"
Where:-
DBName - Name of the Database
-
DBAccount - Account used to login on the SQL Server Management Studio to access the DB
-
DBPassword - Password used to login on the SQL Server Management Studio to access the DB
-
Mode - There are 2 options WA (Windows Authentication) or SQL
-
DBHost - Use the IP or FQDN of your SQL Server\
Below is an example of a successful connection to the database:
-
-
{width="5.208333333333333in" height="3.8125in"}
Wichtige Einschränkungen der Express-Version 2017
Wie Version 2016 (2016 hat noch die Volltextsuche), jedoch ohne Volltextsuche.
-
Es wird nur ein Prozessor, aber bis zu 4 Prozessorkerne verwendet.
-
Maximal genutzter Arbeitsspeicher pro Instanz: ca. 2 GB
-
Eine Datenbank darf maximal 10 GB groß sein.
-
Der Dienst „SQL Server-Agent" ist nicht enthalten.
-
Die Volltextindexierung und -Suche ist in der kostenlosen Edition nicht mehr enthalten.
Aus <https://blog.officemanager.de/2012/01/sql-server-express-limits/>
Upgrade von Version auf Version :
SQL Server 2017 (14.x) Express* | SQL Server 2017 (14.x) Enterprise (Server+CAL or Core License)
SQL Server 2017 (14.x) Developer
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web |
---|
SQL Server 2016 (13.x) Express | SQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Express
SQL Server 2017 (14.x) Developer |
---|