Download Database Tables

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Data center wikipedia , lookup

Versant Object Database wikipedia , lookup

Expense and cost recovery system (ECRS) wikipedia , lookup

Data model wikipedia , lookup

Entity–attribute–value model wikipedia , lookup

Database wikipedia , lookup

Data analysis wikipedia , lookup

Information privacy law wikipedia , lookup

3D optical data storage wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

Business intelligence wikipedia , lookup

Clusterpoint wikipedia , lookup

Data vault modeling wikipedia , lookup

Database model wikipedia , lookup

Transcript
What is a Virtual DataClass?
Applies To
• Data Connector 7.0
Question
What is a Virtual DataClass?
Answer
Virtual DataClasses is a brand new functionality in Connector 7.0. Here are a few key points:
·
A Virtual DataClass allows you to federate data into the Symantec CMDB. This is done by
creating a key from a resource type in the CMDB to an external source. You can then reference
data from the other data source without importing the data. This data can then be used in reports
and the views in the console. Depending on the way that you need to leverage the data, you can
now choose to federate the data by importing natively to the NS CMDB or federating by
referencing or linking to the data externally.
·
An example: I have collected Inventory and other data about a server using Inventory and
Monitor Solution and am storing that data in the NS database. I also have an external database
containing information about that same server. Rather than importing all the data from the other
database into the NS CMDB, I can create a virtual DataClass to reference the data in my external
source. You can then write reports and view the data in the Symantec Management Console.
This can now be done without the data being imported by using a virtual dataclass. In this
scenario, you can continue to use the other database as the source of truth while making sure that
the data that I am looking at remains always up to date. This is achieved by always looking ‘live’
into the other system for the data.
·
To use virtual data classes, you have to select a data source hosted by the same server hosting
the NS CMDB. However, there is a way to work around this “limitation” and it is to create a
Linked Server.
Here are steps to setup the database and Connector to use Virtual DataClasses:
1- Open SQL Server Management Studio and login to the server hosting the CMDB
2- Open the Server Objects folder
3- Right click on the Linked Servers folder and select New Linked Server.
4- Configure the following options (Using another Notification Server CMDB).
5- Open the Notification Server console, select Settings – All Settings.
6- Open the Notification Server – Resource and DataClass Settings.
7- Right click on the DataClasses folder and select New – Virtual DataClass
8- Configure options based on your database settings. (Created a test database with some test
tables and columns)
9- Click on Save Changes to create the Virtual DataClass.
Security
The “Create/Edit/Delete Virtual DataClass” privilege is required to create a new virtual
DataClass, edit an existing virtual DataClass or delete a virtual DataClass.
To edit an existing virtual DataClass, in addition to the above privilege, the user will also
require having Write permission on the virtual DataClass.
Database Tables
Data Connector does not have any additional tables to support Editable Virtual DataClass.
However, the underlying core support for view based DataClass made changes to the
DataClass table.
Database Table
Description
DataClass
There is one new column added to this existing table –
IsVirtual. This is a bit field. If 1, the DataClass is SQL view
based. If 0, the DataClass is a typical DataClass with
physical tables.
If IsVirtual, DataTableName column will contain the name
of the SQL view, instead of the physical table name.