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 - 2002-10-11 : 11:08:10
|
| Yip Chun Yu writes "Hi guys,As far as I know, there are five ways to develop ASP app. with SQL servers.1. The traditional approach which get recordsets from the database and loop through them, outputting HTMl.2. Get recordsets fromt he database. Convert to XML and apply XSLT to output HTML.3. Get XML document directly from SQL server 2000 using XSD schema and apply XSLT to output HTML.4. Get XML document directly from SQL server 2000 using XSD schema and use server control to perform XSLT transform5. Get XML document directly from SQL server 2000 using XSD schema and use datagrid to display the table.I'm trying to move our application (the first approach) to XML enabled application. Since we will still using ASP rather than .NET framework, any best practices can u suggest?How about the SQLXML 3.0, Can I categorized it as the same as no. 3. approach?your comment/idea is very much appreciated. Thx in advance." |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2002-10-11 : 11:12:16
|
| What advantage are you giving yourself by going to XML? What are you trying to gain? Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-10-11 : 11:16:26
|
Well, there are certainly more than 5 ways to develop SQL Server web apps than the ones you listed.  You left out:2a. Get an ADO Recordset from the database and use GetRows or GetString to convert the data into an array, vastly speeding up performance and eliminating the need for XML. 6. Get XML version of data and use DOM methods to generate the HTML for the web page.I would say that 2, 3, 4, and 5 are really variations, not separate techniques at all. You're always dealing with XML data and have several choices for transforming it into an HTML stream.One suggestion I do have is to try to avoid XSL/T on the client side. The XML should be translated on the server and only HTML should be sent to the client. IE can do XML on the client side but other browsers have varying levels of support, and there really isn't much benefit to using client-side XML methods IMHO.I should also mention that none of these methods may be useful; it depends entirely on what your application is supposed to do. The latest and greatest programming techniques may be the WORST way to go about getting the application written. I've seen a number of XML apps that simply did not need it at all. They worked, but XML is not an end unto itself.It would help if you can describe WHAT your application(s) do and what features they need, it will help us help you better determine which method is best.Edited by - robvolk on 10/11/2002 11:18:04 |
|
|
|
|
|
|
|
|
ASP, SQL 2000 and XML