I added a new varchar based column to a table. Values for this new column for all new records are populated via my powerbuilder app. the powerbuilder app when saving the datawindow that has this new column calls a stored procedure that processes some data from the table I have modified but not necesaarrily the column I have added to the table. All this works fine, the problem I encounter when I take the values from one of the columns in this table that existed before my changes and copy that data to my new column. As soon as I do that and I try to bring data for this individual in my app the stored procedure that works fine suddenly goes into lala land and hangs. I cannot understand why, I have tried to recompile the procedure, made the new column so there are no null values in it, nothing works. Can someone help please? |
check if the stored procedure is blocking on another connection
I am actually running this app in my test env and I am running it against the local copy of the database. There are no other users and nobody else is connected to this database, I can surely chk for the blocked connection and thank u for your comments but i m not sure if that is the cause.
Are there any other symptoms? Does the CPU usage go up, indicating there is an infinite loop? Does the disk light come on and stay on, indicating that too many rows are being updated (possibly because there's something missing from a WHERE clause)?
Please show us the code for the stored procedure.
Here is the code for the procedure, can i put print statements in sqla procs like i used to do to debug my syabase procs: if yes is the syntax same as syabse:
ok: i found out the print statements, works the same way as sybase but if I have a print statement in my stored procedure and i execute it from interactive sql (sql central) where does the output get printed?
AFAIK it should show up in the Server's console window - as long as that is visible. If you're using a console log file (dbengX -o MyFile.txt), the output might appear in the log file, too.
Personally, I would recommend the MESSAGE statement which works similar to PRINT but gives much more control over the output destination - e.g. you can specify
and (depending on your client) that might be shown there. I don't know whether Sybase Central does show such messages but it could do so.