Another question on backups

I have a database that takes up around 12 gigs or so that I would like
to back up to a network share.
As part of our recovery procedures, I'm also backing up the source files
that we use to create about 90% of the data on our database (the
database is a sales information system, with reports generated over the
web). There may be some data entry into the project, but it is minimal.
Is there a way to back up the things I'd need to restore the tables,
such as the data structure of them, the stored procedures that load them
and the jobs that execute those stored procedures? In other words, back
up everything but the data inside the 90% of the tables which we can
re-create on the next table load?
I'm looking for a way to whittle down the amount of data I'm backing up,
actually backing up just what I specifically need to have to get going
again.
BCscript the database and store it in Source Safe.
Greg Jackson
PDX, Oregon|||Hi,
There are 2 options for you:-
1. Use generate script to script all the objects (ALL DDLs) and right click
above the job and script the jobs.
2. Do a full database backup once and perform a differential backup daily.
For jobs backup the MSDB database.
Differential backup will backup only the changes after the last backup
and will be very fast in your case since you have very less changes
on a daily basis.
Thanks
Hari
SQL Server MVP
"Blasting Cap" <goober@.christian.net> wrote in message
news:ueeTd0ocFHA.584@.TK2MSFTNGP15.phx.gbl...
>I have a database that takes up around 12 gigs or so that I would like to
>back up to a network share.
> As part of our recovery procedures, I'm also backing up the source files
> that we use to create about 90% of the data on our database (the database
> is a sales information system, with reports generated over the web).
> There may be some data entry into the project, but it is minimal.
> Is there a way to back up the things I'd need to restore the tables, such
> as the data structure of them, the stored procedures that load them and
> the jobs that execute those stored procedures? In other words, back up
> everything but the data inside the 90% of the tables which we can
> re-create on the next table load?
> I'm looking for a way to whittle down the amount of data I'm backing up,
> actually backing up just what I specifically need to have to get going
> again.
> BC
>

Another question on backups

I have a database that takes up around 12 gigs or so that I would like
to back up to a network share.
As part of our recovery procedures, I'm also backing up the source files
that we use to create about 90% of the data on our database (the
database is a sales information system, with reports generated over the
web). There may be some data entry into the project, but it is minimal.
Is there a way to back up the things I'd need to restore the tables,
such as the data structure of them, the stored procedures that load them
and the jobs that execute those stored procedures? In other words, back
up everything but the data inside the 90% of the tables which we can
re-create on the next table load?
I'm looking for a way to whittle down the amount of data I'm backing up,
actually backing up just what I specifically need to have to get going
again.
BCscript the database and store it in Source Safe.
Greg Jackson
PDX, Oregon|||Hi,
There are 2 options for you:-
1. Use generate script to script all the objects (ALL DDLs) and right click
above the job and script the jobs.
2. Do a full database backup once and perform a differential backup daily.
For jobs backup the MSDB database.
Differential backup will backup only the changes after the last backup
and will be very fast in your case since you have very less changes
on a daily basis.
Thanks
Hari
SQL Server MVP
"Blasting Cap" <goober@.christian.net> wrote in message
news:ueeTd0ocFHA.584@.TK2MSFTNGP15.phx.gbl...
>I have a database that takes up around 12 gigs or so that I would like to
>back up to a network share.
> As part of our recovery procedures, I'm also backing up the source files
> that we use to create about 90% of the data on our database (the database
> is a sales information system, with reports generated over the web).
> There may be some data entry into the project, but it is minimal.
> Is there a way to back up the things I'd need to restore the tables, such
> as the data structure of them, the stored procedures that load them and
> the jobs that execute those stored procedures? In other words, back up
> everything but the data inside the 90% of the tables which we can
> re-create on the next table load?
> I'm looking for a way to whittle down the amount of data I'm backing up,
> actually backing up just what I specifically need to have to get going
> again.
> BC
>

Another question on backups

I have a database that takes up around 12 gigs or so that I would like
to back up to a network share.
As part of our recovery procedures, I'm also backing up the source files
that we use to create about 90% of the data on our database (the
database is a sales information system, with reports generated over the
web). There may be some data entry into the project, but it is minimal.
Is there a way to back up the things I'd need to restore the tables,
such as the data structure of them, the stored procedures that load them
and the jobs that execute those stored procedures? In other words, back
up everything but the data inside the 90% of the tables which we can
re-create on the next table load?
I'm looking for a way to whittle down the amount of data I'm backing up,
actually backing up just what I specifically need to have to get going
again.
BC
script the database and store it in Source Safe.
Greg Jackson
PDX, Oregon
|||Hi,
There are 2 options for you:-
1. Use generate script to script all the objects (ALL DDLs) and right click
above the job and script the jobs.
2. Do a full database backup once and perform a differential backup daily.
For jobs backup the MSDB database.
Differential backup will backup only the changes after the last backup
and will be very fast in your case since you have very less changes
on a daily basis.
Thanks
Hari
SQL Server MVP
"Blasting Cap" <goober@.christian.net> wrote in message
news:ueeTd0ocFHA.584@.TK2MSFTNGP15.phx.gbl...
>I have a database that takes up around 12 gigs or so that I would like to
>back up to a network share.
> As part of our recovery procedures, I'm also backing up the source files
> that we use to create about 90% of the data on our database (the database
> is a sales information system, with reports generated over the web).
> There may be some data entry into the project, but it is minimal.
> Is there a way to back up the things I'd need to restore the tables, such
> as the data structure of them, the stored procedures that load them and
> the jobs that execute those stored procedures? In other words, back up
> everything but the data inside the 90% of the tables which we can
> re-create on the next table load?
> I'm looking for a way to whittle down the amount of data I'm backing up,
> actually backing up just what I specifically need to have to get going
> again.
> BC
>

Anonymous Pull using FTP - still insists on using original UNC for file share

I've been trying to set up an anonymous pull subscription for merge
replication - SQL 2000 on both sides, post SP3 & same on both machines.
However, when I set up the replication and try to do the initial sync, the
subscription insists on trying to use the original UNC path where I stored the
files from the publisher. Copying the files locally doesn't seem to help as
it still tries to access the UNC. Same with FTP - I set up the site &
specified to use it, but it still tries to access the UNC that way. I
verified that it can access the files via FTP and even copied the files
locally to specify a local path.
I tried reading through the BOL, but didn't come up with much to guide me on
what to try next to get it to read the local files. Any suggestions? This is
the only subscriber I'll have, but it's not on the domain and in our DMZ.
Thanks for any ideas you may have.
-Pete Schott
the connection information on how the subscriber connects with the publisher
to pull the subscription is stored on the publisher.
Do a sp_helpmergepublication 'PublicationName' in your publication database
to verify the publication is 1) enabled for the internet 2) has an alternate
snapshot folder that maps to the root or a virtual directory on your ftp
server, 30 has an ftp address
I take it when you created your pull subscription you chose to download your
files using ftp?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Peter A. Schott" <pschott@.no.spamm.hear.drivefinancial.com> wrote in
message news:1qrpc01577kh0g5vsfcvl7r00ioc4d6scg@.4ax.com...
> I've been trying to set up an anonymous pull subscription for merge
> replication - SQL 2000 on both sides, post SP3 & same on both machines.
> However, when I set up the replication and try to do the initial sync, the
> subscription insists on trying to use the original UNC path where I stored
the
> files from the publisher. Copying the files locally doesn't seem to help
as
> it still tries to access the UNC. Same with FTP - I set up the site &
> specified to use it, but it still tries to access the UNC that way. I
> verified that it can access the files via FTP and even copied the files
> locally to specify a local path.
> I tried reading through the BOL, but didn't come up with much to guide me
on
> what to try next to get it to read the local files. Any suggestions?
This is
> the only subscriber I'll have, but it's not on the domain and in our DMZ.
> Thanks for any ideas you may have.
> -Pete Schott
|||Well, I did that - it's enabled for Internet, has an alternate snapshot
folder, and the folder maps to the root of the virtual/ftp directory. It's
able to pull several of the files, but then dies trying to get to the full UNC
path.
It does the same thing if I specify to use an alternate/local path instead. I
can't seem to get away from that UNC. at all.
Any ideas? Has anyone got some steps that work all of the time to apply an
initial snapshot anonymously over FTP?
TIA,
-pete
"Hilary Cotter" <hilaryk@.att.net> wrote:

> the connection information on how the subscriber connects with the publisher
> to pull the subscription is stored on the publisher.
> Do a sp_helpmergepublication 'PublicationName' in your publication database
> to verify the publication is 1) enabled for the internet 2) has an alternate
> snapshot folder that maps to the root or a virtual directory on your ftp
> server, 30 has an ftp address
> I take it when you created your pull subscription you chose to download your
> files using ftp?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Peter A. Schott" <pschott@.no.spamm.hear.drivefinancial.com> wrote in
> message news:1qrpc01577kh0g5vsfcvl7r00ioc4d6scg@.4ax.com...
> the
> as
> on
> This is
>