Contents

Introduction to using AccuMark SQL Storage Areas ................................................................................. 2

Subfolders ............................................................................................................................................... 2
Permissions for SQL Storage Area Access ................................................................................................. 3
Permissions for AccuMark Data Types ..................................................................................................... 3
Optional CAD Relational Database (RDBMS) ............................................................................................ 4
AccuMark and YuniquePLM Integration ................................................................................................... 4
Backup and Restore of AccuMark SQL Storage Areas ............................................................................... 5
Firewalls and SQL .................................................................................................................................... 5
SQL specifics ............................................................................................................................................ 6
Support versions of SQL for AccuMark ..................................................................................................... 7
SQL Configuration for AccuMark .............................................................................................................. 8
Additional SQL Functions ....................................................................................................................... 10

© 2018 Gerber Technology LLC All Rights Reserved.

Page 1 of 10
Introduction to using AccuMark SQL Storage Areas
AccuMark data can be optionally stored in SQL storage areas, which are SQL databases, instead of or in
addition to the userroot storage areas. These SQL storage areas are equipped to look and feel the same
as userroot storage areas.

Using SQL databases as storage areas allow for larger amounts of data to be stored in a single storage
area as compared to V8 userroot storage areas. V9 userroot storage areas have a flat-file format which
also eliminates the control file and data file limitations.

While there is no physical limit to the number if data items for a SQL storage area, it is recommended
not to exceed a maximum of 100,000 data items per data type.

SQL storage areas can also eliminate the potential file locking problems that can occur when accessing
data across networks, because it does not use separate control and data files.

In addition, using SQL storage areas has these advantages:

• Allows the ability to create sub-storage areas or sub-folders
• Allows the ability to set allow or deny permissions to individual storage areas
• Allows the ability to set read or write permissions to individual data types

SQL is now used for AccuPlan and MTM (Made To Measure) to contain its data in addition to using
AccuMark’s SQL storage areas.

Subfolders
Subfolders are like having additional storage areas within a parent storage area or other subfolders.
Subfolders are contained within the parent SQL database, they are not separate databases. They can
help you to further organize your data. Using subfolders can be similar in effect to the way you organize
your documents in windows folders, giving you the ability to have folders inside of folders.

See the AccuMark IT document called “InstallAndConfigureSQL2014ExpressForAccuMark” for details on

installing SQL 2014 Express and using it for AccuMark SQL storage areas and subfolders.

Subfolders for SQL storage areas have been implemented in AccuMark V8.2 however WebPDM will not
support or recognize subfolders prior to the WebPDM 5.1 release. Also, these older versions of
WebPDM will not be able to access subfolders more than 4 levels deep (the number of subfolders as in
tree, each subfolder that is down-and-to-the-right count as a level).

SQL storage areas created in AccuMark V8.2 or earlier are required to be upgraded in order to be used
with later versions of AccuMark software. Accepting the upgrade to the new SQL database structure /
schema will prevent older AccuMark versions from accessing the upgraded data. Therefore, the upgrade
should be scheduled when all systems in the Workgroup / Domain can be updated.

© 2018 Gerber Technology LLC All Rights Reserved.

Page 2 of 10
SQL storage areas are similar to userroot storage areas from a perspective of creating and accessing

Permissions for SQL Storage Area Access

Depending on your SQL environment, various user permissions are needed for creation of SQL
databases (AccuMark SQL storage areas), accessing and updating of data within those storage areas and
subfolders. Permissions can be set for individual users or for groups. If you have several users who
require the same kinds of permissions, it may be easier to set up windows groups for this purpose
(instead of having to grant permissions on each and every user individually). For information on the
required permissions and creating windows user groups, see the AccuMark document
“CreatingGroupsAndSettingSQL-DBPermissions”.

Permissions for AccuMark Data Types

Special additional permissions can be granted for users to further restrict access to the individual
AccuMark data types. Permissions include read-only or read / write access. The AccuMark SQL Manager
is a wizard that will guide you through the setup of such permissions and is invoked from the AccuMark
Explorer; File: Options in the Storage Areas section. For details on the AccuMark data types and how to
setup the read and write controls, refer to the AccuMark document called “Read-Write Controls”.

Note: SQL Manager requires SQL Server 2005 Backwards Compatibility Components to be installed when
using SQL 2008, 2012, or 2014 versions. Refer to the AccuMark document called
“SQLServer2005BackwardCompatibilityComponents” for details and setup information.

© 2018 Gerber Technology LLC All Rights Reserved.

Page 3 of 10
Optional CAD Relational Database (RDBMS)
Using AccuMark SQL storage areas also enable the ability to use the optional CAD Relational Database
(RDBMS). The RDBMS collects statistical information from markers, models and their pieces for use by a
PLM or ERP system. It can also contains thumbnail images of the markers and model’s pieces as well as
specified annotation on the images (for details about RDBMS and its contents see document “RDBMS-
TableVariablesUpdated by AM”).

The generation of images can take time, and may be especially notable when your RDBMS is not local,
located on a WAN server a distance away, or on a slow network server. To assist with this issue, a new
application was created in AccuMark V10 called syncImages to solely generate images and update the
statistics for the selected storage areas. This allows your IT or Administrator to run syncImages on any
system that can connect and write to the SQL device and to be able to run it at the end of the day or
scheduled to be run at some time when the SQL server is not so busy. This also means that you no
longer have to set up each individual user’s system to generate images saving user’s time as well (for
details see document syncImages.docx).

AccuMark and YuniquePLM Integration

AccuMark and YuniquePLM incorporates swift and easy methods for data sharing, where data created in
one solution can be integrated into and viewed and used in the other. A major benefit is the ability for a
user working in one solution to gain access to and use data from the other solution. Users can share
updates effortlessly providing a extraordinary means to get product out the door faster, easier and with
accuracy. This can be extremely useful for suppliers, sample rooms and manufacturers who need up to
date information that is precise and able to get production done with the utmost confidence.

AccuMark Model editor can retrieve PLM Materials, and PDS can retrieve PLM materials and images.
PLM and PDS can exchange measurement labels and measurements. PLM can retrieve model
information including model options and AccuMark’s bill on materials. Markers generated in AccuMark
can be retrieved in PLM and its information used for bill of materials and other information. Starting
with AccuMark V13 you can now export 3D images into PLM!

AccuMark integrates with YuniquePLM V8 and later through APIs. This eliminates the need for a RDBMS
to pass data between the products. It is more efficient and reliable for data exchange. A PLM Login
Credentials dialog is used to connect the systems.

AccuMark integrates with YuniquePLM V7 and earlier through the use of the RDBMS. The RDBMS you
configure in SQL Support will need to connect to the same SQL database that YPLM reads from. Settings
are needed from YPLM for AM configuration.

© 2018 Gerber Technology LLC All Rights Reserved.

Page 4 of 10
To Setup YuniquePLM V8 with AccuMark
A connection is established through AccuMark, in the AccuMark Explorer’s – File – Options on the
Configuration section. The YuniquePLM Login Credentials uses the PLM Server URL, Port and Protocol
settings, PLM & API instance names and the user’s PLM login name and password. For more details on
the setup and configuration refer to the document “YuniquePLM V8 & AccuMark V12 Integration Guide”

To Setup YuniquePLM V7 with AccuMark

In YuniquePLM the Admin Folder – Setting – SYSTEM – Server – General is where you will obtain the
RDBMS database name to use from the CADDatabaseCatalog Setting Key. This database name will then
be entered into SQL Support.

In YPLM the Admin Folder – WS Clients and Tools contains the information that will be used for
AccuMark’s YuniquePLM Credentials. This connection information is needed in order for the two
applications to “talk to” each other.

Refer to the document YuniquePLM & AccuMark Compatibility Chart (750).pdf for detailed information
about the compatibility between AccuMark and YuniquePLM versions.

Backup and Restore of AccuMark SQL Storage Areas

Backups should be an important part of your routine for assuring that you have current copies of your
AccuMark SQL storage area databases. Situations can occur like accidental loss of data or corruption of
data which can be restored through backed up copies of your data. Ensure that backups are done on a
routine basis and stored in a safe location. Most companies will have policies and procedures in place
for backing up and restoration of data.

The SQL Server Management Studio is one tool that can be used for backups. The AccuMark document
called “SQL2014BackupAndRestore” contains information on how to use SSMS for creating backups and
restoring of information.

Firewalls and SQL

If others need to access to SQL Server, you may need to open the firewall on the system hosting SQL.
Refer to the AccuMark document called “FirewallsAndSQL” for instructions to add exceptions for SQL
applications.

© 2018 Gerber Technology LLC All Rights Reserved.

Page 5 of 10
SQL specifics
It is highly recommended to install the latest service packs and updates for SQL and SQL Express.

Refer to the Microsoft websites for information regarding the hardware and software requirements for
the various versions of SQL. Localized versions of SQL Server are available and should correspond to your
local language version operating system. Verify that your operating system settings match the language
of the localized SQL Server or SQL Express being installed.

If you are storing data in a native language, for example saving AccuMark data items with Chinese data
names, then you will most likely need the corresponding version of SQL that can handle the language
characters. Consult the Microsoft documentation for details and specifications.

NOTE: Consideration should be used for using the Express versions. Having over 5 users access the
express version and you may start to experience slower response times, more than 20 storage areas and
you may start to experience slower response times.

© 2018 Gerber Technology LLC All Rights Reserved.

Page 6 of 10
Support versions of SQL for AccuMark
Refer to the AccuMark Release Notes for up to date information on the supported versions of SQL and
their coordination with the versions of AccuMark software.

AccuMark Version SQL Version

AM V8.1 SQL Server 2000 or MSDE 2000

AM V8.2 SQL 2005 or SQL 2005 Express, SQL Server 2000, MSDE 2000
AM V8.3 SQL 2005 or SQL 2005 Express, SQL Server 2000
AM V8.3.1 SQL 2005 or SQL 2005 Express, SQL 2008 Express or SQL 2008
AM V8.4 SQL 2005, SQL 2005 Express, SQL 2008, and SQL 2008 Express
AM V8.5.0 SQL 2005, SQL 2005 Express, SQL 2008, and SQL 2008 Express
AM V8.5.1 SQL 2005, SQL 2005 Express, SQL 2008, and SQL 2008 Express
SQL 2005, SQL 2005 Express, SQL 2008, and SQL 2008 Express,
AM 9.0.0
SQL 2012, SQL 2012 Express
AM 10.0.0/10.1.0, SQL 2008 R2, and SQL 2008 R2 Express, SQL 2012, SQL 2012 Express, SQL
10.2.0 and 10.3.0 2014, SQL 2014 Express

SQL 2008 R2, and SQL 2008 R2 Express, SQL 2012 and SQL 2012 Express, SQL
AM 10.4.0
2014 and SQL 2014 Express, SQL 2016 and SQL 2016 Express

SQL 2008 R2, and SQL 2008 R2 Express, NOTE: Microsoft Extended Support End
Date is 7/9/2019
AM 11.0.0, 12.0.0, SQL Server 2012 and SQL 2012 Express with Service Pack 3
12.1.0 SQL 2014 and SQL 2014 Express
SQL 2016 and SQL 2016 Express
SQL 2017 Server and SQL 2017 Express
SQL 2008 R2, and SQL 2008 R2 Express, NOTE: Microsoft Extended Support End
Date is 7/9/2019
SQL Server 2012 and SQL 2012 Express with Service Pack 3. Extended support for
AM 12.2.0, 13.0.0 SQL Server 2012, including service pack 4, ends July 12, 2022
SQL 2014 and SQL 2014 Express
SQL 2016 and SQL 2016 Express
SQL 2017 Server and SQL 2017 Express

© 2018 Gerber Technology LLC All Rights Reserved.

Page 7 of 10
SQL Configuration for AccuMark
Once you have a SQL instance setup, you then tell AccuMark to connect to it through the AccuMark
Explorer’s File – Options – Configuration, select the SQL Support button.

© 2018 Gerber Technology LLC All Rights Reserved.

Page 8 of 10
SQL Support dialog definitions

Top section is to configure connections for SQL storage area databases:

• Device – non-editable field for SQL devices, referenced from AccuMark Explorer. You can fill in
any of the device rows
• DSN – usually not used, only for special connections where an ODBC connection has been
defined for the SQL instance
• SQL Server Name – the name of the SQL instance you want to connect to
• TCP Port – optional field allowing you to specify a port other than the default port that is used
by SQL. Corporations may configure an instance of the SQL Server Database Engine to listen on a
specific fixed port through the SQL Server Configuration Manager
• Server Path (optional) – location for the SQL server database(s) if they are in a location other
than the SQL default location
• Authentication – method used to connect to the SQL instance
o Windows – windows authentication uses the user’s windows login credentials
o SQL – SQL authentication is set up in the SQL instance for SQL user logins. This is mainly
used when wanting to set up specific SQL permissions for users
• Username and Password – used with SQL Authentication

Lower section is to configure an optional CAD Data Relational Database (RDBMS) that can optionally be
used to communicate with YuniquePLM V7 or earlier:

• DSN – usually not used, only for special connections where an ODBC connection has been
defined for the SQL instance
• Server – the name of the SQL instance you want to connect to where the RDBMS will be located
(does not have to be the same as used for the SQL storage areas)
• TCP Port – optional field allowing you to specify a port other than the default port that is used
by SQL. Corporations may configure an instance of the SQL Server Database Engine to listen on a
specific fixed port through the SQL Server Configuration Manager
• Authentication – method used to connect to the SQL instance
o Windows – windows authentication uses the user’s windows login credentials to
connect
o SQL – SQL authentication is set up in the SQL instance for SQL user logins. This is mainly
used when wanting to set up specific SQL permissions for users
• Username and Password – used with SQL Authentication
• Generate Images – option to generate thumbnail images for the marker, model and its piece
data that is being written into the RDBMS
• Images Location – by default, images go into c:\userroot\temp; users can alternately select
another location to use
• Annotation File for Image Generation – optionally enter the annotation to use for images

© 2018 Gerber Technology LLC All Rights Reserved.

Page 9 of 10
Additional SQL Functions
Various additional functions can be performed on SQL storage areas and are available from the
AccuMark Explorer: File – Options in the Storage Areas section.

This includes the ability to:

• Perform a check on all

or selected SQL storage
areas and/or subfolders

• Optionally run a Sync

which will update the
SQL storage areas
and/or subfolder data
into the CAD Relational
Database

• Upgrade a Pre V8.2

version of a SQL storage
area to a V8 or V9
storage area

• Run SQL Manager

SQL Manager is a separate

application that lets you
grant access right to SQL
storage areas and guides
you to setting up user’s
read and write permissions
for data item types. Refer to
the document “Read-Write
Controls” for details.

Additional information can be found in the AccuMark Online Help.

© 2018 Gerber Technology LLC All Rights Reserved.

Page 10 of 10