|
| XAL3.55 / SQl 2005 / XAL Database exceeds size |
 |
Wed, 26 Mar 2008 08:11:12 -070 |
Hi Team,
I am running XAL 3.55 against SQl 2005. Since the migration to 2005 XAl says
that XAL ecceeds licensed DB size. (Datenbank überschreitet erlaubte Grösse.)
Is there a switch to turn that erroneus message and delay off?
Best
Wolfgang
--
|
| Post Reply
|
| Re: XAL3.55 / SQl 2005 / XAL Database exceeds size |
 |
Fri, 28 Mar 2008 02:05:57 -070 |
On Mar 26, 3:11 pm, axconsultant
<axconsult...@discussions.microsoft.com> wrote:
> Hi Team,
>
> I am running XAL 3.55 against SQl 2005. Since the migration to 2005 XAl
says
> that XAL ecceeds licensed DB size. (Datenbank überschreitet erlaubte
Grösse.)
>
> Is there a switch to turn that erroneus message and delay off?
>
> Best
>
> Wolfgang
> --
> axconsultant
Sounds to me like you need to run the sqldatasize script.
I have included the script below if you can't find it.
#LOCALMACRO.SQLDbSize Str2Num(SysInfo(6070,'')) #ENDMACRO
#LOCALMACRO.SQLDbSizeUpdate Str2Num(SysInfo(6071,''))
#ENDMACRO
REAL &datasize
SET &datasize=#SQLDBSIZE
|
| Post Reply
|
| Re: XAL3.55 / SQl 2005 / XAL Database exceeds size |
 |
Fri, 28 Mar 2008 03:54:00 -070 |
MrPye,
thx for the swift contribution.
I forgot to mention that I did that via the SQL Menu. :-)
So actual SQL ist 10+G and XAL calced size is 4+GB.
What I mean is that in CH,DE and AT the DB-Size costing has long been
abolished.
As the DB is growing (real 10+ GB - according to XAL 4+GB) We get these
anoying and useless messages.
I would like to avoid asking MS to recieve an updated Code Letter with like
10+ GB of DB Size since this is a real hazzle hence drags ressources. :-)
Best
Wolfgang
--
axconsultant
"MrPye" wrote:
> On Mar 26, 3:11 pm, axconsultant
> <axconsult...@discussions.microsoft.com> wrote:
> > Hi Team,
> >
> > I am running XAL 3.55 against SQl 2005. Since the migration to 2005
XAl says
> > that XAL ecceeds licensed DB size. (Datenbank überschreitet erlaubte
Grösse.)
> >
> > Is there a switch to turn that erroneus message and delay off?
> >
> > Best
> >
> > Wolfgang
> > --
> > axconsultant
>
> Sounds to me like you need to run the sqldatasize script.
> I have included the script below if you can't find it.
>
> #LOCALMACRO.SQLDbSize Str2Num(SysInfo(6070,'')) #ENDMACRO
> #LOCALMACRO.SQLDbSizeUpdate Str2Num(SysInfo(6071,''))
> #ENDMACRO
> REAL &datasize
>
> SET &datasize=#SQLDBSIZE
> set &datasize=#SQLDBSIZEUPDATE
|
| Post Reply
|
| Re: XAL3.55 / SQl 2005 / XAL Database exceeds size |
 |
Thu, 3 Apr 2008 08:23:01 -0700 |
Hi Wolfgang,
we had the sam problem - only a modified codeletter from MS helped...
Paul
"axconsultant" wrote:
> MrPye,
>
> thx for the swift contribution.
> I forgot to mention that I did that via the SQL Menu. :-)
> So actual SQL ist 10+G and XAL calced size is 4+GB.
>
> What I mean is that in CH,DE and AT the DB-Size costing has long been
> abolished.
>
> As the DB is growing (real 10+ GB - according to XAL 4+GB) We get these
> anoying and useless messages.
>
> I would like to avoid asking MS to recieve an updated Code Letter with like
> 10+ GB of DB Size since this is a real hazzle hence drags ressources. :-)
>
> Best
>
> Wolfgang
>
>
> --
> axconsultant
>
>
> "MrPye" wrote:
>
> > On Mar 26, 3:11 pm, axconsultant
> > <axconsult...@discussions.microsoft.com> wrote:
> > > Hi Team,
> > >
> > > I am running XAL 3.55 against SQl 2005. Since the migration to
2005 XAl says
> > > that XAL ecceeds licensed DB size. (Datenbank überschreitet
erlaubte Grösse.)
> > >
> > > Is there a switch to turn that erroneus message and delay off?
> > >
> > > Best
> > >
> > > Wolfgang
> > > --
> > > axconsultant
> >
> > Sounds to me like you need to run the sqldatasize script.
> > I have included the script below if you can't find it.
> >
> > #LOCALMACRO.SQLDbSize Str2Num(SysInfo(6070,'')) #ENDMACRO
> > #LOCALMACRO.SQLDbSizeUpdate Str2Num(SysInfo(6071,''))
> > #ENDMACRO
> > REAL &datasize
> >
> > SET &datasize=#SQLDBSIZE
> > set &datasize=#SQLDBSIZEUPDATE
|
| Post Reply
|
| Re: XAL3.55 / SQl 2005 / XAL Database exceeds size |
 |
Thu, 3 Apr 2008 10:25:00 -0700 |
I suspected that.
Thank you very much anyway.
Wolfgang
--
axconsultant
"Paul P" wrote:
> Hi Wolfgang,
> we had the sam problem - only a modified codeletter from MS helped...
> Paul
>
> "axconsultant" wrote:
>
> > MrPye,
> >
> > thx for the swift contribution.
> > I forgot to mention that I did that via the SQL Menu. :-)
> > So actual SQL ist 10+G and XAL calced size is 4+GB.
> >
> > What I mean is that in CH,DE and AT the DB-Size costing has long been
> > abolished.
> >
> > As the DB is growing (real 10+ GB - according to XAL 4+GB) We get
these
> > anoying and useless messages.
> >
> > I would like to avoid asking MS to recieve an updated Code Letter with
like
> > 10+ GB of DB Size since this is a real hazzle hence drags ressources.
:-)
> >
> > Best
> >
> > Wolfgang
> >
> >
> > --
> > axconsultant
> >
> >
> > "MrPye" wrote:
> >
> > > On Mar 26, 3:11 pm, axconsultant
> > > <axconsult...@discussions.microsoft.com> wrote:
> > > > Hi Team,
> > > >
> > > > I am running XAL 3.55 against SQl 2005. Since the migration
to 2005 XAl says
> > > > that XAL ecceeds licensed DB size. (Datenbank überschreitet
erlaubte Grösse.)
> > > >
> > > > Is there a switch to turn that erroneus message and delay
off?
> > > >
> > > > Best
> > > >
> > > > Wolfgang
> > > > --
> > > > axconsultant
> > >
> > > Sounds to me like you need to run the sqldatasize script.
> > > I have included the script below if you can't find it.
> > >
> > > #LOCALMACRO.SQLDbSize Str2Num(SysInfo(6070,''))
#ENDMACRO
> > > #LOCALMACRO.SQLDbSizeUpdate Str2Num(SysInfo(6071,''))
> > > #ENDMACRO
> > > REAL &datasize
> > >
> > > SET &datasize=#SQLDBSIZE
> > > set &datasize=#SQLDBSIZEUPDATE
|
| Post Reply
|
|
|
|
|
|
|
|
|
|