OK, all you wizards out there....here's one for you:
Let's say I have 4 GP companies defined on ServerA. Can I set up a 5th company on ServerB? If so, how do I reference the data & log files in GP Utilities when I set up the new company? Can I use a UNC to point to the other server, or do I have to map a drive that points to the server, then use that mapping to reference the location?
*This post is locked for comments
I gave up trying to reference the other server :-)
Tim's approach is what I ended up using....and it works fine. I hadn't noticed that there was also a copy of the DYNAMICS database on the test server, so it was pretty easy to implement this approach. I did have to run utilities to get the test databases up to the current SP, since apparently they had been restored from an earlier backup.
Thanks to all for your suggestions!
In addition
you may install 2nd instance of GP in each of the client machine and point this instance to your test sql server using ODBC. the 2 instances of GP will remember the last ODBC that was used, so no need to select which odbc during launching, just user ID and password.
you may also create 2 icons GP live and GP test in each users machine desktop. a universal password in the test machine could also help.
I did not say it was that simple - take a look at the following article and verify with your IT department if this is something you want to implement.
As an experiment, I tried setting up another database via GP utilities on ServerB, but I get the following message when using a mapped drive:
Warning...The device 'T:\' (my mapped drive) could not be found. Microsoft Dynamics GP Utilities is unable to determine if there is enough available disk space to create the database. A minimum of 70MB is needed.
A similar message appeared when I tried using a UNC instead of a mapped drive letter.
As long as in your scenario you are only referring to the actual physical location of log files and data files, then you should have no problems implementing this.
Now, SQL Server does not support UNC for physical database files, so you would have to work with either a SAN or the very unreliable mapped drives.
First, let me say that I have never tried this...but let's talk it through.
You CAN put different db files (data and logs) on different drives.
You CAN map a drive to a different machine.
So what if SQL server A on Machine A referred to tables on Drive X of Machine B? Now, the same SQL server on Machine A would be the controlling SQL server.
If the Dynamics and Company database reside on that dev server the create a new ODBC Data Connection to that server. Your users will have to pick the correct ODBC (make sure the names are easily identifiable) connection when logging in. Remember to append <TEST> to the company name in the dev environment to produce the message about the company being a test company.
Tim
Our IT developers created a test GP database on another server for internal development work. Now, they want it to show up in the list of databases when people log in to GP so they can run tests.
Unfortunately, we don't have enough room on our production server for this test database, so that's why we're trying to see if we can connect to it even though it's on a different server.
There might be other solution, but first may i know why do you want the 5th company in another machine?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,219 Super User 2024 Season 2
Martin Dráb 230,056 Most Valuable Professional
nmaenpaa 101,156