You can create the user in Microsoft SQL Server & Microsoft Azure SQL Database using the following code.
CREATE LOGIN UserNameHere WITH password='Password here'; CREATE USER UserNameHere FROM LOGIN UserNameHere;
CREATE USER UserNameHere FROM LOGIN UserNameHere ; EXEC sp_addrolemember 'db_datareader', 'UserNameHere';
By default ASP.NET Core Identity system has string data type for primary key. We are often use to with int data type as primary key.
Here is the very good article from Microsoft documentation team on this topic.
Please click here to read the article
Sometime we need to do undo checkout from other user’s workspace in Team Foundation Server (TFS). Here is the procedure to do it using Visual Studio’s Command Prompt.
Open the Visual Studio Command Prompt and type the following command:
Recently we were in a situation where we need to merge data from our offline version of application with online database.
We planned to use uniqueidentifier as data type for ID columns instead of int (auto identity).
But when we looked at reviews a lot of people were against this idea, they said if we use uniqueidentifier column as primary key (and clustered index) then there will be lot of fragmentation in our database, also the extra size of key.
Some people suggested that use the int type (auto identity) as primary key and add another column of uniqueidentifier type for this purpose. We decided to go with this idea and added a uniqueidentifier column in each table.
Hosting providers unload your application after certain amount of time if the application is idle. Microsoft Azure provide Always ON option (with some extra cost) to keep the application always running. You can enable these settings from Azure Portal as show below:
However there is an issue if your application is running on HTTPS and you have rewrite rules to redirect HTTP traffic to HTTPS then Always ON settings in Azure will not work.
You can fix it in many ways, here is one of them. Add the following rewrite rule in your web.config, it should be first rule (if you have other rules in web.config):
DateTime.Now returns the time by taking into account server’s time zone on which application is hosted. As Azure web apps has time zone set to UTC even its location is somewhere else say in central US.
When we try to access the server’s time using DateTime.Now, it returns UTC time.
You can fix this issue by adding the following application settings using Azure Portal:
Key: WEBSITE_TIME_ZONE
Value: Time zone of the application where it is hosted in Azure say Central Standard Time
You can get the name of time zones from here
In this article we will see how to take Microsoft SQL Server database backup to Azure storage. At high level, we have to do the following to achieve this: