Obsidian Tables - Revision history

Craig at 14:56, 17 May 2023

2023-05-17T14:56:55Z

← Older revision		Revision as of 14:56, 17 May 2023
Line 56:		Line 56:
	== MS SQL Server Snapshot Isolation ==		== MS SQL Server Snapshot Isolation ==

	For maximum compatibility and to avoid deadlocks, MS SQL Server should be configured to use [https://~~msdn~~.microsoft.com/en-us/~~library~~/~~tcbchxcb(v=vs.110).aspx~~ read committed snapshot isolation].		For maximum compatibility and to avoid deadlocks, MS SQL Server should be configured to use [https://learn.microsoft.com/en-us/dotnet/framework/data/adonet/sql/snapshot-isolation-in-sql-server read committed snapshot isolation].

	This can be enabled on your database by running the following commands:		This can be enabled on your database by running the following commands:

2015-07-30T18:06:31Z

@@ Line 52: / Line 52: @@
 GRANT ANALYZE ANY TO OBSIDIAN_USER;
 GRANT ANALYZE ANY DICTIONARY TO OBSIDIAN_USER;
 </pre>

2015-01-23T23:10:04Z

2013-11-08T03:25:35Z

← Older revision		Revision as of 03:25, 8 November 2013
Line 3:		Line 3:
	'''Note:''' Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.		'''Note:''' Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.

	Obsidian can be configured to use a [[Advanced_Configuration#Table ~~Prefix~~\|table prefix]] when creating its tables.		Obsidian can be configured to use a [[Advanced_Configuration#Table Prefixes\|table prefix]] when creating its tables.

	* custom_calendar		* custom_calendar

2013-11-08T03:25:09Z

← Older revision		Revision as of 03:25, 8 November 2013
Line 3:		Line 3:
	'''Note:''' Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.		'''Note:''' Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.

	Obsidian can be configured to use a table prefix when creating its tables~~. See [[Advanced_Configuration\|Advanced Configuration]] for full details~~.		Obsidian can be configured to use a [[Advanced_Configuration#Table Prefix\|table prefix]] when creating its tables.

	* custom_calendar		* custom_calendar

2013-06-30T18:29:05Z

Oracle Privileges

← Older revision		Revision as of 18:29, 30 June 2013
Line 37:		Line 37:
	== Oracle Privileges ==		== Oracle Privileges ==

	If you are not using the schema owner as your Obsidian database user, the following privileges will need to be granted to your database user:		As of version 2.1, if you are not using the schema owner as your Obsidian database user, the following privileges will need to be granted to your database user:

	<pre>		<pre>

2013-06-30T18:28:17Z

Oracle Privileges

← Older revision		Revision as of 18:28, 30 June 2013
Line 37:		Line 37:
	== Oracle Privileges ==		== Oracle Privileges ==

	If you are not using the schema owner as ~~you~~ Obsidian database user, the following privileges will need to be granted to your database user:		If you are not using the schema owner as your Obsidian database user, the following privileges will need to be granted to your database user:

	<pre>		<pre>

2013-06-30T18:28:05Z

← Older revision		Revision as of 18:28, 30 June 2013
Line 33:		Line 33:
	* user_role		* user_role
	* workflow_script		* workflow_script


			== Oracle Privileges ==

			If you are not using the schema owner as you Obsidian database user, the following privileges will need to be granted to your database user:

			<pre>
			# For each Obsidian table...
			GRANT INSERT,SELECT,UPDATE,DELETE ON OBS_JOB TO OBSIDIAN_USER;

			# Required for alternate schema usage
			GRANT ALTER SESSION TO OBSIDIAN_USER;
			GRANT ANALYZE ANY TO OBSIDIAN_USER;
			GRANT ANALYZE ANY DICTIONARY TO OBSIDIAN_USER;
			</pre>

2013-06-25T02:38:54Z

← Older revision		Revision as of 02:38, 25 June 2013
Line 2:		Line 2:

	'''Note:''' Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.		'''Note:''' Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.

			Obsidian can be configured to use a table prefix when creating its tables. See [[Advanced_Configuration\|Advanced Configuration]] for full details.

	* custom_calendar		* custom_calendar

2013-06-18T21:21:32Z

← Older revision		Revision as of 21:21, 18 June 2013
Line 3:		Line 3:
	'''Note:''' Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.		'''Note:''' Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.

			* custom_calendar
	* event_log		* event_log
	* event_subscriber		* event_subscriber
Line 15:		Line 16:
	* job_history_chain		* job_history_chain
	* job_history_error		* job_history_error
			* job_history_interrupt
	* job_history_result		* job_history_result
	* job_running_host		* job_running_host
	* job_state		* job_state
	* notification		* notification
			* notif_template
			* notif_template_entity
	* operations_parameter		* operations_parameter
	* role		* role