subject:"SV\: SV\: SV\: \[development\-axapta\] SQL Server 2000\: since some weeks DB\-size grows"

Re: SV: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size grows

2004-01-20 Thread jesper.joergensen

Title: Melding

Mit freundlichen Grüßen / Best regards / Med venlig Hilsen
Jesper
J¢rgensenConsulting
mailto: [EMAIL PROTECTED]
Aston
Business SolutionsGmbHKettelerstr. 3-11D-97222 Würzburg-RimparGermany
Tel.+49-9365-8075-0Fax+49-9365-8075-300
Work with a Winner. Aston Business Solutions--Microsoft Global Partner of The
Year 2003No one is more
committed to your success than Aston Business Solutions. As the world's leading
Microsoft Business Solutions partner, we maintain a 92% customer retention rate
and count more than 5,000 distribution, manufacturing, healthcare, and
service-based companies among our loyal clients. Learn how we can help
you achieve your potential.
http://www.astongroup.deThe information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or taking
any action in reliance upon this information by persons or entities other than
the intended recipient is prohibited. If you received this in error, please
contact the sender and delete the material from any
computer.

Original
Message

processed
by Tobit InfoCenter

Subject:
SV: SV: SV:
[development-axapta] SQL Server 2000: since some weeks DB-size grows
(19-Jan-2004 21:28)

From:
[EMAIL PROTECTED]

To:
[EMAIL PROTECTED](and
1 other)

HiAccording to your answer on tadorna regarding SP on
MSSQL server that you recomend SP3a you should upgrade the info on Technet.
The matrix below is cut and paste from Technet this afternoon.it states
that Axapta 3.0 only can use SP2.
Axapta 2.5 introduces support for SQL Server 7.0 Service Pack 2 and SQL
Server 2000.
Below are the SQL Server ODBC Driver requirements for Axapta 2.5:

Axapta Version
Target Database
Required ODBC component versions

Axapta 2.5
SQL Server 7.0 SP1/SP2
ODBC components tested are: 3.70.06.90,
3.70.08.20

Axapta 2.5
SQL Server 2000
ODBC components tested are:
2000.80.19.4
Axapta 3.0 requires SQL Server 2000.
Below are the SQL Server ODBC Driver requirements for Axapta 3.0:

Axapta Version
Target Database
Required ODBC component versions

Axapta 3.0
SQL Server 2000 SP2
ODBC components tested are: 2000.80.194,
2000.80.528

Med vennlig hilsenTorgeir
TomsSystemkonsulent Teknisk
IT==Good
Judgment Comes From Experience. Experiences Comes From Bad
Judgment.=-Opprinnelig
melding-Fra: Kim Truelsen (MICROSOFT BUSINESS SOLUTIONS) [mailto:[EMAIL PROTECTED]]Sendt:
19. januar 2004 10:04Til: [EMAIL PROTECTED]Emne: RE:
SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size
growsOkay. Nice to know, but our recommendation is also SP3a. The
problem seems not to be related to Axapta then, but my described scenarios
could also cause similar problems.Have a nice day.Med venlig
hilsen / Best regardsKim TruelsenMicrosoft DenmarkTuborg
Boulevard 12DK-2900 HellerupPhone + 45 44 89 01 00Mobile + 45
29 49 99 58mailto:[EMAIL PROTECTED]From:
juepeterberlin [mailto:[EMAIL PROTECTED]]Sent:
19. januar 2004 09:58To: [EMAIL PROTECTED]Subject:
Re: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size
growsHi Kim,installing SP3a for SQL-Server solved the
problem.I don't believe it was one of the reasons below, because
page-densitydropped continually and not in leaps. One table
(salesparmline) didneed 800 MB and 600 MB from this was "unused" (looked
with sp_spaceused).At the end 1,5 new records (statistically) in
salesparmline led to thecreation of a new page for salesparmline though 20
maxsize-recordsshould need less than one page.re 1. no
"leaps"re 2. that would 1 GB more and no exponentially growth, in fact
we had3,6 GB and a growth of 400-600 MB per day at last.re 3.
indexes, that doens't explain the "unused" for salesparmlinere 4. that
didn't happen, user data input was "normal" and no externaldata import
took place.regardsJürgen Peter(CAM
Berlin)--- In [EMAIL PROTECTED],
"Kim Truelsen \(MICROSOFTBUSINESS SOLUTIONS\)" [EMAIL PROTECTED]
wrote: Hi all I can maybe give you
some explanation why your database size is
growing 1.
Sometimes changes in the data model are leading thesynchronization
mechanism to create a shadow "X897" table. All datafrom the original table
is copied to this table and the old onedropped and recreated. The
be

SV: SV: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size grows

2004-01-20 Thread Torgeir Toms

Title: Melding





Hi
This 
is ok, but they should upgrade Technet as long as they have a "Database 
Compability" tab.



Med 
vennlig hilsen
Torgeir 
Toms
Systemkonsulent 
Teknisk IT

==
Good 
Judgment Comes From Experience. Experiences Comes From Bad Judgment.
=


  
  -Opprinnelig melding-Fra: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  Sendt: 20. januar 2004 09:21Til: 
  [EMAIL PROTECTED]Emne: Re: SV: SV: SV: 
  [development-axapta] SQL Server 2000: since some weeks DB-size 
  grows
  
  
  
  
  Hi Torgeir,
  I have attached the release notes from Axapta 3.0 SP2. For this version 
  anyhow you should use SP3a for the SQL Server.
  
  Jesper
  
  
  
  

  
  

  Original 
  Message

  processed by Tobit 
  InfoCenter
  

  Subject:
    SV: SV: 
      SV: [development-axapta] SQL Server 2000: since some weeks DB-size 
  grows (19-Jan-2004 21:28)
  

  From:
[EMAIL PROTECTED]
  

  To:
[EMAIL PROTECTED](and 
  1 other)

HiAccording to your answer on tadorna regarding SP on 
MSSQL server that you recomend SP3a you should upgrade the info on Technet. 
The matrix below is cut and paste from Technet this afternoon.it states 
that Axapta 3.0 only can use SP2.
Axapta 2.5 introduces support for SQL Server 7.0 Service Pack 2 and 
SQL Server 2000.
Below are the SQL Server ODBC Driver requirements for Axapta 2.5: 


  
  
Axapta Version
Target Database
Required ODBC component versions
  
Axapta 2.5
SQL Server 7.0 SP1/SP2
ODBC components tested are: 3.70.06.90, 
3.70.08.20
  
Axapta 2.5
SQL Server 2000
ODBC components tested are: 
2000.80.19.4 
Axapta 3.0 requires SQL Server 2000.
Below are the SQL Server ODBC Driver requirements for Axapta 3.0: 


  
  
Axapta Version
Target Database
Required ODBC component versions
  
Axapta 3.0
SQL Server 2000 SP2
ODBC components tested are: 2000.80.194, 
2000.80.528





Med vennlig hilsenTorgeir 
TomsSystemkonsulent Teknisk 
IT==Good 
Judgment Comes From Experience. Experiences Comes From Bad 
Judgment.=-Opprinnelig 
melding-Fra: Kim Truelsen (MICROSOFT BUSINESS SOLUTIONS) [mailto:[EMAIL PROTECTED]]Sendt: 
19. januar 2004 10:04Til: [EMAIL PROTECTED]Emne: 
RE: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size 
growsOkay. Nice to know, but our recommendation is also SP3a. 
The problem seems not to be related to Axapta then, but my described 
scenarios could also cause similar problems.Have a nice 
day.Med venlig hilsen / Best regardsKim 
TruelsenMicrosoft DenmarkTuborg Boulevard 12DK-2900 
HellerupPhone + 45 44 89 01 00Mobile + 45 29 49 99 58mailto:[EMAIL PROTECTED]From: 
juepeterberlin [mailto:[EMAIL PROTECTED]]Sent: 
19. januar 2004 09:58To: [EMAIL PROTECTED]Subject: 
Re: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size 
growsHi Kim,installing SP3a for SQL-Server solved the 
problem.I don't believe it was one of the reasons below, because 
page-densitydropped continually and not in leaps. One table 
(salesparmline) didneed 800 MB and 600 MB from this was "unused" (looked 
with sp_spaceused).At the end 1,5 new records (statistically) in 
salesparmline led to thecreation of a new page for salesparmline though 
20 maxsize-recordsshould need less than one page.re 1. no 
"leaps"re 2. that would 1 GB more and no exponentially growth, in 
fact we had3,6 GB and a growth of 400-600 MB per day at last.re 
3. indexes, that doens't explain the "unused" for salesparmlinere 4. 
that didn't happen, user data input was "normal" and no externaldata 
import took place.regardsJürgen Peter(CAM 
Berlin)--- In 
[EMAIL PROTECTED], "Kim Truelsen \(MICROSOFTBUSINESS 
SOLUTIONS\)" [EMAIL PROTECTED] wrote: Hi 
all I can maybe give you some explanation 
why your database size is growing 
1. Sometimes changes in the data model are 
leading thesynchronization mechanism to create a shadow "X897" table. 
All datafrom the original table is copied to this table and the old 
onedropped and recreated. The behaviour was very normal in 2.5, 
butdoesn't show up that much in 3.0. The space of

SV: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size grows

2004-01-19 Thread Torgeir Toms

Title: Melding





HiAccording to your answer on tadorna regarding SP on MSSQL 
server that you recomend SP3a you should upgrade the info on Technet. The matrix 
below is cut and paste from Technet this afternoon.it states that Axapta 3.0 
only can use SP2.
Axapta 2.5 introduces support for SQL Server 7.0 Service Pack 2 and SQL 
Server 2000.
Below are the SQL Server ODBC Driver requirements for Axapta 2.5: 


  
  
Axapta Version
Target Database
Required ODBC component versions
  
Axapta 2.5
SQL Server 7.0 SP1/SP2
ODBC components tested are: 3.70.06.90, 
3.70.08.20
  
Axapta 2.5
SQL Server 2000
ODBC components tested are: 
2000.80.19.4 
Axapta 3.0 requires SQL Server 2000.
Below are the SQL Server ODBC Driver requirements for Axapta 3.0: 


  
  
Axapta Version
Target Database
Required ODBC component versions
  
Axapta 3.0
SQL Server 2000 SP2
ODBC components tested are: 2000.80.194, 
  2000.80.528





Med vennlig hilsenTorgeir 
TomsSystemkonsulent Teknisk 
IT==Good 
Judgment Comes From Experience. Experiences Comes From Bad 
Judgment.=-Opprinnelig 
melding-Fra: Kim Truelsen (MICROSOFT BUSINESS SOLUTIONS) [mailto:[EMAIL PROTECTED]]Sendt: 
19. januar 2004 10:04Til: [EMAIL PROTECTED]Emne: RE: 
SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size 
growsOkay. Nice to know, but our recommendation is also SP3a. The 
problem seems not to be related to Axapta then, but my described scenarios could 
also cause similar problems.Have a nice day.Med venlig hilsen / 
Best regardsKim TruelsenMicrosoft DenmarkTuborg Boulevard 
12DK-2900 HellerupPhone + 45 44 89 01 00Mobile + 45 29 49 99 
58mailto:[EMAIL PROTECTED]From: 
juepeterberlin [mailto:[EMAIL PROTECTED]]Sent: 
19. januar 2004 09:58To: [EMAIL PROTECTED]Subject: Re: 
SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size 
growsHi Kim,installing SP3a for SQL-Server solved the 
problem.I don't believe it was one of the reasons below, because 
page-densitydropped continually and not in leaps. One table (salesparmline) 
didneed 800 MB and 600 MB from this was "unused" (looked with 
sp_spaceused).At the end 1,5 new records (statistically) in 
salesparmline led to thecreation of a new page for salesparmline though 20 
maxsize-recordsshould need less than one page.re 1. no 
"leaps"re 2. that would 1 GB more and no exponentially growth, in fact 
we had3,6 GB and a growth of 400-600 MB per day at last.re 3. 
indexes, that doens't explain the "unused" for salesparmlinere 4. that 
didn't happen, user data input was "normal" and no externaldata import took 
place.regardsJürgen Peter(CAM 
Berlin)--- In [EMAIL PROTECTED], 
"Kim Truelsen \(MICROSOFTBUSINESS SOLUTIONS\)" [EMAIL PROTECTED] 
wrote: Hi all I can maybe give you some 
explanation why your database size is growing 
1. Sometimes changes in the data model are leading 
thesynchronization mechanism to create a shadow "X897" table. All 
datafrom the original table is copied to this table and the old 
onedropped and recreated. The behaviour was very normal in 2.5, 
butdoesn't show up that much in 3.0. The space of the table X897 
(where897 is the number of the table) is the same as the original 
andtherefore the used database space will rise. 
2. Cross References. If you updated your cross 
references doingupdate or later. It can explain the expansion of your DB. 
(Around 1 GB) 3. Indexes. If you have 
added a lot of indexes on large tables. Itmight also explain 
something. 4. Import of external data and 
deletion afterwards of the data fromthe 
tables??? I hope that might give you some 
clue. Med venlig 
hilsen / Best regards Kim 
Truelsen Microsoft Denmark 
Tuborg Boulevard 12 DK-2900 
Hellerup Phone + 45 44 89 01 00 
Mobile + 45 29 49 99 58 mailto:[EMAIL PROTECTED]... mailto:[EMAIL PROTECTED] 
 From: Torgeir Toms [mailto:[EMAIL PROTECTED]...] Sent: 18. 
januar 2004 17:27 To: [EMAIL PROTECTED] 
Subject: SV: SV: SV: [development-axapta] SQL Server 2000: sincesome weeks 
DB-size grows exponentially Very Good - should 
find out more on this. Maybe Kim Trulsen on thislist from MBS can throw some 
light on this ?? Med vennlig hilsen Torgeir 
Toms Systemkonsulent Teknisk IT 
== Good Judgment Comes From Experience. 
Experiences Comes From BadJudgment. 
= -Opprinnelig 
melding- Fra: juepeterberlin [mailto:[EMAIL PROTECTED]...] 
Sendt: 18. januar 2004 14:49 Til: 
[EMAIL PROTECTED] Emne: Re: SV: SV: 
[development-axapta] SQL Server 2000: since someweeks DB-size grows 
exponentially well whatever the background reason your 
tip worked out fine, many thanks again regards 
Jürgen Peter (CAM Berlin) --- In 
[EMAIL PROTECTED], "Torgeir Toms" 
[EMAIL PROTECTED]

SV: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size grows exponentially

2004-01-18 Thread Torgeir Toms





Very Good - should find out more on this. Maybe Kim Trulsen on this list from MBS can throw some light on this ??


Med vennlig hilsen
Torgeir Toms
Systemkonsulent Teknisk IT
 
==
Good Judgment Comes From Experience. Experiences Comes From Bad Judgment.
=

-Opprinnelig melding-
Fra: juepeterberlin [mailto:[EMAIL PROTECTED] 
Sendt: 18. januar 2004 14:49
Til: [EMAIL PROTECTED]
Emne: Re: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size grows exponentially


well whatever the background reason your tip worked out fine,

many thanks again
regards
Jürgen Peter
(CAM Berlin)



--- In [EMAIL PROTECTED], Torgeir Toms 
[EMAIL PROTECTED] wrote:
 No
 Not realy. Perhaps MSTechnet can help you
 Med vennlig hilsen
 Torgeir Toms
 Systemkonsulent Teknisk IT
 _
 
 ==
 Good Judgment Comes From Experience. Experiences Comes From Bad 
Judgment.
 =
 
 -Opprinnelig melding-
 Fra: juepeterberlin [mailto:[EMAIL PROTECTED] 
 Sendt: 12. januar 2004 22:44
 Til: [EMAIL PROTECTED]
 Emne: Re: SV: [development-axapta] SQL Server 2000: since some 
weeks DB-size grows exponentially
 
 
 Thanks very much Torgeir,
 
 we will try that.
 
 Do you know more about the background of this error?
 
 regards
 Jürgen Peter
 (CAM Berlin GmbH)
 
 
 --- In [EMAIL PROTECTED], Torgeir Toms 
 [EMAIL PROTECTED] wrote:
  i have experienced that - its an error in SQL Server. I applyed 
 SP3a. It fixed it
  
  
  Med vennlig hilsen
  Torgeir Toms
  Systemkonsulent Teknisk IT
  ==
  Good Judgment Comes From Experience. Experiences Comes From Bad 
 Judgment.
  =
  
  -Opprinnelig melding-
  Fra: Preston A. Larimer [mailto:[EMAIL PROTECTED] 
  Sendt: 12. januar 2004 16:05
  Til: [EMAIL PROTECTED]
  Emne: RE: [development-axapta] SQL Server 2000: since some weeks 
 DB-size grows exponentially
  
  
  Looks like you have 3 gigs of unused space, more than likely 
 during the upgrade your database grew in size due to the 
transaction 
 logs and it hasn't shrunk back yet. If your maintenance jobs and 
 backups are set correctly to shrink the database you should see 
the 
 size deflate on the next scheduled maintenance run or you could 
 always try to shrink the files manually from the enterprise 
manager, 
 back up first though.
  
  -Preston
  
  -Original Message-
  From: juepeterberlin [mailto:[EMAIL PROTECTED] 
  Sent: Monday, January 12, 2004 9:51 AM
  To: [EMAIL PROTECTED]
  Subject: [development-axapta] SQL Server 2000: since some weeks 
DB-
 size grows exponentially
  
  Hi all,
  
  since some weeks our DB-size went from 2GB to 5.5 GB although 
the 
  user data input was more or less the same.
  
  sp_spaceused on the DB results in 
  
  database_size 5620.00 MB
  unallocated space 50.03 MB 
  reserved 5375968 KB
  data 1516608 KB
  index_size 818368 KB
  unused 3040992 KB 
  
  We use Axapta 3.0 SP2 with SQL Server 2000. There is a 
 possibility, 
  that this growth began with going from SP1 to SP2.
  
  Does someone know anything how such unusual database growth and 
  such an high unused factor could happen?
  
  
  regards
  Jürgen Peter
  (CAM Berlin GmbH)
  
  
  
  
  
  
  Yahoo! Groups Links
  · To visit your group on the web, go to:
  http://groups.yahoo.com/group/development-axapta/
  
  · To unsubscribe from this group, send an email to:
  [EMAIL PROTECTED]
  
  · Your use of Yahoo! Groups is subject to the Yahoo! 
Terms 
 of Service. 
  
  
  
  
  Yahoo! Groups Links
  
  To visit your group on the web, go to:
  http://groups.yahoo.com/group/development-axapta/
  
  To unsubscribe from this group, send an email to:
  [EMAIL PROTECTED]
  
  Your use of Yahoo! Groups is subject to the Yahoo! Terms of 
 Service.
 
 
 Yahoo! Groups Sponsor
 ADVERTISEMENT
 
 
 
 
 
 
 Yahoo! Groups Links
 
 To visit your group on the web, go to:
 http://groups.yahoo.com/group/development-axapta/
 
 To unsubscribe from this group, send an email to:
 [EMAIL PROTECTED]
 
 Your use of Yahoo! Groups is subject to the Yahoo! Terms of 
Service.


Yahoo! Groups Sponsor
ADVERTISEMENT






Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
 
To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
 
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 






Yahoo! Groups Links

To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/
To unsubscribe from this group, send an email to:[EMAIL PROTECTED]
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Re: SV: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size grows

SV: SV: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size grows

SV: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size grows

SV: SV: SV: [development-axapta] SQL Server 2000: since some weeks DB-size grows exponentially

4 matches

Site Navigation

Mail list logo

Footer information