![]() ![]() And if you don’t access to that location, you can not copy the backup file for further processing like compression, encryption, storage, etc. The *.bak file is placed somewhere on the drive local to that SQL server. The main issue with remote SQL servers is that you can run SQL scripts, including BACKUP DATABASE command, but accessing the resulting *.bak file is problematic. What is the problem with Remote SQL Server backups? Local SQL Server is a server where you have full access to the file system like a local server you can physically access or a dedicated/virtual server that you have full control of. Remote SQL Server is a server where you have limited access to the server’s file system like in a shared hosting environment. We will explain why and show all the available options to make the backups anyway.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |