Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Connection to existing databases
January 24, 2020
15:49, EET
Avatar
jsessig
Member
Members
Forum Posts: 4
Member Since:
January 24, 2020
sp_UserOfflineSmall Offline

I just installed the OPC UA Historian and want to connect to an existing database in a Microsoft SQL instance. The MS SQL instance is reachable through network connection and does not reside on the same server as the OPC UA Historian.

When testing the connection, I get an error message.
“Could not connect: CREATE DATABASE permission denied in database ‘master’.”
And with that error message, it is not possible to proceed.

Is there any chance to configure the connection to an existing database, where the user will have CREATE DATABASE permission, but, due to company guidelines, not on the database master?

Regards,
Jochen

January 28, 2020
17:54, EET
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 983
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline

Hi,

Generally the application needs/assumes full access and thus it is not guaranteed if it will work properly if not. So basically the answer is “No”.

You could try manually creating database named “ProsysOPCUAHistorian” to see if it works. Still the user must have permissions to run “IF NOT EXISTS (SELECT name FROM master.dbo.sysdatabases WHERE name = N’ProsysOPCUAHistorian’) CREATE DATABASE ProsysOPCUAHistorian”.

January 29, 2020
11:52, EET
Avatar
jsessig
Member
Members
Forum Posts: 4
Member Since:
January 24, 2020
sp_UserOfflineSmall Offline

Hi,

thank you for the answer.
A skeleton database, where OPC UA Historian should store the data already exists in the MS SQL instance, but wth a generic name.

So the OPC UA Historian database must be named “ProsysOPCUAHistorian”? Using another name for the database is not possible?
If this database with the required name exists in my Microsoft SQL instance I can proceed with the configuration?

January 29, 2020
12:51, EET
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 983
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline

The application needs to be in full control of the database, and that is the only tested scenario. It will create and manage it’s own tables. And to clarify, it wont work with existing tables etc., it must actually be able to create them (and modify/delete them etc. everything). It uses liquibase internally to version control the database such that a future version of the application can rely and the database schema being compatible.

Currently that database name is hardcoded. Given the other requirements I’m not sure it would make that much sense for it to be configurable, but we will think that in the future.

January 29, 2020
13:56, EET
Avatar
jsessig
Member
Members
Forum Posts: 4
Member Since:
January 24, 2020
sp_UserOfflineSmall Offline

Okay.
Renaming the database to “ProsysOPCUAHistorian” did the job.

Connection is established and tables are created in the database.

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 518

Currently Online:
21 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 135

pramanj: 86

Francesco Zambon: 81

rocket science: 77

ibrahim: 76

Sabari: 62

kapsl: 57

gjevremovic: 49

Xavier: 43

fred: 41

Member Stats:

Guest Posters: 0

Members: 680

Moderators: 16

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1467

Posts: 6260

Newest Members:

sagarchau, elviralangwell4, Donnavek, Eddiefauth, DonaldPooma, fidelduke938316, Jan-Pfizer, DavidROunc, fen.pang@woodside.com, aytule

Moderators: Jouni Aro: 1009, Otso Palonen: 32, Tuomas Hiltunen: 5, Pyry: 1, Petri: 0, Bjarne Boström: 983, Heikki Tahvanainen: 402, Jukka Asikainen: 1, moldzh08: 0, Jimmy Ni: 26, Teppo Uimonen: 21, Markus Johansson: 42, Niklas Nurminen: 0, Matti Siponen: 321, Lusetti: 0, Ari-Pekka Soikkeli: 5

Administrators: admin: 1