-> I opened a Power BI report and clicked on Refresh and got below error,
AW_Territories_Lookup – Could not find file ‘C:\temp\AdventureWorks_Territories.csv’.
-> I checked the file “C:\temp\AdventureWorks_Territories.csv”. It seems like someone have renamed the file to “C:\temp\AdventureWorks_Territories_AW.csv”.
-> One way to solve this issue is to rename the file from AdventureWorks_Territories_AW.csv to AdventureWorks_Territories.csv in location C:\temp.
-> In my case that was not possible as the team who changed it have used it on other reports.
-> Hence in my Power BI report, I clicked on “Transform data” and clicked on “Data source settings”.
-> I clicked on the file “C:\temp\AdventureWorks_Territories.csv” and clicked on “Change Source”.
-> Once the above changes are completed. Clicking refresh will just complete fine.
Thank You, Vivek Janakiraman
Disclaimer: The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.
-> Below queries will be used to create the required database and objects on Publisher JBRESEARCH\IN2019,
create database JBDB GO use [JBDB] GO create table Table1( SNO INT PRIMARY KEY , SNAME VARCHAR(255)) GO create table Table2( SNO INT PRIMARY KEY , SNAME VARCHAR(255)) GO create table Table3( SNO INT PRIMARY KEY , SNAME VARCHAR(255)) GO insert into Table1 values (1,'A') GO insert into Table2 values (1,'A') GO insert into Table3 values (1,'A') GO
-> Configure Distribution using below queries on Publisher JBRESEARCH\IN2019,
EXEC sp_addarticle @publication = N'JBDBREPL',@article =N'Table1',@source_object =N'Table1' GO EXEC sp_addarticle @publication = N'JBDBREPL',@article =N'Table2',@source_object =N'Table2' GO EXEC sp_addarticle @publication = N'JBDBREPL',@article =N'Table3',@source_object =N'Table3' GO
-> Checking the available data on objects Table1, Table2 and Table3 on Publisher JBRESEARCH\IN2019.
select * from JBDB..Table1 GO select * from JBDB..Table2 GO select * from JBDB..Table3
-> Backup JBDB database using below query on Publisher JBRESEARCH\IN2019,
use master backup database JBDB to disk = 'c:\temp\JBDB_14OCT2020.bak' with STATS=1
-> Let us add some new data using below query after the database backup on Publisher JBRESEARCH\IN2019. We are adding new data to check if replication picks up these data too after replication configuration. In real world scenario there is high possibility that new data will be added when we are performing backup on the publisher and then restore it in subscriber.
use [JBDB] GO insert into Table1 values (2,'B') GO insert into Table2 values (2,'B') GO insert into Table3 values (2,'B') GO insert into Table1 values (3,'C') GO insert into Table2 values (3,'C') GO insert into Table3 values (3,'C') GO
-> Checking the available data on objects Table1, Table2 and Table3 on Publisher JBRESEARCH\IN2019.
select * from JBDB..Table1 GO select * from JBDB..Table2 GO select * from JBDB..Table3 GO
-> Restore database JBDBSub on the Subscriber SQL Server Instance JBRESEARCH\IN2019_1 using the backup that was performed on Publisher server JBRESEARCH\IN2019.
USE [master] RESTORE DATABASE [JBDBSub] FROM DISK = N'C:\Temp\JBDB_14OCT2020.bak' WITH FILE = 1 , MOVE N'JBDB' TO N'C:\Program Files\Microsoft SQL Server\MSSQL15.IN2019_1\MSSQL\DATA\JBDB.mdf' , MOVE N'JBDB_log' TO N'C:\Program Files\Microsoft SQL Server\MSSQL15.IN2019_1\MSSQL\DATA\JBDB_log.ldf', NOUNLOAD, STATS = 1 GO
-> Execute below query to get LastLSN details from the database backup that was performed on Publisher server JBRESEARCH\IN2019.
-> Verify replication monitor to see there are no failures. Query the involved objects on either side to check if data’s are in sync,
Thank You, Vivek Janakiraman
Disclaimer: The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.
-> I tried starting an Azure virtual machine and got below error,
Failed to start virtual machine ‘JBS’. Error: There is an active shared access signature outstanding for disk JBS_DataDisk_0. Call EndGetAccess before attaching or deleting the disk.
-> Above error prevented this virtual machine to come online.
-> I opened the resource group where the virtual machine is placed and then opened the disk “JBS_DataDisk_0”. Clicked on “Disk Export” and then clicked “Cancel Export”.
-> Once the export was cancelled, Azure virtual machine came online and I was able to login to it without any issues.
Thank You, Vivek Janakiraman
Disclaimer: The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.