dbTalk Databases Forums  

Transactional Limitations?

sybase.public.sqlanywhere.general sybase.public.sqlanywhere.general


Discuss Transactional Limitations? in the sybase.public.sqlanywhere.general forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Orlando Ribeiro
 
Posts: n/a

Default Transactional Limitations? - 12-17-2003 , 11:45 AM






Greetings,

I am trying to execute a HUGE SQL Statement (around 40000
lines of code containing create tables, alter tables,
constraint declarations, triggers, stored procedures, etc
etc etc) inside a transaction.

What happens is that around 95% of the file, the application
crashes.

I am using ASA 9 for linux and the ASAProv OLEDB driver...

Could it be a limitation of any of them?

Thanks in advance,
Orlando Ribeiro

--

Reply With Quote
  #2  
Old   
Breck Carter [TeamSybase]
 
Posts: n/a

Default Re: Transactional Limitations? - 12-17-2003 , 12:23 PM






What is the exact symptom? ("crash" is a bit vague...

Breck

On 17 Dec 2003 09:45:09 -0800, Orlando Ribeiro wrote:

Quote:
Greetings,

I am trying to execute a HUGE SQL Statement (around 40000
lines of code containing create tables, alter tables,
constraint declarations, triggers, stored procedures, etc
etc etc) inside a transaction.

What happens is that around 95% of the file, the application
crashes.

I am using ASA 9 for linux and the ASAProv OLEDB driver...

Could it be a limitation of any of them?

Thanks in advance,
Orlando Ribeiro
--
bcarter (AT) risingroad (DOT) com
Mobile and Distributed Enterprise Database Applications
www.risingroad.com


Reply With Quote
  #3  
Old   
Orlando Ribeiro
 
Posts: n/a

Default Re: Transactional Limitations? - 12-18-2003 , 04:00 AM



Well... the error doesn't help much, it's a VB crash. After
analising the ASA log's i found no errors, the queries just
stop arriving. The problem seems to be "client-side".

I know now that it is not an ASA 9 limitation, because the
code executes perfectly on dbisql. This leaves 2 possible
reasons, (i think) both of them related to memory allocation
problems or limitations. The first is related to the ASAProv
OLEDB driver and the second to the Microsoft ADO library.

I'd like to hear your opinion on the first possibility. Is
it possible that a connection opened using the ASAProv OLEDB
driver has this kind of limitations?

I'll be testing the second possibility by changing the
database server...

Thanks,

Orlando Ribeiro

--
Quote:
What is the exact symptom? ("crash" is a bit vague...

Breck

On 17 Dec 2003 09:45:09 -0800, Orlando Ribeiro wrote:

Greetings,

I am trying to execute a HUGE SQL Statement (around 40000
lines of code containing create tables, alter tables,
constraint declarations, triggers, stored procedures, etc
etc etc) inside a transaction.

What happens is that around 95% of the file, the
application >crashes.

I am using ASA 9 for linux and the ASAProv OLEDB
driver...
Could it be a limitation of any of them?

Thanks in advance,
Orlando Ribeiro

--
bcarter (AT) risingroad (DOT) com
Mobile and Distributed Enterprise Database Applications
www.risingroad.com

Reply With Quote
  #4  
Old   
Chris Keating \(iAnywhere Solutions\)
 
Posts: n/a

Default Re: Transactional Limitations? - 12-18-2003 , 09:11 AM



What are the details of the VB crash. The crash details will indicate if the
crash involves the provider.

Since you are able to reproduce this problem, can you submit the test case
for review. If the problem is urgent, open a technical support case. If not,
you can opt to submit the issue as a bug.PLEASE read the important message
as it outlines the service levels of "report a bug' cases. If the service
levels are not suited, open a technical support case.

Within North America, you can reach Technical Support by calling
1-800-8SYBASE. If you are located outside of North America, you can find
the contact information for your local Sybase Support Center by going to the
Sybase home page at http://www.sybase.com, clicking on the "Support" link at
the top of the page, and then choosing "Support Centers" from the left hand
frame.

To report a bug for free, visit CaseXpress at
http://casexpress.sybase.com/cx/cx.stm. When submitting calls through
CaseXpress, please make sure to give an accurate description of the steps
you take to reproduce the bug, and include any files that may be needed
(database, source code) to reproduce the problem.


--

Chris Keating
Sybase Adaptive Server Anywhere Professional Version 8

************************************************** **************************
*
Sign up today for your copy of the SQL Anywhere Studio 9 Developer Edition
and try out the market-leading database for mobile, embedded and small to
medium sized business environments for free!

http://www.ianywhere.com/promos/deved/index.html

************************************************** **************************
*

iAnywhere Solutions http://www.iAnywhere.com

** Please only post to the newsgroup

** Whitepapers can be found at http://www.iAnywhere.com/developer
** EBFs can be found at http://downloads.sybase.com/swx/sdmain.stm
** Use CaseXpress to report bugs http://casexpress.sybase.com

************************************************** **************************
*

<Orlando Ribeiro> wrote

Quote:
Well... the error doesn't help much, it's a VB crash. After
analising the ASA log's i found no errors, the queries just
stop arriving. The problem seems to be "client-side".

I know now that it is not an ASA 9 limitation, because the
code executes perfectly on dbisql. This leaves 2 possible
reasons, (i think) both of them related to memory allocation
problems or limitations. The first is related to the ASAProv
OLEDB driver and the second to the Microsoft ADO library.

I'd like to hear your opinion on the first possibility. Is
it possible that a connection opened using the ASAProv OLEDB
driver has this kind of limitations?

I'll be testing the second possibility by changing the
database server...

Thanks,

Orlando Ribeiro

--
What is the exact symptom? ("crash" is a bit vague...

Breck

On 17 Dec 2003 09:45:09 -0800, Orlando Ribeiro wrote:

Greetings,

I am trying to execute a HUGE SQL Statement (around 40000
lines of code containing create tables, alter tables,
constraint declarations, triggers, stored procedures, etc
etc etc) inside a transaction.

What happens is that around 95% of the file, the
application >crashes.

I am using ASA 9 for linux and the ASAProv OLEDB
driver...
Could it be a limitation of any of them?

Thanks in advance,
Orlando Ribeiro

--
bcarter (AT) risingroad (DOT) com
Mobile and Distributed Enterprise Database Applications
www.risingroad.com



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.