scheduling sql sp needing to access mapped network drives

How to make network drives accessible to a stored procedure? Currently the sp works only if I open a session on the server and execute the sp with SQL Server Management Studio on the server.

If you want to use ressources within the network you will need appropiate permissions either for the service account SQL Server Service is running with or the service account SQL Server Agent is running with (if you do that within a scheduled job). An alternative would be to setup a proxy account for the service [1]

[1] http://www.databasejournal.com/features/mssql/article.php/1580041

In SQL Server 2005 proxy accounts can also be configured through the Configuration interface which you will find in the program collection.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

|||Moving to "SQL Server Database Engine", which is more suitable for this question.|||You want to access via UNC instead of mapped network drive (i.e. \\server\shared).

Do check out security implication posted by Jens.sql

Scheduling a job under SA

I've shceduled a job under sa account (I've changed the password
though),this job access local folder of the box running SQL server.I have
added sa to the sysadmin role and it dose have access to the local folder
..How is it possible as *sa* is a sql server account and how it has the
enough permissions to access local file system?
Thanks a lot
If the job is owned by a sysadmin, it's operating under the
security context of the service account for SQL Agent.
-Sue
On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
wrote:

>I've shceduled a job under sa account (I've changed the password
>though),this job access local folder of the box running SQL server.I have
>added sa to the sysadmin role and it dose have access to the local folder
>.How is it possible as *sa* is a sql server account and how it has the
>enough permissions to access local file system?
>Thanks a lot
>
|||Thanks a lot
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:e36gf11g82of53tigjia7dqobotkfvp5pt@.4ax.com...
> If the job is owned by a sysadmin, it's operating under the
> security context of the service account for SQL Agent.
> -Sue
> On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
> wrote:
>

Scheduling a job under SA

I've shceduled a job under sa account (I've changed the password
though),this job access local folder of the box running SQL server.I have
added sa to the sysadmin role and it dose have access to the local folder
.How is it possible as *sa* is a sql server account and how it has the
enough permissions to access local file system?
Thanks a lotIf the job is owned by a sysadmin, it's operating under the
security context of the service account for SQL Agent.
-Sue
On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
wrote:

>I've shceduled a job under sa account (I've changed the password
>though),this job access local folder of the box running SQL server.I have
>added sa to the sysadmin role and it dose have access to the local folder
>.How is it possible as *sa* is a sql server account and how it has the
>enough permissions to access local file system?
>Thanks a lot
>|||Thanks a lot
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:e36gf11g82of53tigjia7dqobotkfvp5pt@.
4ax.com...
> If the job is owned by a sysadmin, it's operating under the
> security context of the service account for SQL Agent.
> -Sue
> On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
> wrote:
>
>

Scheduling a job under SA

I've shceduled a job under sa account (I've changed the password
though:)),this job access local folder of the box running SQL server.I have
added sa to the sysadmin role and it dose have access to the local folder
.How is it possible as *sa* is a sql server account and how it has the
enough permissions to access local file system?
Thanks a lotIf the job is owned by a sysadmin, it's operating under the
security context of the service account for SQL Agent.
-Sue
On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
wrote:
>I've shceduled a job under sa account (I've changed the password
>though:)),this job access local folder of the box running SQL server.I have
>added sa to the sysadmin role and it dose have access to the local folder
>.How is it possible as *sa* is a sql server account and how it has the
>enough permissions to access local file system?
>Thanks a lot
>|||Thanks a lot
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:e36gf11g82of53tigjia7dqobotkfvp5pt@.4ax.com...
> If the job is owned by a sysadmin, it's operating under the
> security context of the service account for SQL Agent.
> -Sue
> On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
> wrote:
>>I've shceduled a job under sa account (I've changed the password
>>though:)),this job access local folder of the box running SQL server.I
>>have
>>added sa to the sysadmin role and it dose have access to the local folder
>>.How is it possible as *sa* is a sql server account and how it has the
>>enough permissions to access local file system?
>>Thanks a lot
>sql

Scheduled sql cannot access the network drives?

I have a stored procedure performing several tsql operations with MS
Access and Excel files stored into the network file system, and
therefore using OpenDataSouce with these files in the network,
accessible through mapped network drives.

My user has a profile that maps the necessary network drives at boot.
SQL Server runs on the server with an account created for that. This
accont has also a profile mapping the necessary network drives.

The stored procedure runs fine only if I launch it with SQL Server
Management Studio on the server, logging in directly on the server (at
this point the network drives are mapped correctly).

If I launch the Stored Procedure with SQL Server Management Studio on
my client, it doesn't find the network drives and fails.

The same happens when I schedule the stored procedure on the server
with SQL Server Agent, which runs with an account performing the
mapping in its profile.

Any ideas how to make it work?

A suggestion in common, don′t use mapped network driver, use UNC paths !

If you want to use ressources within the network you will need appropiate permissions either for the service account SQL Server Service is running with or the service account SQL Server Agent is running with (if you do that within a scheduled job). An alternative would be to setup a proxy account for the service [1]

[1] http://www.databasejournal.com/features/mssql/article.php/1580041

In SQL Server 2005 proxy accounts can also be configured through the Configuration interface which you will find in the program collection.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

Scheduled Jobs failing, unknown owner?

The job failed. The owner () of job SetShopperSiteReleaseTimes does not have server access
The majority of our Jobs, run by the SQL agent, return teh above messages when running our scheduled DTS packages. We recently went through a domain migration from one domain name to another
I have changed everything that I can identify as being a problem. The server works normally for normal user, and it is only the scheduled jobs (when run by the agent) that have a problem
The Agent is running under a proper domain trust account, as it needs it to enable replication between a few other servers. Owners of the DTS packages were set to the wrong name, this has since been changed using the sp_reassign_dtsowner (or similar, I forgot exact name) stored procedure
I'm loath to believe it is a domain authentication issue with the new domain, because normal Windows authentication between SQL and other applications works just fine. It is only the agent which seems to be having a problem. The agent also runs replication successfully
I suspect something is not quite right with the DTS packages themselves, but I don't know more than this
Anybody have any ideas? Thanks.Who owns the jobs ? If you set the job owner to sa does the job run ok ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jerry Haltom" <jhaltom@.feedbackplusinc.com> wrote in message
news:C2372C43-2874-4B6E-9865-5AFB7016962C@.microsoft.com...
The job failed. The owner () of job SetShopperSiteReleaseTimes does not
have server access.
The majority of our Jobs, run by the SQL agent, return teh above messages
when running our scheduled DTS packages. We recently went through a domain
migration from one domain name to another.
I have changed everything that I can identify as being a problem. The server
works normally for normal user, and it is only the scheduled jobs (when run
by the agent) that have a problem.
The Agent is running under a proper domain trust account, as it needs it to
enable replication between a few other servers. Owners of the DTS packages
were set to the wrong name, this has since been changed using the
sp_reassign_dtsowner (or similar, I forgot exact name) stored procedure.
I'm loath to believe it is a domain authentication issue with the new
domain, because normal Windows authentication between SQL and other
applications works just fine. It is only the agent which seems to be having
a problem. The agent also runs replication successfully.
I suspect something is not quite right with the DTS packages themselves, but
I don't know more than this.
Anybody have any ideas? Thanks.|||A job has an owner... You may open a job and see the owner on the first
tab... When a job is scheduled to run from SQL Agent, the first thing that
happens is that the owner is validated ( the owner must exist.)... If the
owner exists, the job runs, if the owner does NOT exist, the error you are
seeing is returned...
After the owner has been successfully validated, the job actually runs under
the permissions that SQL Agent runs with, ( Not the owners permissions.)
Try changing the owner of the job to someone you know exists ( like YOUR
login) and see if it fixes the problem..
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jerry Haltom" <jhaltom@.feedbackplusinc.com> wrote in message
news:C2372C43-2874-4B6E-9865-5AFB7016962C@.microsoft.com...
> The job failed. The owner () of job SetShopperSiteReleaseTimes does not
have server access.
> The majority of our Jobs, run by the SQL agent, return teh above messages
when running our scheduled DTS packages. We recently went through a domain
migration from one domain name to another.
> I have changed everything that I can identify as being a problem. The
server works normally for normal user, and it is only the scheduled jobs
(when run by the agent) that have a problem.
> The Agent is running under a proper domain trust account, as it needs it
to enable replication between a few other servers. Owners of the DTS
packages were set to the wrong name, this has since been changed using the
sp_reassign_dtsowner (or similar, I forgot exact name) stored procedure.
> I'm loath to believe it is a domain authentication issue with the new
domain, because normal Windows authentication between SQL and other
applications works just fine. It is only the agent which seems to be having
a problem. The agent also runs replication successfully.
> I suspect something is not quite right with the DTS packages themselves,
but I don't know more than this.
> Anybody have any ideas? Thanks.

Scheduled Jobs Failing

I have some Local Packages to import data from Access into SQL which run
fine on but wont run as a scheduled jobs with any steps. TSQL steps run fine
but
DTSRUN /S<server> /E /N<localpackagename>
fails even though it runs on its own.
I noticed that on SQL Server Agent Properties and the Job System tab there
is a checkbox at the bottom relating to CmdExec. On setting this on my
laptop then unsetting it the job does not run on that either now.
Can someone get me out of this hole
Thanks
Andy Willis
Have a look at this:
http://www.support.microsoft.com/?id=269074 How to Run a DTS Package as a
Scheduled Job
Andrew J. Kelly SQL MVP
"Andy Willis" <andrewrwillis@.blueyonder.co.uk> wrote in message
news:e8qeFIT4EHA.208@.TK2MSFTNGP12.phx.gbl...
>I have some Local Packages to import data from Access into SQL which run
> fine on but wont run as a scheduled jobs with any steps. TSQL steps run
> fine
> but
> DTSRUN /S<server> /E /N<localpackagename>
> fails even though it runs on its own.
> I noticed that on SQL Server Agent Properties and the Job System tab there
> is a checkbox at the bottom relating to CmdExec. On setting this on my
> laptop then unsetting it the job does not run on that either now.
> Can someone get me out of this hole
> Thanks
> Andy Willis
>

Scheduled Job Running MS Access in Background not Foreground

We had a scheduled job, within it a step would run an Access app. Before Access would pop up, and if it errors out it will shut itself down and the job would see it as an error and try and rerun the Access app.
After migrating to a new server (install is identical except for hardware), the Access app when called from a job will run in the background, meaning you can only see that it's running by going into the Task Manager and going into the Processes tab. Also
now when Access errors out, (in the background there is a dialog box indicating an error in Access and someone has to go and click ok, which can't be done, since Access is running as a background process) it will sit there waiting for someone to click OK
on the error dialog box. The scheduled job will just hang there since the job thinks Access is still running.
Does anyone know how to get the job to NOT run the Access app in the background and to know when Access errors out?
Can't you just write code to catch the error in the Access database?
"ckaneko" <anonymous@.discussions.microsoft.com> wrote in message
news:DB4CB092-B1B9-4388-9780-EFDCFC9052DB@.microsoft.com...
> We had a scheduled job, within it a step would run an Access app. Before
Access would pop up, and if it errors out it will shut itself down and the
job would see it as an error and try and rerun the Access app.
> After migrating to a new server (install is identical except for
hardware), the Access app when called from a job will run in the background,
meaning you can only see that it's running by going into the Task Manager
and going into the Processes tab. Also now when Access errors out, (in the
background there is a dialog box indicating an error in Access and someone
has to go and click ok, which can't be done, since Access is running as a
background process) it will sit there waiting for someone to click OK on the
error dialog box. The scheduled job will just hang there since the job
thinks Access is still running.
> Does anyone know how to get the job to NOT run the Access app in the
background and to know when Access errors out?

Scheduled Job Running MS Access in Background not Foreground

We had a scheduled job, within it a step would run an Access app. Before Ac
cess would pop up, and if it errors out it will shut itself down and the job
would see it as an error and try and rerun the Access app.
After migrating to a new server (install is identical except for hardware),
the Access app when called from a job will run in the background, meaning yo
u can only see that it's running by going into the Task Manager and going in
to the Processes tab. Also
now when Access errors out, (in the background there is a dialog box indicat
ing an error in Access and someone has to go and click ok, which can't be do
ne, since Access is running as a background process) it will sit there waiti
ng for someone to click OK
on the error dialog box. The scheduled job will just hang there since the j
ob thinks Access is still running.
Does anyone know how to get the job to NOT run the Access app in the backgro
und and to know when Access errors out?Can't you just write code to catch the error in the Access database?
"ckaneko" <anonymous@.discussions.microsoft.com> wrote in message
news:DB4CB092-B1B9-4388-9780-EFDCFC9052DB@.microsoft.com...
> We had a scheduled job, within it a step would run an Access app. Before
Access would pop up, and if it errors out it will shut itself down and the
job would see it as an error and try and rerun the Access app.
> After migrating to a new server (install is identical except for
hardware), the Access app when called from a job will run in the background,
meaning you can only see that it's running by going into the Task Manager
and going into the Processes tab. Also now when Access errors out, (in the
background there is a dialog box indicating an error in Access and someone
has to go and click ok, which can't be done, since Access is running as a
background process) it will sit there waiting for someone to click OK on the
error dialog box. The scheduled job will just hang there since the job
thinks Access is still running.
> Does anyone know how to get the job to NOT run the Access app in the
background and to know when Access errors out?

Scheduled Job Running MS Access in Background not Foreground

We had a scheduled job, within it a step would run an Access app. Before Access would pop up, and if it errors out it will shut itself down and the job would see it as an error and try and rerun the Access app
After migrating to a new server (install is identical except for hardware), the Access app when called from a job will run in the background, meaning you can only see that it's running by going into the Task Manager and going into the Processes tab. Also now when Access errors out, (in the background there is a dialog box indicating an error in Access and someone has to go and click ok, which can't be done, since Access is running as a background process) it will sit there waiting for someone to click OK on the error dialog box. The scheduled job will just hang there since the job thinks Access is still running
Does anyone know how to get the job to NOT run the Access app in the background and to know when Access errors out?Can't you just write code to catch the error in the Access database?
"ckaneko" <anonymous@.discussions.microsoft.com> wrote in message
news:DB4CB092-B1B9-4388-9780-EFDCFC9052DB@.microsoft.com...
> We had a scheduled job, within it a step would run an Access app. Before
Access would pop up, and if it errors out it will shut itself down and the
job would see it as an error and try and rerun the Access app.
> After migrating to a new server (install is identical except for
hardware), the Access app when called from a job will run in the background,
meaning you can only see that it's running by going into the Task Manager
and going into the Processes tab. Also now when Access errors out, (in the
background there is a dialog box indicating an error in Access and someone
has to go and click ok, which can't be done, since Access is running as a
background process) it will sit there waiting for someone to click OK on the
error dialog box. The scheduled job will just hang there since the job
thinks Access is still running.
> Does anyone know how to get the job to NOT run the Access app in the
background and to know when Access errors out?

scheduled backups with the wizard not running"

Hello all,
I am very new to SQL. We are running SQL 2000. We are using one instance to
run Project Web Access and I need to setup a disaster recovery. I have
donwloaded the disaster recovery from the project server site. I have a
pretty good idea how go about backing up the databases in case the server
melts into a puddle. I have setup syncronized database transaction log
marking to have a consistent recovery point.
The problem I am running into is that I am trying to use the SQL wizard to
backup my databases and transaction logs at night. I have made sure to setup
the schedule transactions, but it wont run at night.
Can someone please shine light on my problem.
Thank,s
Joe Hernandez
Is SQL Agent actually running? By the way it does little good to backup
the log only once a night. Themain purpose of transaction log backups is to
minimize the amount of data loss. If you only backup the logs at night you
run the risk of loosing up to 24 hours worth of changes. You might want to
start with no more than an hour apart for the logs.
Andrew J. Kelly SQL MVP
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
> Hello all,
> I am very new to SQL. We are running SQL 2000. We are using one instance
> to
> run Project Web Access and I need to setup a disaster recovery. I have
> donwloaded the disaster recovery from the project server site. I have a
> pretty good idea how go about backing up the databases in case the server
> melts into a puddle. I have setup syncronized database transaction log
> marking to have a consistent recovery point.
> The problem I am running into is that I am trying to use the SQL wizard to
> backup my databases and transaction logs at night. I have made sure to
> setup
> the schedule transactions, but it wont run at night.
> Can someone please shine light on my problem.
> Thank,s
> Joe Hernandez
|||Andrew,
Thanks for your answer
How do I check that the SQL agent is running?
The reason why I setup the transaction log to backup once a day, is because
I have the automatic log and data marking happening at night, and I am trying
to back up the databases at night as well. If I backup the transaction log
every hour and the actual databases at night, I understood that I can only
restore up to the point where I backed up the database? Ithought too often
backup of the transaction log creates an overhead on the SQL performance.
Please advice
Joe Hernandez
"Andrew J. Kelly" wrote:

> Is SQL Agent actually running? By the way it does little good to backup
> the log only once a night. Themain purpose of transaction log backups is to
> minimize the amount of data loss. If you only backup the logs at night you
> run the risk of loosing up to 24 hours worth of changes. You might want to
> start with no more than an hour apart for the logs.
> --
> Andrew J. Kelly SQL MVP
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
>
>
|||You might want to do some more research on your backup strategies. This may
help as well:
http://www.microsoft.com/technet/pro...n/sqlops0.mspx
But here are some general comments about what I see so far. First off I am
not quite sure what you mean by "Mark" the backups. There is nothing
special required to issue a backup in SQL Server other than the BACKUP
command. A FULL backup is required in order to do any restores or even to
do a LOG backup. But doing additional FULL Backups will not in any way
invalidate the LOG backups or the process. They work together. The Log
chain is constant and spans FULL backups. When you need to Restore a DB you
always start from the last FULL backup and then only need to apply the LOG
backups since that one. But the act of doing a FULL backup does not in any
way invalidate the other log backups. Backups in general are very
lightweight, especially the log backups. You should not be afraid to backup
the logs during the day. Actually that is when they are most useful.
To check to see if SQL Agent is running you can open Enterprise Manager and
go to the Management Node. Then when you expand that you will see the SQL
Agent node. If you see a Green arrow it is running. Right click on it to
start or stop it.
Andrew J. Kelly SQL MVP
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:C1624CF6-C205-4973-B418-4CD8224F0F84@.microsoft.com...[vbcol=seagreen]
> Andrew,
> Thanks for your answer
> How do I check that the SQL agent is running?
> The reason why I setup the transaction log to backup once a day, is
> because
> I have the automatic log and data marking happening at night, and I am
> trying
> to back up the databases at night as well. If I backup the transaction log
> every hour and the actual databases at night, I understood that I can only
> restore up to the point where I backed up the database? Ithought too often
> backup of the transaction log creates an overhead on the SQL performance.
> Please advice
> Joe Hernandez
> "Andrew J. Kelly" wrote:
|||in the instace of SQL I am running 3 databases for projectwebaccess. one for
sharepoint service, projectserver and one for reporting services.
According to the disaster recovery for project server because I am using 3
different databases they say it is necessary to use marked transactions in
the transaction log of each database to facilitate recovery, I guess the idea
is that by applying marked transactions to all the databases at the same time
I create a consistent point in all databases, they right: "Recovery of
related databases to any time earlier than the point of failure can only be
accomplished by recovering to a marked transaction.
Thanks for the info on the SQL agent, it was not running. I since then
turned it on and was able to run a schedule back up
Joe H
"Andrew J. Kelly" wrote:

> You might want to do some more research on your backup strategies. This may
> help as well:
> http://www.microsoft.com/technet/pro...n/sqlops0.mspx
> But here are some general comments about what I see so far. First off I am
> not quite sure what you mean by "Mark" the backups. There is nothing
> special required to issue a backup in SQL Server other than the BACKUP
> command. A FULL backup is required in order to do any restores or even to
> do a LOG backup. But doing additional FULL Backups will not in any way
> invalidate the LOG backups or the process. They work together. The Log
> chain is constant and spans FULL backups. When you need to Restore a DB you
> always start from the last FULL backup and then only need to apply the LOG
> backups since that one. But the act of doing a FULL backup does not in any
> way invalidate the other log backups. Backups in general are very
> lightweight, especially the log backups. You should not be afraid to backup
> the logs during the day. Actually that is when they are most useful.
> To check to see if SQL Agent is running you can open Enterprise Manager and
> go to the Management Node. Then when you expand that you will see the SQL
> Agent node. If you see a Green arrow it is running. Right click on it to
> start or stop it.
> --
> Andrew J. Kelly SQL MVP
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:C1624CF6-C205-4973-B418-4CD8224F0F84@.microsoft.com...
>
>
|||Hello,
I think what they are talking about is you may need to keep all your
databases in a consistent state: Meaning if you restore one database and
replay transaction logs to a point and time - you may need to ensure you do
the same on the others to ensure they line up.
Not familiar with Project server so without researching it I can only gather
this is what they mean.
I consult for many, many clients who ALL use SQL - everyone of them I have
set up with full backups at night, and frequent transaction log dumps during
the day to facilitate the best recovery options.
For other clients who demand a little more I set up log shipping; which is a
great DR method and takes only a few hours to set up.
Cheers
Ian
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:35C74E8D-4AAC-4E2E-9E43-B4E82AD402FB@.microsoft.com...[vbcol=seagreen]
> in the instace of SQL I am running 3 databases for projectwebaccess. one
> for
> sharepoint service, projectserver and one for reporting services.
> According to the disaster recovery for project server because I am using 3
> different databases they say it is necessary to use marked transactions in
> the transaction log of each database to facilitate recovery, I guess the
> idea
> is that by applying marked transactions to all the databases at the same
> time
> I create a consistent point in all databases, they right: "Recovery of
> related databases to any time earlier than the point of failure can only
> be
> accomplished by recovering to a marked transaction.
> Thanks for the info on the SQL agent, it was not running. I since then
> turned it on and was able to run a schedule back up
> Joe H
> "Andrew J. Kelly" wrote:
|||If you are updating data across more than one db at a time you should wrap
them in a transaction. Then if you restore to a point in time (nothing
special needed just proper log backups) on each db you should have
consistency between them.
Andrew J. Kelly SQL MVP
"Ian McQuade" <imcquade@.altara.com> wrote in message
news:eomnZE%23CGHA.3992@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I think what they are talking about is you may need to keep all your
> databases in a consistent state: Meaning if you restore one database and
> replay transaction logs to a point and time - you may need to ensure you
> do the same on the others to ensure they line up.
> Not familiar with Project server so without researching it I can only
> gather this is what they mean.
> I consult for many, many clients who ALL use SQL - everyone of them I have
> set up with full backups at night, and frequent transaction log dumps
> during the day to facilitate the best recovery options.
> For other clients who demand a little more I set up log shipping; which is
> a great DR method and takes only a few hours to set up.
> Cheers
> Ian
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:35C74E8D-4AAC-4E2E-9E43-B4E82AD402FB@.microsoft.com...
>
|||Ian,
Thanks for your explanation. So it sounds like I am on the right track that
as long as I keep backups of my databases and transaction log, I should be
able to restore in the event of hardware and/or software malfunction. Good
because I am having a hard time running the automated script to mark all logs
and databases at the same time.
How hard is it to setup log shipping, do you know of a good place to go to
get good notes on that?
thanks for your help
Joe Hernandez
"Ian McQuade" wrote:

> Hello,
> I think what they are talking about is you may need to keep all your
> databases in a consistent state: Meaning if you restore one database and
> replay transaction logs to a point and time - you may need to ensure you do
> the same on the others to ensure they line up.
> Not familiar with Project server so without researching it I can only gather
> this is what they mean.
> I consult for many, many clients who ALL use SQL - everyone of them I have
> set up with full backups at night, and frequent transaction log dumps during
> the day to facilitate the best recovery options.
> For other clients who demand a little more I set up log shipping; which is a
> great DR method and takes only a few hours to set up.
> Cheers
> Ian
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:35C74E8D-4AAC-4E2E-9E43-B4E82AD402FB@.microsoft.com...
>
>

scheduled backups with the wizard not running"

Hello all,
I am very new to SQL. We are running SQL 2000. We are using one instance to
run Project Web Access and I need to setup a disaster recovery. I have
donwloaded the disaster recovery from the project server site. I have a
pretty good idea how go about backing up the databases in case the server
melts into a puddle. I have setup syncronized database transaction log
marking to have a consistent recovery point.
The problem I am running into is that I am trying to use the SQL wizard to
backup my databases and transaction logs at night. I have made sure to setup
the schedule transactions, but it wont run at night.
Can someone please shine light on my problem.
Thank,s
Joe HernandezIs SQL Agent actually running? By the way it does little good to backup
the log only once a night. Themain purpose of transaction log backups is to
minimize the amount of data loss. If you only backup the logs at night you
run the risk of loosing up to 24 hours worth of changes. You might want to
start with no more than an hour apart for the logs.
--
Andrew J. Kelly SQL MVP
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
> Hello all,
> I am very new to SQL. We are running SQL 2000. We are using one instance
> to
> run Project Web Access and I need to setup a disaster recovery. I have
> donwloaded the disaster recovery from the project server site. I have a
> pretty good idea how go about backing up the databases in case the server
> melts into a puddle. I have setup syncronized database transaction log
> marking to have a consistent recovery point.
> The problem I am running into is that I am trying to use the SQL wizard to
> backup my databases and transaction logs at night. I have made sure to
> setup
> the schedule transactions, but it wont run at night.
> Can someone please shine light on my problem.
> Thank,s
> Joe Hernandez|||Andrew,
Thanks for your answer
How do I check that the SQL agent is running?
The reason why I setup the transaction log to backup once a day, is because
I have the automatic log and data marking happening at night, and I am trying
to back up the databases at night as well. If I backup the transaction log
every hour and the actual databases at night, I understood that I can only
restore up to the point where I backed up the database? Ithought too often
backup of the transaction log creates an overhead on the SQL performance.
Please advice
Joe Hernandez
"Andrew J. Kelly" wrote:
> Is SQL Agent actually running? By the way it does little good to backup
> the log only once a night. Themain purpose of transaction log backups is to
> minimize the amount of data loss. If you only backup the logs at night you
> run the risk of loosing up to 24 hours worth of changes. You might want to
> start with no more than an hour apart for the logs.
> --
> Andrew J. Kelly SQL MVP
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
> > Hello all,
> >
> > I am very new to SQL. We are running SQL 2000. We are using one instance
> > to
> > run Project Web Access and I need to setup a disaster recovery. I have
> > donwloaded the disaster recovery from the project server site. I have a
> > pretty good idea how go about backing up the databases in case the server
> > melts into a puddle. I have setup syncronized database transaction log
> > marking to have a consistent recovery point.
> >
> > The problem I am running into is that I am trying to use the SQL wizard to
> > backup my databases and transaction logs at night. I have made sure to
> > setup
> > the schedule transactions, but it wont run at night.
> >
> > Can someone please shine light on my problem.
> >
> > Thank,s
> >
> > Joe Hernandez
>
>|||You might want to do some more research on your backup strategies. This may
help as well:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
But here are some general comments about what I see so far. First off I am
not quite sure what you mean by "Mark" the backups. There is nothing
special required to issue a backup in SQL Server other than the BACKUP
command. A FULL backup is required in order to do any restores or even to
do a LOG backup. But doing additional FULL Backups will not in any way
invalidate the LOG backups or the process. They work together. The Log
chain is constant and spans FULL backups. When you need to Restore a DB you
always start from the last FULL backup and then only need to apply the LOG
backups since that one. But the act of doing a FULL backup does not in any
way invalidate the other log backups. Backups in general are very
lightweight, especially the log backups. You should not be afraid to backup
the logs during the day. Actually that is when they are most useful.
To check to see if SQL Agent is running you can open Enterprise Manager and
go to the Management Node. Then when you expand that you will see the SQL
Agent node. If you see a Green arrow it is running. Right click on it to
start or stop it.
--
Andrew J. Kelly SQL MVP
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:C1624CF6-C205-4973-B418-4CD8224F0F84@.microsoft.com...
> Andrew,
> Thanks for your answer
> How do I check that the SQL agent is running?
> The reason why I setup the transaction log to backup once a day, is
> because
> I have the automatic log and data marking happening at night, and I am
> trying
> to back up the databases at night as well. If I backup the transaction log
> every hour and the actual databases at night, I understood that I can only
> restore up to the point where I backed up the database? Ithought too often
> backup of the transaction log creates an overhead on the SQL performance.
> Please advice
> Joe Hernandez
> "Andrew J. Kelly" wrote:
>> Is SQL Agent actually running? By the way it does little good to backup
>> the log only once a night. Themain purpose of transaction log backups is
>> to
>> minimize the amount of data loss. If you only backup the logs at night
>> you
>> run the risk of loosing up to 24 hours worth of changes. You might want
>> to
>> start with no more than an hour apart for the logs.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
>> news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
>> > Hello all,
>> >
>> > I am very new to SQL. We are running SQL 2000. We are using one
>> > instance
>> > to
>> > run Project Web Access and I need to setup a disaster recovery. I have
>> > donwloaded the disaster recovery from the project server site. I have a
>> > pretty good idea how go about backing up the databases in case the
>> > server
>> > melts into a puddle. I have setup syncronized database transaction log
>> > marking to have a consistent recovery point.
>> >
>> > The problem I am running into is that I am trying to use the SQL wizard
>> > to
>> > backup my databases and transaction logs at night. I have made sure to
>> > setup
>> > the schedule transactions, but it wont run at night.
>> >
>> > Can someone please shine light on my problem.
>> >
>> > Thank,s
>> >
>> > Joe Hernandez
>>|||in the instace of SQL I am running 3 databases for projectwebaccess. one for
sharepoint service, projectserver and one for reporting services.
According to the disaster recovery for project server because I am using 3
different databases they say it is necessary to use marked transactions in
the transaction log of each database to facilitate recovery, I guess the idea
is that by applying marked transactions to all the databases at the same time
I create a consistent point in all databases, they right: "Recovery of
related databases to any time earlier than the point of failure can only be
accomplished by recovering to a marked transaction.
Thanks for the info on the SQL agent, it was not running. I since then
turned it on and was able to run a schedule back up
Joe H
"Andrew J. Kelly" wrote:
> You might want to do some more research on your backup strategies. This may
> help as well:
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
> But here are some general comments about what I see so far. First off I am
> not quite sure what you mean by "Mark" the backups. There is nothing
> special required to issue a backup in SQL Server other than the BACKUP
> command. A FULL backup is required in order to do any restores or even to
> do a LOG backup. But doing additional FULL Backups will not in any way
> invalidate the LOG backups or the process. They work together. The Log
> chain is constant and spans FULL backups. When you need to Restore a DB you
> always start from the last FULL backup and then only need to apply the LOG
> backups since that one. But the act of doing a FULL backup does not in any
> way invalidate the other log backups. Backups in general are very
> lightweight, especially the log backups. You should not be afraid to backup
> the logs during the day. Actually that is when they are most useful.
> To check to see if SQL Agent is running you can open Enterprise Manager and
> go to the Management Node. Then when you expand that you will see the SQL
> Agent node. If you see a Green arrow it is running. Right click on it to
> start or stop it.
> --
> Andrew J. Kelly SQL MVP
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:C1624CF6-C205-4973-B418-4CD8224F0F84@.microsoft.com...
> > Andrew,
> > Thanks for your answer
> >
> > How do I check that the SQL agent is running?
> >
> > The reason why I setup the transaction log to backup once a day, is
> > because
> > I have the automatic log and data marking happening at night, and I am
> > trying
> > to back up the databases at night as well. If I backup the transaction log
> > every hour and the actual databases at night, I understood that I can only
> > restore up to the point where I backed up the database? Ithought too often
> > backup of the transaction log creates an overhead on the SQL performance.
> >
> > Please advice
> >
> > Joe Hernandez
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Is SQL Agent actually running? By the way it does little good to backup
> >> the log only once a night. Themain purpose of transaction log backups is
> >> to
> >> minimize the amount of data loss. If you only backup the logs at night
> >> you
> >> run the risk of loosing up to 24 hours worth of changes. You might want
> >> to
> >> start with no more than an hour apart for the logs.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> >> news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
> >> > Hello all,
> >> >
> >> > I am very new to SQL. We are running SQL 2000. We are using one
> >> > instance
> >> > to
> >> > run Project Web Access and I need to setup a disaster recovery. I have
> >> > donwloaded the disaster recovery from the project server site. I have a
> >> > pretty good idea how go about backing up the databases in case the
> >> > server
> >> > melts into a puddle. I have setup syncronized database transaction log
> >> > marking to have a consistent recovery point.
> >> >
> >> > The problem I am running into is that I am trying to use the SQL wizard
> >> > to
> >> > backup my databases and transaction logs at night. I have made sure to
> >> > setup
> >> > the schedule transactions, but it wont run at night.
> >> >
> >> > Can someone please shine light on my problem.
> >> >
> >> > Thank,s
> >> >
> >> > Joe Hernandez
> >>
> >>
> >>
>
>|||Hello,
I think what they are talking about is you may need to keep all your
databases in a consistent state: Meaning if you restore one database and
replay transaction logs to a point and time - you may need to ensure you do
the same on the others to ensure they line up.
Not familiar with Project server so without researching it I can only gather
this is what they mean.
I consult for many, many clients who ALL use SQL - everyone of them I have
set up with full backups at night, and frequent transaction log dumps during
the day to facilitate the best recovery options.
For other clients who demand a little more I set up log shipping; which is a
great DR method and takes only a few hours to set up.
Cheers
Ian
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:35C74E8D-4AAC-4E2E-9E43-B4E82AD402FB@.microsoft.com...
> in the instace of SQL I am running 3 databases for projectwebaccess. one
> for
> sharepoint service, projectserver and one for reporting services.
> According to the disaster recovery for project server because I am using 3
> different databases they say it is necessary to use marked transactions in
> the transaction log of each database to facilitate recovery, I guess the
> idea
> is that by applying marked transactions to all the databases at the same
> time
> I create a consistent point in all databases, they right: "Recovery of
> related databases to any time earlier than the point of failure can only
> be
> accomplished by recovering to a marked transaction.
> Thanks for the info on the SQL agent, it was not running. I since then
> turned it on and was able to run a schedule back up
> Joe H
> "Andrew J. Kelly" wrote:
>> You might want to do some more research on your backup strategies. This
>> may
>> help as well:
>> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
>> But here are some general comments about what I see so far. First off I
>> am
>> not quite sure what you mean by "Mark" the backups. There is nothing
>> special required to issue a backup in SQL Server other than the BACKUP
>> command. A FULL backup is required in order to do any restores or even
>> to
>> do a LOG backup. But doing additional FULL Backups will not in any way
>> invalidate the LOG backups or the process. They work together. The Log
>> chain is constant and spans FULL backups. When you need to Restore a DB
>> you
>> always start from the last FULL backup and then only need to apply the
>> LOG
>> backups since that one. But the act of doing a FULL backup does not in
>> any
>> way invalidate the other log backups. Backups in general are very
>> lightweight, especially the log backups. You should not be afraid to
>> backup
>> the logs during the day. Actually that is when they are most useful.
>> To check to see if SQL Agent is running you can open Enterprise Manager
>> and
>> go to the Management Node. Then when you expand that you will see the
>> SQL
>> Agent node. If you see a Green arrow it is running. Right click on it to
>> start or stop it.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
>> news:C1624CF6-C205-4973-B418-4CD8224F0F84@.microsoft.com...
>> > Andrew,
>> > Thanks for your answer
>> >
>> > How do I check that the SQL agent is running?
>> >
>> > The reason why I setup the transaction log to backup once a day, is
>> > because
>> > I have the automatic log and data marking happening at night, and I am
>> > trying
>> > to back up the databases at night as well. If I backup the transaction
>> > log
>> > every hour and the actual databases at night, I understood that I can
>> > only
>> > restore up to the point where I backed up the database? Ithought too
>> > often
>> > backup of the transaction log creates an overhead on the SQL
>> > performance.
>> >
>> > Please advice
>> >
>> > Joe Hernandez
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> Is SQL Agent actually running? By the way it does little good to
>> >> backup
>> >> the log only once a night. Themain purpose of transaction log backups
>> >> is
>> >> to
>> >> minimize the amount of data loss. If you only backup the logs at
>> >> night
>> >> you
>> >> run the risk of loosing up to 24 hours worth of changes. You might
>> >> want
>> >> to
>> >> start with no more than an hour apart for the logs.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in
>> >> message
>> >> news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
>> >> > Hello all,
>> >> >
>> >> > I am very new to SQL. We are running SQL 2000. We are using one
>> >> > instance
>> >> > to
>> >> > run Project Web Access and I need to setup a disaster recovery. I
>> >> > have
>> >> > donwloaded the disaster recovery from the project server site. I
>> >> > have a
>> >> > pretty good idea how go about backing up the databases in case the
>> >> > server
>> >> > melts into a puddle. I have setup syncronized database transaction
>> >> > log
>> >> > marking to have a consistent recovery point.
>> >> >
>> >> > The problem I am running into is that I am trying to use the SQL
>> >> > wizard
>> >> > to
>> >> > backup my databases and transaction logs at night. I have made sure
>> >> > to
>> >> > setup
>> >> > the schedule transactions, but it wont run at night.
>> >> >
>> >> > Can someone please shine light on my problem.
>> >> >
>> >> > Thank,s
>> >> >
>> >> > Joe Hernandez
>> >>
>> >>
>> >>
>>|||If you are updating data across more than one db at a time you should wrap
them in a transaction. Then if you restore to a point in time (nothing
special needed just proper log backups) on each db you should have
consistency between them.
--
Andrew J. Kelly SQL MVP
"Ian McQuade" <imcquade@.altara.com> wrote in message
news:eomnZE%23CGHA.3992@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I think what they are talking about is you may need to keep all your
> databases in a consistent state: Meaning if you restore one database and
> replay transaction logs to a point and time - you may need to ensure you
> do the same on the others to ensure they line up.
> Not familiar with Project server so without researching it I can only
> gather this is what they mean.
> I consult for many, many clients who ALL use SQL - everyone of them I have
> set up with full backups at night, and frequent transaction log dumps
> during the day to facilitate the best recovery options.
> For other clients who demand a little more I set up log shipping; which is
> a great DR method and takes only a few hours to set up.
> Cheers
> Ian
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:35C74E8D-4AAC-4E2E-9E43-B4E82AD402FB@.microsoft.com...
>> in the instace of SQL I am running 3 databases for projectwebaccess. one
>> for
>> sharepoint service, projectserver and one for reporting services.
>> According to the disaster recovery for project server because I am using
>> 3
>> different databases they say it is necessary to use marked transactions
>> in
>> the transaction log of each database to facilitate recovery, I guess the
>> idea
>> is that by applying marked transactions to all the databases at the same
>> time
>> I create a consistent point in all databases, they right: "Recovery of
>> related databases to any time earlier than the point of failure can only
>> be
>> accomplished by recovering to a marked transaction.
>> Thanks for the info on the SQL agent, it was not running. I since then
>> turned it on and was able to run a schedule back up
>> Joe H
>> "Andrew J. Kelly" wrote:
>> You might want to do some more research on your backup strategies. This
>> may
>> help as well:
>> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
>> But here are some general comments about what I see so far. First off I
>> am
>> not quite sure what you mean by "Mark" the backups. There is nothing
>> special required to issue a backup in SQL Server other than the BACKUP
>> command. A FULL backup is required in order to do any restores or even
>> to
>> do a LOG backup. But doing additional FULL Backups will not in any way
>> invalidate the LOG backups or the process. They work together. The Log
>> chain is constant and spans FULL backups. When you need to Restore a DB
>> you
>> always start from the last FULL backup and then only need to apply the
>> LOG
>> backups since that one. But the act of doing a FULL backup does not in
>> any
>> way invalidate the other log backups. Backups in general are very
>> lightweight, especially the log backups. You should not be afraid to
>> backup
>> the logs during the day. Actually that is when they are most useful.
>> To check to see if SQL Agent is running you can open Enterprise Manager
>> and
>> go to the Management Node. Then when you expand that you will see the
>> SQL
>> Agent node. If you see a Green arrow it is running. Right click on it
>> to
>> start or stop it.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in
>> message
>> news:C1624CF6-C205-4973-B418-4CD8224F0F84@.microsoft.com...
>> > Andrew,
>> > Thanks for your answer
>> >
>> > How do I check that the SQL agent is running?
>> >
>> > The reason why I setup the transaction log to backup once a day, is
>> > because
>> > I have the automatic log and data marking happening at night, and I am
>> > trying
>> > to back up the databases at night as well. If I backup the transaction
>> > log
>> > every hour and the actual databases at night, I understood that I can
>> > only
>> > restore up to the point where I backed up the database? Ithought too
>> > often
>> > backup of the transaction log creates an overhead on the SQL
>> > performance.
>> >
>> > Please advice
>> >
>> > Joe Hernandez
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> Is SQL Agent actually running? By the way it does little good to
>> >> backup
>> >> the log only once a night. Themain purpose of transaction log
>> >> backups is
>> >> to
>> >> minimize the amount of data loss. If you only backup the logs at
>> >> night
>> >> you
>> >> run the risk of loosing up to 24 hours worth of changes. You might
>> >> want
>> >> to
>> >> start with no more than an hour apart for the logs.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in
>> >> message
>> >> news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
>> >> > Hello all,
>> >> >
>> >> > I am very new to SQL. We are running SQL 2000. We are using one
>> >> > instance
>> >> > to
>> >> > run Project Web Access and I need to setup a disaster recovery. I
>> >> > have
>> >> > donwloaded the disaster recovery from the project server site. I
>> >> > have a
>> >> > pretty good idea how go about backing up the databases in case the
>> >> > server
>> >> > melts into a puddle. I have setup syncronized database transaction
>> >> > log
>> >> > marking to have a consistent recovery point.
>> >> >
>> >> > The problem I am running into is that I am trying to use the SQL
>> >> > wizard
>> >> > to
>> >> > backup my databases and transaction logs at night. I have made sure
>> >> > to
>> >> > setup
>> >> > the schedule transactions, but it wont run at night.
>> >> >
>> >> > Can someone please shine light on my problem.
>> >> >
>> >> > Thank,s
>> >> >
>> >> > Joe Hernandez
>> >>
>> >>
>> >>
>>
>|||Ian,
Thanks for your explanation. So it sounds like I am on the right track that
as long as I keep backups of my databases and transaction log, I should be
able to restore in the event of hardware and/or software malfunction. Good
because I am having a hard time running the automated script to mark all logs
and databases at the same time.
How hard is it to setup log shipping, do you know of a good place to go to
get good notes on that?
thanks for your help
Joe Hernandez
"Ian McQuade" wrote:
> Hello,
> I think what they are talking about is you may need to keep all your
> databases in a consistent state: Meaning if you restore one database and
> replay transaction logs to a point and time - you may need to ensure you do
> the same on the others to ensure they line up.
> Not familiar with Project server so without researching it I can only gather
> this is what they mean.
> I consult for many, many clients who ALL use SQL - everyone of them I have
> set up with full backups at night, and frequent transaction log dumps during
> the day to facilitate the best recovery options.
> For other clients who demand a little more I set up log shipping; which is a
> great DR method and takes only a few hours to set up.
> Cheers
> Ian
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:35C74E8D-4AAC-4E2E-9E43-B4E82AD402FB@.microsoft.com...
> > in the instace of SQL I am running 3 databases for projectwebaccess. one
> > for
> > sharepoint service, projectserver and one for reporting services.
> > According to the disaster recovery for project server because I am using 3
> > different databases they say it is necessary to use marked transactions in
> > the transaction log of each database to facilitate recovery, I guess the
> > idea
> > is that by applying marked transactions to all the databases at the same
> > time
> > I create a consistent point in all databases, they right: "Recovery of
> > related databases to any time earlier than the point of failure can only
> > be
> > accomplished by recovering to a marked transaction.
> >
> > Thanks for the info on the SQL agent, it was not running. I since then
> > turned it on and was able to run a schedule back up
> >
> > Joe H
> >
> > "Andrew J. Kelly" wrote:
> >
> >> You might want to do some more research on your backup strategies. This
> >> may
> >> help as well:
> >> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
> >>
> >> But here are some general comments about what I see so far. First off I
> >> am
> >> not quite sure what you mean by "Mark" the backups. There is nothing
> >> special required to issue a backup in SQL Server other than the BACKUP
> >> command. A FULL backup is required in order to do any restores or even
> >> to
> >> do a LOG backup. But doing additional FULL Backups will not in any way
> >> invalidate the LOG backups or the process. They work together. The Log
> >> chain is constant and spans FULL backups. When you need to Restore a DB
> >> you
> >> always start from the last FULL backup and then only need to apply the
> >> LOG
> >> backups since that one. But the act of doing a FULL backup does not in
> >> any
> >> way invalidate the other log backups. Backups in general are very
> >> lightweight, especially the log backups. You should not be afraid to
> >> backup
> >> the logs during the day. Actually that is when they are most useful.
> >>
> >> To check to see if SQL Agent is running you can open Enterprise Manager
> >> and
> >> go to the Management Node. Then when you expand that you will see the
> >> SQL
> >> Agent node. If you see a Green arrow it is running. Right click on it to
> >> start or stop it.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> >> news:C1624CF6-C205-4973-B418-4CD8224F0F84@.microsoft.com...
> >> > Andrew,
> >> > Thanks for your answer
> >> >
> >> > How do I check that the SQL agent is running?
> >> >
> >> > The reason why I setup the transaction log to backup once a day, is
> >> > because
> >> > I have the automatic log and data marking happening at night, and I am
> >> > trying
> >> > to back up the databases at night as well. If I backup the transaction
> >> > log
> >> > every hour and the actual databases at night, I understood that I can
> >> > only
> >> > restore up to the point where I backed up the database? Ithought too
> >> > often
> >> > backup of the transaction log creates an overhead on the SQL
> >> > performance.
> >> >
> >> > Please advice
> >> >
> >> > Joe Hernandez
> >> >
> >> > "Andrew J. Kelly" wrote:
> >> >
> >> >> Is SQL Agent actually running? By the way it does little good to
> >> >> backup
> >> >> the log only once a night. Themain purpose of transaction log backups
> >> >> is
> >> >> to
> >> >> minimize the amount of data loss. If you only backup the logs at
> >> >> night
> >> >> you
> >> >> run the risk of loosing up to 24 hours worth of changes. You might
> >> >> want
> >> >> to
> >> >> start with no more than an hour apart for the logs.
> >> >>
> >> >> --
> >> >> Andrew J. Kelly SQL MVP
> >> >>
> >> >>
> >> >> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
> >> >> > Hello all,
> >> >> >
> >> >> > I am very new to SQL. We are running SQL 2000. We are using one
> >> >> > instance
> >> >> > to
> >> >> > run Project Web Access and I need to setup a disaster recovery. I
> >> >> > have
> >> >> > donwloaded the disaster recovery from the project server site. I
> >> >> > have a
> >> >> > pretty good idea how go about backing up the databases in case the
> >> >> > server
> >> >> > melts into a puddle. I have setup syncronized database transaction
> >> >> > log
> >> >> > marking to have a consistent recovery point.
> >> >> >
> >> >> > The problem I am running into is that I am trying to use the SQL
> >> >> > wizard
> >> >> > to
> >> >> > backup my databases and transaction logs at night. I have made sure
> >> >> > to
> >> >> > setup
> >> >> > the schedule transactions, but it wont run at night.
> >> >> >
> >> >> > Can someone please shine light on my problem.
> >> >> >
> >> >> > Thank,s
> >> >> >
> >> >> > Joe Hernandez
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>

scheduled backups with the wizard not running"

Hello all,
I am very new to SQL. We are running SQL 2000. We are using one instance to
run Project Web Access and I need to setup a disaster recovery. I have
donwloaded the disaster recovery from the project server site. I have a
pretty good idea how go about backing up the databases in case the server
melts into a puddle. I have setup syncronized database transaction log
marking to have a consistent recovery point.
The problem I am running into is that I am trying to use the SQL wizard to
backup my databases and transaction logs at night. I have made sure to setup
the schedule transactions, but it wont run at night.
Can someone please shine light on my problem.
Thank,s
Joe HernandezIs SQL Agent actually running? By the way it does little good to backup
the log only once a night. Themain purpose of transaction log backups is to
minimize the amount of data loss. If you only backup the logs at night you
run the risk of loosing up to 24 hours worth of changes. You might want to
start with no more than an hour apart for the logs.
Andrew J. Kelly SQL MVP
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
> Hello all,
> I am very new to SQL. We are running SQL 2000. We are using one instance
> to
> run Project Web Access and I need to setup a disaster recovery. I have
> donwloaded the disaster recovery from the project server site. I have a
> pretty good idea how go about backing up the databases in case the server
> melts into a puddle. I have setup syncronized database transaction log
> marking to have a consistent recovery point.
> The problem I am running into is that I am trying to use the SQL wizard to
> backup my databases and transaction logs at night. I have made sure to
> setup
> the schedule transactions, but it wont run at night.
> Can someone please shine light on my problem.
> Thank,s
> Joe Hernandez|||Andrew,
Thanks for your answer
How do I check that the SQL agent is running?
The reason why I setup the transaction log to backup once a day, is because
I have the automatic log and data marking happening at night, and I am tryin
g
to back up the databases at night as well. If I backup the transaction log
every hour and the actual databases at night, I understood that I can only
restore up to the point where I backed up the database? Ithought too often
backup of the transaction log creates an overhead on the SQL performance.
Please advice
Joe Hernandez
"Andrew J. Kelly" wrote:

> Is SQL Agent actually running? By the way it does little good to backup
> the log only once a night. Themain purpose of transaction log backups is
to
> minimize the amount of data loss. If you only backup the logs at night yo
u
> run the risk of loosing up to 24 hours worth of changes. You might want t
o
> start with no more than an hour apart for the logs.
> --
> Andrew J. Kelly SQL MVP
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:CB184888-D70E-480C-BB23-2F3CE6014FBF@.microsoft.com...
>
>|||You might want to do some more research on your backup strategies. This may
help as well:
http://www.microsoft.com/technet/pr...in/sqlops0.mspx
But here are some general comments about what I see so far. First off I am
not quite sure what you mean by "Mark" the backups. There is nothing
special required to issue a backup in SQL Server other than the BACKUP
command. A FULL backup is required in order to do any restores or even to
do a LOG backup. But doing additional FULL Backups will not in any way
invalidate the LOG backups or the process. They work together. The Log
chain is constant and spans FULL backups. When you need to Restore a DB you
always start from the last FULL backup and then only need to apply the LOG
backups since that one. But the act of doing a FULL backup does not in any
way invalidate the other log backups. Backups in general are very
lightweight, especially the log backups. You should not be afraid to backup
the logs during the day. Actually that is when they are most useful.
To check to see if SQL Agent is running you can open Enterprise Manager and
go to the Management Node. Then when you expand that you will see the SQL
Agent node. If you see a Green arrow it is running. Right click on it to
start or stop it.
Andrew J. Kelly SQL MVP
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:C1624CF6-C205-4973-B418-4CD8224F0F84@.microsoft.com...[vbcol=seagreen]
> Andrew,
> Thanks for your answer
> How do I check that the SQL agent is running?
> The reason why I setup the transaction log to backup once a day, is
> because
> I have the automatic log and data marking happening at night, and I am
> trying
> to back up the databases at night as well. If I backup the transaction log
> every hour and the actual databases at night, I understood that I can only
> restore up to the point where I backed up the database? Ithought too often
> backup of the transaction log creates an overhead on the SQL performance.
> Please advice
> Joe Hernandez
> "Andrew J. Kelly" wrote:
>|||in the instace of SQL I am running 3 databases for projectwebaccess. one for
sharepoint service, projectserver and one for reporting services.
According to the disaster recovery for project server because I am using 3
different databases they say it is necessary to use marked transactions in
the transaction log of each database to facilitate recovery, I guess the ide
a
is that by applying marked transactions to all the databases at the same tim
e
I create a consistent point in all databases, they right: "Recovery of
related databases to any time earlier than the point of failure can only be
accomplished by recovering to a marked transaction.
Thanks for the info on the SQL agent, it was not running. I since then
turned it on and was able to run a schedule back up
Joe H
"Andrew J. Kelly" wrote:

> You might want to do some more research on your backup strategies. This ma
y
> help as well:
> [url]http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx[/url
]
> But here are some general comments about what I see so far. First off I a
m
> not quite sure what you mean by "Mark" the backups. There is nothing
> special required to issue a backup in SQL Server other than the BACKUP
> command. A FULL backup is required in order to do any restores or even to
> do a LOG backup. But doing additional FULL Backups will not in any way
> invalidate the LOG backups or the process. They work together. The Log
> chain is constant and spans FULL backups. When you need to Restore a DB y
ou
> always start from the last FULL backup and then only need to apply the LOG
> backups since that one. But the act of doing a FULL backup does not in an
y
> way invalidate the other log backups. Backups in general are very
> lightweight, especially the log backups. You should not be afraid to back
up
> the logs during the day. Actually that is when they are most useful.
> To check to see if SQL Agent is running you can open Enterprise Manager an
d
> go to the Management Node. Then when you expand that you will see the SQL
> Agent node. If you see a Green arrow it is running. Right click on it to
> start or stop it.
> --
> Andrew J. Kelly SQL MVP
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:C1624CF6-C205-4973-B418-4CD8224F0F84@.microsoft.com...
>
>|||Hello,
I think what they are talking about is you may need to keep all your
databases in a consistent state: Meaning if you restore one database and
replay transaction logs to a point and time - you may need to ensure you do
the same on the others to ensure they line up.
Not familiar with Project server so without researching it I can only gather
this is what they mean.
I consult for many, many clients who ALL use SQL - everyone of them I have
set up with full backups at night, and frequent transaction log dumps during
the day to facilitate the best recovery options.
For other clients who demand a little more I set up log shipping; which is a
great DR method and takes only a few hours to set up.
Cheers
Ian
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:35C74E8D-4AAC-4E2E-9E43-B4E82AD402FB@.microsoft.com...[vbcol=seagreen]
> in the instace of SQL I am running 3 databases for projectwebaccess. one
> for
> sharepoint service, projectserver and one for reporting services.
> According to the disaster recovery for project server because I am using 3
> different databases they say it is necessary to use marked transactions in
> the transaction log of each database to facilitate recovery, I guess the
> idea
> is that by applying marked transactions to all the databases at the same
> time
> I create a consistent point in all databases, they right: "Recovery of
> related databases to any time earlier than the point of failure can only
> be
> accomplished by recovering to a marked transaction.
> Thanks for the info on the SQL agent, it was not running. I since then
> turned it on and was able to run a schedule back up
> Joe H
> "Andrew J. Kelly" wrote:
>|||If you are updating data across more than one db at a time you should wrap
them in a transaction. Then if you restore to a point in time (nothing
special needed just proper log backups) on each db you should have
consistency between them.
Andrew J. Kelly SQL MVP
"Ian McQuade" <imcquade@.altara.com> wrote in message
news:eomnZE%23CGHA.3992@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I think what they are talking about is you may need to keep all your
> databases in a consistent state: Meaning if you restore one database and
> replay transaction logs to a point and time - you may need to ensure you
> do the same on the others to ensure they line up.
> Not familiar with Project server so without researching it I can only
> gather this is what they mean.
> I consult for many, many clients who ALL use SQL - everyone of them I have
> set up with full backups at night, and frequent transaction log dumps
> during the day to facilitate the best recovery options.
> For other clients who demand a little more I set up log shipping; which is
> a great DR method and takes only a few hours to set up.
> Cheers
> Ian
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:35C74E8D-4AAC-4E2E-9E43-B4E82AD402FB@.microsoft.com...
>|||Ian,
Thanks for your explanation. So it sounds like I am on the right track that
as long as I keep backups of my databases and transaction log, I should be
able to restore in the event of hardware and/or software malfunction. Good
because I am having a hard time running the automated script to mark all log
s
and databases at the same time.
How hard is it to setup log shipping, do you know of a good place to go to
get good notes on that?
thanks for your help
Joe Hernandez
"Ian McQuade" wrote:

> Hello,
> I think what they are talking about is you may need to keep all your
> databases in a consistent state: Meaning if you restore one database and
> replay transaction logs to a point and time - you may need to ensure you d
o
> the same on the others to ensure they line up.
> Not familiar with Project server so without researching it I can only gath
er
> this is what they mean.
> I consult for many, many clients who ALL use SQL - everyone of them I have
> set up with full backups at night, and frequent transaction log dumps duri
ng
> the day to facilitate the best recovery options.
> For other clients who demand a little more I set up log shipping; which is
a
> great DR method and takes only a few hours to set up.
> Cheers
> Ian
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:35C74E8D-4AAC-4E2E-9E43-B4E82AD402FB@.microsoft.com...
>
>

Scheduled Backups

I have setup several backup sets via the individual database.
But - in SQL Server 2000 - my brain has faded away. I can't find where to
access those scheduled backups that I setup?
Can anyone help me find where to change scheduled backup times? I am sure
it's right in front of my face, and I am just missing it.
Thanks
KevinHi,
1. Open SQl Server Enterprise manager
2. Expand the server you need to change the backup job timings
3. Go to "Management" Option
4. Expand " SQL Server Agent"
5. Select "Jobs"
6. Now in the right side of window pane all the jobs will be displayed.
7. Double click on ur job , select the schedules , click EDIT and change the
timings
8. Click OK and APPLY.
Thanks
Hari
MCDBA
"Kevin Hill" <khill@.nospam.com> wrote in message
news:6o5Ec.791$T05.626@.chiapp18.algx.net...
> I have setup several backup sets via the individual database.
> But - in SQL Server 2000 - my brain has faded away. I can't find where to
> access those scheduled backups that I setup?
> Can anyone help me find where to change scheduled backup times? I am sure
> it's right in front of my face, and I am just missing it.
> Thanks
> Kevin
>|||Using Enterprise Manager
your server > Management > SQL Server Agent > Jobs
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Kevin Hill" <khill@.nospam.com> wrote in message
news:6o5Ec.791$T05.626@.chiapp18.algx.net...
> I have setup several backup sets via the individual database.
> But - in SQL Server 2000 - my brain has faded away. I can't find where to
> access those scheduled backups that I setup?
> Can anyone help me find where to change scheduled backup times? I am sure
> it's right in front of my face, and I am just missing it.
> Thanks
> Kevin
>

Schedule Trucate and Shrink

Hello all,
I am very new to sql server as we have just replaced our enterprise
application (was access) Our Datafile is around 3GB and the log grows 3GB in
a day. I have auto job routines scheduled in EM and happening every night
for backups etc and they are then auto (scheduled) backed up to tape. The
log file is still 2.5GB in the am after the all the jobs run so I am
shrinking the DB every few days and the log drops to 768KB.
My question is I see all the DBCC shrinfile commands Truncate etc... my
question is (pardon my ignorance) where the heck to I put these, how do they
run and how can i schedule them?
Please be gentle with you reply.
MIf your log naturally grows 3gb a day you should (1) not shrink it and (2)
possibly schedule more frequent log backups. If you require point in time
recovery you should use the truncate log command, if you do not require
point in time recovery, life is easy, set the db to simple recovery mode and
you won't have to worry about the tran logs.
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Maureen" <nosend2me@.hotmail.com> wrote in message
news:u9GckFtuDHA.3140@.TK2MSFTNGP11.phx.gbl...
> Hello all,
> I am very new to sql server as we have just replaced our enterprise
> application (was access) Our Datafile is around 3GB and the log grows 3GB
in
> a day. I have auto job routines scheduled in EM and happening every night
> for backups etc and they are then auto (scheduled) backed up to tape. The
> log file is still 2.5GB in the am after the all the jobs run so I am
> shrinking the DB every few days and the log drops to 768KB.
> My question is I see all the DBCC shrinfile commands Truncate etc... my
> question is (pardon my ignorance) where the heck to I put these, how do
they
> run and how can i schedule them?
> Please be gentle with you reply.
> M
>|||Ray,
Thanks for the note.
I need to keep to possible "point in time" recovery. here is a normal day.
12.01 AM E.M.-Sql-Maintenence Plan begins and optimizes/backup data/backup
log report Scheduled daily
5:00 AM Complete Server Backup to Tape NTBACKUP Scheduled including backup
to tape of SqlBackup
8:00 AM Workday begins (Tape changed from [Day1,2,3,4,5 etc]-Nightly to
[Day1,2,3,4,5]-Daily
Regular Work Day....
5:00 PM SqlBackup to tape Complete
5:30 PM Workday end (Tape changed from [Day1,2,3,4,5 etc]-Daily to
[Day1,2,3,4,5]-Nightly
I can easily add a couple more backups to tape or disk during the day. The
server has hardware raid with 5 drives in a raid 5 (data is on these
spmdles) PLUS 2 drives raid 10 for the logs. I am well covered for potential
failure. What I would like to know is where do I issue the Truncate Log
Command AND how do I schedule it to run at 7:30AM every day?
M
"Ray Higdon" <rayhigdon@.higdonconsulting.com> wrote in message
news:e9wR7etuDHA.540@.tk2msftngp13.phx.gbl...
> If your log naturally grows 3gb a day you should (1) not shrink it and (2)
> possibly schedule more frequent log backups. If you require point in time
> recovery you should use the truncate log command, if you do not require
> point in time recovery, life is easy, set the db to simple recovery mode
and
> you won't have to worry about the tran logs.
> HTH
> --
> Ray Higdon MCSE, MCDBA, CCNA
> --
> "Maureen" <nosend2me@.hotmail.com> wrote in message
> news:u9GckFtuDHA.3140@.TK2MSFTNGP11.phx.gbl...
> > Hello all,
> >
> > I am very new to sql server as we have just replaced our enterprise
> > application (was access) Our Datafile is around 3GB and the log grows
3GB
> in
> > a day. I have auto job routines scheduled in EM and happening every
night
> > for backups etc and they are then auto (scheduled) backed up to tape.
The
> > log file is still 2.5GB in the am after the all the jobs run so I am
> > shrinking the DB every few days and the log drops to 768KB.
> >
> > My question is I see all the DBCC shrinfile commands Truncate etc... my
> > question is (pardon my ignorance) where the heck to I put these, how do
> they
> > run and how can i schedule them?
> >
> > Please be gentle with you reply.
> > M
> >
> >
>|||Ray,
I have read a little further and think I may have found the answer. Are
these commands issues as part of a SQL job? I have not even looked at this
section of EM as all I have in place currently is done as a maintenance
plan. If this is the case I'll have a look at this Friday as I do not have
access to the server from here.
M
"Maureen" <nosend2me@.hotmail.com> wrote in message
news:Obo8ODuuDHA.1196@.TK2MSFTNGP12.phx.gbl...
> Ray,
> Thanks for the note.
> I need to keep to possible "point in time" recovery. here is a normal
day.
> 12.01 AM E.M.-Sql-Maintenence Plan begins and optimizes/backup data/backup
> log report Scheduled daily
> 5:00 AM Complete Server Backup to Tape NTBACKUP Scheduled including backup
> to tape of SqlBackup
> 8:00 AM Workday begins (Tape changed from [Day1,2,3,4,5 etc]-Nightly to
> [Day1,2,3,4,5]-Daily
> Regular Work Day....
> 5:00 PM SqlBackup to tape Complete
> 5:30 PM Workday end (Tape changed from [Day1,2,3,4,5 etc]-Daily to
> [Day1,2,3,4,5]-Nightly
> I can easily add a couple more backups to tape or disk during the day. The
> server has hardware raid with 5 drives in a raid 5 (data is on these
> spmdles) PLUS 2 drives raid 10 for the logs. I am well covered for
potential
> failure. What I would like to know is where do I issue the Truncate Log
> Command AND how do I schedule it to run at 7:30AM every day?
> M
>
> "Ray Higdon" <rayhigdon@.higdonconsulting.com> wrote in message
> news:e9wR7etuDHA.540@.tk2msftngp13.phx.gbl...
> > If your log naturally grows 3gb a day you should (1) not shrink it and
(2)
> > possibly schedule more frequent log backups. If you require point in
time
> > recovery you should use the truncate log command, if you do not require
> > point in time recovery, life is easy, set the db to simple recovery mode
> and
> > you won't have to worry about the tran logs.
> >
> > HTH
> >
> > --
> > Ray Higdon MCSE, MCDBA, CCNA
> > --
> > "Maureen" <nosend2me@.hotmail.com> wrote in message
> > news:u9GckFtuDHA.3140@.TK2MSFTNGP11.phx.gbl...
> > > Hello all,
> > >
> > > I am very new to sql server as we have just replaced our enterprise
> > > application (was access) Our Datafile is around 3GB and the log grows
> 3GB
> > in
> > > a day. I have auto job routines scheduled in EM and happening every
> night
> > > for backups etc and they are then auto (scheduled) backed up to tape.
> The
> > > log file is still 2.5GB in the am after the all the jobs run so I am
> > > shrinking the DB every few days and the log drops to 768KB.
> > >
> > > My question is I see all the DBCC shrinfile commands Truncate etc...
my
> > > question is (pardon my ignorance) where the heck to I put these, how
do
> > they
> > > run and how can i schedule them?
> > >
> > > Please be gentle with you reply.
> > > M
> > >
> > >
> >
> >
>|||If you need point in time recovery, you need to write "backup log"
statements, not truncate log. See BOL for details
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Maureen" <nosend2me@.hotmail.com> wrote in message
news:e8$qHKuuDHA.640@.tk2msftngp13.phx.gbl...
> Ray,
> I have read a little further and think I may have found the answer. Are
> these commands issues as part of a SQL job? I have not even looked at this
> section of EM as all I have in place currently is done as a maintenance
> plan. If this is the case I'll have a look at this Friday as I do not have
> access to the server from here.
> M
>
> "Maureen" <nosend2me@.hotmail.com> wrote in message
> news:Obo8ODuuDHA.1196@.TK2MSFTNGP12.phx.gbl...
> > Ray,
> >
> > Thanks for the note.
> >
> > I need to keep to possible "point in time" recovery. here is a normal
> day.
> >
> > 12.01 AM E.M.-Sql-Maintenence Plan begins and optimizes/backup
data/backup
> > log report Scheduled daily
> > 5:00 AM Complete Server Backup to Tape NTBACKUP Scheduled including
backup
> > to tape of SqlBackup
> > 8:00 AM Workday begins (Tape changed from [Day1,2,3,4,5 etc]-Nightly to
> > [Day1,2,3,4,5]-Daily
> > Regular Work Day....
> > 5:00 PM SqlBackup to tape Complete
> > 5:30 PM Workday end (Tape changed from [Day1,2,3,4,5 etc]-Daily to
> > [Day1,2,3,4,5]-Nightly
> >
> > I can easily add a couple more backups to tape or disk during the day.
The
> > server has hardware raid with 5 drives in a raid 5 (data is on these
> > spmdles) PLUS 2 drives raid 10 for the logs. I am well covered for
> potential
> > failure. What I would like to know is where do I issue the Truncate Log
> > Command AND how do I schedule it to run at 7:30AM every day?
> >
> > M
> >
> >
> >
> > "Ray Higdon" <rayhigdon@.higdonconsulting.com> wrote in message
> > news:e9wR7etuDHA.540@.tk2msftngp13.phx.gbl...
> > > If your log naturally grows 3gb a day you should (1) not shrink it and
> (2)
> > > possibly schedule more frequent log backups. If you require point in
> time
> > > recovery you should use the truncate log command, if you do not
require
> > > point in time recovery, life is easy, set the db to simple recovery
mode
> > and
> > > you won't have to worry about the tran logs.
> > >
> > > HTH
> > >
> > > --
> > > Ray Higdon MCSE, MCDBA, CCNA
> > > --
> > > "Maureen" <nosend2me@.hotmail.com> wrote in message
> > > news:u9GckFtuDHA.3140@.TK2MSFTNGP11.phx.gbl...
> > > > Hello all,
> > > >
> > > > I am very new to sql server as we have just replaced our enterprise
> > > > application (was access) Our Datafile is around 3GB and the log
grows
> > 3GB
> > > in
> > > > a day. I have auto job routines scheduled in EM and happening every
> > night
> > > > for backups etc and they are then auto (scheduled) backed up to
tape.
> > The
> > > > log file is still 2.5GB in the am after the all the jobs run so I am
> > > > shrinking the DB every few days and the log drops to 768KB.
> > > >
> > > > My question is I see all the DBCC shrinfile commands Truncate etc...
> my
> > > > question is (pardon my ignorance) where the heck to I put these, how
> do
> > > they
> > > > run and how can i schedule them?
> > > >
> > > > Please be gentle with you reply.
> > > > M
> > > >
> > > >
> > >
> > >
> >
> >
>

Schedule export from sql database to access

Hi
Can someone explain/help how can I create a schedule at SQL Server 2000 that
exports at X time of the day a SQL database into a access database without
exporting the views that the SQL database has.
Thanks
[]
Ricky
Take a look at the Import/Export wizard and sql agent in BooksOnLine.
Andrew J. Kelly SQL MVP
"Ricky" <newsgroupsmail@.gmail.com> wrote in message
news:OTItwJhVHHA.4872@.TK2MSFTNGP03.phx.gbl...
> Hi
> Can someone explain/help how can I create a schedule at SQL Server 2000
> that
> exports at X time of the day a SQL database into a access database without
> exporting the views that the SQL database has.
>
> Thanks
> []
> Ricky
>
>

Schedule export from sql database to access

Hi
Can someone explain/help how can I create a schedule at SQL Server 2000 that
exports at X time of the day a SQL database into a access database without
exporting the views that the SQL database has.
Thanks
[]
RickyTake a look at the Import/Export wizard and sql agent in BooksOnLine.
Andrew J. Kelly SQL MVP
"Ricky" <newsgroupsmail@.gmail.com> wrote in message
news:OTItwJhVHHA.4872@.TK2MSFTNGP03.phx.gbl...
> Hi
> Can someone explain/help how can I create a schedule at SQL Server 2000
> that
> exports at X time of the day a SQL database into a access database without
> exporting the views that the SQL database has.
>
> Thanks
> []
> Ricky
>
>

Schedule export from sql database to access

Hi
Can someone explain/help how can I create a schedule at SQL Server 2000 that
exports at X time of the day a SQL database into a access database without
exporting the views that the SQL database has.
Thanks
[]
RickyTake a look at the Import/Export wizard and sql agent in BooksOnLine.
--
Andrew J. Kelly SQL MVP
"Ricky" <newsgroupsmail@.gmail.com> wrote in message
news:OTItwJhVHHA.4872@.TK2MSFTNGP03.phx.gbl...
> Hi
> Can someone explain/help how can I create a schedule at SQL Server 2000
> that
> exports at X time of the day a SQL database into a access database without
> exporting the views that the SQL database has.
>
> Thanks
> []
> Ricky
>
>