Remote database cutting - New server

[steve_v...@my-deja.com]

Ok we have our new server... Quad processor, 500 mhz.. 2 gig memory.
Our database is 1.5 gig or so large.
How in the heck are we getting Insufficient memory errors when we try
to cut databases on certain tables?? The entire database can fit into
memory! The Synch server is not running and this is occuring at about
8:00pm when no one is on the system.
I attempted the cut on the main SQL server which has the Quad proc etc.
Any ideas what I can change to help this?? No subscription rules apply
as he gets it all (Manager)

Sent via Deja.com http://www.deja.com/
Before you buy.

[Kari]

I can't wait to hear answers on this. We have the same problem and I
ususally have to cut the history down for those users who have too
large a number of accounts. This is especially hellish when we have to
cut a new remote office database.
It is driving me crazy. It is interesting to see that hardware is
obviously not the problem.
Kari Storm
NewsBank, inc.

In article <8kikli$3p9$1...@nnrp1.deja.com>,

[mea...@my-deja.com]

Ok - I have two things that may have something to do with your problems.

First:
Remember that you are cutting an Interbase database.
According to Borland about 2 years ago, Interbase cannot handle more
that 1gb of data.
After that the engine will fail (I know this is true from experience)
If you are trying to cut a 1gb remote database you will have problems.

Second:
Make sure your server is configured to use all of the memory.
I do not remember what the initial settings for MS SQL are, but you can
limit the amount of memory that the database engine will use.
From enterprise manager, right click on the server and choose
properties.
Click the memory tab and make sure that the server is set to
dynamically allocate memory and that the maximum amount of memory to
use is the entire 2gb (unless you use the server to run other
applications regularly).

Also remember that the memory being used by MS SQL can be much more
than the database itself.
The log file may be getting too large and during the cutting of a large
database you may have to set it to truncate on checkpoint.
Also, the tempdb can often be very large if you use temporary tables
and cursors (SalesLogix used cursors every time it opens the History
table).
Make sure that these are not getting bloated at the same time that you
are trying to cut a remote database.

Have either of you called SalesLogix support yet?
I know their support can be tough to use, but it may be worth trying.

In article <8kkqs1$l1o$1...@nnrp1.deja.com>,

[steve_v...@my-deja.com]

I called Saleslogix support and was told be 3 reps and one manager that
the Interbase database I am trying to cut (200 - 300 megs) is too
large and I will get insufficient memory errors no matter what. They
said I must reduce the amount of History and am sending over. We have
only two years on the system. They said reduce the history to 1 year.

In article <8klhvi$7on$1...@nnrp1.deja.com>,

[mea...@my-deja.com]

Isn't that pathetic?
I deal with text files bigger than that every day.

Interesting fact - a single text field in an MSSQL database can hold up
to 2gb of data (yes, one field, one row, 2,147,483,647 bytes of data).
Sad that Interbase cannot handle half of what MSSQL can have in a
single field...

In article <8kvp9q$9qa$1...@nnrp1.deja.com>,

[steve_v...@my-deja.com]

Is anyone able to successfully cut remote dbs during the day? WHen I
try I constantly lock people (WG users). I currently do any remote db
cutting after 5:00 but I was curious.

THanks
Steve

In article <8lhvtr$111$1...@nnrp1.deja.com>,

[Kari]

Hi-

Yes I have been able to. But summer is our slow period so there is not
as much workgroup activity to disturb. I find that it realloy doesn't
bother anyone until it gets to the History table. I usually just tell
the workgroup users that they are going to have to put up with it for a
while. I also try to only cut the "small" users databases during the
day - those with less than 5000 accounts.

Sometimes you have to do what you have to do. I will say that even
with a large database (I had to start cutting a new Remote Office last
Friday during the day) we don't get lock outs - just unbeliveable
slowdowns.

Kari

In article <8n6nlt$dn0$1...@nnrp1.deja.com>,

[steve_v...@my-deja.com]

I am curious what happens when you cut a database for a remote office.
Aren't they huge over 5000 accounts and 300 megs?

In article <8n934i$1kj$1...@nnrp1.deja.com>,

[Kari]

Hi-

Yes they are a bit of a drag to do, but because it takes so long and we
need the weekend to get it installed I usually have to start it on a
Friday. (Luckily we have only had to do this twice) I warn the users
ahead of time so they cannot complain _too_ much.

Our main DB is about 1.5G. A lot of that is history - so much in fact
that the history bombs out on the remote office creation and we have to
import the history separately. This last one took about 6 and a half
hours to cut. The main slowdown for workgroup users seems to be when
it hits the history table (I think we are up to 8 years of history
there now - and yes I would love to get rid of some but everyone claims
they need it). I don't think I would be able to cut the Remote Office
during the day other than in the summer - Since we sell our product
mostly to public schools summer is a slow time AND we have early hours
on Fridays in the summer so there were probably only 7 workgroup users
tops on that afternoon. Even so they did not experience lock outs -
just a slow down.

Kari

In article <8o5nka$bmr$1...@nnrp1.deja.com>,

[mea...@my-deja.com]

I have been working on data warehousing solutions for my History table.
We have 20 years of history is our system, but before SalesLogix the
notes were at a minimum.
Now that users can enter notes, the table has quickly gotten very large
and we are pushing 1.5 million records.
I plan to solve this by archiving some of these notes to another
database and only keeping the last 5 notes per contact.
My users will still need another way to look at the older notes if they
have to, so I will need to implement a system where they can bring them
up if they really need them.

I will keep everyone informed when I make some progress.

In article <8o5r5k$fpg$1...@nnrp1.deja.com>,

[steve_v...@my-deja.com]

Kari,

How do you import the Notes/History when it bombs out. We get an
Insufficient memory error on ours while copying the History table and
then it moves on. Just curious of the commands you use to import it.

THanks
Steve

In article <8o5s0c$h2o$1...@nnrp1.deja.com>,

[Kari]

The first time we did used the Table copy command and this time we
imported through Access queries. Exported the table in Access, deleted
anything in the new database history table with a query and then
imported again with a query.
Just be careful that the queries are set to run on the new remote
database and that it isn't still looking at the live host DB.

In article <8o911c$1v8$1...@nnrp1.deja.com>,