best practicies to validate a DB data

  • Thread starter Thread starter Fabiano
  • Start date Start date
F

Fabiano

Please,

i need to develop an webservice wich deploy a method that must do lots of
validation on a database. What can i do?

1. Create an Stored Procedure and inside of it validate everything and
return a error code to method and to user
or
2. Create lots of Stored Procedures wich one validate a specific data and
return a error code or else to user
or
3. Create lots of SQL statement and validate through a SQLCommand what i
need.


I fear the performance, best code, and state-of-the-art programm practicies.

tks in adv.

Fabiano
 
Hi,

1 would be the fastest
2 would be fast & flexible
3 would be even more flexible at cost of speed and centralization*

*depends who accesses the database and how
 
Hi Fabiano,

I have written an application generator that allows developers to
build business applications for MS SQL Server in just a fraction of
the time it used to take. All you need to do is create the tables and
answer a few yes or no questions about each table. The generator does
the rest.

Since it sounds like you are writing a stored procedure intensive
application, I believe that I have a tool that will be of enormous
help to you.

In order to demonstrate the my generator, I am issuing a promotion:

The Promotion will cost you nothing. All you have to do is send me the
T-SQL scripts necessary to create your tables and to define the
indexes and foreign key relationships or I can create them for you. My
generator will do the job, and I will deliver the finished and fully
functional UI.exe along with a finished and fully functional SQL
Server back end which contains a robust security system and a
comprehensive data dictionary, completely free of charge.

The benefits of this system are as follows:
1. The system generates true Client Server and Multi Tier
applications.
2. There is Zero Coding for common functionality such as;
Adds, Updates, and Deletes,
Creating application wide unique Ids for each record,
Maintaining an Audit trail for each table,
Posting to the general ledger,
Rolling down changes to dependent tables,
Cascading deletes,
Transactions and rollbacks,
Calling validation and business rule stored procedures,
Calling post processing stored procedures,
Importing and revalidating data,
Security,
Spell checking, language translation and more.
3. There is zero work of any kind for generation of data entry screens
and their lookups.
4. The back end is completely independent from the front end. You can
hit the database with any application or user interface and still be
sure that you have complete security and valid data.
5. Easy navigation through out the application. The generated user
interface is a familiar modern metaphor with a navigation tree on top
or at the side and data entry screens at the bottom. Also, the
generated user interface remembers customizations to each data entry
screen. This allows you to make sweeping changes to the interface, and
regenerate all data entry screens, without loosing your
customizations.
6. Consistent look and feel via OOP Inheritance and code generators.
7. Major changes in look and functionality are made in one place only,
and ripple down to all affected parts of the system without programmer
intervention. Again, this was accomplished with OOP inheritance and
also with code generators.
8. Users to have the ability to create queries and reports on the fly.
And the ability to save and reload those queries and reports in many
formats including Excel and HTML.
9. Users to have complete flexibility in customizing the look and feel
of the system. The extent to which each user can customize the
interface must be seen to be believed. This high level of
customizability creates a high degree of user acceptance.
10. Logical use of hot keys and local popup menus allow for easy mouse
free operation, permitting the user to keep his or her hands on the
keyboard, if the user so desires.
11. All custom code added to generated data entry screens and
generated backend code persists after regeneration.
12. Comes with a business rule generator
13. Comes with a data import utility
14. Comes with a data revalidation utility to use when you change your
business rules.

You all this without programming.
Please let me know how I can help
(e-mail address removed)

Key words: form generator, RAD, rapid application development, code
generator,
generative programming, application generator, backend generator, UI
generator, user interface generator, CASE tool, stored procedure
generator
 
Back
Top