User profile for kzumbusch – Support

Activity overview Badges (0) Posts (1) Comments (1)

Comments

Changing the default database type is okay and understandable. And the update should work well for our release build server and other installations that are already set up to use a SQL Server database. But on my development workstation I'm not able to use 6.11 out of the box which was possible with 6.8. With 6.11 I need access to a SQL Server with my Windows credentials to setup Smart Assembly using the UI. As the newer versions of Visual Studio (>= 2012) no longer provide a SQL Server Express instance but use localdb instead there is no way to setup Smart Assembly locally without additional effort. Accessing a remote SQL Server with SQL Server login credentials is also not possible. My regular user account has no access to any SQL Server in our network. I have a separate administrative account as I am the main SQL Server administrator in our company. Automatically using an account with this range of permissions is neither allowed in our company nor advisable from a security point of view. If any application requires sysadmin privileges for a database server it is off the market for us. I'm working in a rather small company where employees fill out multiple roles. I'm a full time developer and the main database admin for the SQL Servers of our development team. But please consider scenarios where the developer has to ask a database administrator to provide a database for an application. The database administrator will probably select a database name like "zumbuschk-smartassembly" to allow multiple databases for the same application. In this case I would not be able to configure Smart Assembly from the UI. I've been a database administrator for Microsoft SQL Server and Oracle database servers for quite some time and applications or setups requiring sysadmin privileges on a database server are the worst nightmare you can encounter. I've even seen setups that explicitly ask for the password of the database user "sa" as the username was hard coded in the setup or automatically create new database users without any hints. That is why I react quite allergic to applications that require huge security violations in database setups. Requiring sysadmin privileges and automatically creating databases with a default name are two things I will never accept in any application. Kind regards Kay Zumbusch / comments

Changing the default database type is okay and understandable. And the update should work well for our release build server and other installations that are already set up to use a SQL Server datab...

0 votes

Total activity: 3
Last activity: February 06, 2025 00:43
Member since: February 06, 2025 00:43

Following: 0 users
Followed by: 0 users
Votes: 0
Subscriptions: 1