SQL & Laserfiche

asked on December 13, 2015 • Show version history

Dears

I have got these questions from one of our clients, asking about relation between sql and laserfiche.

3. Is there any field(s) in this database that contain(s) XML or Binary information? No
4. What kind of usage ,
• Is it for OLTP transactions , I mean DML transactions like insert , update and delete ..?
• Or is it for ROLAP and MOLAP ( HOLAP) , I mean BI , dashboard and BAM (business activity monitor) ..?

5. Is any special configuration(s) that should be considered while DB implementations such as:

o   DTC (Distributed transaction coordinator)
o   Service broker
o   CLR and assembly, if so what type of assemble, external access, unsafe, safe and is supported by GAC (Global assembly cache) or needs any other external .dll file..?
o   RCSI (Read Committed snapshot isolation level)
o   Encryption and if so what kind of encryption algorithm and what the key provisioning used there , I mean what DMK , Certificate , asymmetric key …etc.?
o   Elevated privileges for application service account?
o   certain data engineering solution like data archiving, data migration, data cleansing jobs ….?
o   Special scheduled jobs to send reports or do some DML operations..?
o   SSRS (SQL Server Reporting service) Reports..? No if so please mentioned their URLs and grant content manager privileges for us
o   Any OLAP cubes or BI solution running there..?
o   Linked server or distributed queries
o   Replication or transaction log shipping with other DBs on other servers..?
o   Any direct access from outside by any other users or systems …?

0 0

replied on December 21, 2015 • Show version history

3. Yes, security identifiers are stored as binary strings. In addition, LF supports a binary field type, but that is user data.

4. The workload can be characterized as primarily OLTP.

5a. LF products do not use transaction coordinators or service brokers.

5b. LF products do not use .NET stored procedures and do not require any .NET assemblies to be installed on SQL Server server machines.

5c. LF doesn't encrypt the data stored in databases. You can use SQL Server's Transparent Data Encryption feature if you like.

5d. LF applications expect to log in as a user with dbowner access to the database they store their data in, but otherwise do not require instance-wide privileges.

5e. It's recommended to schedule regular maintenance procedures to gather statistics, etc., but LF products do not require the configuration of scheduled jobs.

5f. LF products do not use SQL Server Reporting Service.

5g. LF products do not use the OLAP/BI functionality of SQL Server and does not make use of OLAP cubes.

5h. LF products do not require the configuration of linked servers for any built-in functionality.

5i. LF products do not require the use log shipping or other forms of database replication.

5j. LF architecture dictates that only the primary service application requires direct access to the database, and other programs wishing to access the data must go through the application service. Therefore direct access for outside users is not required.

2 0

Question

Question

Replies

Sign in to reply to this post.