tag:blogger.com,1999:blog-7098835175438692935.post8221152201680794241..comments2023-07-28T08:03:48.407-07:00Comments on Accounting++: Firebird: choosing an owner for database deploymentFulvio Senorehttp://www.blogger.com/profile/08431327146202932326noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7098835175438692935.post-26099737114497131772013-08-10T07:25:18.286-07:002013-08-10T07:25:18.286-07:00This a nice text indeed. The reasons why one would...This a nice text indeed. The reasons why one would think about db owner change are very well explained.<br /><br />I wrote another tool for db owner change, see DBUSubst in my web page http://www1.cuni.cz/~svejdar/?s=oact It is based on Thomas Steinmaurer ideas, but is more detailed and more general. And I believe it is simple to use. It can actually substitute one user for another, regardless whether one of them is a db owner. The new user inherits all objects that the old user owned, he grants all the privileges that the old user granted, and he is granted all the privileges that were granted to the old user.<br /><br />Best wishes, Vitezslav Svejdar<br />Anonymoushttps://www.blogger.com/profile/01971592280558980941noreply@blogger.comtag:blogger.com,1999:blog-7098835175438692935.post-83798653180066749882013-08-10T07:22:44.771-07:002013-08-10T07:22:44.771-07:00This comment has been removed by the author.Anonymoushttps://www.blogger.com/profile/01971592280558980941noreply@blogger.comtag:blogger.com,1999:blog-7098835175438692935.post-77276657520631221722012-02-26T12:35:09.989-08:002012-02-26T12:35:09.989-08:00A good summary!
Perhaps it's worth to be ment...A good summary!<br /><br />Perhaps it's worth to be mentioned that you can use the SYSDBA role trick to prevent SYSDBA from connecting. Others might say that this isn't bullet-proof if someone knows the Firebird database file internals and a HEX editor a bit, right, but at least you can dismiss SYSDBA connections issued "by accident", e.g. during development.<br /><br />Another option with Firebird 2.1 and higher is to create an ON CONNECT trigger with a user-defined condition (e.g. CURRENT_USER <> MYOWNER), which throws an exception and therefore aborts the connection process. Again, not bullet-proof, because e.g. isql has a command-line option to dismiss such database triggers.<br /><br />While FBOwnerMigrator has worked now for many years and a lot of people, I must say, it hacks system tables directly, which you should avoid whenever you can. But the whole process has been tested carefully and if you are interested in the tool, you have to request the download by sending an email with a notice that you have to use it on your own risks. ;-)<br /><br />Regards,<br />Thomas SteinmaurerThomas Steinmaurerhttps://www.blogger.com/profile/02455261978609299596noreply@blogger.com