Stored procedures sound like the best way to go.  They'll be the fastest,
too.  The only thing that may change that is if you have lots of
conditional processing.  Conditional processing in SQL requires the use of
a cursor, which will be a lot slower and more resource intensive on your db
server.

Keep in mind that depending on your DBMS and whether your web applications
are primarily reading or writing, you may be able to define a view that is
laid out the same as the old database so you don't have to rewrite the web
applications when the database changes.  Some DBMSs even allow you to
update and insert on a view.  YMMV.
|-------------------------+-----------------------------------------------|
|Eric A. Laney            |Of all the animals, the boy is the most        |
|Systems Engineer         |unmanageable.                                  |
|LAN Optimization Team    |                                               |
|Verizon Data Services    |                                               |
|Voice: 813.978.4404      |                                               |
|Pager: 888.985.8519      |                                               |
|-------------------------+-----------------------------------------------|





                                                                                       
                           
                    "Andrew                                                            
                           
                    Scott"               To:     SQL <[EMAIL PROTECTED]>           
                           
                    <andrewcs@tig        cc:                                           
                           
                    .com.au>             Subject:     Point me in the Right Direction  
                           
                                                                                       
                           
                    08/31/2001                                                         
                           
                    12:13 PM                                                           
                           
                    Please                                                             
                           
                    respond to                                                         
                           
                    sql                                                                
                           
                                                                                       
                           
                                                                                       
                           




I have taken over from a project where the DB is a mess, now the site is
live and I am redeveloping this and redesigning the DB to be more
compact than it is now.

Here is my question. I am not too up on StoredProcs. Or other methods,
so forgive me if I don't explain this well. But I am looking for a
method, that would be able to take a row from a current table and split
the data into multiple tables. I am assuming that this would be better
done in a SP, or would there be a better method?

Any help, advice or pointers would be grateful.


Regards,
Andrew Scott
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to