I have SQL 2000 on a W2K advanced server. I want to use SQL server's
backup routine to backup the databases to a directory on a separate
computer. I have set up the SQL Client Agent on that other server hoping
that would somehow facilitate this, but there doesn't seem to be any way
to force SQL server to backup the file to a device that is not local to
the server itself.
I understand that one possible option would be to install a full version
of SQL 2000 on the other server and has the primary backup to that
secondary server. But that would mean 2 licenses of SQL Server. I
don't think we have 2 licenses, though I will check on that.
Surely there is some way to backup databases to an non-local device.
CurtisHowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?id=555128
The same technique applies to manual backup jobs as well.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message
news:eiqgAsisEHA.1468@.TK2MSFTNGP12.phx.gbl...
> I have SQL 2000 on a W2K advanced server. I want to use SQL server's
> backup routine to backup the databases to a directory on a separate
> computer. I have set up the SQL Client Agent on that other server hoping
> that would somehow facilitate this, but there doesn't seem to be any way
> to force SQL server to backup the file to a device that is not local to
> the server itself.
> I understand that one possible option would be to install a full version
> of SQL 2000 on the other server and has the primary backup to that
> secondary server. But that would mean 2 licenses of SQL Server. I
> don't think we have 2 licenses, though I will check on that.
> Surely there is some way to backup databases to an non-local device.
> Curtis|||So, if I understand correctly the MSSQLSERVER service must be switched
from running under the LocalSystem account to running under a
domain-level account, such as, let's say, DataAdmin with a password. And
which account is not local to the server, but global to the domain. Right?
If that's true, what rights do I have to give the DataAdmin account?
Curtis
Geoff N. Hiten wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?id=555128
> The same technique applies to manual backup jobs as well.
>|||Curtis,
Per the KB article ...
2) The SQL Server service account must have FULL CONTROL rights to the file
system folder and to the share
Tunji
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message news:envLaWjsEHA.160@.
TK2MSFTNGP11.phx.gbl...
So, if I understand correctly the MSSQLSERVER service must be switched
from running under the LocalSystem account to running under a
domain-level account, such as, let's say, DataAdmin with a password. And
which account is not local to the server, but global to the domain. Right?
If that's true, what rights do I have to give the DataAdmin account?
Curtis
Geoff N. Hiten wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?id=555128
>
> The same technique applies to manual backup jobs as well.
>|||Everything works better if you give the domain-level account (DataAdmin in
your example) local administrator rights on the SQL server host computer.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message
news:envLaWjsEHA.160@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> So, if I understand correctly the MSSQLSERVER service must be switched
> from running under the LocalSystem account to running under a
> domain-level account, such as, let's say, DataAdmin with a password. And
> which account is not local to the server, but global to the domain. Right?
> If that's true, what rights do I have to give the DataAdmin account?
> Curtis
> Geoff N. Hiten wrote:
>
Showing posts with label w2k. Show all posts
Showing posts with label w2k. Show all posts
Sunday, March 25, 2012
Backing up Databases using SQLServer
I have SQL 2000 on a W2K advanced server. I want to use SQL server's
backup routine to backup the databases to a directory on a separate
computer. I have set up the SQL Client Agent on that other server hoping
that would somehow facilitate this, but there doesn't seem to be any way
to force SQL server to backup the file to a device that is not local to
the server itself.
I understand that one possible option would be to install a full version
of SQL 2000 on the other server and has the primary backup to that
secondary server. But that would mean 2 licenses of SQL Server. I
don't think we have 2 licenses, though I will check on that.
Surely there is some way to backup databases to an non-local device.
Curtis
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?id=555128
The same technique applies to manual backup jobs as well.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message
news:eiqgAsisEHA.1468@.TK2MSFTNGP12.phx.gbl...
> I have SQL 2000 on a W2K advanced server. I want to use SQL server's
> backup routine to backup the databases to a directory on a separate
> computer. I have set up the SQL Client Agent on that other server hoping
> that would somehow facilitate this, but there doesn't seem to be any way
> to force SQL server to backup the file to a device that is not local to
> the server itself.
> I understand that one possible option would be to install a full version
> of SQL 2000 on the other server and has the primary backup to that
> secondary server. But that would mean 2 licenses of SQL Server. I
> don't think we have 2 licenses, though I will check on that.
> Surely there is some way to backup databases to an non-local device.
> Curtis
|||So, if I understand correctly the MSSQLSERVER service must be switched
from running under the LocalSystem account to running under a
domain-level account, such as, let's say, DataAdmin with a password. And
which account is not local to the server, but global to the domain. Right?
If that's true, what rights do I have to give the DataAdmin account?
Curtis
Geoff N. Hiten wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?id=555128
> The same technique applies to manual backup jobs as well.
>
|||Curtis,
Per the KB article ...
2) The SQL Server service account must have FULL CONTROL rights to the file system folder and to the share
Tunji
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message news:envLaWjsEHA.160@.TK2MSFTNGP11.phx.gbl...
So, if I understand correctly the MSSQLSERVER service must be switched
from running under the LocalSystem account to running under a
domain-level account, such as, let's say, DataAdmin with a password. And
which account is not local to the server, but global to the domain. Right?
If that's true, what rights do I have to give the DataAdmin account?
Curtis
Geoff N. Hiten wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?id=555128
> The same technique applies to manual backup jobs as well.
>
|||Everything works better if you give the domain-level account (DataAdmin in
your example) local administrator rights on the SQL server host computer.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message
news:envLaWjsEHA.160@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> So, if I understand correctly the MSSQLSERVER service must be switched
> from running under the LocalSystem account to running under a
> domain-level account, such as, let's say, DataAdmin with a password. And
> which account is not local to the server, but global to the domain. Right?
> If that's true, what rights do I have to give the DataAdmin account?
> Curtis
> Geoff N. Hiten wrote:
backup routine to backup the databases to a directory on a separate
computer. I have set up the SQL Client Agent on that other server hoping
that would somehow facilitate this, but there doesn't seem to be any way
to force SQL server to backup the file to a device that is not local to
the server itself.
I understand that one possible option would be to install a full version
of SQL 2000 on the other server and has the primary backup to that
secondary server. But that would mean 2 licenses of SQL Server. I
don't think we have 2 licenses, though I will check on that.
Surely there is some way to backup databases to an non-local device.
Curtis
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?id=555128
The same technique applies to manual backup jobs as well.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message
news:eiqgAsisEHA.1468@.TK2MSFTNGP12.phx.gbl...
> I have SQL 2000 on a W2K advanced server. I want to use SQL server's
> backup routine to backup the databases to a directory on a separate
> computer. I have set up the SQL Client Agent on that other server hoping
> that would somehow facilitate this, but there doesn't seem to be any way
> to force SQL server to backup the file to a device that is not local to
> the server itself.
> I understand that one possible option would be to install a full version
> of SQL 2000 on the other server and has the primary backup to that
> secondary server. But that would mean 2 licenses of SQL Server. I
> don't think we have 2 licenses, though I will check on that.
> Surely there is some way to backup databases to an non-local device.
> Curtis
|||So, if I understand correctly the MSSQLSERVER service must be switched
from running under the LocalSystem account to running under a
domain-level account, such as, let's say, DataAdmin with a password. And
which account is not local to the server, but global to the domain. Right?
If that's true, what rights do I have to give the DataAdmin account?
Curtis
Geoff N. Hiten wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?id=555128
> The same technique applies to manual backup jobs as well.
>
|||Curtis,
Per the KB article ...
2) The SQL Server service account must have FULL CONTROL rights to the file system folder and to the share
Tunji
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message news:envLaWjsEHA.160@.TK2MSFTNGP11.phx.gbl...
So, if I understand correctly the MSSQLSERVER service must be switched
from running under the LocalSystem account to running under a
domain-level account, such as, let's say, DataAdmin with a password. And
which account is not local to the server, but global to the domain. Right?
If that's true, what rights do I have to give the DataAdmin account?
Curtis
Geoff N. Hiten wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?id=555128
> The same technique applies to manual backup jobs as well.
>
|||Everything works better if you give the domain-level account (DataAdmin in
your example) local administrator rights on the SQL server host computer.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message
news:envLaWjsEHA.160@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> So, if I understand correctly the MSSQLSERVER service must be switched
> from running under the LocalSystem account to running under a
> domain-level account, such as, let's say, DataAdmin with a password. And
> which account is not local to the server, but global to the domain. Right?
> If that's true, what rights do I have to give the DataAdmin account?
> Curtis
> Geoff N. Hiten wrote:
Backing up Databases using SQLServer
I have SQL 2000 on a W2K advanced server. I want to use SQL server's
backup routine to backup the databases to a directory on a separate
computer. I have set up the SQL Client Agent on that other server hoping
that would somehow facilitate this, but there doesn't seem to be any way
to force SQL server to backup the file to a device that is not local to
the server itself.
I understand that one possible option would be to install a full version
of SQL 2000 on the other server and has the primary backup to that
secondary server. But that would mean 2 licenses of SQL Server. I
don't think we have 2 licenses, though I will check on that.
Surely there is some way to backup databases to an non-local device.
CurtisHowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?id=555128
The same technique applies to manual backup jobs as well.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message
news:eiqgAsisEHA.1468@.TK2MSFTNGP12.phx.gbl...
> I have SQL 2000 on a W2K advanced server. I want to use SQL server's
> backup routine to backup the databases to a directory on a separate
> computer. I have set up the SQL Client Agent on that other server hoping
> that would somehow facilitate this, but there doesn't seem to be any way
> to force SQL server to backup the file to a device that is not local to
> the server itself.
> I understand that one possible option would be to install a full version
> of SQL 2000 on the other server and has the primary backup to that
> secondary server. But that would mean 2 licenses of SQL Server. I
> don't think we have 2 licenses, though I will check on that.
> Surely there is some way to backup databases to an non-local device.
> Curtis|||So, if I understand correctly the MSSQLSERVER service must be switched
from running under the LocalSystem account to running under a
domain-level account, such as, let's say, DataAdmin with a password. And
which account is not local to the server, but global to the domain. Right?
If that's true, what rights do I have to give the DataAdmin account?
Curtis
Geoff N. Hiten wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?id=555128
> The same technique applies to manual backup jobs as well.
>|||This is a multi-part message in MIME format.
--=_NextPart_000_01D8_01C4B22C.EC0EE200
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Curtis,
Per the KB article ... 2) The SQL Server service account must have FULL CONTROL rights to the =file system folder and to the share
Tunji
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message =news:envLaWjsEHA.160@.TK2MSFTNGP11.phx.gbl...
So, if I understand correctly the MSSQLSERVER service must be switched =
from running under the LocalSystem account to running under a domain-level account, such as, let's say, DataAdmin with a password. =And which account is not local to the server, but global to the domain. =Right?
If that's true, what rights do I have to give the DataAdmin account?
Curtis
Geoff N. Hiten wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?id=3D555128
> > The same technique applies to manual backup jobs as well.
>
--=_NextPart_000_01D8_01C4B22C.EC0EE200
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Curtis,
Per the KB article ...
2) The SQL Server service account must have FULL CONTROL =rights to the file system folder and to the share
Tunji
"Curtis Vaughan" wrote in =message news:envLaWjsEHA.160@.T=K2MSFTNGP11.phx.gbl...So, if I understand correctly the MSSQLSERVER service must be switched =from running under the LocalSystem account to running under a =domain-level account, such as, let's say, DataAdmin with a password. And which =account is not local to the server, but global to the domain. Right?If =that's true, what rights do I have to give the DataAdmin account?CurtisGeoff N. Hiten wrote:> HowTo: =Backup to UNC name using Database Maintenance Wizard>http://support.microsoft.com/?id=3D555128">http://support.microso=ft.com/?id=3D555128> > The same technique applies to manual backup jobs as well.>
--=_NextPart_000_01D8_01C4B22C.EC0EE200--|||Everything works better if you give the domain-level account (DataAdmin in
your example) local administrator rights on the SQL server host computer.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message
news:envLaWjsEHA.160@.TK2MSFTNGP11.phx.gbl...
> So, if I understand correctly the MSSQLSERVER service must be switched
> from running under the LocalSystem account to running under a
> domain-level account, such as, let's say, DataAdmin with a password. And
> which account is not local to the server, but global to the domain. Right?
> If that's true, what rights do I have to give the DataAdmin account?
> Curtis
> Geoff N. Hiten wrote:
> > HowTo: Backup to UNC name using Database Maintenance Wizard
> > http://support.microsoft.com/?id=555128
> >
> > The same technique applies to manual backup jobs as well.
> >|||Yeh! It's working!!!
Thanks everyone!!!
Geoff N. Hiten wrote:
> Everything works better if you give the domain-level account (DataAdmin in
> your example) local administrator rights on the SQL server host computer.
>sql
backup routine to backup the databases to a directory on a separate
computer. I have set up the SQL Client Agent on that other server hoping
that would somehow facilitate this, but there doesn't seem to be any way
to force SQL server to backup the file to a device that is not local to
the server itself.
I understand that one possible option would be to install a full version
of SQL 2000 on the other server and has the primary backup to that
secondary server. But that would mean 2 licenses of SQL Server. I
don't think we have 2 licenses, though I will check on that.
Surely there is some way to backup databases to an non-local device.
CurtisHowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?id=555128
The same technique applies to manual backup jobs as well.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message
news:eiqgAsisEHA.1468@.TK2MSFTNGP12.phx.gbl...
> I have SQL 2000 on a W2K advanced server. I want to use SQL server's
> backup routine to backup the databases to a directory on a separate
> computer. I have set up the SQL Client Agent on that other server hoping
> that would somehow facilitate this, but there doesn't seem to be any way
> to force SQL server to backup the file to a device that is not local to
> the server itself.
> I understand that one possible option would be to install a full version
> of SQL 2000 on the other server and has the primary backup to that
> secondary server. But that would mean 2 licenses of SQL Server. I
> don't think we have 2 licenses, though I will check on that.
> Surely there is some way to backup databases to an non-local device.
> Curtis|||So, if I understand correctly the MSSQLSERVER service must be switched
from running under the LocalSystem account to running under a
domain-level account, such as, let's say, DataAdmin with a password. And
which account is not local to the server, but global to the domain. Right?
If that's true, what rights do I have to give the DataAdmin account?
Curtis
Geoff N. Hiten wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?id=555128
> The same technique applies to manual backup jobs as well.
>|||This is a multi-part message in MIME format.
--=_NextPart_000_01D8_01C4B22C.EC0EE200
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Curtis,
Per the KB article ... 2) The SQL Server service account must have FULL CONTROL rights to the =file system folder and to the share
Tunji
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message =news:envLaWjsEHA.160@.TK2MSFTNGP11.phx.gbl...
So, if I understand correctly the MSSQLSERVER service must be switched =
from running under the LocalSystem account to running under a domain-level account, such as, let's say, DataAdmin with a password. =And which account is not local to the server, but global to the domain. =Right?
If that's true, what rights do I have to give the DataAdmin account?
Curtis
Geoff N. Hiten wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?id=3D555128
> > The same technique applies to manual backup jobs as well.
>
--=_NextPart_000_01D8_01C4B22C.EC0EE200
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Curtis,
Per the KB article ...
2) The SQL Server service account must have FULL CONTROL =rights to the file system folder and to the share
Tunji
"Curtis Vaughan"
--=_NextPart_000_01D8_01C4B22C.EC0EE200--|||Everything works better if you give the domain-level account (DataAdmin in
your example) local administrator rights on the SQL server host computer.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Curtis Vaughan" <curtis@.npc-usa.com> wrote in message
news:envLaWjsEHA.160@.TK2MSFTNGP11.phx.gbl...
> So, if I understand correctly the MSSQLSERVER service must be switched
> from running under the LocalSystem account to running under a
> domain-level account, such as, let's say, DataAdmin with a password. And
> which account is not local to the server, but global to the domain. Right?
> If that's true, what rights do I have to give the DataAdmin account?
> Curtis
> Geoff N. Hiten wrote:
> > HowTo: Backup to UNC name using Database Maintenance Wizard
> > http://support.microsoft.com/?id=555128
> >
> > The same technique applies to manual backup jobs as well.
> >|||Yeh! It's working!!!
Thanks everyone!!!
Geoff N. Hiten wrote:
> Everything works better if you give the domain-level account (DataAdmin in
> your example) local administrator rights on the SQL server host computer.
>sql
Thursday, March 22, 2012
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
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...
>
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
> >>
> >>
> >>
>
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
> >>
> >>
> >>
>
Sunday, March 11, 2012
AWE, SQL Server Enterprise, W2k STANDARD + 4GB RAM
Hi
Enabling AWE on SQL Enterprise Ed on a W2K STANDARD ed does appear to work (there seemed to be some doubt). I have reserved 3.5GB max server memory, and it has been allocated. The AWE counters in perfmon also seem to indicate it is functioning.
Does anyone have any experience with this configuration (good or bad)?
Also, any tips as to monitor memory usage - SQLServer/SQL Cache Memory doesn't appear to be of any use.
RegardsHi Stuart,
Not sure what you have done yet, but refers to the following article for
configuring AWE on SQL Server
HOW TO: Configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/defaul...kb;en-us;274750
On 24 Mar 2004 08:04:17 -0800, Stuart wrote:
> Hi
> Enabling AWE on SQL Enterprise Ed on a W2K STANDARD ed does appear to
> work (there seemed to be some doubt). I have reserved 3.5GB max server
> memory, and it has been allocated. The AWE counters in perfmon also
> seem to indicate it is functioning.
> Does anyone have any experience with this configuration (good or bad)?
> Also, any tips as to monitor memory usage - SQLServer/SQL Cache Memory
> doesn't appear to be of any use.
> Regards
> Stuart|||Thanks - have read the MS articles (they often seem contradictory as
to whether AWE would work on W2k Server Standard)
However, even though AWE it does work on W2K server, there seems to be
some doubt as to whether there is any point in doing this, e.g.
http://www.sql-server-performance.com/awe_memory.asp says should leave
AWE off for my config.
To date, the config is looking quite good - enabling AWE has doubled
the available RAM to SQL and the Page Life Expectancy has gone up to
about 3 hours (up from a few seconds)
.
Regards
Stuart
Yih-Yoon Lee <yihyoon@.hotmail.com> wrote in message news:<1lywgm6zbxldi.sdsrs0dj91ss$.dlg@.4
0tude.net>...
> Hi Stuart,
> Not sure what you have done yet, but refers to the following article for
> configuring AWE on SQL Server
> HOW TO: Configure memory for more than 2 GB in SQL Server
> http://support.microsoft.com/defaul...kb;en-us;274750
> On 24 Mar 2004 08:04:17 -0800, Stuart wrote:
>
Enabling AWE on SQL Enterprise Ed on a W2K STANDARD ed does appear to work (there seemed to be some doubt). I have reserved 3.5GB max server memory, and it has been allocated. The AWE counters in perfmon also seem to indicate it is functioning.
Does anyone have any experience with this configuration (good or bad)?
Also, any tips as to monitor memory usage - SQLServer/SQL Cache Memory doesn't appear to be of any use.
RegardsHi Stuart,
Not sure what you have done yet, but refers to the following article for
configuring AWE on SQL Server
HOW TO: Configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/defaul...kb;en-us;274750
On 24 Mar 2004 08:04:17 -0800, Stuart wrote:
> Hi
> Enabling AWE on SQL Enterprise Ed on a W2K STANDARD ed does appear to
> work (there seemed to be some doubt). I have reserved 3.5GB max server
> memory, and it has been allocated. The AWE counters in perfmon also
> seem to indicate it is functioning.
> Does anyone have any experience with this configuration (good or bad)?
> Also, any tips as to monitor memory usage - SQLServer/SQL Cache Memory
> doesn't appear to be of any use.
> Regards
> Stuart|||Thanks - have read the MS articles (they often seem contradictory as
to whether AWE would work on W2k Server Standard)
However, even though AWE it does work on W2K server, there seems to be
some doubt as to whether there is any point in doing this, e.g.
http://www.sql-server-performance.com/awe_memory.asp says should leave
AWE off for my config.
To date, the config is looking quite good - enabling AWE has doubled
the available RAM to SQL and the Page Life Expectancy has gone up to
about 3 hours (up from a few seconds)
.Regards
Stuart
Yih-Yoon Lee <yihyoon@.hotmail.com> wrote in message news:<1lywgm6zbxldi.sdsrs0dj91ss$.dlg@.4
0tude.net>...
> Hi Stuart,
> Not sure what you have done yet, but refers to the following article for
> configuring AWE on SQL Server
> HOW TO: Configure memory for more than 2 GB in SQL Server
> http://support.microsoft.com/defaul...kb;en-us;274750
> On 24 Mar 2004 08:04:17 -0800, Stuart wrote:
>
Saturday, February 25, 2012
AWE and limiting below 4GB SQL Server Memory Allocation
We are running W2K Advanced Server with SQL Server
Enterprise Edition. Problem is SQL Server takes almost
all of the memory 7.8GB of 8GB and Peoplesoft application
pages like crazy. Anyway, is there a way to limit the
below 4GB SQL Server memory and use all of the above 4GB
limit? Peoplesoft can't address the above 4GB line. The
real soluition is getting the !#@.$ application off of the
server. But I can't do that right now. Is there a patch
or some way to limit the below 4GB SQL Server memory to
say 2GB and let it have all 4GB above the 4GB line?You cannot tell sql server to use what memory area. You
should set the max memory for sql server to 4gb in sql
enterprise manager. At startup sql server will grab the
first 4gb of memory. So, configure sql server in service
control manager to start manually. Start the Peoplesoft
application first so that it will get the memory it needs.
Then start the sql server and it will grab 4gb of memory
out of available memory. SQL server will lock that memory
and won't dynamically release/acquire memory as it needs
(this is a feature of AWE).
This isn't perfect solution, but you will survive.
>--Original Message--
>We are running W2K Advanced Server with SQL Server
>Enterprise Edition. Problem is SQL Server takes almost
>all of the memory 7.8GB of 8GB and Peoplesoft application
>pages like crazy. Anyway, is there a way to limit the
>below 4GB SQL Server memory and use all of the above 4GB
>limit? Peoplesoft can't address the above 4GB line. The
>real soluition is getting the !#@.$ application off of the
>server. But I can't do that right now. Is there a patch
>or some way to limit the below 4GB SQL Server memory to
>say 2GB and let it have all 4GB above the 4GB line?
>.
>
Enterprise Edition. Problem is SQL Server takes almost
all of the memory 7.8GB of 8GB and Peoplesoft application
pages like crazy. Anyway, is there a way to limit the
below 4GB SQL Server memory and use all of the above 4GB
limit? Peoplesoft can't address the above 4GB line. The
real soluition is getting the !#@.$ application off of the
server. But I can't do that right now. Is there a patch
or some way to limit the below 4GB SQL Server memory to
say 2GB and let it have all 4GB above the 4GB line?You cannot tell sql server to use what memory area. You
should set the max memory for sql server to 4gb in sql
enterprise manager. At startup sql server will grab the
first 4gb of memory. So, configure sql server in service
control manager to start manually. Start the Peoplesoft
application first so that it will get the memory it needs.
Then start the sql server and it will grab 4gb of memory
out of available memory. SQL server will lock that memory
and won't dynamically release/acquire memory as it needs
(this is a feature of AWE).
This isn't perfect solution, but you will survive.
>--Original Message--
>We are running W2K Advanced Server with SQL Server
>Enterprise Edition. Problem is SQL Server takes almost
>all of the memory 7.8GB of 8GB and Peoplesoft application
>pages like crazy. Anyway, is there a way to limit the
>below 4GB SQL Server memory and use all of the above 4GB
>limit? Peoplesoft can't address the above 4GB line. The
>real soluition is getting the !#@.$ application off of the
>server. But I can't do that right now. Is there a patch
>or some way to limit the below 4GB SQL Server memory to
>say 2GB and let it have all 4GB above the 4GB line?
>.
>
Subscribe to:
Posts (Atom)