Showing posts with label point. Show all posts
Showing posts with label point. Show all posts

Tuesday, March 27, 2012

backing up sql 2000

I just inherited a couple servers that use Sql 2000 on
them, can u point me where i can find detailed
information on how to backup, or do routine maintenance
on sql 2000?
thanks
rob davisBooks Online (BOL) is always a good place to start. This is installed as pa
rt of the SQL Server Client Tools. It has also been recently updated and ca
n be downloaded for free from -
http://www.microsoft.com/downloads/...&displaylang=en
Search for the word "backup" and also Database Maintenance Plan Wizard as pl
aces to start.
HTH,
James|||thank you
quote:

>--Original Message--
>Books Online (BOL) is always a good place to start.

This is installed as part of the SQL Server Client
Tools. It has also been recently updated and can be
downloaded for free from -
quote:

>http://www.microsoft.com/downloads/details.aspx?

FamilyId=A6F79CB1-A420-445F-8A4B-
BD77A7DA194B&displaylang=en
quote:

>Search for the word "backup" and also Database

Maintenance Plan Wizard as places to start.
quote:

>HTH,
>James
>.
>
sql

backing up sql 2000

I just inherited a couple servers that use Sql 2000 on
them, can u point me where i can find detailed
information on how to backup, or do routine maintenance
on sql 2000?
thanks
rob davisBooks Online (BOL) is always a good place to start. This is installed as part of the SQL Server Client Tools. It has also been recently updated and can be downloaded for free from
http://www.microsoft.com/downloads/details.aspx?FamilyId=A6F79CB1-A420-445F-8A4B-BD77A7DA194B&displaylang=e
Search for the word "backup" and also Database Maintenance Plan Wizard as places to start
HTH
James|||thank you
>--Original Message--
>Books Online (BOL) is always a good place to start.
This is installed as part of the SQL Server Client
Tools. It has also been recently updated and can be
downloaded for free from -
>http://www.microsoft.com/downloads/details.aspx?
FamilyId=A6F79CB1-A420-445F-8A4B-
BD77A7DA194B&displaylang=en
>Search for the word "backup" and also Database
Maintenance Plan Wizard as places to start.
>HTH,
>James
>.
>

Backing up MS SQL?

Hi

I'm hoping that some could point me in the right direction for "best
practice" in:

1) securely backing up a complete sql7 and 2000 server containing many
databases.

2) backing up an individual database

3) Securing the transaction on the hour as a mile stone to return to in the
event of error or system failure.

Thanks

MarkHi

The first place to start is Books Online:
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adm
insql.chm::/ad_bkprst_9zcj.htm

John

"mark" <kardtech@.on.aibn.com> wrote in message
news:uFRIb.46$b06.7@.newsfep3-gui.server.ntli.net...
> Hi
> I'm hoping that some could point me in the right direction for "best
> practice" in:
> 1) securely backing up a complete sql7 and 2000 server containing many
> databases.
> 2) backing up an individual database
> 3) Securing the transaction on the hour as a mile stone to return to in
the
> event of error or system failure.
> Thanks
> Mark|||Standard Answer then. Thanks for NO help

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:b8UIb.3645$PB3.32098570@.news-text.cableinet.net...
> Hi
> The first place to start is Books Online:
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adm
> insql.chm::/ad_bkprst_9zcj.htm
> John
> "mark" <kardtech@.on.aibn.com> wrote in message
> news:uFRIb.46$b06.7@.newsfep3-gui.server.ntli.net...
> > Hi
> > I'm hoping that some could point me in the right direction for "best
> > practice" in:
> > 1) securely backing up a complete sql7 and 2000 server containing many
> > databases.
> > 2) backing up an individual database
> > 3) Securing the transaction on the hour as a mile stone to return to in
> the
> > event of error or system failure.
> > Thanks
> > Mark|||"mark" <kardtech@.on.aibn.com> wrote in message
news:iuUIb.85$b06.63@.newsfep3-gui.server.ntli.net...
> Standard Answer then. Thanks for NO help

What about the standard answer don't you like?

With more detail:

1) For backing up the actual installation, I generally find it easier to
reinstall the application if need be.

2) Backing up individual databases, look into creating a maintenance plan.
Or roll your own and use backup database as appropriate.

3) use BACKUP LOG on the required databases.

I'd also recommend getting a book on high availabilibity. The one from MS
press is quite good.

>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:b8UIb.3645$PB3.32098570@.news-text.cableinet.net...
> > Hi
> > The first place to start is Books Online:
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adm
> > insql.chm::/ad_bkprst_9zcj.htm
> > John
> > "mark" <kardtech@.on.aibn.com> wrote in message
> > news:uFRIb.46$b06.7@.newsfep3-gui.server.ntli.net...
> > > Hi
> > > > I'm hoping that some could point me in the right direction for "best
> > > practice" in:
> > > > 1) securely backing up a complete sql7 and 2000 server containing many
> > > databases.
> > > > 2) backing up an individual database
> > > > 3) Securing the transaction on the hour as a mile stone to return to
in
> > the
> > > event of error or system failure.
> > > > Thanks
> > > > Mark
> >|||Thankyou

"Greg D. Moore (Strider)" <mooregr@.greenms.com> wrote in message
news:7oWIb.34408$q55.5924@.twister.nyroc.rr.com...
> "mark" <kardtech@.on.aibn.com> wrote in message
> news:iuUIb.85$b06.63@.newsfep3-gui.server.ntli.net...
> > Standard Answer then. Thanks for NO help
> What about the standard answer don't you like?
> With more detail:
> 1) For backing up the actual installation, I generally find it easier to
> reinstall the application if need be.
> 2) Backing up individual databases, look into creating a maintenance plan.
> Or roll your own and use backup database as appropriate.
> 3) use BACKUP LOG on the required databases.
> I'd also recommend getting a book on high availabilibity. The one from MS
> press is quite good.
>
> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > news:b8UIb.3645$PB3.32098570@.news-text.cableinet.net...
> > > Hi
> > > > The first place to start is Books Online:
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adm
> > > insql.chm::/ad_bkprst_9zcj.htm
> > > > John
> > > > "mark" <kardtech@.on.aibn.com> wrote in message
> > > news:uFRIb.46$b06.7@.newsfep3-gui.server.ntli.net...
> > > > Hi
> > > > > > I'm hoping that some could point me in the right direction for "best
> > > > practice" in:
> > > > > > 1) securely backing up a complete sql7 and 2000 server containing
many
> > > > databases.
> > > > > > 2) backing up an individual database
> > > > > > 3) Securing the transaction on the hour as a mile stone to return to
> in
> > > the
> > > > event of error or system failure.
> > > > > > Thanks
> > > > > > Mark
> > > > > >|||"mark" <kardtech@.on.aibn.com> wrote in message
news:uFRIb.46$b06.7@.newsfep3-gui.server.ntli.net...
> Hi
> I'm hoping that some could point me in the right direction for "best
> practice" in:
> 1) securely backing up a complete sql7 and 2000 server containing many
> databases.

1.1) Schedule a complete backup of all production databases and include
the system databases master, msdb, model at some appropriate
timeslot.
To do this for the first time, try using Enterprise Manager, select
the
"schedule" option and then examine the TSQL code in the scheduled
task. Modify the schedule times to suit your operations.

1.2) Take a copy of the backup files offsite.

> 2) backing up an individual database

As above, so here below ... much like the
Hermetic tradition.

> 3) Securing the transaction on the hour as a mile stone to return to in
the
> event of error or system failure.

You will need to examine the differential backup strategies available
and gauge the best approach for this method in relation to your data.

The M$ documentation is not too bad at all if you are prepared to
go and experiment and learn by practice the operations therein
documented, and I'd be surprised if step by step instructions on
all of the above are not clearly established within it.

Pete Brown
Falls Creek
OZ

Tuesday, March 20, 2012

backing up

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

backing up

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

backing up

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

Sunday, March 11, 2012

AXSCPHST.DLL error in SQL Agent Error Log

I'm getting the following errors in my SQL Server Agent Error Logs:
[000] Unable to locate entry point for AXSCPHST.DLL in The specified module
could not be found (reason: ?)
[125] Subsystem 'ActiveScripting' could not be loaded (reason:
Initialization failed [subsystem code 0])
I'm running SQL Server 2000 SP4 on Windows Server 2003.
Any clue as to why these errors are appearing and how to eliminate them?
All my DTS tasks with scripts seem to be working inspite of the errors.
Scott
I am having the same problem, do you have a solution?
|||Check the path for the String Value in this registry key.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsof t SQL
Server\80\Tools\ClientSetup]
"SQLPath"="C:\\Program Files\\Microsoft SQL Server\\80\\Tools"
Occasionally it will be missing the "s" at the end. Microsoft says that it
happens during the upgrade from MSDE to full SQL.

AXSCPHST.DLL error in SQL Agent Error Log

I'm getting the following errors in my SQL Server Agent Error Logs:
[000] Unable to locate entry point for AXSCPHST.DLL in The specified mod
ule
could not be found (reason: ')
[125] Subsystem 'ActiveScripting' could not be loaded (reason:
Initialization failed [subsystem code 0])
I'm running SQL Server 2000 SP4 on Windows Server 2003.
Any clue as to why these errors are appearing and how to eliminate them?
All my DTS tasks with scripts seem to be working inspite of the errors.
ScottI am having the same problem, do you have a solution?|||Check the path for the String Value in this registry key.
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\Microsoft SQL
Server\80\Tools\ClientSetup]
"SQLPath"="C:\\Program Files\\Microsoft SQL Server\\80\\Tools"
Occasionally it will be missing the "s" at the end. Microsoft says that it
happens during the upgrade from MSDE to full SQL.