azure-sql-database

问题 I moved a database from SQL Server 2012 to Azure. I don't want to use the user master , so I created a user test . This is what I did for database XXX on Azure: create user test from login test with default_schema=[dbo] exec sp_addrolemember 'db_owner','test' I checked, and the database objects I am interested in are all in the schema dbo . The table Users is in the schema dbo . The connection string in my web project has test as the login. It produces the error message: The SELECT permission

问题 I am trying to use the following template: -- ================================================= -- Create User as DBO template for SQL Azure Database -- ================================================= -- For login <login_name, sysname, login_name>, create a user in the database CREATE USER <user_name, sysname, user_name> FOR LOGIN <login_name, sysname, login_name> WITH DEFAULT_SCHEMA = <default_schema, sysname, dbo> GO -- Add user to the database owner role EXEC sp_addrolemember N'db_owner'

问题 Specifically looking for a way to perform point in time restore to a new Database, preserve the original database; using Managed API instead of REST API or Templates . Code I have so far: public async Task CreateDatabaseFromRestorePointAsync( string resourceGroupName, string serverName, string databaseName, DateTime time) { using (SqlManagementClient sqlMgmtClient = GetSqlManagementClient()) { DatabaseInner myDb = await sqlMgmtClient.Databases.GetAsync( resourceGroupName, serverName,

问题 After upgrading to Entity Framework 6 we've implemented our own DbExecutionStrategy . In addition to existing SqlAzureExecutionStrategy our strategy also logs exceptions. As turned out, every 15-30 minutes Entity Framework throws internal SqlException System.Data.SqlClient.SqlException (0x80131904): Invalid column name 'CreatedOn'. It's an internal error. Seems like EF does some regular checks if CreatedOn column exists on some table. Is there any elegant way to prevent this exception to be

问题 Is there any specific reason why we can't use SSIS in windows azure ? 回答1: Windows Azure only supports a subset of features of SQL Server via the Azure SQL components. SSIS can only be used locally ( on-premise in cloud terminology) for the time being, but SSIS will likely be ported eventually. As an alternative - you could use SSIS locally and combine it with SQL Data Sync if you intend on changing ( insert/update/delete ) any of the data via SSIS ( versus just exporting - selects ). Windows

问题 I need to know what will happen when a database in SQL Azure exeeds its size. For example I defined a 1GB database and this is going over its size limit. Will it change to a 5GB database? 回答1: You won't be able to go over 1GB unless you specifically allow for it. You'll actually get an error code when attempting to go beyond 1GB. To increase max size, execute this T-SQL: ALTER DATABASE MyDatabase MODIFY (EDITION='WEB', MAXSIZE=5GB ) For more info about altering database sizes, see this blog

问题 I need to know what will happen when a database in SQL Azure exeeds its size. For example I defined a 1GB database and this is going over its size limit. Will it change to a 5GB database? 回答1: You won't be able to go over 1GB unless you specifically allow for it. You'll actually get an error code when attempting to go beyond 1GB. To increase max size, execute this T-SQL: ALTER DATABASE MyDatabase MODIFY (EDITION='WEB', MAXSIZE=5GB ) For more info about altering database sizes, see this blog

问题 Scenario I want to use virtual network in order to limit access to Azure Database only from my App Service, so that I can turn of "Allow access to App Services" in firewall settings What I have done: I went to App Service -> Networking -> VNET Integration -> Setup -> Create New Virtual Network I've created new VNET with default settings. When VNET was created I went to App Service -> Networking -> VNET Integration and ensured that the VNET is connected I went to SQL Firewall settigs ->

问题 I am running a .Net MVC Azure Web Site with a SQL Azure database accessed using Entity Framework 6. Intermittently (1 in a thousand or so requests), I get the error "System.ComponentModel.Win32Exception: The semaphore timeout period has expired" System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) ---> System.ComponentModel.Win32Exception: The semaphore

问题 When I am querying from database in continuous looping, after some time I get an error : An exception has been raised that is likely due to a transient failure. If you are connecting to a SQL Azure database consider using SqlAzureExecutionStrategy. Normally it is working fine. 回答1: When connecting to SQL Database you have to account for transient connection failures. These connection failures can happen for example when updates are rolled out, hardware fails etc. The error you see indicates