Backing Up System Databases...

I am rather new to the area of performing DBA type activities (so don't be
too hard on me).
When I create a maintenance plan, which of the system databases should I
choose to back up (if it is not necessary or recommended to back all of them
up)?
Thank you,
JasonBoth master and msdb should be done daily. You could do model every once in
a while. Generally, it doesn't change - unless you choose to add an object
that you want to appear in all future DB's.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Jason Richmeier" <JasonRichmeier@.discussions.microsoft.com> wrote in
message news:179C142F-CEBC-4E16-870D-FCC20881E5F3@.microsoft.com...
I am rather new to the area of performing DBA type activities (so don't be
too hard on me).
When I create a maintenance plan, which of the system databases should I
choose to back up (if it is not necessary or recommended to back all of them
up)?
Thank you,
Jason|||Or just include model for daily backup anyway since it's so tiny.
Linchi
"Tom Moreau" wrote:

> Both master and msdb should be done daily. You could do model every once
in
> a while. Generally, it doesn't change - unless you choose to add an objec
t
> that you want to appear in all future DB's.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Jason Richmeier" <JasonRichmeier@.discussions.microsoft.com> wrote in
> message news:179C142F-CEBC-4E16-870D-FCC20881E5F3@.microsoft.com...
> I am rather new to the area of performing DBA type activities (so don't be
> too hard on me).
> When I create a maintenance plan, which of the system databases should I
> choose to back up (if it is not necessary or recommended to back all of th
em
> up)?
> Thank you,
> Jason
>

Backing Up System Databases...

I am rather new to the area of performing DBA type activities (so don't be
too hard on me).
When I create a maintenance plan, which of the system databases should I
choose to back up (if it is not necessary or recommended to back all of them
up)?
Thank you,
JasonBoth master and msdb should be done daily. You could do model every once in
a while. Generally, it doesn't change - unless you choose to add an object
that you want to appear in all future DB's.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Jason Richmeier" <JasonRichmeier@.discussions.microsoft.com> wrote in
message news:179C142F-CEBC-4E16-870D-FCC20881E5F3@.microsoft.com...
I am rather new to the area of performing DBA type activities (so don't be
too hard on me).
When I create a maintenance plan, which of the system databases should I
choose to back up (if it is not necessary or recommended to back all of them
up)?
Thank you,
Jason|||Or just include model for daily backup anyway since it's so tiny.
Linchi
"Tom Moreau" wrote:
> Both master and msdb should be done daily. You could do model every once in
> a while. Generally, it doesn't change - unless you choose to add an object
> that you want to appear in all future DB's.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Jason Richmeier" <JasonRichmeier@.discussions.microsoft.com> wrote in
> message news:179C142F-CEBC-4E16-870D-FCC20881E5F3@.microsoft.com...
> I am rather new to the area of performing DBA type activities (so don't be
> too hard on me).
> When I create a maintenance plan, which of the system databases should I
> choose to back up (if it is not necessary or recommended to back all of them
> up)?
> Thank you,
> Jason
>sql

Backing up logins info/data

We currently backup the system databases, user databases and logs every nigh
t
To be on the safe side should we also backup the logins data, in case we
have to recreate the master database ?
If so what would be the best approach to backup the logins info/data ?
ThanksHi
You can generate script of Logins by using sp_help_revlogin (search on
internet)
"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in
message news:62AEF9F6-6A8E-4D9D-BD59-0B5E48A7D408@.microsoft.com...
> We currently backup the system databases, user databases and logs every
> night
> To be on the safe side should we also backup the logins data, in case we
> have to recreate the master database ?
> If so what would be the best approach to backup the logins info/data ?
> Thanks|||Logins are in the master database, so these are included in the backup of th
e master database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in mes
sage
news:62AEF9F6-6A8E-4D9D-BD59-0B5E48A7D408@.microsoft.com...
> We currently backup the system databases, user databases and logs every ni
ght
> To be on the safe side should we also backup the logins data, in case we
> have to recreate the master database ?
> If so what would be the best approach to backup the logins info/data ?
> Thankssql

Backing up logins info/data

We currently backup the system databases, user databases and logs every night
To be on the safe side should we also backup the logins data, in case we
have to recreate the master database ?
If so what would be the best approach to backup the logins info/data ?
Thanks
Hi
You can generate script of Logins by using sp_help_revlogin (search on
internet)
"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in
message news:62AEF9F6-6A8E-4D9D-BD59-0B5E48A7D408@.microsoft.com...
> We currently backup the system databases, user databases and logs every
> night
> To be on the safe side should we also backup the logins data, in case we
> have to recreate the master database ?
> If so what would be the best approach to backup the logins info/data ?
> Thanks
|||Logins are in the master database, so these are included in the backup of the master database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in message
news:62AEF9F6-6A8E-4D9D-BD59-0B5E48A7D408@.microsoft.com...
> We currently backup the system databases, user databases and logs every night
> To be on the safe side should we also backup the logins data, in case we
> have to recreate the master database ?
> If so what would be the best approach to backup the logins info/data ?
> Thanks

Backing up logins info/data

We currently backup the system databases, user databases and logs every night
To be on the safe side should we also backup the logins data, in case we
have to recreate the master database ?
If so what would be the best approach to backup the logins info/data ?
ThanksHi
You can generate script of Logins by using sp_help_revlogin (search on
internet)
"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in
message news:62AEF9F6-6A8E-4D9D-BD59-0B5E48A7D408@.microsoft.com...
> We currently backup the system databases, user databases and logs every
> night
> To be on the safe side should we also backup the logins data, in case we
> have to recreate the master database ?
> If so what would be the best approach to backup the logins info/data ?
> Thanks|||Logins are in the master database, so these are included in the backup of the master database.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in message
news:62AEF9F6-6A8E-4D9D-BD59-0B5E48A7D408@.microsoft.com...
> We currently backup the system databases, user databases and logs every night
> To be on the safe side should we also backup the logins data, in case we
> have to recreate the master database ?
> If so what would be the best approach to backup the logins info/data ?
> Thanks

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
> >>
> >>
> >>
>

backing up

we want to back up our new point of sale system with is
running a sequel server. on to a zip drive software does
not come with any instructions for how to do so any ideas?
Personally, I would probably try to backup to disk first, and then =
backup to your removable drive.
Either way, something like this should work for you, just change the =
drive letter.
Test this from Query Analyzer. When it works create a scheduled job. =
You will also want to backup msdb as well as your user database(s). =
Make sure that you backup each database to a separate file.
BACKUP DATABASE master TO DISK =3D 'c:\master.bak' WITH INIT
go
EXEC master..xp_cmdshell 'copy c:\master.bak x:\master.bak'
GO
--=20
Keith
"chris" <anonymous@.discussions.microsoft.com> wrote in message =
news:b80c01c43791$fc4f2f50$a001280a@.phx.gbl...
> we want to back up our new point of sale system with is=20
> running a sequel server. on to a zip drive software does=20
> not come with any instructions for how to do so any ideas?

backing up

we want to back up our new point of sale system with is
running a sequel server. on to a zip drive software does
not come with any instructions for how to do so any ideas?Personally, I would probably try to backup to disk first, and then =
backup to your removable drive.
Either way, something like this should work for you, just change the =
drive letter.
Test this from Query Analyzer. When it works create a scheduled job. =
You will also want to backup msdb as well as your user database(s). =
Make sure that you backup each database to a separate file.
BACKUP DATABASE master TO DISK =3D 'c:\master.bak' WITH INIT
go
EXEC master..xp_cmdshell 'copy c:\master.bak x:\master.bak'
GO
--=20
Keith
"chris" <anonymous@.discussions.microsoft.com> wrote in message =
news:b80c01c43791$fc4f2f50$a001280a@.phx.gbl...
> we want to back up our new point of sale system with is=20
> running a sequel server. on to a zip drive software does=20
> not come with any instructions for how to do so any ideas?

backing up

we want to back up our new point of sale system with is
running a sequel server. on to a zip drive software does
not come with any instructions for how to do so any ideas?Personally, I would probably try to backup to disk first, and then =backup to your removable drive.
Either way, something like this should work for you, just change the =drive letter.
Test this from Query Analyzer. When it works create a scheduled job. =You will also want to backup msdb as well as your user database(s). =Make sure that you backup each database to a separate file.
BACKUP DATABASE master TO DISK =3D 'c:\master.bak' WITH INIT
go
EXEC master..xp_cmdshell 'copy c:\master.bak x:\master.bak'
GO
-- Keith
"chris" <anonymous@.discussions.microsoft.com> wrote in message =news:b80c01c43791$fc4f2f50$a001280a@.phx.gbl...
> we want to back up our new point of sale system with is > running a sequel server. on to a zip drive software does > not come with any instructions for how to do so any ideas?

Background replication

We are developing a embedded system based on Windows CE 5 and SQL Server CE 3 in C++ where we need to do merge replication in background while the front end application still need to perform operations on the database. A solution would be to run the merge replication on a separate thread while the application thread still can access the database to do inserts and updates. I have been researching if it is possible to access the database with queries during a merge replication, but I can not find an answere. Does anyone have experience of this and generally know if it is possible to implement with SQL Server CE 3 in the native API?

Best regards

Johan Johansson

This article may help you understand the implications of a user trying to access SQL Mobile while merge replication is happening.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql2k5mobilesynch.asp

Darren

|||

Thanks Darren, this is exactly what I was looking for.

Best regards

Johan

back upwith out any machine specific data

How can i take back up of a data base
with out having any machine/system specific
data in the .bak file?

What exactly do you mean by machine specific data?

When you take a backup your database is backed up, nothing more, nothing less.

If you are talking about the file location this can be changed in the RESTORE statement.

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||

Data or information? What issues are you trying to prevent with this? If you do a restore headeronly, you will see the server name that backed up the file. Is that the kind of thing you are concerned about?

Otherwise, as WesleyB said, you can backup on one server and restore to another.

-Sue

|||i cant restore a db ,in another system

i am getting error like

System.Data.SqlClient.SqlError: Directory lookup for the file "D:\Microsoft SQL Server 2005\mydatabase.mdf" failed with the operating system error 2(The system cannot find the file specified.). (Microsoft.SqlServer.Smo)

i am trying to restore from a .bak file

i have sql servrer in D:
but on another system it in c:
|||

That's where the MOVE statement is for.

From BOL:

RESTORE DATABASE TestDB
FROM AdventureWorksBackups
WITH MOVE 'AdventureWorks_Data' TO 'C:\MySQLServer\testdb.mdf',
MOVE 'AdventureWorks_Log' TO 'C:\MySQLServer\testdb.ldf';

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

back upwith out any machine specific data

How can i take back up of a data basewith out having any machine/system specific data in the .bak file?

What are you trying to accomplish? You can obviously move a database backup file from one machine to another.

|||

then why i cant restore a db ,in another system

i am getting error like

System.Data.SqlClient.SqlError:Directory lookup for the file "D:\Microsoft SQL Server2005\mydatabase.mdf" failed with the operating system error 2(Thesystem cannot find the file specified.). (Microsoft.SqlServer.Smo)

i am trying to restore from a .bak file

where d:is the place where sql server is installed in my system

and and in another system it is in c:

|||

Yes, the path to the data and log files is stored with the backup. This is for convenience when you are restoring a backup to the same machine from which it was taken. Unfortunately it is inconvenient when moving to another machine. It the restore database dialog, you have to find the options for where to store the data and transaction log files. Modify these settings to fit the local machine. If you need more specific details, please indicate which version of Sql Server you are using.

Hope this helps,

Matt

|||

i am using sql server 2005

|||

in the restore window, after adding the backup file, go to the "options" page and change the two paths for .mdf and and .ldf files

Back up system DBs

I noticed the transaction logs for master and other system dbs can't be backed up. What are some of the practices of backing up System DBs as far as method, frequency and what type of situation would there be a need to restore from them?
Thanks
You cannot backup logs for the syetm dbs because they are in simple =
recovery model.
Daily full backup should easily suffice unless you are in the habit of =
creating many databases or logins per day.
Mike John
"Niles" <Niles@.discussions.microsoft.com> wrote in message =
news:3BE5FB23-C2DC-42CB-9572-BB7A0C7A03DF@.microsoft.com...
> I noticed the transaction logs for master and other system dbs can't =
be backed up. What are some of the practices of backing up System DBs =
as far as method, frequency and what type of situation would there be a =
need to restore from them?
> Thanks
|||Hi,
Backup the system databases once a day. I recommend you to take a backup of
Master database inbetween
if you add a new database/new login/ adding roles / changing
configurations/....
Take the backup of MSDB inbetween if you add or modify a Job, add
operator/alert, replications , Logshipping...
Thanks
Hari
MCDBA
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:3BE5FB23-C2DC-42CB-9572-BB7A0C7A03DF@.microsoft.com...
> I noticed the transaction logs for master and other system dbs can't be
backed up. What are some of the practices of backing up System DBs as far
as method, frequency and what type of situation would there be a need to
restore from them?
> Thanks
|||I prefer to do only db backup for master and model. For msdb, I also do log backup (because of
backup history is stored there). As Agent set msdb to simple recovery at startup, I just have a job
scheduled to autostart that set msdb to full recovery.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:3BE5FB23-C2DC-42CB-9572-BB7A0C7A03DF@.microsoft.com...
> I noticed the transaction logs for master and other system dbs can't be backed up. What are some
of the practices of backing up System DBs as far as method, frequency and what type of situation
would there be a need to restore from them?
> Thanks

Back up system DBs

I noticed the transaction logs for master and other system dbs can't be back
ed up. What are some of the practices of backing up System DBs as far as me
thod, frequency and what type of situation would there be a need to restore
from them?
ThanksYou cannot backup logs for the syetm dbs because they are in simple =
recovery model.
Daily full backup should easily suffice unless you are in the habit of =
creating many databases or logins per day.
Mike John
"Niles" <Niles@.discussions.microsoft.com> wrote in message =
news:3BE5FB23-C2DC-42CB-9572-BB7A0C7A03DF@.microsoft.com...
> I noticed the transaction logs for master and other system dbs can't =
be backed up. What are some of the practices of backing up System DBs =
as far as method, frequency and what type of situation would there be a =
need to restore from them?
> Thanks|||Hi,
Backup the system databases once a day. I recommend you to take a backup of
Master database inbetween
if you add a new database/new login/ adding roles / changing
configurations/....
Take the backup of MSDB inbetween if you add or modify a Job, add
operator/alert, replications , Logshipping...
Thanks
Hari
MCDBA
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:3BE5FB23-C2DC-42CB-9572-BB7A0C7A03DF@.microsoft.com...
> I noticed the transaction logs for master and other system dbs can't be
backed up. What are some of the practices of backing up System DBs as far
as method, frequency and what type of situation would there be a need to
restore from them?
> Thanks|||I prefer to do only db backup for master and model. For msdb, I also do log
backup (because of
backup history is stored there). As Agent set msdb to simple recovery at sta
rtup, I just have a job
scheduled to autostart that set msdb to full recovery.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:3BE5FB23-C2DC-42CB-9572-BB7A0C7A03DF@.microsoft.com...
> I noticed the transaction logs for master and other system dbs can't be backed up.
What are some
of the practices of backing up System DBs as far as method, frequency and wh
at type of situation
would there be a need to restore from them?
> Thanks

Back up system DBs

I noticed the transaction logs for master and other system dbs can't be backed up. What are some of the practices of backing up System DBs as far as method, frequency and what type of situation would there be a need to restore from them?
ThanksYou cannot backup logs for the syetm dbs because they are in simple =recovery model.
Daily full backup should easily suffice unless you are in the habit of =creating many databases or logins per day.
Mike John
"Niles" <Niles@.discussions.microsoft.com> wrote in message =news:3BE5FB23-C2DC-42CB-9572-BB7A0C7A03DF@.microsoft.com...
> I noticed the transaction logs for master and other system dbs can't =be backed up. What are some of the practices of backing up System DBs =as far as method, frequency and what type of situation would there be a =need to restore from them?
> Thanks|||Hi,
Backup the system databases once a day. I recommend you to take a backup of
Master database inbetween
if you add a new database/new login/ adding roles / changing
configurations/....
Take the backup of MSDB inbetween if you add or modify a Job, add
operator/alert, replications , Logshipping...
Thanks
Hari
MCDBA
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:3BE5FB23-C2DC-42CB-9572-BB7A0C7A03DF@.microsoft.com...
> I noticed the transaction logs for master and other system dbs can't be
backed up. What are some of the practices of backing up System DBs as far
as method, frequency and what type of situation would there be a need to
restore from them?
> Thanks|||I prefer to do only db backup for master and model. For msdb, I also do log backup (because of
backup history is stored there). As Agent set msdb to simple recovery at startup, I just have a job
scheduled to autostart that set msdb to full recovery.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:3BE5FB23-C2DC-42CB-9572-BB7A0C7A03DF@.microsoft.com...
> I noticed the transaction logs for master and other system dbs can't be backed up. What are some
of the practices of backing up System DBs as far as method, frequency and what type of situation
would there be a need to restore from them?
> Thanks

back up from .bak file

I got a .bak file from my friend
I want to restore the data base (presently I don’t have any database in my system).

But while I try to restore it
I am getting an error

“
System.Data.SqlClient.SqlError: Directory lookup for the file "D:\Microsoft SQL Server 2005\mydatabase.mdf" failed with the operating system error 2(The system cannot find the file specified.). (Microsoft.SqlServer.Smo)

”

I have installed Microsoft sql server in a different directory
Not where he is installed

I can successfully restore the back up files of data base on my own system
But not the backup files created from others systemsWhen you restore the backup, there is a place on the dialog that will list all of the assoicated files for the backup and where they should be placed (.mdf, .ldf, etc.) The paths will default to the location that they were backed up from. You need to change these paths to where you want the files placed.

back up failure error

the problem is
source:kernel
backup medium ::reportloerror:write failure on backup device\\.\tape0.operating system error 23(data error(cyclic reduncancy check));Delete your backup device and start from scratch.

AWE RAM (SQL 2K not recognizing available AWE RAM)

I have a server with SQL Server 2000 Enterprise Edition with SP3.
The boot.ini is set with /3gb /PAE. The server system properties list 8GB of RAM. Within SQL Server sp_configure AWE running is set to 1. SQL Server Memory properties the Maximum is set to 5.12 GB. But SQL Server does not recognize AWE setting.
I look in the SQL Server errorlog after the server was rebooted and did not list AWE memory settings.
The Server Performance Monitor Counter under SQL Server Memory Manager with Target Server Memory list 2.7GB.
This should be 5.12 GB of memory for SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
___________________________________________________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
___________________________________________________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ___________________________________________________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ___________________________________________________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the ?Lock Pages in Memory?
privilege:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
_1_server_1fnd.asp
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
--
Andrew J. Kelly SQL MVP
"Eric Cárdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> > I have a server with SQL Server 2000 Enterprise Edition
> > with SP3. The boot.ini is set with /3gb /PAE. The server
> > system properties list 8GB of RAM. Within SQL Server
> > sp_configure AWE running is set to 1. SQL Server Memory
> > properties the Maximum is set to 5.12 GB. But SQL Server
> > does not recognize AWE setting. I look in the SQL Server
> > errorlog after the server was rebooted and did not list
> > AWE memory settings. The Server Performance Monitor
> > Counter under SQL Server Memory Manager with Target Server
> > Memory list 2.7GB. This should be 5.12 GB of memory for
> > SQL Server.
> >
> > Please help me resolve this problem.
> >
> > Mike
> >
> > __________________________________________________________
> > [boot loader]
> > timeout=10
> > default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> > Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> > ___________________________________________________________
> > sp_configure "show advanced options", 1
> > RECONFIGURE
> > GO
> > sp_configure "awe enabled", 1
> > RECONFIGURE
> > GO
> > sp_configure "max server memory", 5120
> > RECONFIGURE
> > GO
> > sp_configure "min server memory", 0
> > RECONFIGURE
> > GO
> > ___________________________________________________________
> > Output from SP_CONFIGURE
> > name minimum
> > maximum config_value run_value
> > -- -- --
> > -- --
> > affinity mask -2147483648
> > 2147483647 0 0
> > allow updates 0
> > 1 0 0
> > awe enabled 0
> > 1 1 1
> > c2 audit mode 0
> > 1 0 0
> > cost threshold for parallelism 0
> > 32767 5 5
> > Cross DB Ownership Chaining 0
> > 1 0 0
> > cursor threshold -1
> > 2147483647 -1 -1
> > default full-text language 0
> > 2147483647 1033 1033
> > default language 0
> > 9999 0 0
> > fill factor (%) 0
> > 100 0 0
> > index create memory (KB) 704
> > 2147483647 0 0
> > lightweight pooling 0
> > 1 0 0
> > locks 5000
> > 2147483647 0 0
> > max degree of parallelism 0
> > 32 0 0
> > max server memory (MB) 4
> > 2147483647 5120 5120
> > max text repl size (B) 0
> > 2147483647 65536 65536
> > max worker threads 32
> > 32767 255 255
> > media retention 0
> > 365 0 0
> > min memory per query (KB) 512
> > 2147483647 1024 1024
> > min server memory (MB) 0
> > 2147483647 0 0
> > nested triggers 0
> > 1 1 1
> > network packet size (B) 512
> > 65536 4096 4096
> > open objects 0
> > 2147483647 0 0
> > priority boost 0
> > 1 0 0
> > query governor cost limit 0
> > 2147483647 0 0
> > query wait (s) -1
> > 2147483647 -1 -1
> > recovery interval (min) 0
> > 32767 0 0
> > remote access 0
> > 1 1 1
> > remote login timeout (s) 0
> > 2147483647 20 20
> > remote proc trans 0
> > 1 0 0
> > remote query timeout (s) 0
> > 2147483647 600 600
> > scan for startup procs 0
> > 1 1 0
> > set working set size 0
> > 1 0 0
> > show advanced options 0
> > 1 1 1
> > two digit year cutoff 1753
> > 9999 2049 2049
> > user connections 0
> > 32767 0 0
> > user options 0
> > 32767 56 56
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Cárdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>