![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Breck, I don't know what your position is with Sybase or if your information is an 'official' source. I have two entire systems (production and internal) we went to V11 with. Now, we are in a panic because we have two big issues - internal customers having issues and external customers having issues. You may be here to 'help' - but right now, we are in a predictement where this whole thing is completely frustrating. I'm highly doubting it's fragmentation issues because it's two database, two entirely different systems all behaving in the same manner. It may be changes in the way the database handles things because of our application development tool. Getting support for that tool is worse and close to being unsupported - and you really don't know where they stand on anything. It's far easier to put everything back to the way it was and just leave it alone. My problem is that V9 GPF's when using WIN7 so now I'm in a catch - 22. We give Sybase close to 100K a year in sales --- I'm not going to be placed in some support tree and go through some help line tree. I curse the day I went to V11. But, the issues are probably a combination of our compiler application and something new that Sybase V11 is doing, and the way it is fetching records. For example ... the compiler (RAD TOOL) does a select x from y order by keyfield desc - to find the next primary key. It was extremely fast in V9, but it seems like it is 1 to 5 seconds on V11. I know that "select first" is sub-second, but we do not control what the driver does in the application - again, it is a RAD tool. I have no clue why SQA 11 would handle this different than SQA 9 but it does ... with a huge lag. There are other screens which have slowed to a crawl. There has got to be a way to migrate a DB back to V9. I'm trying it now - but now my SCJVIEW is GPF'ing adn not even allowing me to create an empty database. Why can't I just create an empty database. Run the unload statements over it and it puts it all back. I tried it and my tables are fine, my security is fine, everything is fine - the ONLY problem is the FORMAT TEXT statement is wrong. I went through the file with ULEDIT and pulled that all out. Then I went to recreate the file and SCJVIEW GPF's and won't create an empty database. It's yet another issue now I'm dealing with - and I shouldn't for the price of Sybase SQL Anywhere. -Robert |
#12
| |||
| |||
|
|
Hi, It doesn't like this: FORMAT TEXT Meaning, when it loads the data, it doesn't like that. I tried it with unload statements, and it didn't like QUOTE I tried it with SQL statements, and it doesn't like "FORMAT TEXT" -Robert |
#13
| |||
| |||
|
|
Hi, I really don't want to be placed on hold or sit there and explain my issues. My nerves are already shot. Now its more issues. I am creating the V9 database and when it does it, SCJVIEW GPF's on my WIN2008 server. I do utilities / create database, put in all the parms, press Finish. It creates the .db files and then it says "initializing ultralite" something or other, and then just GPF's on my box. So, I can't even create a blank database. I don't feel like discussing this with someone from Sybase Support Center. They aren't programmers. -Robert "Volker Barth" <No_VBarth (AT) Spam_GLOBAL-FINANZ (DOT) de> wrote in message news:4ae1d2d6$1 (AT) forums-1-dub (DOT) .. V9 uses FORMAT ASCII instead of FORMAT TEXT. I would recommend tech support, too, if you have the time and nerves... Regards Volker Robert Paresi wrote: Hi, It doesn't like this: FORMAT TEXT Meaning, when it loads the data, it doesn't like that. I tried it with unload statements, and it didn't like QUOTE I tried it with SQL statements, and it doesn't like "FORMAT TEXT" -Robert |
#14
| |||
| |||
|
#15
| |||
| |||
|
|
Hi, Could you please look at this and tell me if this shows an issue. This is a database which has an index both DESC and ASC order of Invoice Number: SELECT * FROM BILLDET ORDER BY INVOICENUMBER RunTime Estimate: 0.32643 Actual: 1.4581 SELECT * FROM BILLDET ORDER BY INVOICENUMBER DESC RunTime Estimate: 2.5823 Actual: 4.098 Would there be a setting or a change from V9 to V11 which slows down DESCENDING result sets? That's my first question. -Robert |
#16
| |||
| |||
|
|
Hi, Could you please look at this and tell me if this shows an issue. This is a database which has an index both DESC and ASC order of Invoice Number: SELECT * FROM BILLDET ORDER BY INVOICENUMBER RunTime Estimate: 0.32643 Actual: 1.4581 SELECT * FROM BILLDET ORDER BY INVOICENUMBER DESC RunTime Estimate: 2.5823 Actual: 4.098 Would there be a setting or a change from V9 to V11 which slows down DESCENDING result sets? That's my first question. -Robert |
#17
| |||
| |||
|
#18
| |||||||
| |||||||
|
|
I don't know what your position is with Sybase or if your information is an 'official' source. |
|
You may be here to 'help' - but right now, we are in a predictement where this whole thing is completely frustrating. |
|
I'm highly doubting it's fragmentation issues because it's two database, two entirely different systems all behaving in the same manner. It may be changes in the way the database handles things because of our application development tool. Getting support for that tool is worse and close to being unsupported - and you really don't know where they stand on anything. |
|
It's far easier to put everything back to the way it was and just leave it alone. My problem is that V9 GPF's when using WIN7 so now I'm in a catch - 22. |
|
We give Sybase close to 100K a year in sales --- I'm not going to be placed in some support tree and go through some help line tree. |
|
For example ... the compiler (RAD TOOL) does a select x from y order by keyfield desc - to find the next primary key. It was extremely fast in V9, but it seems like it is 1 to 5 seconds on V11. I know that "select first" is sub-second, but we do not control what the driver does in the application - again, it is a RAD tool. I have no clue why SQA 11 would handle this different than SQA 9 but it does ... with a huge lag. |
|
There has got to be a way to migrate a DB back to V9. |
![]() |
| Thread Tools | |
| Display Modes | |
| |