1. db_owner role should only be given to the administrator who responsible for the database because this role can DROP the database
2. db_datareader and db_datawriter is the minimum access that should be given to normal user to do the basic SELECT, UPDATE, INSERT and DELETE operation to the database

Source:

1. https://docs.microsoft.com/en-us/sql/relational-databases/security/authentication-access/database-level-roles?view=sql-server-ver15
2. https://www.mssqltips.com/sqlservertip/1900/understanding-sql-server-fixed-database-roles/

1. Create an user account on the computer that act as a server, the username and password must used exactly like the account used in client computer
2. In SQL Server Management Studio:
   • Expand “Security” -> expand “Logins” -> “New Login”
     
   • Click “General” -> select “Windows authentication” -> click “Search”
     
   • Type the account name that has been created on server computer, click “Check Names”
     
   • Alternatively you can do this step by clicking “Advanced” button -> “Find Now” -> find the account name in the search results -> click “OK”
     
     
   • Click “Server Roles” -> check for sysadmin
     
   • Click “User Mapping” -> choose database -> check for db_datareader and db_datawriter
     

Note: You do not need to enter the password as SQL Server will ask Windows to validate the user password. (source: https://www.virtual-dba.com/differences-windows-sql-server-authentication/)

1. You can choose what type of login activity that you want the SQL Server to log. By default, SQL Server will log the “Failed logins only” activity only. To choose the login activity, right-click at your “Server <instance name>” -> “Properties”. In Server Properties, click “Security” and choose the activity in Login auditing area:
   • None
   • Failed logins only
   • Successful logins only
   • Both failed and successful logins
     
2. To view the MS SQL Server log files, expand “Management” -> expand “SQL Server Logs“, click any log date that you want to view:
   
3. All the login activities can be viewed in the Log file summary area:
   

1. Open BlueStacks multi-instance manager. Click “New Instance“.
   
2. Select which instance to create:
   Fresh instance – instance with the new Google account (used to run multiple applications with different Google account. e.g. running Whatsapps with two different numbers).
   Clone instance – instance with the same Google account. (used to run multiple applications with the same Google account. e.g. Running Whatsapp and Facebook at the same time).
   
3. Click “Start” button to start that instance or create the shortcut to desktop and start via short cut as sometimes the instance cannot start directly from BlueStacks multi-instance manager.
   

Questions

1. Can I run 2 instances of Bluestacks at the same time, 1 in “Big-Boss” account, another in “Office” account?
   •  No, only 1 user (either “Big-Boss” or “Office) can run multiple instances of Bluestacks.
2. Can I run 2 instances Memu of at the same time, 1 in “Big-Boss” account, another in “Office” account?
   • The same Memu application cannot running on different Windows accounts.
   • But Memu can run on different windows account using 2 instances. It did work but both Memu instances running on 2 different google accounts.
   • However, for Whatsapp,  both Memu instances cannot use the same Whatsapp account.

The VB.Net code should be as follows:-

MSConn = New SqlConnection()
If sAUTHMODE = "WIN" Then
    MSConn.ConnectionString = "Data Source=" & sSERVER & ";Initial Catalog=" & sDATABASENAME & ";User ID=" & sUSERNAME & ";Password=" & sPASSWORD & ";Integrated Security=True" 
ElseIf sAUTHMODE = "SQL" Then
    MSConn.ConnectionString = "Data Source=" & sSERVER & ";Initial Catalog=" & sDATABASENAME & ";User ID=" & sUSERNAME & ";Password=" & sPASSWORD & ";Integrated Security=False"
End If

Otherwise, one of these error messages will appear:-

• Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication.
• Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

If you received this error message

“Just-In-Time debugging this exception failed with the following error: No installed debugger has Just-In-Time debugging enabled. In Visual Studio, Just-In-Time debugging can be enabled from Tools/Options/Debugging/Just-In-Time.

Check the documentation index for ‘Just-in-time debugging, errors’ for more information.”

Solution is available at https://docs.microsoft.com/en-us/visualstudio/debugger/debug-using-the-just-in-time-debugger?view=vs-2019