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
>

another complex query

Hi, here am i back ..
not sure it's possible to solve it in one query ...
there are four tables:
1) headquarters
--
hqID (primary key)
hqname
2) department
--
depID (primary key)
depname
hqID
3) reports
--
repID (p. key)
depID
userID
4) users
--
userID (p.key)
username
I want to get in one query those four fields:
hqID, hqname, depID, depname + varchar(number of distinct users that has
made a report for
each department) . This last field is a concatenation.
The complexity resides in the fact there is need for a COUNT among other
fields ...
E.g.: table reports may look like this:
repID depID userID
1 1 1
2 1 1
3 1 3
4 3 6
5 4 8
This gives:
for dep 1: 2 distinct users
for dep 2: 0
for dep 3: 1 distinct user
for dep 4: 1 distinct user
Thanks for help
ChrisTry:
select
d.depID
, count (distinct r.userID)
from
departments d
left join
reports r on r.depID = d.depID
group by
d.depID
order by
d.depID
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Chris" <ch@.spam.it> wrote in message
news:%23HOudwFBIHA.3900@.TK2MSFTNGP02.phx.gbl...
Hi, here am i back ..
not sure it's possible to solve it in one query ...
there are four tables:
1) headquarters
--
hqID (primary key)
hqname
2) department
--
depID (primary key)
depname
hqID
3) reports
--
repID (p. key)
depID
userID
4) users
--
userID (p.key)
username
I want to get in one query those four fields:
hqID, hqname, depID, depname + varchar(number of distinct users that has
made a report for
each department) . This last field is a concatenation.
The complexity resides in the fact there is need for a COUNT among other
fields ...
E.g.: table reports may look like this:
repID depID userID
1 1 1
2 1 1
3 1 3
4 3 6
5 4 8
This gives:
for dep 1: 2 distinct users
for dep 2: 0
for dep 3: 1 distinct user
for dep 4: 1 distinct user
Thanks for help
Chris|||Thanks
"Tom Moreau" <tom@.dont.spam.me.cips.ca> schreef in bericht
news:estlIZHBIHA.3848@.TK2MSFTNGP05.phx.gbl...
> Try:
> select
> d.depID
> , count (distinct r.userID)
> from
> departments d
> left join
> reports r on r.depID = d.depID
> group by
> d.depID
> order by
> d.depID
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Chris" <ch@.spam.it> wrote in message
> news:%23HOudwFBIHA.3900@.TK2MSFTNGP02.phx.gbl...
> Hi, here am i back ..
> not sure it's possible to solve it in one query ...
> there are four tables:
> 1) headquarters
> --
> hqID (primary key)
> hqname
> 2) department
> --
> depID (primary key)
> depname
> hqID
> 3) reports
> --
> repID (p. key)
> depID
> userID
> 4) users
> --
> userID (p.key)
> username
> I want to get in one query those four fields:
> hqID, hqname, depID, depname + varchar(number of distinct users that has
> made a report for
> each department) . This last field is a concatenation.
> The complexity resides in the fact there is need for a COUNT among other
> fields ...
>
> E.g.: table reports may look like this:
> repID depID userID
> 1 1 1
> 2 1 1
> 3 1 3
> 4 3 6
> 5 4 8
> This gives:
> for dep 1: 2 distinct users
> for dep 2: 0
> for dep 3: 1 distinct user
> for dep 4: 1 distinct user
> Thanks for help
> Chris
>

Annoying scrolling in SSIS

Hi Jamie, I raised questions about this kind of thing way back in the private beta timeframe. It was perceived as not too much of a practical problem. Either that, or it was relatively low priority compared to other things that needed to be fixed. Another "feature" is that when you lay shapes out nicely on the designer, close and re-open the package they can be moved! Which is a nuisance. Andrew Watt MVP - InfoPath wrote in message news:8cf48857-f836-4a83-b5f3-ea3a5246be4e@.discussions.microsoft.com... >I have a package with 2 and only 2 tasks in it - which obviously easily
> fit onto the control-flow surface at the same time.
> When I open the package though, why-oh-why is there nothing on the
> screen therefore forcing me to scroll all the way over to the left and
> all the way up to the top to see my 2 tasks (at which point the scroll
> bars disappear). >
> Oh and I close the package down, open it straight back up again and the
> same things happens. >
> Very annoying. Anyone concur? >
> -Jamie >
>I have a package with 2 and only 2 tasks in it - which obviously easily fit onto the control-flow surface at the same time.
When I open the package though, why-oh-why is there nothing on the screen therefore forcing me to scroll all the way over to the left and all the way up to the top to see my 2 tasks (at which point the scroll bars disappear).

Oh and I close the package down, open it straight back up again and the same things happens.

OK its nothing major but its very annoying. Anyone concur?

-Jamie