Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Migration ASE 12.5.4 to ASE 15.7

3 posts in General Discussion Last posting was on 2013-02-25 20:09:30.0Z
Karthik M Posted on 2013-02-06 12:54:01.0Z
Sender: 7a61.51125187.846930886@sybase.com
From: Karthik M
Newsgroups: sybase.public.ase.general
Subject: Migration ASE 12.5.4 to ASE 15.7
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <51125269.7abc.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 6 Feb 2013 04:54:01 -0800
X-Trace: forums-1-dub 1360155241 172.20.134.41 (6 Feb 2013 04:54:01 -0800)
X-Original-Trace: 6 Feb 2013 04:54:01 -0800, 172.20.134.41
Lines: 10
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31693
Article PK: 1307472

ALL,

I have included ORDER BY Clause & INSENSITIVE keyword as
part of migration work. I would like to test the procedure
to ensure the output result order is same between two
versions.

what are all the test cases that i need to prepare apart
from running the procedure on both the version and capturing
the resultset i.e PRE vs POST ?


Rob V Posted on 2013-02-06 19:54:11.0Z
From: Rob V <rob@sypron.nl>
Reply-To: rob@sypron.nl
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: Migration ASE 12.5.4 to ASE 15.7
References: <51125269.7abc.1681692777@sybase.com>
In-Reply-To: <51125269.7abc.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <5112b4e3$1@forums-1-dub>
Date: 6 Feb 2013 11:54:11 -0800
X-Trace: forums-1-dub 1360180451 172.20.134.152 (6 Feb 2013 11:54:11 -0800)
X-Original-Trace: 6 Feb 2013 11:54:11 -0800, vip152.sybase.com
Lines: 60
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31694
Article PK: 1307486


On 06-Feb-2013 13:54, Karthik M wrote:
> ALL,
>
> I have included ORDER BY Clause & INSENSITIVE keyword as
> part of migration work. I would like to test the procedure
> to ensure the output result order is same between two
> versions.
>
> what are all the test cases that i need to prepare apart
> from running the procedure on both the version and capturing
> the resultset i.e PRE vs POST ?
>

You should run tests that are as representative as possible of the
real-life situation in your production system. That means: use a
life-size test database, test your queries with realistic
parameters/search argument values, and test with at least as many
concurrently active users as your production system would. Nobody here
can tell you what these all mean, but I would expect you or someone in
your organisation to have the required information.
In addition, you should look at the query plans for your queries in
different circumstances so as to be able to address any issues that
might be causes by a change in the query plan.
When migrating to ASE 15, it is strongly recommended to carefully review
the following documents:

- Optimizer 15 best practices whitepaper:
`http://www.sybase.com/detail?id=1056243

- Compatibility Mode: http://www.sybase.com/detail?id=1063556

- Required SQL Code Changes for ASE 15 migration:
http://www.sybase.com/detail?id=1063534

- ASE 15 migration checklist: http://www.sybase.com/detail?id=1058962


As for your remark about the keywords you included: I don't think that
is enough information for anyone to be able to guess exactly what your
system is doing... so if you want more feedback, you will need to be
more specific and describe more detail.

--
HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Professional DBA for Sybase ASE, IQ, Replication Server

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE"
"The Complete Sybase IQ Quick Reference Guide"
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter: @rob_verschoor
Sypron B.V., The Netherlands | Chamber of Commerce 27138666
-----------------------------------------------------------------


Sid. Posted on 2013-02-25 20:09:30.0Z
Sender: 4db2.512bc1a3.1804289383@sybase.com
From: Sid.
Newsgroups: sybase.public.ase.general
Subject: Re: Migration ASE 12.5.4 to ASE 15.7
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <512bc4fa.4f21.1681692777@sybase.com>
References: <5112b4e3$1@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 25 Feb 2013 12:09:30 -0800
X-Trace: forums-1-dub 1361822970 172.20.134.41 (25 Feb 2013 12:09:30 -0800)
X-Original-Trace: 25 Feb 2013 12:09:30 -0800, 172.20.134.41
Lines: 83
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31713
Article PK: 1307918


> On 06-Feb-2013 13:54, Karthik M wrote:
> > ALL,
> >
> > I have included ORDER BY Clause & INSENSITIVE keyword as
> > part of migration work. I would like to test the
> > procedure to ensure the output result order is same
> > between two versions.
> >
> > what are all the test cases that i need to prepare apart
> > from running the procedure on both the version and
> > capturing the resultset i.e PRE vs POST ?
> >
>
> You should run tests that are as representative as
> possible of the real-life situation in your production
> system. That means: use a life-size test database, test
> your queries with realistic parameters/search argument
> values, and test with at least as many concurrently
> active users as your production system would. Nobody here
> can tell you what these all mean, but I would expect you
> or someone in your organisation to have the required
> information. In addition, you should look at the query
> plans for your queries in different circumstances so as
> to be able to address any issues that might be causes by
> a change in the query plan. When migrating to ASE 15, it
> is strongly recommended to carefully review the following
> documents:
>
> - Optimizer 15 best practices whitepaper:
> `http://www.sybase.com/detail?id=1056243
>
> - Compatibility Mode:
> http://www.sybase.com/detail?id=1063556
>
> - Required SQL Code Changes for ASE 15 migration:
> http://www.sybase.com/detail?id=1063534
>
> - ASE 15 migration checklist:
> http://www.sybase.com/detail?id=1058962
>
>
> As for your remark about the keywords you included: I
> don't think that is enough information for anyone to be
> able to guess exactly what your system is doing... so if
> you want more feedback, you will need to be more specific
> and describe more detail.
>
> --
> HTH,
>
> Rob V.
> ----------------------------------------------------------
> ------- Rob Verschoor
>
> Certified Professional DBA for Sybase ASE, IQ, Replication
> Server
>
> Author of Sybase books (order online at
> www.sypron.nl/shop): "Tips, Tricks & Recipes for Sybase
> ASE" "The Complete Sybase IQ Quick Reference Guide"
> "The Complete Sybase ASE Quick Reference Guide"
> "The Complete Sybase Replication Server Quick Reference
> Guide"
>
> rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter:
> @rob_verschoor Sypron B.V., The Netherlands | Chamber of
> Commerce 27138666
> ----------------------------------------------------------
> -------

Here is what you could do. We are doing the same.
1. You need one 1254 and another 157x servers in db sync in
QA or DEV environment.
2. Capture exec proc or necessary SQL statements from
application log or thru Audit from PROD.
3. Write Java or Unix Shell scripts that would execute
indevidual SQL one at a time on both servers ( QA or DEV )
and redirects the output to seperate files.
4. Compare and log the exception for analysis.

Good Luck.

Sid.