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 |
|
karuna
Aged Yak Warrior
582 Posts |
 Posted - 2002-05-16 : 02:15:30
|
| Hi All, I have a small doubt...When I do coding of sql in asp pages I thought I'am working with back end.But one of my friend says Backend programming of SQL is different.Its not just you write your query in an asp page...Is it so???...If thats the case what is SQL backend programming...If some one can give me a picture it would be help full...Thanks.KarunakaranKarunakaranDon't wait for things to happen,Make them to happen... |
|
|
khalik
Constraint Violating Yak Guru
443 Posts |
Posted - 2002-05-16 : 03:41:23
|
| AFAIK writing SQL stament is not Back end Programing ... never...ur SP... Functions...Triggers... all that stuff... may be some else can be more in detail======================================Ask to your self before u ask someone |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-05-16 : 08:29:15
|
| The terminology might be a little different in various countries, but here's how I understand front-end and back-end:Front-end is what is displayed to the end-user, whoever is using the program. For a web page, it is the HTML that the browser interprets to display what they see. In a VB/C++ standard application, it is the form, input boxes and message boxes that the user interacts with. The code that works to support these screens is part of the front-end, even though the user cannot see it.Back-end is usually a database of some kind, or some other server, that operates without DIRECT user intervention. The user would interact with the front-end, and the front-end would communicate with the back-end and give it commands to execute.If your code contains a SQL statement of some kind, you're manipulating the back-end. You might GENERATE the SQL on the front-end, but it is EXECUTED on the back-end. IMHO any SQL statement is considered back-end programming.I wouldn't worry too much about making distinctions between front-end and back-end, it's all programming! |
|
|
|
rihardh
Constraint Violating Yak Guru
307 Posts |
Posted - 2002-05-16 : 08:39:45
|
| As robvolk said, don't worry too much. My terminology of back-end programming is writing code that manipulates the back-end (DB). Because the SW that we use in a back-end (server) allows us to write code directly to objects which recide on the server (procedures, functions,...) it is easyer to differ the front from the back-end. In my opinnion front-end programming includes everything that is in a .exe file on a client computer. |
|
|
|
joldham
Wiseass Yak Posting Master
300 Posts |
Posted - 2002-05-16 : 08:41:18
|
What your friend may have been refering to is that instead of building a SQL statement in your asp code, you can create a Stored Procedure in the database and pass it parameters. In other words, instead of buildingstrSQL = "SELECT contacts FROM tbl_contacts WHERE contactid =" & Request("contactid")you could build a stored procedureCreate Procedure usp_contacts@contactid intASSELECT contacts FROM tbl_contacts WHERE contactid = @contactidwith your asp page as follows:strSQL = "exec usp_contacts " & Request("contactid")This would allow you to leave the data access to the SQL developers and the webpage programming to the web developers (if your company is so lucky to be so big that the two are not the same).While this is a simple example, you can imagine what it would be like to build a 100 line query in asp. Putting this code in a stored procedure would leave 1 line of code in the asp page instead of 100 lines. Also, it allows you to make changes on the server end, without having to make changes to the webpage or any other application that runs this same procedure. The SQL logic is now on the back-end instead of being generated by the coding in an asp page.I agree with robvolkquote:
If your code contains a SQL statement of some kind, you're manipulating the back-end. You might GENERATE the SQL on the front-end, but it is EXECUTED on the back-end. IMHO any SQL statement is considered back-end programming. I wouldn't worry too much about making distinctions between front-end and back-end, it's all programming!
Jeremy |
|
|
|
simondeutsch
Aged Yak Warrior
547 Posts |
Posted - 2002-05-16 : 10:05:10
|
| If front end/back end is synonymous with client/server, then code in an ASP page or .exe that manipulates the server is still considered front end, because it adds to the size of the client. If your data manipulation was all in code, no stored procs, views, etc, you have a fat client, and SQL Server's capabilities are wasted.Sarah Berger MCSD |
|
|
|
karuna
Aged Yak Warrior
582 Posts |
Posted - 2002-05-21 : 13:46:34
|
| Thanks everybody for the replies.....KarunakaranDon't wait for things to happen,Make them to happen... |
|
|
|
henrikop
Constraint Violating Yak Guru
280 Posts |
Posted - 2002-05-21 : 16:13:58
|
Just a last thought:If I explain an application I say it's two parts:1) User Interface (IMHO Front end)2) Database (Back end)Everything that has to do with the DATA (Select statements, SP's, Triggers, INSERT INTO, etc.) I reckon as back-end wherever the code is executed. Everything that has to do with the lay-out moving between forms, button's and such, I reckon as front-end. However, sometimes lay-out is stored in a table (some HTML statements) and that makes the difference so small...It's just a modern word invented by an article writer and after that it started to live it's own live. I dislike abstract words like that without being specific what you mean.I use to play Bullsh*t bingo. You write five 'modern' words on a paper before you go to a meeting. Whenever the last of the five words on your list are spoken you shout out 'Bullsh*t!!' and you win the Bingo (and get in trouble, hehe).Think of words like:Sub-optimalisation, Transparancy, Forthcoming insight, hectic, and so on....  .Henri~~~SQL is nothing, writing it everything. |
|
|
|
|
|
|
|
|
Back end Programing ???