Installing GP - does it have to go on the SQL server

(0) Share

Report

Posted on by Scott Kelley

Hi all, I have what should be an easy question.

When you install Great Plains, does there have to be an instance of it on the same server SQL is running from or can your GP server and your SQL be seperate? We have a GP consultant that insists GP must also be installed on the SQL server but can't explain why and we'd rather keep our SQL pure if possible.

Thanks

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (2)

Verified answer

Melissa Sandrovich on at

Like (0)

Report

It does not have to go on the SQL server. We have many clients that don't want applications like GP installed ontheir SQL server. You will still be able to perform all the same funstions as having it installed on the server, and you will need the sa credentials.

Thanks!

Melissa

Was this reply helpful? Yes No
Verified answer

Victoria Yudin 22,769 on at

Like (0)

Report

Scott,

While many companies choose to install the Dynamics GP application on the SQL Server, for testing, troubleshooting or administrative purposes, there is no requirement to do so. Dynamics GP does not need to be installed or running on a server and administrative functions can be performed from any client machine where the application is installed.

Older versions of GP had a client/server choice when installing the application, but the only difference was that the 'server' option installed some additional tools and there was no reason the 'server' installation had to be on an actual server. Starting with GP 2010, there is just one version of the installation, there is no longer a choice for client or server.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Best practices say that there should be a client installed on the SQL Server. There will be times when troubleshooting and such will need to be done. You may have the situatuion where you want to use SQL Mgmt to run a query or script then immeadiately use the GP UI. Another time when you want to use the GP backup function within the GP UI, can only be done on the server.

The client on the server is not to be used in a day to day production, but is very helpful to have when it is needed.

Warren

Was this reply helpful? Yes No
sandipdjadhav 18,306 on at

Like (0)

Report

I will prefer to install GP Server Edition on "SQL Server" where my GP database reside. It will help me on Upgrade and installation of SP.

If you don't want to installed GP on SQL Server then on Client Machine install SQL Server and connect to GP SQL Server Instance that will help you on Upgrade and on SP installation process.

Thanks

Sandip

Was this reply helpful? Yes No
Victoria Yudin 22,769 on at

Like (0)

Report

Sandip, there is no more 'server' installation option in GP 2010. Just one install - it's all the same. :-)

Was this reply helpful? Yes No
Victoria Yudin 22,769 on at

Like (0)

Report

Scott, there you have it.

While there is no requirement to install the Dynamics GP application on the SQL Server, most consultants recommend it. I am not sure I would go so far as to say it's a "best practice", because I would argue that keeping the SQL Server as "clean" as possible is also a "best practice". But hopefully you can make a more informed decision now.

Was this reply helpful? Yes No
Scott Kelley 70 on at

Like (0)

Report

Thanks for all the input folks - this helps. We suspected the GP consultant that told us this didn't really know for sure and only had experience with it being installed on the same machine as SQL.

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Hi Scott,

There is no obligation to put the Dynamics GP application on the SQL server, but you need to have at least one reference location where you put the shared dictionnaries and where you do your hotfixes / updates first, before applying them to the clients.

In case you're dealing with Terminal Server or Citrix, it's even more important, since you not necessarly want to share your 'Master' reference application to your users. In all the installations I've managed for GP, the 'Master' application was always installed along the SQL server and it doesn't hurt, because it is _not_ your main application source that you use every day. Only to do maintenance and apply patches to your Dynamics GP. I've not seen any arguments against putting the GP apps on the SQL server...

Was this reply helpful? Yes No
MG-16101311-0 26,225 on at

Like (0)

Report

@Warren: "Best practice"? Not quite sure about that one. Most of my clients have the GP administrative client installed on their application server, not their database server. For a number of them, GP and it's databases represent a small part of their corporate applications and they will tell you without hesitation the last thing they want is to put accounting software on their database server.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Scott, for clients who do not want the GP client on their SQL Server, I recommend an "administrative" cllient machine, and use that for shared dictionaries and SQL Client tools. Also, wise to have MS Office instllaed there too.

Was this reply helpful? Yes No