New answers tagged sql-azure
Passwords are case-sensitive. Passwords should always be at least 8 characters long, and cannot exceed 128 characters. Passwords can include a-z, A-Z, 0-9, and most non-alphanumeric characters. Passwords cannot contain single quotes, or the login_name. https://msdn.microsoft.com/en-us/library/ms189751.aspx
I wouldn't have been able to find the solution to this problem if you hadn't decided to open the VM on azure and check the version numbers, so thank you! After I saw your post, I googled "sql 12.0.2430.0" and found a hotfix from microsoft that fixed the problem. You can find the hotfix Here The update added full support for the new Azure SQL database ...
The problem was with our company firewall. The port 1433 was blocked on the firewall. After removing the outgoing and incoming restrictions on firewall the SMSS started working.
Although this doesn't answer your specific question, it may preclude you from needing to ask the question in the first place: It's possible to set a length on your string variables in your C# model object, which will cause Entity Framework to generate SQL that uses a fixed-length nvarchar type (e.g. nvarchar(50)), instead of nvarchar(max). For example, ...
BCP is one way to go. I've actually used the method stated here: Bulk insert with Azure SQL. Basically you bulk insert your data to a local MSSQL database (which is supported). Create a txt file with all data and bulk insert it into your azure table by using the BCP command in command prompt.
Top 50 recent answers are included