Local Computer drives are not visible when creating backup through wizardSQL Server 2000: Database copy wizard - Claims files already exist (they don't) or there is not enough disk space (there is)When successfully configured SQL Server for database mirroring, got an error saying it's not configured for database mirroringRestoring SQL Server backup to SQL Azure on SQL Management StudioMS SQL Start Mirroring Error
Methodology: Writing unit tests for another developer
Counterfeit checks were created for my account. How does this type of fraud work?
What is the "ls" directory in my home directory?
Umlaut character order when sorting
What mathematical theory is required for high frequency trading?
Cut the gold chain
What constitutes a syllable?
"Correct me if I'm wrong"
Designing a magic-compatible polearm
Has a life raft ever been successfully deployed on a modern commercial flight?
Mathematically modelling RC circuit with a linear input
King or Queen-Which piece is which?
What triggered jesuits' ban on infinitesimals in 1632?
macOS: How to take a picture from camera after 1 minute
Do I have to explain the mechanical superiority of the player-character within the fiction of the game?
Dmesg full of I/O errors, smart ok, four disks affected
Extending prime numbers digit by digit while retaining primality
FD Battery Stations... How Do You Log?
Subtract the Folded Matrix
Why is oilcloth made with linseed oil?
What is the oldest commercial MS-DOS program that can run on modern versions of Windows without third-party software?
Can you use one creature for both convoke and delve for Hogaak?
Are there any individual aliens that have gained superpowers in the Marvel universe?
Rejecting an offer after accepting it just 10 days from date of joining
Local Computer drives are not visible when creating backup through wizard
SQL Server 2000: Database copy wizard - Claims files already exist (they don't) or there is not enough disk space (there is)When successfully configured SQL Server for database mirroring, got an error saying it's not configured for database mirroringRestoring SQL Server backup to SQL Azure on SQL Management StudioMS SQL Start Mirroring Error
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
When I connect to a database on a remote server through SSMS running on my own computer and I follow the backup wizard for a database, none of my local computer drives are listed. All I can see are drives on the remote server and I can't get access to them since I do not have enough permissions.
It seems weird, why I can't see my own computer drive volumes when creating a backup file?
Here's what I do:
On Object Explorer
, right click on database then click on Tasks > Backup
, Add > ...
Part of error message: Can not access the specified path on server
.
sql-server ssms
add a comment |
When I connect to a database on a remote server through SSMS running on my own computer and I follow the backup wizard for a database, none of my local computer drives are listed. All I can see are drives on the remote server and I can't get access to them since I do not have enough permissions.
It seems weird, why I can't see my own computer drive volumes when creating a backup file?
Here's what I do:
On Object Explorer
, right click on database then click on Tasks > Backup
, Add > ...
Part of error message: Can not access the specified path on server
.
sql-server ssms
add a comment |
When I connect to a database on a remote server through SSMS running on my own computer and I follow the backup wizard for a database, none of my local computer drives are listed. All I can see are drives on the remote server and I can't get access to them since I do not have enough permissions.
It seems weird, why I can't see my own computer drive volumes when creating a backup file?
Here's what I do:
On Object Explorer
, right click on database then click on Tasks > Backup
, Add > ...
Part of error message: Can not access the specified path on server
.
sql-server ssms
When I connect to a database on a remote server through SSMS running on my own computer and I follow the backup wizard for a database, none of my local computer drives are listed. All I can see are drives on the remote server and I can't get access to them since I do not have enough permissions.
It seems weird, why I can't see my own computer drive volumes when creating a backup file?
Here's what I do:
On Object Explorer
, right click on database then click on Tasks > Backup
, Add > ...
Part of error message: Can not access the specified path on server
.
sql-server ssms
sql-server ssms
edited Jun 3 at 10:13
Daniel K
330111
330111
asked Jun 3 at 5:58
Mohammad lm71Mohammad lm71
1064
1064
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This behaviour is expected.
SQL Server runs on the remote server, in a service account so it cannot not see your own volumes. Why would SQL Server have any special rights to see your local computer?.
You have to create a file share on your local computer, assign appropriate permissions and then you CAN use UNC format (computernamesharename) to use that local file share.
SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it'sOBVIOUS
that what you said is not that obvious !!!
– Mohammad lm71
Jun 3 at 7:21
1
No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.
– TomTom
Jun 3 at 7:30
Youobviously
didn't pay attention to the wordthrough
inI connect ... through SSMS running on my own computer
. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.
– Mohammad lm71
Jun 3 at 9:38
SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).
– TomTom
Jun 3 at 9:39
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969888%2flocal-computer-drives-are-not-visible-when-creating-backup-through-wizard%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This behaviour is expected.
SQL Server runs on the remote server, in a service account so it cannot not see your own volumes. Why would SQL Server have any special rights to see your local computer?.
You have to create a file share on your local computer, assign appropriate permissions and then you CAN use UNC format (computernamesharename) to use that local file share.
SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it'sOBVIOUS
that what you said is not that obvious !!!
– Mohammad lm71
Jun 3 at 7:21
1
No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.
– TomTom
Jun 3 at 7:30
Youobviously
didn't pay attention to the wordthrough
inI connect ... through SSMS running on my own computer
. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.
– Mohammad lm71
Jun 3 at 9:38
SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).
– TomTom
Jun 3 at 9:39
add a comment |
This behaviour is expected.
SQL Server runs on the remote server, in a service account so it cannot not see your own volumes. Why would SQL Server have any special rights to see your local computer?.
You have to create a file share on your local computer, assign appropriate permissions and then you CAN use UNC format (computernamesharename) to use that local file share.
SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it'sOBVIOUS
that what you said is not that obvious !!!
– Mohammad lm71
Jun 3 at 7:21
1
No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.
– TomTom
Jun 3 at 7:30
Youobviously
didn't pay attention to the wordthrough
inI connect ... through SSMS running on my own computer
. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.
– Mohammad lm71
Jun 3 at 9:38
SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).
– TomTom
Jun 3 at 9:39
add a comment |
This behaviour is expected.
SQL Server runs on the remote server, in a service account so it cannot not see your own volumes. Why would SQL Server have any special rights to see your local computer?.
You have to create a file share on your local computer, assign appropriate permissions and then you CAN use UNC format (computernamesharename) to use that local file share.
This behaviour is expected.
SQL Server runs on the remote server, in a service account so it cannot not see your own volumes. Why would SQL Server have any special rights to see your local computer?.
You have to create a file share on your local computer, assign appropriate permissions and then you CAN use UNC format (computernamesharename) to use that local file share.
edited Jun 3 at 10:34
Daniel K
330111
330111
answered Jun 3 at 7:00
TomTomTomTom
46.2k642120
46.2k642120
SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it'sOBVIOUS
that what you said is not that obvious !!!
– Mohammad lm71
Jun 3 at 7:21
1
No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.
– TomTom
Jun 3 at 7:30
Youobviously
didn't pay attention to the wordthrough
inI connect ... through SSMS running on my own computer
. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.
– Mohammad lm71
Jun 3 at 9:38
SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).
– TomTom
Jun 3 at 9:39
add a comment |
SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it'sOBVIOUS
that what you said is not that obvious !!!
– Mohammad lm71
Jun 3 at 7:21
1
No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.
– TomTom
Jun 3 at 7:30
Youobviously
didn't pay attention to the wordthrough
inI connect ... through SSMS running on my own computer
. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.
– Mohammad lm71
Jun 3 at 9:38
SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).
– TomTom
Jun 3 at 9:39
SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it's
OBVIOUS
that what you said is not that obvious !!!– Mohammad lm71
Jun 3 at 7:21
SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it's
OBVIOUS
that what you said is not that obvious !!!– Mohammad lm71
Jun 3 at 7:21
1
1
No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.
– TomTom
Jun 3 at 7:30
No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.
– TomTom
Jun 3 at 7:30
You
obviously
didn't pay attention to the word through
in I connect ... through SSMS running on my own computer
. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.– Mohammad lm71
Jun 3 at 9:38
You
obviously
didn't pay attention to the word through
in I connect ... through SSMS running on my own computer
. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.– Mohammad lm71
Jun 3 at 9:38
SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).
– TomTom
Jun 3 at 9:39
SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).
– TomTom
Jun 3 at 9:39
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969888%2flocal-computer-drives-are-not-visible-when-creating-backup-through-wizard%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown