Moving to new SQL server

[chrism1]

Just setup a new server running sql. We still have the old server running along side it (in the same domain) with SQl server and Macola program/data files.

What is the easiest way to transfer both programs and data to the new server?

For giggles I tranferred the Macola program directory and remapped a workstation to the new server. I went to setup a new company on the new server and it listed the companies already existing on the old server -- what file in the program directory holds this info?

Thanks

 

[MacolaHelp]

You may have a dilemma here. Have you changed the names of the server? When you install macola, it creates users thru visual menu builder & writes registry entries as well as the macola7.cfg file on the server. It can be tricky to get them all in sync depending on how far you have gone down this path already rather than a re-install. Before you go any further, you should probably discuss more on this forum as to what exactly you have done. You could be venturing into dangerous territory right now.

 

[chrism1]

The server names are different.

I found the macsql.cfg file where the names of companies and server locations are found.

I tried SQL's data transport utility to move the data,pwe,screens, and msllockdb databases. They failed with an error message that an object could not be copied -- the login 'username_sql' does not exist. I then detached the databases and copied them.

I have one workstation that I mapped to the new server for testing. Right now I cannot login to Macola as supervisor (or anybody else). I get a password incorrect message.

I've got some other suggestions dealing with SQL that I'll try today.

 

[Rob7]

chrism1,
If you do not install the Macola software onto the new server, you will have lots of problems. The install hits the registry with quite a bit of stuff and this needs to be correct. Moving the data is one thing. In SQL, this is pretty easy using dts, but I would recommend doing a clean macola install, create your company, then dts the data from the old server to the new server. Please do not confuse the issues of moving Macola and moving the data. These are two different issues. I just went through this mud hole with another client. Not a fun trip.

Rob

 

[chrism1]

So far so good.

I copied the program directory and mapped using the same drive mappings. There are a couple config files I had to modify for the new server name.

I could not use DTS. I Detached and copied data,pwe,screens,msllockdb.

I had problems with SQL transferring user/logins. I'm now able to login in as Supervisor (Thanks Dennis!). But I am still working on logging in as other users.

What registry entries are we talking about - server? workstation?

 

[MacolaHelp]

chrism1: I agree w/Rob on the reinstall. You will not save yourself any time in the long run by trying to copy programs from the old server to the new. Because of how Macola uses VMB to create & update user security in sql & how the program installation writes info to the server registry, you are planting a time bomb in the new server that will go off when you least expect it by trying to shortcut the fresh install. I have had the experience of moving dbs from one server to another & renaming an existing macola application server & it is not pretty. Once you install, you can then detach dbs from the old server & move or copy/paste to the new server if you want to test first to be sure everything works right. I have not found DTS to be useful or quick enough to move databases. It has other valuable uses such as updating files between dbs, etc., but not the tool of choice for moving dbs. You should be able to get your screens db from the old server, attach it on the new server & synchronize security in macola VMB.

 

[dgillz]

Chris,

Did you get the screens database copied over? This database has the Macola users in it. Also, check your Data_xx directories in Enterprise Manager and make sure the users are listed in the "users" section. Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

dgilsdorf@trianglepartners.com

 

[MacolaHelp]

chrism1: see macola doucment 02.309.939 in the infomine section of the website regarding moving sql. You have access to the site if you have paid your 10% annual maintenance. If you don't have access, post your email & I will send to you.

 

[Rob7]

During Macola install, server registries are modified. During the client install, done from the server, the workstation registries are modified. The registries on the server must be modified correctly or the application will give unpredicable results.

Rob

 

[chrism1]

Ok...

I installed Macola fresh onto the new server.

I then copied the old install over the top and tweaked a couple config files.

I then detached,copied, and attached the databases.

I still had issues with user_sql accounts not having the proper rights to login but used enterprise manager to square this away.

So far things are running fine.

Thanks

 

[tpllc]

There is a document on the macola web site that describes how to do this. You need to change the supervisor password back to supervisor. Then install the same version of Progression on the new server. Then copy the database from the old server to the new server. The document describes the correct databases that must be copied. Then there is a synchonize with SQL function im Progression that will handle the security. It is basically this simple but you should get a copy of tat document before you start.

Steve Henley
trianglepartners.com
Exact Software consulting, sales and implementations.