The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Why sysdba
Posted: 11 Aug 08 1:00 AM
|
So whats the reason we have to use the Sysdba login?
One of the guys asked in here and I didnt have the answer |
|
|
|
Re: Why sysdba
Posted: 11 Aug 08 9:47 AM
|
I think SalesLogix is internally designed in such a way , that it always use sysdba schema .
-Harendra |
|
|
|
Re: Why sysdba
Posted: 12 Aug 08 2:57 AM
|
Historical reasons ! In the beginning it was decided that, to avoid the need to setup each physical user with a database logon (especially under Oracle which didn't support windows authentication) then the security layer would be devolved to the application and the app itself would log in as the user "sysdba" (of course, it could equally have been slxuser, myfreakinid or anything else - but sysdba was used!). This makes sense in that you only have to worry/define one database login and all your users are then up and running. For the most part, aside from the install, as sysdba has full rights over the database, it can do anything (backup, schema changes etc) and this is all done through the provided tools. It was part of the design that you didn't need DBA skills - as DB changes, form changes etc. could be done by the average user. From a setup point of view this was ideal - as you could install and "set/forget" the database side !
|
|
|
|
Re: Why sysdba
Posted: 12 Aug 08 8:19 AM
|
But you have to keep in mind there is no reason to keep the standard password of sysdba
I know that wasn't the question, but I have seen a lot of SalesLogix installations with the default password!
Cheers, Thomas |
|
|
|
Re: Why sysdba
Posted: 12 Aug 08 9:09 AM
|
Originally posted by Thomas Aussem
But you have to keep in mind there is no reason to keep the standard password of sysdba
I know that wasn't the question, but I have seen a lot of SalesLogix installations with the default password!
Cheers, Thomas |
|
Yes, you can now.. in fact, v7.5 default is NOT the same as previous versions |
|
|
|
Re: Why sysdba
Posted: 12 Aug 08 4:52 PM
|
Hey Guys,
Thanks for the history and technical lesson and the preview of 7.5 , great answer
Marc
|
|
|
|
Re: Why sysdba
Posted: 12 Aug 08 6:47 PM
|
On the flip side, if users could login to the db as themselves it would be easier to troubleshoot issues at the db level (eg locks, users initiating long-running queries etc), because you can associate a specific user (not just SYSDBA) with a troublesome PID. But it isn't going to happen.
Phil |
|
|
|
Re: Why sysdba
Posted: 13 Aug 08 2:08 AM
|
True and true (you can use the macadress/machinename for that anyway ?!) |
|
|
|
Re: Why sysdba
Posted: 29 May 09 1:50 PM
|
I know that this is an old thread, but wanted to clarify something:
Even though we are using a single SQL login as an application login, we can still determine who owns the connections by looking at the machine associated with the Connection (off course, this wouldn't be applicable for a web client implementation, but then you could typically look at the UserID embeded on the Security Joins that are being run on the session that is causing problems).
|
|
|
|
Re: Why sysdba
Posted: 30 May 09 9:59 PM
|
The reason it had to be "SYSDBA" as opposed to some other ID (such as "SLXADMIN" or "OPENSESAME") was because of the need for Local Interbase compatibility on remote clients. For the early versions of SalesLogix, Local Interbase was used exclusively as the SQL-compliant database engine for remotes, and at the time, Local Interbase only allowed for one "super-user" account, the name of which was hard-coded into it - "SYSDBA." You could change the password, but the SLX folks wanted the remote client to be relatively easy to install, so they just stuck with the default.
Most of the people in Scottsdale who even remember this have long since moved on to other companies, but as you all know, I've been a Delphi programmer since version 1.0 - and Interbase has always shipped with Delphi, since the mid-90's. It was the path of least resistance, it had a small memory footprint, and it was essentially free for them to distribute, so that's why they used it. |
|
|
|