Wrox Programmer Forums
|
SQL Server ASP Discussions about ASP programming with Microsoft's SQL Server. For more ASP forums, see the ASP forum category.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server ASP section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old August 24th, 2008, 02:35 PM
Friend of Wrox
 
Join Date: Jun 2008
Posts: 1,649
Thanks: 3
Thanked 141 Times in 140 Posts
Default

1. should i use views instead of writing direct queries to code.
2. or should i use stored procedures to fetch data


YES!

Use SP's for both. Even if the SP does that same thing as a View, it just allows you to make changes, later, with more flexibility.

3. should i use any sql account (guest sort of) to fire sql queries. who do not have any update or delete or insert rights.

Yes, that's a good idea, too.

4. from where i can get resources for proper sql server handling.
SQLTeam.com is a good place to start. They specialize in SQL Server.

5. and is it possible to access those pages which are on server, but do not have any direct hyperlink visibility.
Yes. Absolutely. If a person can guess the page name, they can access the page. It's better to protect *ALL* pages. If you have some private pages, protect them with a password-based login.
 
Old August 25th, 2008, 06:30 AM
Authorized User
 
Join Date: Feb 2006
Posts: 67
Thanks: 7
Thanked 0 Times in 0 Posts
Send a message via Yahoo to beetle_jaipur
Default

Thankx sir,

that was a true help for me to get rid of this error. honestly, i am very thankful to you for those valuable support and help

ashok sharma










Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.