Backing up remote SQL Server

I have written a SQL DB, and ASP.NET website for a client. The clients
database and webpage are not inhouse but on a hosting provider.
This provider says they only backup for disastor purposes--which didn't make
me feel to good.
So my question...
How can I help this non-techie client to backup her remote SQL Server
Database regularly?
What is the best means of doing this?
Some software for her--again figure very low tech small business--no IT
department'
Some other service to do it?
Thanks,
ShaneWrite one or a few ASPI.NET pages from which the user does backups. From
here you can use .ExecuteNonQuery and execute the appropriate BACKUP
DATABASE command. Note that the backup file will be created from the SQL
Server machine's perspective.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:%233WRgI5BEHA.3748@.tk2msftngp13.phx.gbl...
> I have written a SQL DB, and ASP.NET website for a client. The clients
> database and webpage are not inhouse but on a hosting provider.
> This provider says they only backup for disastor purposes--which didn't
make
> me feel to good.
> So my question...
> How can I help this non-techie client to backup her remote SQL Server
> Database regularly?
> What is the best means of doing this?
> Some software for her--again figure very low tech small business--no IT
> department'
> Some other service to do it?
> Thanks,
> Shane
>|||ok...
But where does that file reside?
If still no hosting site that isn't much of a backup.
Are you saying try to backup to a local protected directory, download the
backup file and in case of disaster client sends that backup file to people
on host site to restore?
Thanks,
Shane
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23Jy4hi5BEHA.3928@.TK2MSFTNGP11.phx.gbl...
> Write one or a few ASPI.NET pages from which the user does backups. From
> here you can use .ExecuteNonQuery and execute the appropriate BACKUP
> DATABASE command. Note that the backup file will be created from the SQL
> Server machine's perspective.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:%233WRgI5BEHA.3748@.tk2msftngp13.phx.gbl...
> make
>|||SQL Server does the backup, regardless of who submits the backup command.
Backup on C:\ and it is on C:\ on the SQL Server machine. You can then FTP
down the backup file or do whatever you want with it.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:%235k0gt5BEHA.3928@.TK2MSFTNGP11.phx.gbl...
> ok...
> But where does that file reside?
> If still no hosting site that isn't much of a backup.
> Are you saying try to backup to a local protected directory, download the
> backup file and in case of disaster client sends that backup file to
people
> on host site to restore?
> Thanks,
> Shane
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in
> message news:%23Jy4hi5BEHA.3928@.TK2MSFTNGP11.phx.gbl...
clients
didn't
IT
>|||Ok. Thanks.
My client isn't too good at even FTP, so I would have to some how provide a
secure link I suppose. Thanks for the reply.
Shane
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OtLfke6BEHA.916@.tk2msftngp13.phx.gbl...
> SQL Server does the backup, regardless of who submits the backup command.
> Backup on C:\ and it is on C:\ on the SQL Server machine. You can then FTP
> down the backup file or do whatever you want with it.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:%235k0gt5BEHA.3928@.TK2MSFTNGP11.phx.gbl...
the
> people
> in
From
SQL
message
> clients
> didn't
Server
> IT
>

backing up remote database

when I try to schedule a backup, or just do a backup, of a remote database
I get this error message:
"database 'msdb' cannot be opened. It has been marked SUSPECT by recovery."
I can connect to the database and view it.
I checked the error logs and there is no information about this error
listed.
I googled the error but did not find any solutions
Any insights to this error message ?
Answered in .programming
Please don't multi-post.
Regards
Mike
"TJS" wrote:

> when I try to schedule a backup, or just do a backup, of a remote database
> I get this error message:
> "database 'msdb' cannot be opened. It has been marked SUSPECT by recovery."
> I can connect to the database and view it.
> I checked the error logs and there is no information about this error
> listed.
> I googled the error but did not find any solutions
> Any insights to this error message ?
>
>

Backing up a database to a remote shared folder

We are using SQL 2K with sp4 on W2K servers but they are in windows workgroup
not domain. The SQL service is started by the local system account. I am
having a hard time trying to back up a database to a remote shared folder
located in another W2K server in the same windows workgroup. I believe it is
an authentication/permission issue. I am aware that SQL server looks at
network shared folder differently than the way Windows see but don't know
how to get around it under the workgroup setup. If it is under domain setup,
I have no problem.
Any help on this is very much appreciated.
Wingman
The account that SQL Server runs under must have permissions to that share.
Make sure you use UNC for the path and not a mapped drive.
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
> We are using SQL 2K with sp4 on W2K servers but they are in windows
> workgroup
> not domain. The SQL service is started by the local system account. I am
> having a hard time trying to back up a database to a remote shared folder
> located in another W2K server in the same windows workgroup. I believe it
> is
> an authentication/permission issue. I am aware that SQL server looks at
> network shared folder differently than the way Windows see but don't know
> how to get around it under the workgroup setup. If it is under domain
> setup,
> I have no problem.
> Any help on this is very much appreciated.
> Wingman
|||Yep, I know about the UNC part but how do I assign the local account that run
SQL server to that share under the WorkGroup envirnoment. I am not very
familar with the Windows Workgroup setup. From the computer that I have the
shared folder, I can't see any user account from other computers. I believe
it is because of the Workgroup setup but then again it may be just my
inexperience in this area. Please advise.
Wingman
"Andrew J. Kelly" wrote:

> The account that SQL Server runs under must have permissions to that share.
> Make sure you use UNC for the path and not a mapped drive.
> --
> Andrew J. Kelly SQL MVP
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
>
>
|||You'd have to create an account with same name and password as the service account on that other
machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...[vbcol=seagreen]
> Yep, I know about the UNC part but how do I assign the local account that run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have the
> shared folder, I can't see any user account from other computers. I believe
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
|||I am not sure if you can use the local service account or not in a workgroup
for this. You could set the permissions on the share to allow everyone to
read and write to it but that would obviously allow anyone with access to
that workgroup to access that share. Maybe someone with more experience in
WorkGroups can pipe in.
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...[vbcol=seagreen]
> Yep, I know about the UNC part but how do I assign the local account that
> run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have
> the
> shared folder, I can't see any user account from other computers. I
> believe
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
|||Yep, this does it. Thanks!!!
"Tibor Karaszi" wrote:

> You'd have to create an account with same name and password as the service account on that other
> machine.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...
>
sql

Backing up a database to a remote shared folder

We are using SQL 2K with sp4 on W2K servers but they are in windows workgrou
p
not domain. The SQL service is started by the local system account. I am
having a hard time trying to back up a database to a remote shared folder
located in another W2K server in the same windows workgroup. I believe it i
s
an authentication/permission issue. I am aware that SQL server looks at
network shared folder differently than the way Windows see but don't know
how to get around it under the workgroup setup. If it is under domain setup
,
I have no problem.
Any help on this is very much appreciated.
WingmanThe account that SQL Server runs under must have permissions to that share.
Make sure you use UNC for the path and not a mapped drive.
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
> We are using SQL 2K with sp4 on W2K servers but they are in windows
> workgroup
> not domain. The SQL service is started by the local system account. I am
> having a hard time trying to back up a database to a remote shared folder
> located in another W2K server in the same windows workgroup. I believe it
> is
> an authentication/permission issue. I am aware that SQL server looks at
> network shared folder differently than the way Windows see but don't know
> how to get around it under the workgroup setup. If it is under domain
> setup,
> I have no problem.
> Any help on this is very much appreciated.
> Wingman|||Yep, I know about the UNC part but how do I assign the local account that ru
n
SQL server to that share under the WorkGroup envirnoment. I am not very
familar with the Windows Workgroup setup. From the computer that I have the
shared folder, I can't see any user account from other computers. I believe
it is because of the Workgroup setup but then again it may be just my
inexperience in this area. Please advise.
Wingman
"Andrew J. Kelly" wrote:

> The account that SQL Server runs under must have permissions to that share
.
> Make sure you use UNC for the path and not a mapped drive.
> --
> Andrew J. Kelly SQL MVP
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
>
>|||You'd have to create an account with same name and password as the service a
ccount on that other
machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...[vbcol=seagreen]
> Yep, I know about the UNC part but how do I assign the local account that
run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have t
he
> shared folder, I can't see any user account from other computers. I belie
ve
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
>|||I am not sure if you can use the local service account or not in a workgroup
for this. You could set the permissions on the share to allow everyone to
read and write to it but that would obviously allow anyone with access to
that workgroup to access that share. Maybe someone with more experience in
WorkGroups can pipe in.
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...[vbcol=seagreen]
> Yep, I know about the UNC part but how do I assign the local account that
> run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have
> the
> shared folder, I can't see any user account from other computers. I
> believe
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
>|||Yep, this does it. Thanks!!!
"Tibor Karaszi" wrote:

> You'd have to create an account with same name and password as the service
account on that other
> machine.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...
>

Backing up a database to a remote shared folder

We are using SQL 2K with sp4 on W2K servers but they are in windows workgroup
not domain. The SQL service is started by the local system account. I am
having a hard time trying to back up a database to a remote shared folder
located in another W2K server in the same windows workgroup. I believe it is
an authentication/permission issue. I am aware that SQL server looks at
network shared folder differently than the way Windows see but don't know
how to get around it under the workgroup setup. If it is under domain setup,
I have no problem.
Any help on this is very much appreciated.
WingmanThe account that SQL Server runs under must have permissions to that share.
Make sure you use UNC for the path and not a mapped drive.
--
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
> We are using SQL 2K with sp4 on W2K servers but they are in windows
> workgroup
> not domain. The SQL service is started by the local system account. I am
> having a hard time trying to back up a database to a remote shared folder
> located in another W2K server in the same windows workgroup. I believe it
> is
> an authentication/permission issue. I am aware that SQL server looks at
> network shared folder differently than the way Windows see but don't know
> how to get around it under the workgroup setup. If it is under domain
> setup,
> I have no problem.
> Any help on this is very much appreciated.
> Wingman|||Yep, I know about the UNC part but how do I assign the local account that run
SQL server to that share under the WorkGroup envirnoment. I am not very
familar with the Windows Workgroup setup. From the computer that I have the
shared folder, I can't see any user account from other computers. I believe
it is because of the Workgroup setup but then again it may be just my
inexperience in this area. Please advise.
Wingman
"Andrew J. Kelly" wrote:
> The account that SQL Server runs under must have permissions to that share.
> Make sure you use UNC for the path and not a mapped drive.
> --
> Andrew J. Kelly SQL MVP
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
> > We are using SQL 2K with sp4 on W2K servers but they are in windows
> > workgroup
> > not domain. The SQL service is started by the local system account. I am
> > having a hard time trying to back up a database to a remote shared folder
> > located in another W2K server in the same windows workgroup. I believe it
> > is
> > an authentication/permission issue. I am aware that SQL server looks at
> > network shared folder differently than the way Windows see but don't know
> > how to get around it under the workgroup setup. If it is under domain
> > setup,
> > I have no problem.
> >
> > Any help on this is very much appreciated.
> >
> > Wingman
>
>|||You'd have to create an account with same name and password as the service account on that other
machine.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...
> Yep, I know about the UNC part but how do I assign the local account that run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have the
> shared folder, I can't see any user account from other computers. I believe
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
>> The account that SQL Server runs under must have permissions to that share.
>> Make sure you use UNC for the path and not a mapped drive.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
>> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
>> > We are using SQL 2K with sp4 on W2K servers but they are in windows
>> > workgroup
>> > not domain. The SQL service is started by the local system account. I am
>> > having a hard time trying to back up a database to a remote shared folder
>> > located in another W2K server in the same windows workgroup. I believe it
>> > is
>> > an authentication/permission issue. I am aware that SQL server looks at
>> > network shared folder differently than the way Windows see but don't know
>> > how to get around it under the workgroup setup. If it is under domain
>> > setup,
>> > I have no problem.
>> >
>> > Any help on this is very much appreciated.
>> >
>> > Wingman
>>|||I am not sure if you can use the local service account or not in a workgroup
for this. You could set the permissions on the share to allow everyone to
read and write to it but that would obviously allow anyone with access to
that workgroup to access that share. Maybe someone with more experience in
WorkGroups can pipe in.
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...
> Yep, I know about the UNC part but how do I assign the local account that
> run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have
> the
> shared folder, I can't see any user account from other computers. I
> believe
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
>> The account that SQL Server runs under must have permissions to that
>> share.
>> Make sure you use UNC for the path and not a mapped drive.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
>> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
>> > We are using SQL 2K with sp4 on W2K servers but they are in windows
>> > workgroup
>> > not domain. The SQL service is started by the local system account. I
>> > am
>> > having a hard time trying to back up a database to a remote shared
>> > folder
>> > located in another W2K server in the same windows workgroup. I believe
>> > it
>> > is
>> > an authentication/permission issue. I am aware that SQL server looks
>> > at
>> > network shared folder differently than the way Windows see but don't
>> > know
>> > how to get around it under the workgroup setup. If it is under domain
>> > setup,
>> > I have no problem.
>> >
>> > Any help on this is very much appreciated.
>> >
>> > Wingman
>>|||Yep, this does it. Thanks!!!
"Tibor Karaszi" wrote:
> You'd have to create an account with same name and password as the service account on that other
> machine.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...
> > Yep, I know about the UNC part but how do I assign the local account that run
> > SQL server to that share under the WorkGroup envirnoment. I am not very
> > familar with the Windows Workgroup setup. From the computer that I have the
> > shared folder, I can't see any user account from other computers. I believe
> > it is because of the Workgroup setup but then again it may be just my
> > inexperience in this area. Please advise.
> >
> > Wingman
> >
> > "Andrew J. Kelly" wrote:
> >
> >> The account that SQL Server runs under must have permissions to that share.
> >> Make sure you use UNC for the path and not a mapped drive.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> >> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
> >> > We are using SQL 2K with sp4 on W2K servers but they are in windows
> >> > workgroup
> >> > not domain. The SQL service is started by the local system account. I am
> >> > having a hard time trying to back up a database to a remote shared folder
> >> > located in another W2K server in the same windows workgroup. I believe it
> >> > is
> >> > an authentication/permission issue. I am aware that SQL server looks at
> >> > network shared folder differently than the way Windows see but don't know
> >> > how to get around it under the workgroup setup. If it is under domain
> >> > setup,
> >> > I have no problem.
> >> >
> >> > Any help on this is very much appreciated.
> >> >
> >> > Wingman
> >>
> >>
> >>
>

Back up on remote computer.

We have 5 computer (peer-to-peer).
SQL Serve is intalled on one machine. I want to do the
backup (put the backup files) on remote machine but it
doesn't show the network drives. It just shows the local
drives.
How can I do the backup on remote machine?
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:01be01c4a00d$b3c7a0c0$a401280a@.phx.gbl...
> We have 5 computer (peer-to-peer).
> SQL Serve is intalled on one machine. I want to do the
> backup (put the backup files) on remote machine but it
> doesn't show the network drives. It just shows the local
> drives.
> How can I do the backup on remote machine?
|||Backup to the fully-qualified UNC name rather than a mapped drive letter.
For example: \\machine_name\share\backups. The mapped drives visible to you
on your machine won't necessarily be available to SQL Server.
David Portas
SQL Server MVP
|||Good one, Geoff,. Short and straight to the point.
(The MS disclaimer is probably more text than the actual KB. :-) )
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:eZ9$YLBoEHA.2096@.TK2MSFTNGP15.phx.gbl...
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?kbid=555128
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> <anonymous@.discussions.microsoft.com> wrote in message
> news:01be01c4a00d$b3c7a0c0$a401280a@.phx.gbl...
>
|||The MSDN Article you mentioned/wrote says:
"1) The SQL Server service must be running under a domain-
level account."
My questions are:
(1) How do I know whether my SQL Server service is running
under a domain-level account or not?
(2) All our computers are in a Workgroup. What steps
should I take to start the SQL Server service to run under
domain-level account.
Our SQL Server is Standard Edition and version is 2000
SP3a.

>--Original Message--
>HowTo: Backup to UNC name using Database Maintenance
Wizard
>http://support.microsoft.com/?kbid=555128
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
><anonymous@.discussions.microsoft.com> wrote in message
>news:01be01c4a00d$b3c7a0c0$a401280a@.phx.gbl...
>
>.
>
|||Comments Inline
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:346801c4a020$e318d6b0$a501280a@.phx.gbl...
> The MSDN Article you mentioned/wrote says:
> "1) The SQL Server service must be running under a domain-
> level account."
> My questions are:
> (1) How do I know whether my SQL Server service is running
> under a domain-level account or not?
>
Look under the Services applet in Control Panel for the SQL Server service
(MSSQLSERVER) or Enterprise manager Properties page Security tab. A
domain-level account is one that authenticates as Domain_Name\LoginName

> (2) All our computers are in a Workgroup. What steps
> should I take to start the SQL Server service to run under
> domain-level account.
I haven't tried this in a workgroup. It might work if you have a login and
password that is the same on both servers that you run the SQL service
under. The other option is to create a domain.[vbcol=seagreen]
> Our SQL Server is Standard Edition and version is 2000
> SP3a.
>
> Wizard
|||Thanks. There seemed to be a need for something to explain how to do this.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uYgKQsBoEHA.3460@.tk2msftngp13.phx.gbl...
> Good one, Geoff,. Short and straight to the point.
> (The MS disclaimer is probably more text than the actual KB. :-) )
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:eZ9$YLBoEHA.2096@.TK2MSFTNGP15.phx.gbl...
>
|||We have 5 machines. First machine Windows 2000 Server (SQL
Server 2000 Standard is installed here). Rest of the
machines have Windows 2000 Pro.
Keep the above scenario in mind, could you explain me what
you wrote earlier:

>It might work if you have a login and password that is
> the same on both servers that you run the SQL service
>under. The other option is to create a domain.
|||OK. Create a login on the SQL host computer. Put it in the local
administrators group on that machine. Change the SQL Service to run under
that login. Create a login on the backup target machine with the exact same
username and password. Grant that login full control over the file share
and the NTFS folder you want to back up to. No guarantees, but this may
work in a workgroup.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:426701c4a023$dc891f50$a301280a@.phx.gbl...
> We have 5 machines. First machine Windows 2000 Server (SQL
> Server 2000 Standard is installed here). Rest of the
> machines have Windows 2000 Pro.
> Keep the above scenario in mind, could you explain me what
> you wrote earlier:
>
|||On Windows 2000 Server Machine the SQLServer Services are
running under Administrator. Also on the other computer
(windows 2000 professional) login is administrator (and
obviously has all rights on the shared folder).
This doesn't work when I try to backup on that shared
folder. The error says that location of the (backup) file
cannot be verified..do u want to continue...and when I
say YES then after a couple of seconds the backup process
stops."
SO does this CONCLUDE that this is not possible in
Workgroup scenario?
Thank you.

>--Original Message--
>OK. Create a login on the SQL host computer. Put it in
the local
>administrators group on that machine. Change the SQL
Service to run under
>that login. Create a login on the backup target machine
with the exact same
>username and password. Grant that login full control
over the file share
>and the NTFS folder you want to back up to. No
guarantees, but this may[vbcol=seagreen]
>work in a workgroup.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
><anonymous@.discussions.microsoft.com> wrote in message
>news:426701c4a023$dc891f50$a301280a@.phx.gbl...
(SQL[vbcol=seagreen]
what
>
>.
>

Back up on remote computer.

We have 5 computer (peer-to-peer).
SQL Serve is intalled on one machine. I want to do the
backup (put the backup files) on remote machine but it
doesn't show the network drives. It just shows the local
drives.
How can I do the backup on remote machine?HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:01be01c4a00d$b3c7a0c0$a401280a@.phx.gbl...
> We have 5 computer (peer-to-peer).
> SQL Serve is intalled on one machine. I want to do the
> backup (put the backup files) on remote machine but it
> doesn't show the network drives. It just shows the local
> drives.
> How can I do the backup on remote machine?|||Backup to the fully-qualified UNC name rather than a mapped drive letter.
For example: \\machine_name\share\backups. The mapped drives visible to you
on your machine won't necessarily be available to SQL Server.
--
David Portas
SQL Server MVP
--|||Good one, Geoff,. Short and straight to the point.
(The MS disclaimer is probably more text than the actual KB. :-) )
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:eZ9$YLBoEHA.2096@.TK2MSFTNGP15.phx.gbl...
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?kbid=555128
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> <anonymous@.discussions.microsoft.com> wrote in message
> news:01be01c4a00d$b3c7a0c0$a401280a@.phx.gbl...
>> We have 5 computer (peer-to-peer).
>> SQL Serve is intalled on one machine. I want to do the
>> backup (put the backup files) on remote machine but it
>> doesn't show the network drives. It just shows the local
>> drives.
>> How can I do the backup on remote machine?
>|||The MSDN Article you mentioned/wrote says:
"1) The SQL Server service must be running under a domain-
level account."
My questions are:
(1) How do I know whether my SQL Server service is running
under a domain-level account or not?
(2) All our computers are in a Workgroup. What steps
should I take to start the SQL Server service to run under
domain-level account.
Our SQL Server is Standard Edition and version is 2000
SP3a.
>--Original Message--
>HowTo: Backup to UNC name using Database Maintenance
Wizard
>http://support.microsoft.com/?kbid=555128
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
><anonymous@.discussions.microsoft.com> wrote in message
>news:01be01c4a00d$b3c7a0c0$a401280a@.phx.gbl...
>> We have 5 computer (peer-to-peer).
>> SQL Serve is intalled on one machine. I want to do the
>> backup (put the backup files) on remote machine but it
>> doesn't show the network drives. It just shows the local
>> drives.
>> How can I do the backup on remote machine?
>
>.
>|||Comments Inline
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:346801c4a020$e318d6b0$a501280a@.phx.gbl...
> The MSDN Article you mentioned/wrote says:
> "1) The SQL Server service must be running under a domain-
> level account."
> My questions are:
> (1) How do I know whether my SQL Server service is running
> under a domain-level account or not?
>
Look under the Services applet in Control Panel for the SQL Server service
(MSSQLSERVER) or Enterprise manager Properties page Security tab. A
domain-level account is one that authenticates as Domain_Name\LoginName
> (2) All our computers are in a Workgroup. What steps
> should I take to start the SQL Server service to run under
> domain-level account.
I haven't tried this in a workgroup. It might work if you have a login and
password that is the same on both servers that you run the SQL service
under. The other option is to create a domain.
> Our SQL Server is Standard Edition and version is 2000
> SP3a.
>
> >--Original Message--
> >HowTo: Backup to UNC name using Database Maintenance
> Wizard
> >http://support.microsoft.com/?kbid=555128
> >
> >--
> >Geoff N. Hiten
> >Microsoft SQL Server MVP
> >Senior Database Administrator
> >Careerbuilder.com
> >
> >I support the Professional Association for SQL Server
> >www.sqlpass.org
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:01be01c4a00d$b3c7a0c0$a401280a@.phx.gbl...
> >> We have 5 computer (peer-to-peer).
> >>
> >> SQL Serve is intalled on one machine. I want to do the
> >> backup (put the backup files) on remote machine but it
> >> doesn't show the network drives. It just shows the local
> >> drives.
> >>
> >> How can I do the backup on remote machine?
> >
> >
> >.
> >|||Thanks. There seemed to be a need for something to explain how to do this.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uYgKQsBoEHA.3460@.tk2msftngp13.phx.gbl...
> Good one, Geoff,. Short and straight to the point.
> (The MS disclaimer is probably more text than the actual KB. :-) )
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:eZ9$YLBoEHA.2096@.TK2MSFTNGP15.phx.gbl...
> > HowTo: Backup to UNC name using Database Maintenance Wizard
> > http://support.microsoft.com/?kbid=555128
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > <anonymous@.discussions.microsoft.com> wrote in message
> > news:01be01c4a00d$b3c7a0c0$a401280a@.phx.gbl...
> >> We have 5 computer (peer-to-peer).
> >>
> >> SQL Serve is intalled on one machine. I want to do the
> >> backup (put the backup files) on remote machine but it
> >> doesn't show the network drives. It just shows the local
> >> drives.
> >>
> >> How can I do the backup on remote machine?
> >
> >
>|||We have 5 machines. First machine Windows 2000 Server (SQL
Server 2000 Standard is installed here). Rest of the
machines have Windows 2000 Pro.
Keep the above scenario in mind, could you explain me what
you wrote earlier:
>It might work if you have a login and password that is
> the same on both servers that you run the SQL service
>under. The other option is to create a domain.|||OK. Create a login on the SQL host computer. Put it in the local
administrators group on that machine. Change the SQL Service to run under
that login. Create a login on the backup target machine with the exact same
username and password. Grant that login full control over the file share
and the NTFS folder you want to back up to. No guarantees, but this may
work in a workgroup.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:426701c4a023$dc891f50$a301280a@.phx.gbl...
> We have 5 machines. First machine Windows 2000 Server (SQL
> Server 2000 Standard is installed here). Rest of the
> machines have Windows 2000 Pro.
> Keep the above scenario in mind, could you explain me what
> you wrote earlier:
> >It might work if you have a login and password that is
> > the same on both servers that you run the SQL service
> >under. The other option is to create a domain.
>|||On Windows 2000 Server Machine the SQLServer Services are
running under Administrator. Also on the other computer
(windows 2000 professional) login is administrator (and
obviously has all rights on the shared folder).
This doesn't work when I try to backup on that shared
folder. The error says that location of the (backup) file
cannot be verified..do u want to continue...and when I
say YES then after a couple of seconds the backup process
stops."
SO does this CONCLUDE that this is not possible in
Workgroup scenario?
Thank you.
>--Original Message--
>OK. Create a login on the SQL host computer. Put it in
the local
>administrators group on that machine. Change the SQL
Service to run under
>that login. Create a login on the backup target machine
with the exact same
>username and password. Grant that login full control
over the file share
>and the NTFS folder you want to back up to. No
guarantees, but this may
>work in a workgroup.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
><anonymous@.discussions.microsoft.com> wrote in message
>news:426701c4a023$dc891f50$a301280a@.phx.gbl...
>> We have 5 machines. First machine Windows 2000 Server
(SQL
>> Server 2000 Standard is installed here). Rest of the
>> machines have Windows 2000 Pro.
>> Keep the above scenario in mind, could you explain me
what
>> you wrote earlier:
>> >It might work if you have a login and password that is
>> > the same on both servers that you run the SQL service
>> >under. The other option is to create a domain.
>
>.
>|||Do the Administrator account have the same password on the two machines?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:36e801c4a05b$6dd83310$a501280a@.phx.gbl...
> On Windows 2000 Server Machine the SQLServer Services are
> running under Administrator. Also on the other computer
> (windows 2000 professional) login is administrator (and
> obviously has all rights on the shared folder).
> This doesn't work when I try to backup on that shared
> folder. The error says that location of the (backup) file
> cannot be verified..do u want to continue...and when I
> say YES then after a couple of seconds the backup process
> stops."
> SO does this CONCLUDE that this is not possible in
> Workgroup scenario?
> Thank you.
> >--Original Message--
> >OK. Create a login on the SQL host computer. Put it in
> the local
> >administrators group on that machine. Change the SQL
> Service to run under
> >that login. Create a login on the backup target machine
> with the exact same
> >username and password. Grant that login full control
> over the file share
> >and the NTFS folder you want to back up to. No
> guarantees, but this may
> >work in a workgroup.
> >
> >--
> >Geoff N. Hiten
> >Microsoft SQL Server MVP
> >Senior Database Administrator
> >Careerbuilder.com
> >
> >I support the Professional Association for SQL Server
> >www.sqlpass.org
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:426701c4a023$dc891f50$a301280a@.phx.gbl...
> >> We have 5 machines. First machine Windows 2000 Server
> (SQL
> >> Server 2000 Standard is installed here). Rest of the
> >> machines have Windows 2000 Pro.
> >>
> >> Keep the above scenario in mind, could you explain me
> what
> >> you wrote earlier:
> >>
> >> >It might work if you have a login and password that is
> >> > the same on both servers that you run the SQL service
> >> >under. The other option is to create a domain.
> >>
> >
> >
> >.
> >|||Yes.
>--Original Message--
>Do the Administrator account have the same password on
the two machines?
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:36e801c4a05b$6dd83310$a501280a@.phx.gbl...
>> On Windows 2000 Server Machine the SQLServer Services
are
>> running under Administrator. Also on the other computer
>> (windows 2000 professional) login is administrator (and
>> obviously has all rights on the shared folder).
>> This doesn't work when I try to backup on that shared
>> folder. The error says that location of the (backup)
file
>> cannot be verified..do u want to continue...and when I
>> say YES then after a couple of seconds the backup
process
>> stops."
>> SO does this CONCLUDE that this is not possible in
>> Workgroup scenario?
>> Thank you.
>> >--Original Message--
>> >OK. Create a login on the SQL host computer. Put it
in
>> the local
>> >administrators group on that machine. Change the SQL
>> Service to run under
>> >that login. Create a login on the backup target
machine
>> with the exact same
>> >username and password. Grant that login full control
>> over the file share
>> >and the NTFS folder you want to back up to. No
>> guarantees, but this may
>> >work in a workgroup.
>> >
>> >--
>> >Geoff N. Hiten
>> >Microsoft SQL Server MVP
>> >Senior Database Administrator
>> >Careerbuilder.com
>> >
>> >I support the Professional Association for SQL Server
>> >www.sqlpass.org
>> >
>> ><anonymous@.discussions.microsoft.com> wrote in message
>> >news:426701c4a023$dc891f50$a301280a@.phx.gbl...
>> >> We have 5 machines. First machine Windows 2000
Server
>> (SQL
>> >> Server 2000 Standard is installed here). Rest of the
>> >> machines have Windows 2000 Pro.
>> >>
>> >> Keep the above scenario in mind, could you explain
me
>> what
>> >> you wrote earlier:
>> >>
>> >> >It might work if you have a login and password
that is
>> >> > the same on both servers that you run the SQL
service
>> >> >under. The other option is to create a domain.
>> >>
>> >
>> >
>> >.
>> >
>
>.
>|||Are you using an UNC path or a mapped drive?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:12fb01c4a074$c5073190$a601280a@.phx.gbl...
> Yes.
> >--Original Message--
> >Do the Administrator account have the same password on
> the two machines?
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >http://www.karaszi.com/sqlserver/default.asp
> >http://www.solidqualitylearning.com/
> >
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:36e801c4a05b$6dd83310$a501280a@.phx.gbl...
> >> On Windows 2000 Server Machine the SQLServer Services
> are
> >> running under Administrator. Also on the other computer
> >> (windows 2000 professional) login is administrator (and
> >> obviously has all rights on the shared folder).
> >>
> >> This doesn't work when I try to backup on that shared
> >> folder. The error says that location of the (backup)
> file
> >> cannot be verified..do u want to continue...and when I
> >> say YES then after a couple of seconds the backup
> process
> >> stops."
> >>
> >> SO does this CONCLUDE that this is not possible in
> >> Workgroup scenario?
> >>
> >> Thank you.
> >>
> >> >--Original Message--
> >> >OK. Create a login on the SQL host computer. Put it
> in
> >> the local
> >> >administrators group on that machine. Change the SQL
> >> Service to run under
> >> >that login. Create a login on the backup target
> machine
> >> with the exact same
> >> >username and password. Grant that login full control
> >> over the file share
> >> >and the NTFS folder you want to back up to. No
> >> guarantees, but this may
> >> >work in a workgroup.
> >> >
> >> >--
> >> >Geoff N. Hiten
> >> >Microsoft SQL Server MVP
> >> >Senior Database Administrator
> >> >Careerbuilder.com
> >> >
> >> >I support the Professional Association for SQL Server
> >> >www.sqlpass.org
> >> >
> >> ><anonymous@.discussions.microsoft.com> wrote in message
> >> >news:426701c4a023$dc891f50$a301280a@.phx.gbl...
> >> >> We have 5 machines. First machine Windows 2000
> Server
> >> (SQL
> >> >> Server 2000 Standard is installed here). Rest of the
> >> >> machines have Windows 2000 Pro.
> >> >>
> >> >> Keep the above scenario in mind, could you explain
> me
> >> what
> >> >> you wrote earlier:
> >> >>
> >> >> >It might work if you have a login and password
> that is
> >> >> > the same on both servers that you run the SQL
> service
> >> >> >under. The other option is to create a domain.
> >> >>
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >|||I am using UNC path.
>--Original Message--
>Are you using an UNC path or a mapped drive?
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:12fb01c4a074$c5073190$a601280a@.phx.gbl...
>> Yes.
>> >--Original Message--
>> >Do the Administrator account have the same password on
>> the two machines?
>> >
>> >--
>> >Tibor Karaszi, SQL Server MVP
>> >http://www.karaszi.com/sqlserver/default.asp
>> >http://www.solidqualitylearning.com/
>> >
>> >
>> ><anonymous@.discussions.microsoft.com> wrote in message
>> >news:36e801c4a05b$6dd83310$a501280a@.phx.gbl...
>> >> On Windows 2000 Server Machine the SQLServer
Services
>> are
>> >> running under Administrator. Also on the other
computer
>> >> (windows 2000 professional) login is administrator
(and
>> >> obviously has all rights on the shared folder).
>> >>
>> >> This doesn't work when I try to backup on that
shared
>> >> folder. The error says that location of the (backup)
>> file
>> >> cannot be verified..do u want to continue...and
when I
>> >> say YES then after a couple of seconds the backup
>> process
>> >> stops."
>> >>
>> >> SO does this CONCLUDE that this is not possible in
>> >> Workgroup scenario?
>> >>
>> >> Thank you.
>> >>
>> >> >--Original Message--
>> >> >OK. Create a login on the SQL host computer. Put
it
>> in
>> >> the local
>> >> >administrators group on that machine. Change the
SQL
>> >> Service to run under
>> >> >that login. Create a login on the backup target
>> machine
>> >> with the exact same
>> >> >username and password. Grant that login full
control
>> >> over the file share
>> >> >and the NTFS folder you want to back up to. No
>> >> guarantees, but this may
>> >> >work in a workgroup.
>> >> >
>> >> >--
>> >> >Geoff N. Hiten
>> >> >Microsoft SQL Server MVP
>> >> >Senior Database Administrator
>> >> >Careerbuilder.com
>> >> >
>> >> >I support the Professional Association for SQL
Server
>> >> >www.sqlpass.org
>> >> >
>> >> ><anonymous@.discussions.microsoft.com> wrote in
message
>> >> >news:426701c4a023$dc891f50$a301280a@.phx.gbl...
>> >> >> We have 5 machines. First machine Windows 2000
>> Server
>> >> (SQL
>> >> >> Server 2000 Standard is installed here). Rest of
the
>> >> >> machines have Windows 2000 Pro.
>> >> >>
>> >> >> Keep the above scenario in mind, could you
explain
>> me
>> >> what
>> >> >> you wrote earlier:
>> >> >>
>> >> >> >It might work if you have a login and password
>> that is
>> >> >> > the same on both servers that you run the SQL
>> service
>> >> >> >under. The other option is to create a domain.
>> >> >>
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>.
>|||That is strange. I just did exactly that. I have a workgroup, and SQL Server is running under a
service account that also exists on the other machine, having the same password on both machines. I
executed below command, and it worked perfectly:
BACKUP DATABASE pubs TO DISK = '\\TibMedia\C\pubs.bak'
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:3b8001c4a0ad$30389f20$a501280a@.phx.gbl...
>I am using UNC path.
>>--Original Message--
>>Are you using an UNC path or a mapped drive?
>>--
>>Tibor Karaszi, SQL Server MVP
>>http://www.karaszi.com/sqlserver/default.asp
>>http://www.solidqualitylearning.com/
>>
>><anonymous@.discussions.microsoft.com> wrote in message
>>news:12fb01c4a074$c5073190$a601280a@.phx.gbl...
>> Yes.
>> >--Original Message--
>> >Do the Administrator account have the same password on
>> the two machines?
>> >
>> >--
>> >Tibor Karaszi, SQL Server MVP
>> >http://www.karaszi.com/sqlserver/default.asp
>> >http://www.solidqualitylearning.com/
>> >
>> >
>> ><anonymous@.discussions.microsoft.com> wrote in message
>> >news:36e801c4a05b$6dd83310$a501280a@.phx.gbl...
>> >> On Windows 2000 Server Machine the SQLServer
> Services
>> are
>> >> running under Administrator. Also on the other
> computer
>> >> (windows 2000 professional) login is administrator
> (and
>> >> obviously has all rights on the shared folder).
>> >>
>> >> This doesn't work when I try to backup on that
> shared
>> >> folder. The error says that location of the (backup)
>> file
>> >> cannot be verified..do u want to continue...and
> when I
>> >> say YES then after a couple of seconds the backup
>> process
>> >> stops."
>> >>
>> >> SO does this CONCLUDE that this is not possible in
>> >> Workgroup scenario?
>> >>
>> >> Thank you.
>> >>
>> >> >--Original Message--
>> >> >OK. Create a login on the SQL host computer. Put
> it
>> in
>> >> the local
>> >> >administrators group on that machine. Change the
> SQL
>> >> Service to run under
>> >> >that login. Create a login on the backup target
>> machine
>> >> with the exact same
>> >> >username and password. Grant that login full
> control
>> >> over the file share
>> >> >and the NTFS folder you want to back up to. No
>> >> guarantees, but this may
>> >> >work in a workgroup.
>> >> >
>> >> >--
>> >> >Geoff N. Hiten
>> >> >Microsoft SQL Server MVP
>> >> >Senior Database Administrator
>> >> >Careerbuilder.com
>> >> >
>> >> >I support the Professional Association for SQL
> Server
>> >> >www.sqlpass.org
>> >> >
>> >> ><anonymous@.discussions.microsoft.com> wrote in
> message
>> >> >news:426701c4a023$dc891f50$a301280a@.phx.gbl...
>> >> >> We have 5 machines. First machine Windows 2000
>> Server
>> >> (SQL
>> >> >> Server 2000 Standard is installed here). Rest of
> the
>> >> >> machines have Windows 2000 Pro.
>> >> >>
>> >> >> Keep the above scenario in mind, could you
> explain
>> me
>> >> what
>> >> >> you wrote earlier:
>> >> >>
>> >> >> >It might work if you have a login and password
>> that is
>> >> >> > the same on both servers that you run the SQL
>> service
>> >> >> >under. The other option is to create a domain.
>> >> >>
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>>
>>.

Avoiding the usage of DTC

Hello

I am running an script and the following sentence throws and error because the DTC service is not running in the Remote Server:

insert into MyLocalTable
execute synonym_MyRemoteProcedure @.SomeParameter

Since a transaction is not declared within the script, why is the DTC required?
How can I avoid the usage of the DTC? Is there a way to say "this code is not within a distributed transaction"?

Thanks a lot.You are still in an explicit transaction. As far as I know, the requirement that the DTC service be running can not be bypassed. You can try using just a select statement to get the data from the remote server, as the "black box" nature of the stored procedure may be causing this.

Avoiding "Violation of Primary Key" with replication

I have a centralized database (server A), and two remote databases
(server B & C) all with a copy of the same database with a table with
user entered, primary key like ProductID. There is a possiblity that
the same ProductID gets entered into both B & C (which is ok).
I create a snapshot of B and replicate to A.
Is there a way to replicate C to server A and have replication ignore
any Primary Key violations during replication?
you can select the continue on data consistency profile. To do this right
click on your distribution agent and select agent profiles.
I would however advise you to come up with some partitioning scheme -
whether this involves adding another column to your pk with a location
specific parameter, or if you are using the identity property on you pk, go
to server b and type
DBCC Checkident ('YourTable',1000000)
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<dkolva@.atlab.com> wrote in message
news:1110815869.167577.303520@.g14g2000cwa.googlegr oups.com...
> I have a centralized database (server A), and two remote databases
> (server B & C) all with a copy of the same database with a table with
> user entered, primary key like ProductID. There is a possiblity that
> the same ProductID gets entered into both B & C (which is ok).
> I create a snapshot of B and replicate to A.
> Is there a way to replicate C to server A and have replication ignore
> any Primary Key violations during replication?
>

avoid a server from being linked?

i say
that the server can listen
TCP/uid+pwd connections
but it reject links from remote sql servers
atte,
Hernn Castelo
SGA - UTN - FRBA
I am not sure what you are asking but it sound like you want to prevent a
SQL server from being used a s a linked server. If this is the question, I
am not sure that you can do this. As long as a user has a valid method to
connect then a linked server can be created.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||excuse me for my english!
exactly
that is what i wanted to know...
atte,
Hernn Castelo
SGA - UTN - FRBA
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> escribi en el mensaje
news:lwrz76K0EHA.3028@.cpmsftngxa10.phx.gbl...
> I am not sure what you are asking but it sound like you want to prevent a
> SQL server from being used a s a linked server. If this is the question, I
> am not sure that you can do this. As long as a user has a valid method to
> connect then a linked server can be created.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

avoid a server from being linked?

i say
that the server can listen
TCP/uid+pwd connections
but it reject links from remote sql servers
atte,
Hernn Castelo
SGA - UTN - FRBAI am not sure what you are asking but it sound like you want to prevent a
SQL server from being used a s a linked server. If this is the question, I
am not sure that you can do this. As long as a user has a valid method to
connect then a linked server can be created.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||excuse me for my english!
exactly
that is what i wanted to know...
atte,
Hernn Castelo
SGA - UTN - FRBA
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> escribi en el mensaje
news:lwrz76K0EHA.3028@.cpmsftngxa10.phx.gbl...
> I am not sure what you are asking but it sound like you want to prevent a
> SQL server from being used a s a linked server. If this is the question, I
> am not sure that you can do this. As long as a user has a valid method to
> connect then a linked server can be created.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

avoid a server from being linked?

i say
that the server can listen
TCP/uid+pwd connections
but it reject links from remote sql servers
--
atte,
Hernán Castelo
SGA - UTN - FRBAI am not sure what you are asking but it sound like you want to prevent a
SQL server from being used a s a linked server. If this is the question, I
am not sure that you can do this. As long as a user has a valid method to
connect then a linked server can be created.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||excuse me for my english!
exactly
that is what i wanted to know...
--
atte,
Hernán Castelo
SGA - UTN - FRBA
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> escribió en el mensaje
news:lwrz76K0EHA.3028@.cpmsftngxa10.phx.gbl...
> I am not sure what you are asking but it sound like you want to prevent a
> SQL server from being used a s a linked server. If this is the question, I
> am not sure that you can do this. As long as a user has a valid method to
> connect then a linked server can be created.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>