Hi everyone.

Trying to use bdbpre / bdbpost to rebuild some 000 tables. I'm using MS SQL2000 with Windows 2000

When I try to execute bdbpre (or bdbpost), for example:

bdbpre -N ttadv301 -C000 > h:\dump\xxx.pre

I get the error:
bdbpre: FATAL ERROR: 'Logon: to server failed errno 0'

The BSE, BSE_TMP, and PATH environment variables are active and correctly defined.

What am I missing?

I have instructions from Baan on the bdbpre / post process for MSSQL / Win 2000. They instruct me to do the following first.
1. Backup (!)
2. Turn off Transactional Logging (for large sequences, if the logging has to auto expand, it can cause table locks). If you are not doing a huge table or have plenty of space, you can leave it on, but I would keep an eye on it. If you have to auto expand the transactional log or the db in MSSQL, you can get record locks and dropped tables!
3. From the BSE\bin directory, type the following
>fillenv.bat
--- maybe that's the piece you are missing
>SET RDS_FULL=10
>SET USER=baan

The last 2 they told me were for performance.

Step 3 has to be run every time you enter a shell.
Hope that helps.

The -set USER=baan is what you miss.

Tried the set USER=baan and it works.

However, never needed to do this on Oracle/Informix databases on NT.

Thanks Ibencic and Omeluuk for your prompt answers.

Fred

P.S.: Ibencic, where did you find those instructions from baan on how to work with bebpre/bdbpost on W2K/MSQL?
The only instructions I have are the ones that come in the online help and are for the UNIX binaries. For NT I had to discover the differences by myself.

That was in an email from Baan support...
We had to open a case because our Create Runtime (through the session) took a dive, and we lost some data. BTW..it took a dive because we ran the Create Runtime with reconfigure while having the transactional logging on, and the db had to do an 'auto expand'. This caused table locks and dropped tables during the Create DD.