shouldbe_q931 wrote:
I've inherited a Firebird database on Windows without any documentation, and I'm trying to document how it is setup if it is ever needed to be rebuilt.
Windows reports that the product version is 2.1.2.18118
Perfmon reports that fbserver is using 16 threads, which following dodument makes me presume it is "Superserver", but is there any other way of confirming ?
Helen Borrie answers:
The database and the server are two separate things. You can access a database from any model (Superserver, Classic or embedded, for v.2.1).
> Windows reports that the product version is 2.1.2.18118
That's the build number, i.e., Firebird 2.1, sub-release 2 (very old), build 18118.
> Perfmon reports that fbserver is using 16 threads, which following > http://www.firebirdsql.org/.../qsg2-classic-or-super.html > makes me presume it is "Superserver", but is there any other way of > confirming ?
Yes, probably SS. But the most conclusive way is to inspect the executable details in the Services applet. For SS, the executable is fbserver.exe; for Classic, fb_inet_server.exe.
The installation might also have the Guardian running (fbguard.exe) as a service. That's an option that will restart the Firebird SS service if it is stopped for some reason. It's unnecessary for SS running as a service (Windows services can be set up to do it anyway) but useful if, for some reason, SS is running as an application. Guardian should NOT be used with Classic.
If it is an embedded installation, that's different, as the server and client components are merged into one DLL and there won't be a service installed. Its "native" name is fbembed.dll but it is often renamed to fbclient.dll or gds32.dll and would be located in the same directory as the client application. The (possibly renamed) fbembed.dll is used in lieu of the client-only library, fbclient.dll.