Framework:Database on SQL Server - Revision history

Admin at 08:38, 29 March 2017

2017-03-29T08:38:15Z

← Older revision		Revision as of 09:38, 29 March 2017
Line 42:		Line 42:
	It is possible to create the CoPlanner data tables as a view which then is given the corresponding name as in the CoPlanner object management.		It is possible to create the CoPlanner data tables as a view which then is given the corresponding name as in the CoPlanner object management.

	For this purpose, ~~there is~~ a ~~specific menu item~~ in the ~~CoPlanner under Administration – Create views~~. Existing views are not deleted thereby, but if there exist already views with a name that is to be created such views are overwritten.		For this purpose, you find a macro "CreateViews" in the object management. Existing views are not deleted thereby, but if there exist already views with a name that is to be created such views are overwritten.

	If required, you can delete all views (except for the “time” view) and have all CoPlanner data tables newly created as views.		If required, you can delete all views (except for the “time” view) and have all CoPlanner data tables newly created as views.

Admin at 07:50, 15 July 2010

2010-07-15T07:50:53Z

← Older revision		Revision as of 08:50, 15 July 2010
Line 55:		Line 55:
	From within the developer menu you can backup and restore the entire database as well as all definitions of the server directories.		From within the developer menu you can backup and restore the entire database as well as all definitions of the server directories.
	The following data is saved:		The following data is saved:
	:*The entire SQL database which is set in the connection string in SvrConfig.xml.		:*The entire SQL database which is set in the connection string in [[Technics:CoPlanner-Server#SvrConfig.xml\|SvrConfig.xml]].
	:*The “Agg Masks”, “Reports” “Report” and “Transfer” server directories as well as their sub-directories.		:*The “Agg Masks”, “Reports” “Report” and “Transfer” server directories as well as their sub-directories.
	Please note:		Please note:
	:*Any existing content in the saved directories will be overwritten during the restoring process.		:*Any existing content in the saved directories will be overwritten during the restoring process.
	:*Configuration data (SvrConfig.xml, [[Technics:CoPlanner-Server#CopServer.exe.config\|CopServer.exe.config]], [[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]] and [[Technics:CoPlanner_Win-Client#coplanner.exe.config_File\|coplanner.exe.config]]) are not saved.		:*Configuration data ([[Technics:CoPlanner-Server#SvrConfig.xml\|SvrConfig.xml]], [[Technics:CoPlanner-Server#CopServer.exe.config\|CopServer.exe.config]], [[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]] and [[Technics:CoPlanner_Win-Client#coplanner.exe.config_File\|coplanner.exe.config]]) are not saved.
	:*The database contained in the backup will be restored with the name which is defined in the SvrConfig.xml in the connection string – irrespective of the name of the originally saved database.		:*The database contained in the backup will be restored with the name which is defined in the [[Technics:CoPlanner-Server#SvrConfig.xml\|SvrConfig.xml]] in the connection string – irrespective of the name of the originally saved database.
	:*OLAP data is not saved.		:*OLAP data is not saved.
	:*In case of doubt, carry out a backup before the restoring process.		:*In case of doubt, carry out a backup before the restoring process.
Line 86:		Line 86:
	{\| {{Bausteindesign1}}		{\| {{Bausteindesign1}}
	\|-		\|-
	\| <span style="color: darkblue;">'''Hint'''</span>  Please ensure that in the ~~svrConfig~~.xml, which is located in the server directory, the <Backuppath> line is correctly defined. You must enter a path for which the SQL server has writing rights. After some time (please be patient – the file is compressed on the server and then transferred to the client) the backup is saved in the directory indicated.		\| <span style="color: darkblue;">'''Hint'''</span>  Please ensure that in the [[Technics:CoPlanner-Server#SvrConfig.xml\|SvrConfig.xml]], which is located in the server directory, the <Backuppath> line is correctly defined. You must enter a path for which the SQL server has writing rights. After some time (please be patient – the file is compressed on the server and then transferred to the client) the backup is saved in the directory indicated.
	Please also note that files which exceed the “BackupRestoreLimitinMB” (default volume = 50 MB) as set in the “copservice.exe.config” server configuration file, are not transferred to the folder indicated but are left in the folder given under “Backuppath” in the ~~“SvrConfig~~.~~xml”~~ configuration file which is used for temporary storage.		Please also note that files which exceed the “BackupRestoreLimitinMB” (default volume = 50 MB) as set in the “copservice.exe.config” server configuration file, are not transferred to the folder indicated but are left in the folder given under “Backuppath” in the “[[Technics:CoPlanner-Server#SvrConfig.xml\|SvrConfig.xml]]” configuration file which is used for temporary storage.
	\|}		\|}

Line 105:		Line 105:
	{\| {{Bausteindesign1}}		{\| {{Bausteindesign1}}
	\|-		\|-
	\| <span style="color: darkblue;">'''Hint'''</span>  Verify if the database which you wish to overwrite by means of the restoring process has been defined in the connection string in SvrConfig.xml.		\| <span style="color: darkblue;">'''Hint'''</span>  Verify if the database which you wish to overwrite by means of the restoring process has been defined in the connection string in [[Technics:CoPlanner-Server#SvrConfig.xml\|SvrConfig.xml]].
	Again, you need to ensure that the <Backuppath> is configured correctly. Furthermore, it is important to make sure that the pooling=false part exists in the connection string. Besides, no other client, query analyzer, enterprise manager or the like must be connected on the SQL server.		Again, you need to ensure that the <Backuppath> is configured correctly. Furthermore, it is important to make sure that the pooling=false part exists in the connection string. Besides, no other client, query analyzer, enterprise manager or the like must be connected on the SQL server.
	If this is not the case, please change the parameters accordingly and restart the server and the client.		If this is not the case, please change the parameters accordingly and restart the server and the client.

Admin at 07:46, 15 July 2010

2010-07-15T07:46:21Z

← Older revision		Revision as of 08:46, 15 July 2010
Line 59:		Line 59:
	Please note:		Please note:
	:*Any existing content in the saved directories will be overwritten during the restoring process.		:*Any existing content in the saved directories will be overwritten during the restoring process.
	:*Configuration data (SvrConfig.xml, CopServer.exe.config, [[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]] and [[Technics:CoPlanner_Win-Client#coplanner.exe.config_File\|coplanner.exe.config]]) are not saved.		:*Configuration data (SvrConfig.xml, [[Technics:CoPlanner-Server#CopServer.exe.config\|CopServer.exe.config]], [[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]] and [[Technics:CoPlanner_Win-Client#coplanner.exe.config_File\|coplanner.exe.config]]) are not saved.
	:*The database contained in the backup will be restored with the name which is defined in the SvrConfig.xml in the connection string – irrespective of the name of the originally saved database.		:*The database contained in the backup will be restored with the name which is defined in the SvrConfig.xml in the connection string – irrespective of the name of the originally saved database.
	:*OLAP data is not saved.		:*OLAP data is not saved.

Admin at 07:44, 15 July 2010

2010-07-15T07:44:24Z

← Older revision		Revision as of 08:44, 15 July 2010
Line 59:		Line 59:
	Please note:		Please note:
	:*Any existing content in the saved directories will be overwritten during the restoring process.		:*Any existing content in the saved directories will be overwritten during the restoring process.
	:*Configuration data (SvrConfig.xml, CopServer.exe.config, [[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]] and coplanner.exe.config) are not saved.		:*Configuration data (SvrConfig.xml, CopServer.exe.config, [[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]] and [[Technics:CoPlanner_Win-Client#coplanner.exe.config_File\|coplanner.exe.config]]) are not saved.
	:*The database contained in the backup will be restored with the name which is defined in the SvrConfig.xml in the connection string – irrespective of the name of the originally saved database.		:*The database contained in the backup will be restored with the name which is defined in the SvrConfig.xml in the connection string – irrespective of the name of the originally saved database.
	:*OLAP data is not saved.		:*OLAP data is not saved.

Admin at 07:39, 15 July 2010

2010-07-15T07:39:19Z

← Older revision		Revision as of 08:39, 15 July 2010
Line 59:		Line 59:
	Please note:		Please note:
	:*Any existing content in the saved directories will be overwritten during the restoring process.		:*Any existing content in the saved directories will be overwritten during the restoring process.
	:*Configuration data (SvrConfig.xml, CopServer.exe.config, ClientConfig.xml and coplanner.exe.config) are not saved.		:*Configuration data (SvrConfig.xml, CopServer.exe.config, [[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]] and coplanner.exe.config) are not saved.
	:*The database contained in the backup will be restored with the name which is defined in the SvrConfig.xml in the connection string – irrespective of the name of the originally saved database.		:*The database contained in the backup will be restored with the name which is defined in the SvrConfig.xml in the connection string – irrespective of the name of the originally saved database.
	:*OLAP data is not saved.		:*OLAP data is not saved.

Admin at 06:38, 7 May 2010

2010-05-07T06:38:39Z

← Older revision		Revision as of 07:38, 7 May 2010
Line 3:		Line 3:
	You need to distinguish between system tables and data tables.		You need to distinguish between system tables and data tables.

	Data tables are created via the object ~~management~~. They have a COPSYS_ID as their name.		Data tables are created via the [[Framework:Object_administration\|object administration]]. They have a COPSYS_ID as their name.

	System tables are tables pre-defined by the CoPlanner and start with “tb_”. These are:		System tables are tables pre-defined by the CoPlanner and start with “tb_”. These are:

Admin at 06:35, 6 May 2010

2010-05-06T06:35:17Z

← Older revision		Revision as of 07:35, 6 May 2010
Line 129:		Line 129:

	[[Category:Framework\|Database on SQL Server]]		[[Category:Framework\|Database on SQL Server]]
	[[de:Datenbank am SQL-Server]]		[[de:Framework:Datenbank am SQL-Server]]

Admin at 06:34, 6 May 2010

2010-05-06T06:34:50Z

← Older revision		Revision as of 07:34, 6 May 2010
Line 129:		Line 129:

	[[Category:Framework\|Database on SQL Server]]		[[Category:Framework\|Database on SQL Server]]
			[[de:Datenbank am SQL-Server]]

Admin at 06:33, 6 May 2010

2010-05-06T06:33:14Z

← Older revision		Revision as of 07:33, 6 May 2010
Line 109:		Line 109:
	If this is not the case, please change the parameters accordingly and restart the server and the client.		If this is not the case, please change the parameters accordingly and restart the server and the client.
	\|}		\|}


	{\| {{Bausteindesign2}}		{\| {{Bausteindesign2}}

Admin at 06:32, 6 May 2010

2010-05-06T06:32:53Z

@@ Line 67: / Line 67: @@
 ===Backup database===
 [[image:Backup database.jpg‎|thumb|center|Framework, Backup database]]
-#Drücken Sie auf den Button [[image:Icon_Dateiauswahl.jpg‎]] und wählen sie ein Verzeichnis auf Ihrem lokalen Client-Rechner.
+{| {{Bausteindesign2}}
-#Drücken Sie "Start". Es wird jetzt am Coplanner-Server ein Backup der Datenbank im definierten Verzeichnis erstellt. Zu beachten ist, dass in der Datei svrConfig.xml, welche sich im Server-Verzeichnis befindet, die Zeile <Backuppath> richtig definiert ist. Es muss ein Pfad angegeben werden, auf welchen der SQL-Server Schreibrechte hat. Das Backup wird nach einiger Zeit (bitte geduldig sein – die Datei wird am Server komprimiert und anschließend auf den Client übertragen) im angegebenen Verzeichnis gespeichert.
+|-
-===Datenbank wiederherstellen===
+After some time there will be a message saying that the backup has been integrated. The server will then be restarted and you can continue to work with the new data.
-#Überprüfen sie, ob in SvrConfig.xml im connectionstring die Datenbank definiert ist, welche Sie mit dem Wiederherstellen überschreiben möchten.
+{| {{Bausteindesign1}}
-Zu beachten ist hierbei wieder die richtige Konfiguration von <Backuppath>. Weiters wichtig ist, dass im Connectionstring der Teil pooling=false; vorhanden ist. Weiters darf auf den SQL-Server kein Query-Analyzer, Enterprise Manager o.ä. verbunden sein. Weiters sollte kein weiterer Client mit dem CoPlanner Server verbunden sein.
+|-
-Wenn nicht, ändern Sie bitte die Parameter entsprechend und starten Sie Server und Client neu.
+| <span style="color: darkblue;">'''Hint'''</span> &nbsp;Close the existing masks before any restoring procedure since the underlying data no longer needs to be available.
-#Drücken sie den Button [[image:Icon_Dateiauswahl.jpg‎]] und wählen sie eine Backup-Datei.
+|}
@@ Line 88: / Line 127: @@
 __NOEDITSECTION__
-[[Category:Framework|Datenbank am SQL-Server]]
+[[Category:Framework|Database on SQL Server]]