Moving SQL and Great Plains

We have SQL 2000 and Great Plains 7.5.
We have 2 Great Plains clients. One on the SQL Server itself and the other
on another client.
We are moving our SQL databases to a new server. This new server will have
the same name on the domain as the old one did. It will also be using the
same IP (the old one will be renamed and will have a different IP).
Anyway, I have a couple of questions:
1 - How do I Install Great Plains on the new SQL Server? It is not a brand
new install, as I have Dictionaries and the database is obviously already
created. Is it just a normal install? What about the dictionaries?
2 - Will my other client work with the new SQL server or will that have to
be re-installed?
Thank you.Kevin,
1. First, it's not necessary to install the Great Plains code on the server
for it to run. Everything you need is in the database when a client
connects to it (assuming you don't have modified forms/reports on the
server), so getting the databases on the new server is all that is
necessary. That aside, when it comes time to do things like year-end
closing or upgrading versions, you'll want the code there since these
processing intensive jobs run best on the server. If you do choose to
install GP code on the server, you'll want to do a new install (server
install) from the CD, preferably to the same file locations as it was on the
original server, delete every file/folder from the new GP code folder, then
copy the code (including dictionaries assuming you have modified
forms/reports/etc.) over the code folder on the new server. This also
ensures that any service packs you applied will come over. If you selected
a different install path on the new server you'll need to update the paths
appropriately in the dex.ini and Dynamics.set files.
2. Your other client will work fine. You just have to make sure your ODBC
connnection is pointing to the server. You'll also have to make sure that
references to mofidifed forms/reports in the Dynamics.set are correct given
the new install on the server.
There are a few ways of getting the databases over to the new server but
that discussion would be more involved.
David Morrison, CPA, MCP
Senior Technology Consultant
Clifton Gunderson Technology Solutions
6399 South Fiddler's Green Circle, Suite 100
Greenwood Village, CO 80111
tel: 303.779.5710 x134
fax: 303.779.0348
www.cliftoncpa.com
"Kevin L" <no_spam@.not_real_email.com> wrote in message
news:ewn$YDJoDHA.488@.tk2msftngp13.phx.gbl...
> We have SQL 2000 and Great Plains 7.5.
> We have 2 Great Plains clients. One on the SQL Server itself and the other
> on another client.
> We are moving our SQL databases to a new server. This new server will have
> the same name on the domain as the old one did. It will also be using the
> same IP (the old one will be renamed and will have a different IP).
> Anyway, I have a couple of questions:
> 1 - How do I Install Great Plains on the new SQL Server? It is not a brand
> new install, as I have Dictionaries and the database is obviously already
> created. Is it just a normal install? What about the dictionaries?
> 2 - Will my other client work with the new SQL server or will that have to
> be re-installed?
> Thank you.
>|||Kevin,
These are questions better posed to the Great Plains support or newsgroups
than here. But here is some information on moving databases between
servers. Moving db's in and of them selves is pretty straight forward but
this does not take into account any Great Plains specific issues that may
arise.
--
Andrew J. Kelly
SQL Server MVP
"Kevin L" <no_spam@.not_real_email.com> wrote in message
news:ewn$YDJoDHA.488@.tk2msftngp13.phx.gbl...
> We have SQL 2000 and Great Plains 7.5.
> We have 2 Great Plains clients. One on the SQL Server itself and the other
> on another client.
> We are moving our SQL databases to a new server. This new server will have
> the same name on the domain as the old one did. It will also be using the
> same IP (the old one will be renamed and will have a different IP).
> Anyway, I have a couple of questions:
> 1 - How do I Install Great Plains on the new SQL Server? It is not a brand
> new install, as I have Dictionaries and the database is obviously already
> created. Is it just a normal install? What about the dictionaries?
> 2 - Will my other client work with the new SQL server or will that have to
> be re-installed?
> Thank you.
>|||Although it is not neccessary to install the Great Plains application on
the SQL server itself, it is very useful to have it there for running
file maintenance procedures and for other tasks such as creating new
companies. In fact, you have to have it on the server in order to be
able to apply GP75 SP1. There are ways around this however.
Brian Rottman
Systems Engineer
BG Technologies / Microsoft Business Solutions Partner
> Kevin,
> 1. First, it's not necessary to install the Great Plains code on the server
> for it to run. Everything you need is in the database when a client
> connects to it (assuming you don't have modified forms/reports on the
> server), so getting the databases on the new server is all that is
> necessary. That aside, when it comes time to do things like year-end
> closing or upgrading versions, you'll want the code there since these
> processing intensive jobs run best on the server. If you do choose to
> install GP code on the server, you'll want to do a new install (server
> install) from the CD, preferably to the same file locations as it was on the
> original server, delete every file/folder from the new GP code folder, then
> copy the code (including dictionaries assuming you have modified
> forms/reports/etc.) over the code folder on the new server. This also
> ensures that any service packs you applied will come over. If you selected
> a different install path on the new server you'll need to update the paths
> appropriately in the dex.ini and Dynamics.set files.
> 2. Your other client will work fine. You just have to make sure your ODBC
> connnection is pointing to the server. You'll also have to make sure that
> references to mofidifed forms/reports in the Dynamics.set are correct given
> the new install on the server.
> There are a few ways of getting the databases over to the new server but
> that discussion would be more involved.
> David Morrison, CPA, MCP
> Senior Technology Consultant
> Clifton Gunderson Technology Solutions
> 6399 South Fiddler's Green Circle, Suite 100
> Greenwood Village, CO 80111
> tel: 303.779.5710 x134
> fax: 303.779.0348
> www.cliftoncpa.com
>
> "Kevin L" <no_spam@.not_real_email.com> wrote in message
> news:ewn$YDJoDHA.488@.tk2msftngp13.phx.gbl...
>>We have SQL 2000 and Great Plains 7.5.
>>We have 2 Great Plains clients. One on the SQL Server itself and the other
>>on another client.
>>We are moving our SQL databases to a new server. This new server will have
>>the same name on the domain as the old one did. It will also be using the
>>same IP (the old one will be renamed and will have a different IP).
>>Anyway, I have a couple of questions:
>>1 - How do I Install Great Plains on the new SQL Server? It is not a brand
>>new install, as I have Dictionaries and the database is obviously already
>>created. Is it just a normal install? What about the dictionaries?
>>2 - Will my other client work with the new SQL server or will that have to
>>be re-installed?
>>Thank you.
>>
>
>