Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-12-11 : 09:41:51
|
| Craig writes "Sql experts,I have read hundreds of posts here and elsewhere and I still do not "get it". I understand SQL, I can write some sql code, create queries joins, use Enterprise Manager. However I still do not understand how to translate all of this data power to the end users that I support. It seems to me that everything is static which makes more work for me on the back end when I would think that the situation should be reversed. As an example, I sort of understand the mechanics of creating a view but just cannot envision a scenario where it is useful. Most users want to not only view data but to update it or manipulate it in some way, so how does a view help with that. If I have a query that summarizes data for a year, it would make more sense to me to create a query that accepts input from the user so that the user could query any year. How do I pass that type of flexibility to the user using SQL and SQL server? That is one question of many that I have in terms of "transferring" this SQL power to my end users. It seems as if the only way is to learn programming as well? When we made the move from Access to an Sql backend I did not have the expectation of learning VB/Java as well as SQL!Yes, I am going to buy a book but I was just wondering how some of you DBAs out there actually interface with your users after all they are the ones who actually use/view/manipulate the data.Not a technical question but thanks anyway for any advice." |
|
|
JustinBigelow
SQL Gigolo
1157 Posts |
Posted - 2001-12-11 : 10:11:53
|
quote:
Craig writes "Sql experts,I have read hundreds of posts here and elsewhere and I still do not "get it". I understand SQL, I can write some sql code, create queries joins, use Enterprise Manager. However I still do not understand how to translate all of this data power to the end users that I support. It seems to me that everything is static which makes more work for me on the back end when I would think that the situation should be reversed. As an example, I sort of understand the mechanics of creating a view but just cannot envision a scenario where it is useful. Most users want to not only view data but to update it or manipulate it in some way, so how does a view help with that.
You can have updateable viewsquote:
If I have a query that summarizes data for a year, it would make more sense to me to create a query that accepts input from the user so that the user could query any year. How do I pass that type of flexibility to the user using SQL and SQL server?
What you are talking about would be implemented via a stored procedure which can accept input parameter (e.g. the year) and also return output parameters.quote:
That is one question of many that I have in terms of "transferring" this SQL power to my end users. It seems as if the only way is to learn programming as well?
To get the most out of SQL Server you will have to learn T-SQL. But it's worth it, you'll be amazed by the power and flexibility that SQL Server provides once you get the hang of it.quote:
When we made the move from Access to an Sql backend I did not have the expectation of learning VB/Java as well as SQL!Yes, I am going to buy a book but I was just wondering how some of you DBAs out there actually interface with your users after all they are the ones who actually use/view/manipulate the data.
IMHO, the users should never interface with SQL Server directly (via a tool like EM or Query Analyzer). It is up to the developers to provide a front end regardless of whether its VB, Java, a website, etc... If there is a seperate front end then the implementation of (Dynamic SQL, Stored procedures, updateable views) should be irrelevant to the end user.quote:
Not a technical question but thanks anyway for any advice."
Hope this helped.Justin |
 |
|
|
|
|
|
|
|
Sql Server 7.0 implementation advice