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.

SQL Anywhere 11 database size

3 posts in General Discussion Last posting was on 2009-05-22 18:03:25.0Z
Michael Ray Posted on 2009-05-19 20:43:05.0Z
Reply-To: "Michael Ray" <ray6@SoftwareForToday.com>
From: "Michael Ray" <ray6@SoftwareForToday.com>
Newsgroups: ianywhere.public.general
Subject: SQL Anywhere 11 database size
Lines: 14
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a1319d9$1@forums-1-dub>
Date: 19 May 2009 13:43:05 -0700
X-Trace: forums-1-dub 1242765785 10.22.241.152 (19 May 2009 13:43:05 -0700)
X-Original-Trace: 19 May 2009 13:43:05 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7571
Article PK: 5976

SQL Anywhere 11 database size.
- When I create a database and specify a 4MB database size, a database
file of 6MB is created. Why the difference in size? It didn't do that with
version 10 (specify 4MB, get 4MB).

--

Thank you.
Michael


Josh Savill [Sybase] Posted on 2009-05-20 12:58:49.0Z
From: "Josh Savill [Sybase]" <no_spam_jsavill_no_spam@sybase.com>
Organization: Sybase iAnywhere
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: SQL Anywhere 11 database size
References: <4a1319d9$1@forums-1-dub>
In-Reply-To: <4a1319d9$1@forums-1-dub>
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: <4a13fe89$1@forums-1-dub>
Date: 20 May 2009 05:58:49 -0700
X-Trace: forums-1-dub 1242824329 10.22.241.152 (20 May 2009 05:58:49 -0700)
X-Original-Trace: 20 May 2009 05:58:49 -0700, vip152.sybase.com
Lines: 16
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7572
Article PK: 5983

Michael,

I've created CR #573160 for this issue. You can monitor the readme files in the EBF fixes to see if
the issue has been resolved in a future EBF.

--
Joshua Savill
Sybase Inc. - Product Manager

Michael Ray wrote:
> SQL Anywhere 11 database size.
> - When I create a database and specify a 4MB database size, a database
> file of 6MB is created. Why the difference in size? It didn't do that with
> version 10 (specify 4MB, get 4MB).
>


Josh Savill [Sybase] Posted on 2009-05-22 18:03:25.0Z
From: "Josh Savill [Sybase]" <no_spam_jsavill_no_spam@sybase.com>
Organization: Sybase iAnywhere
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: SQL Anywhere 11 database size
References: <4a1319d9$1@forums-1-dub> <4a13fe89$1@forums-1-dub>
In-Reply-To: <4a13fe89$1@forums-1-dub>
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: <4a16e8ed@forums-1-dub>
Date: 22 May 2009 11:03:25 -0700
X-Trace: forums-1-dub 1243015405 10.22.241.152 (22 May 2009 11:03:25 -0700)
X-Original-Trace: 22 May 2009 11:03:25 -0700, vip152.sybase.com
Lines: 16
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7577
Article PK: 5979

Michael,

This issue has been fixed. Use CR #573160 to reference the readme file in the EBF fix. This fix
should be in any EBF with a number higher than 2249.

--
Joshua Savill
Sybase Inc. - Product Manager

Josh Savill [Sybase] wrote:
> Michael,
>
> I've created CR #573160 for this issue. You can monitor the readme files
> in the EBF fixes to see if the issue has been resolved in a future EBF.
>