Date Compression

Hi all,

My client has a Production Database running Native Navision 3.7, which is 
now 130GB. To speed up the response time and searching, they want to run Date 
Compression on that DB.

I read in some articles that if the database is customized, then Date 
Compression must not be done. My database is heavily customized and I want 
some method to retrieve back space on the server to make the response time 
faster for the client.

Can I try with Date Compression in this case? What could be other solutions 
to make my system faster?

PS: We are already using the best server hardware but since there are 96 
users working together, the database needs to be shrunk to improve 
performance.

----------- 
Ninan Vineet George
Technical Manager
Infostar Business Solutions,

"Ninan Vineet George" wrote:

> Hi all,
> My client has a Production Database running Native Navision 3.7, which is 
> now 130GB. To speed up the response time and searching, they want to run
Date 
> Compression on that DB.
> I read in some articles that if the database is customized, then Date 
> Compression must not be done. My database is heavily customized and I want

> some method to retrieve back space on the server to make the response time

> faster for the client.
> Can I try with Date Compression in this case? What could be other solutions

> to make my system faster?
> PS: We are already using the best server hardware but since there are 96 
> users working together, the database needs to be shrunk to improve 
> performance.
> 
> ----------- 

130GB with Native Navision 3.7??!! mmmmm
What about SQL Server 2005? You could have a more than one file DB...

Hi Ninan,

As we've told you on mibuso and DUG, Date Compression is not the way to fix 
performance problems. What you need to do is get an expert involved who can 
take a look at your system and determine whether you are set up correctly.

First of all, just because you have "the best server hardware" does
not mean 
that it is set up correctly. With all due respect, I've heard that claim 
many times, and many times I've seen bad set up choices cause severe 
performance problems.

A database that is 130GB is not necessarily bad, it's how those 130GB are 
filled in. The most likely candidate is that your tables are overindexed, 
and you need the tables to be tuned. This means to eliminate indexes and 
SIFT levels before doing anything else. Also you will probably need to 
reindex the tables and get rid of fragmentation. Then there are likely many 
empty SIFT records to get rid of as well.

If you keep asking about date compression, sooner or later someone will tell 
you that is a good idea. Do yourself a favor though and listen to the advice 
you have already been given and get someone involved.
-- 
Daniel Rimmelzwaan
MVP Dynamics NAV
www.risplus.com


"Ninan Vineet George"
<NinanVineetGeorge@discussions.microsoft.com> wrote in 
message news:E0AA5153-023E-4C3E-B3DD-9B0DF3B6BC26@microsoft.com...
> Hi all,
>
> My client has a Production Database running Native Navision 3.7, which is
> now 130GB. To speed up the response time and searching, they want to run 
> Date
> Compression on that DB.
>
> I read in some articles that if the database is customized, then Date
> Compression must not be done. My database is heavily customized and I want
> some method to retrieve back space on the server to make the response time
> faster for the client.
>
> Can I try with Date Compression in this case? What could be other 
> solutions
> to make my system faster?
>
> PS: We are already using the best server hardware but since there are 96
> users working together, the database needs to be shrunk to improve
> performance.
>
> ----------- 
> Ninan Vineet George
> Technical Manager
> Infostar Business Solutions,
> Bangkok 10260.