Is it a reliable unique identifier for a running instance of dbsrv*.exe?


asked 15 Feb '20, 09:16

Breck%20Carter's gravatar image

Breck Carter
accept rate: 20%

Wouldn't the ProcessID be a more natural database server property to distinguish several instances on the same host?

(16 Feb '20, 08:50) Volker Barth
Replies hidden

Yes, that works for applications like Foxhound, which puts ProcessId into the connection names it uses when connecting to target databases...

...but ProcessId was introduced in V12.

SELECT @@VERSION, PROPERTY ( 'ProcessID' ), PROPERTY ( 'OmniIdentifier' );


FYI a non-GUID OmniIdentifier was introduced in V8 but not mentioned in the Help until V9.

The GUID version of OmniIdentifier was introduced in V10.

SELECT @@VERSION, PROPERTY ( 'ProcessID' ), PROPERTY ( 'OmniIdentifier' );





(16 Feb '20, 11:01) Breck Carter

It appears to be a GUID generated at runtime the first time the value is needed. It appears to be used to avoid circular connection attempts via OMNI (ie, prevent a server from using a remote table that is actually in the same server). It should serve your purposes.

permanent link

answered 15 Feb '20, 12:34

John%20Smirnios's gravatar image

John Smirnios
accept rate: 37%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 15 Feb '20, 09:16

question was seen: 721 times

last updated: 17 Feb '20, 07:25

Related questions