Geek asks and answers

SQL for end users: pros and cons

Once, far away in a distant galaxy, I witnessed a discussion between several developers. The subject was if it would be nice to give end users access to the production SQL server (MS SQL 2008) to enable them to create their own reports against their own data.

It was a request from business people - "Our customers want to create custom reports."

The guy who suggested this claimed that:

  • He was able to provide users read-only access through a set of permissions and make the system completely secure.
  • SQL was originally an "end user" and may be right now.
  • Having permissions to execute SQL queries, users will be able to do what they do not want disturbing developers and support.

Other guys who were against this stated:

  • MS SQL crashes quite easily, even max. limited access.
  • Providing SQL and database structure to end users is not a good idea; this is a bad design.
  • SQL is too complicated for non-programmers, and therefore, it will not make their life easier.

What do you think about giving end users access to SQL?

Thank you in advance!

+3
source share
7 answers

, , . , , .

, . - , , . , "" , /.

, -, , . SQL? .

+5

. , .

, , , , .

, , . , . , , .

+2

, . sql, ? (Crystal Reports), .

, , , , .

.

EDIT: . , .

+1

, , , . SQL, , , . - ( MS SQL) / . , . , ( ) . Pro tip: , .

, , , -, . , , , , , - .

+1

, . ( ), ? .

, , .

+1

, . , . , .

, , .

, . , , , , , .

+1

, , . SQL - .

. SQL Server . , , , (, , ), , .

Perhaps it is surprising that even if Microsoft introduced the isolation mode of snapshots 7 years ago, it still seems that more often it seems that the systems go into production with it turned off (by default READ COMMITTED without SI). Therefore, before allowing users to access your production systems, you may need to make these changes and perform some re-checks and refactoring.

0
source

More articles:


All Articles