https://docs.microsoft.com/archive/blogs/joonkyulee/feed.xml Microsoft Database Platform &amp; BigData Analytics Wed, 17 Apr 2019 03:42:56 GMT en-US hourly 1 https://docs.microsoft.com/archive/blogs/joonkyulee/how-to-create-user-defined-restore-points-on-azure-sql-data-warehouse Tue, 26 Jun 2018 00:37:49 GMT https://blogs.msdn.microsoft.com/joonkyulee/?p=295 deleted before creating another restore point. You can trigger snapshots to create user-defined restore points through PowerShell. Backup and restore in Azure SQL Data Warehouse. https://docs.microsoft.com/en-us/azure/sql-data-warehouse/backup-and-restore You can follow up below simple steps to utilize user-defined restore point. Create user-defined restore point 1) Run powershell to create user-defined restore point. $SubscriptionName="<subscription id>" $ResourceGroupName="adwdbrg" $ServerName="adwsv" $DatabaseName="adwdb" $RestorePointLabel="adwdb_restorepoint" Connect-AzureRmAccount Get-AzureRmSubscription Select-AzureRmSubscription -SubscriptionName $SubscriptionName #Create Restore point New-AzureRmSqlDatabaseRestorePoint -ResourceGroupName $ResourceGroupName -ServerName $ServerName -DatabaseName $DatabaseName -RestorePointLabel $RestorePointLabel 2) Sign in with admin account. 3) You can see this output in powershell window when restore point is created. ResourceGroupName        : adwdbrg ServerName               : adwsv DatabaseName             : adwdb Location                 : Central US RestorePointType         : DISCRETE RestorePointCreationDate : 6/26/2018 4:45:44 AM EarliestRestoreDate      : RestorePointLabel        : adwdb_restorepoint Restore database 1) Open SQL Server Management Studio and connect to user database ‘adwdb’. Run below query to check user-defined restore point. select * from sys.pdw_loader_backup_runs where name = 'adwdb_restorepoint' you can see that submit_time is ‘2018-06-26 04:45:44.023’ 2) Click ‘Restore’ button on the ‘adwdb’ SQL data warehouse in Azure Portal. 3) Change database name and choose ‘2018-06-26 04:45:44’ as Restore point (UTC). Click ‘OK’ to start restoring database. 4) New database (‘adwdb_restorepoint’) is created on same SQL Server. Remove user-defined restore point 1) Run powershell to remove user-defined restore point. $SubscriptionName="<subscription id>" $ResourceGroupName="adwdbrg" $ServerName="adwsv" $DatabaseName="adwdb" $RestorePointCreationDate = Get-Date "6/26/2018 4:45:44 AM" Connect-AzureRmAccount Get-AzureRmSubscription Select-AzureRmSubscription -SubscriptionName $SubscriptionName #Remove Restore point Remove-AzureRmSqlDatabaseRestorePoint -ResourceGroupName $ResourceGroupName -ServerName $ServerName -DatabaseName $DatabaseName -RestorePointCreationDate $RestorePointCreationDate 2) Sign in with admin account. 3) You can see this output in PowerShell window when restore point is deleted. ResourceGroupName        : adwdbrg ServerName               : adwsv DatabaseName             : adwdb Location                 : RestorePointType         : RestorePointCreationDate : 6/26/2018 4:45:44 AM EarliestRestoreDate      : RestorePointLabel        :]]> https://docs.microsoft.com/archive/blogs/joonkyulee/mapping-a-login-to-a-user-in-azure-sql-data-warehouse Sun, 08 Oct 2017 08:17:55 GMT https://blogs.msdn.microsoft.com/joonkyulee/?p=246 This message is a result of incorrect mapping a login ("ETLLogin") in master database to a user ("ETLUser")  in user database on new SQL Server. This error can be simply resolved by ALTER USER command to update SID of a user ("ETLUser") in user database. From old SQL Server, 1) Connect to master database and check SID of a login ("ETLLogin") in master database. select name, sid, type_desc from sys.sql_logins where name = 'ETLLogin' ETLLogin 0x010600000000006400000000000000005BE84C3C0FD46B4399F03F785DE81F32 SQL_Login 2) Connect to user database and check a user that has same SID value at first step. In this example, the user ("ETLUser")  has same SID value with the login ("ETLLogin"). SELECT name, sid, type_desc, authentication_type_desc FROM sys.database_principals where sid = 0x010600000000006400000000000000005BE84C3C0FD46B4399F03F785DE81F32 ETLUser 0x010600000000006400000000000000005BE84C3C0FD46B4399F03F785DE81F32 SQL_USER INSTANCE From new SQL Server, 3) Connect to master database and check SID of the login ("ETLLogin") in master database, If it doesn't exist, create new login and note SID value. select name, sid, type_desc from sys.sql_logins where name = 'ETLLogin' ETLLogin 0x01060000000000640000000000000000A8E9A04A1C58C14EAF2FDA894DEF7C66 SQL_Login 4) Connect to user database and check SID of the user ("ETLUser") in user database. The SID of user ("ETLUser") is not equal to that of the login ("ETLLogin"). SELECT name, sid, type_desc, authentication_type_desc FROM sys.database_principals where name = 'ETLUser' ETLUser 0x010600000000006400000000000000005BE84C3C0FD46B4399F03F785DE81F32 SQL_USER INSTANCE 5) Connect to user database and run ALTER USER command to match up SID value between the login ("ETLLogin") and the user ("ETLUser"). ALTER USER ETLUser WITH LOGIN = ETLLogin 6) Connect to user database and check SID of the user ("ETLUser") in user database. It is updated and matched up with SID of the login ("ETLLogin"). SELECT name, sid, type_desc, authentication_type_desc FROM sys.database_principals where name = 'ETLUser' ETLUser 0x01060000000000640000000000000000A8E9A04A1C58C14EAF2FDA894DEF7C66 SQL_USER INSTANCE 7) Now the login ("ETLLogin") can connect to ADW database successfully.]]> https://docs.microsoft.com/archive/blogs/joonkyulee/introduction Sat, 07 Oct 2017 00:00:02 GMT https://blogs.msdn.microsoft.com/joonkyulee/?p=1