Dynamics Blogger

In SQL server, We have an option to restrict databases to single, restricted user or multi users. When we want all users to connect to database, the status would be Multi_User. In case we have a maintenance plan and expect the other users not log into the database under maintenance, We can set the database to Restricted user or Single user mode. Restricted user mode allows connections to SQL server through any user ID which is a member of dbcreator, db_owner or sysadmin roles. In other words, Users like “sa” can log into the database and continue with maintenance activities. I tried to test this option on Dynamics GP Application databases and It seems to work perfect in my tests. I find this useful when I have to do some maintenance routines and do not expect the users to be logged into the application while the maintenance is still on. Once my maintenance routine is complete, I can reset the status to Multi_user mode which then enables connections to Dynamics GP databases. If...

Sometime back I received a call from one of my clients. Client was having some system setup related issue that required a SQL Maintenance to be done. I quickly guided him over phone to go to MS Dynamics GP | Maintenance | SQL and select the required tables. Prior to this, I asked him if he kept a backup of DYNAMICS database and the answer was Yes. However, the system administrator of the client being new to the Dynamics GP environment (which I came to know only later) selected all tables by mistake and hit Drop Tables. Worst part was that there were users working online at this time. More worst was that after this happened, the new system administrator realized he doesn’t have a proper backup. Needless to say, the damage was real quick. All the users working online have been kicked out. There are several companies linked to the DYNAMICS database that got totally messed up. What would I do in this scenario? I realized there must be some way out. Then, came a flashing idea. Why can’t we ...