I periodically have problems when trying to restore a GP company database over the Test database as SQL reports that the database is currently in use.
One way of resolving is to restart the SQL Server but this is only possible on a stand alone test system which is not being used by other people but this approach is overkill.
The better solution is to change the database to single user, restore the database and change the database back to multiple user. This can be done manually through SQL Server Management Studio but is far easier done via a SQL script.
Continue reading “Restoring A Database Without Encountering A Locking Issue”
I have installed SQL Server into Virtual Machines many times in the past but I’ve recently seen an error when trying to do it again;
I had a think about the error and realised that I usually installed SQL from the VM HDD and not, as I was in this case, by attaching the iso image to the VM as external media. I uncompressed the iso onto the VM HDD and ran the installer again from this source and it installed without problem.
When you install Microsoft SQL Server you select the Data, Logs and Backup folder during the installation process. If you subsequently need to change these folders you can only change two of them through the SQL Server Management Studio UI. On the Server Properties dialog there are boxes for the Data and Logs default locations;
Continue reading “How To Change The SQL Server Backup Folder”
Like some other posts recently, this one is the result of a conversation with a colleague at my new company, where I found they were unaware of something I took for granted; the ability to easily rename a comuter which has a stand alone instance of SQL Server installed.
I do this fairly often as I use quite a lot of Virtual Machines for testing different configurations, but I don’t want to have to build a new one every time, so I make copies of a base VM and rename it each time I want a new one (there is often more than one running at any one time and I want to avoid conflicts).
As well as renaming the machine inside the VM, I also rename the SQL Server to make sure it matches the name of the machine; I’ve had problems before with Microsoft Dynamics GP when I’ve not done so.
Doing this is actually very simple. Continue reading “How To Rename A SQL Server”
Backing up the a Microsoft Dynamics GP company to test is, unfortunately, not as simple as backing up one database and restoring it to the Test one. There are two scripts which need to be run after doing so; the first changed the INTERID and Company Name and the second changes the database owner to dynsa.
At my last company, we decided to make this process as easy as possible for clients, so we started creating a SQL Agent Job which would do the backup, restore and run the scripts with minimal effort or could even run on a scheduled basis. The basic purpose was to give the client a test or training system which was always, or could very quickly be, up to date. Continue reading “Copy Microsoft Dynamics GP Live Company To Test Automatically”
After initial acclimatisation pains with Microsoft SQL Server 2008 R2 (I largely skipped 2005 and 2008 RTM) I have become used to Management Studio and do now prefer it to Enterprise Manager and Query Analyser.
One of the things I really like about SQL 2008 R2 is the installation process where you pick the collation. Dealing with Microsoft Dynamics GP so much means I need to be careful with server and database collations as GP, once installed, cannot have it’s database collation changed.
We typically install SQL Server for Microsoft Dynamics GP using the SQL_Latin1_CP1_CI_AS (case insensitive, accent sensitive), which is very easy in SQL 2008 R2 Continue reading “Selecting The Correct Microsoft SQL Server 2000 Collation For Microsoft Dynamics GP”
Well, I’ve just finished installing SQL Server 2008 R2 and Microsoft Dynamics 2010 R2 on the Windows 8 Developer Preview and GP is exactly like it is on Windows 7. Continue reading “Microsoft Dynamics GP 2010 R2 On Windows 8 Developer Preview”
It’s always the small things which catch you out.
The recent test upgrade for a client I did between Microsoft Dynamics GP 10 SP5 and Microsoft Dynamics GP 2010 R2 hit a minor snag during the GP Utilities section of the upgrade which resulted in this error message;
Continue reading “Installing Microsoft Dynamics GP 2010 R2 – Database Compatibility Issue”
SQL-DMO is no longer included in the SQL Server 2008 installation package but can be downloaded as part of the Microsoft SQL Server 2008 Feature Pack