is it really update or maybe ?

Results 1 to 2 of 2

Thread: is it really update or maybe ?

  1. #1
    Join Date
    Dec 1969

    Default is it really update or maybe ?

    I have as ASP web pages with SQL server DB, and all db transactions are stored procedures, and all execution to these stored procedures are like this:<BR>Conn.execute sql ‘ if the stored procedure do not return any value<BR>And<BR>Set rs = Conn.execute (sql) ‘ if the stored procedure return values (read from DB)<BR>And these ASP pages have a heavy load (i.e. many hits or users at same time), my question is: <BR>1- doing like that make error in multi-user at same time ?<BR>2- is every update statement or delete statement will success ?<BR>3- I think in this way the cursor type is forward only (default) , is that will affect?<BR>If yes, what should it be?<BR>4- also what about the lock type, what should it be? Or let it as default ??<BR><BR>note: all the stored procedures are so simple , just simple select, insert, update or delete.<BR>I will be thankful if u help …<BR>

  2. #2
    Join Date
    Dec 1969

    Default RE: is it really update or maybe ?

    SQL Server handles locking for you. you shouldn&#039;t experience any concurrency errors. cursor type doesn&#039;t matter on updates, only on selects<BR><BR>as for locking, again, depends on the statement

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts