Backing up SQL Express

Hi everyone,
Can anyone tell me if tehre is a tool or some preffered means of backing
up SQL Express on a schedule.
I typically use SQL Agent to schedule backup jobs but SQL Express doesnt
seem to come with that.
Many thanks
Simon
What about doing a AT job within Windows with specifying something like
this as the command:
SQLCMD.EXE -S .\SQLExpress -Q -U Username -P Password -Q "BACKUP
DATABASE..."
HTH; Jens Suessmeyer.

Backing up SQL Express

Hi everyone,
Can anyone tell me if tehre is a tool or some preffered means of backing
up SQL Express on a schedule.
I typically use SQL Agent to schedule backup jobs but SQL Express doesnt
seem to come with that.
Many thanks
SimonWhat about doing a AT job within Windows with specifying something like
this as the command:
SQLCMD.EXE -S .\SQLExpress -Q -U Username -P Password -Q "BACKUP
DATABASE..."
HTH; Jens Suessmeyer.

Backing up SQL Express

Hi everyone,
Can anyone tell me if tehre is a tool or some preffered means of backing
up SQL Express on a schedule.
I typically use SQL Agent to schedule backup jobs but SQL Express doesnt
seem to come with that.
Many thanks
SimonWhat about doing a AT job within Windows with specifying something like
this as the command:
SQLCMD.EXE -S .\SQLExpress -Q -U Username -P Password -Q "BACKUP
DATABASE..."
HTH; Jens Suessmeyer.

Back to basic question

And forgive me for asking this over and over again..
My distribution agent states " 1 transaction with 100,000 commands were
delivered "
My default profile has the Commitbatchsize as 100 and CommitBatchThreshold
as 1000.
So in this case, how does distribution agent work ? Does it read/buffer all
the 100,000 commands from msrepl_commands since its 1 transaction before it
fires them off to the subscriber ?
And how does the default profile play a role here ? If it does read/buffers
100,000 commands before it pushes it across, does it commit 1000 commands at
a time on the subscriber due to the commitbatchthreshold ? And if if fails
halfway saying after inserting 50,000 commands, does it just rollback the
last few commands that were not committed or does it rollback all 50,000
commands ?
Using transactional replication
Hassan,
why not do a test of these parameters? If you have Lumigent's logreader, you
can use it on the the live subscriber transaction log to verify the
behaviour for yourself. Create and publish a 100 record test table on the
publisher, modify the Commitbatchsize and CommitBatchThreshold parameters
and make an update of the 100 records. There's no need for an explicit
transaction, just an update of the table that affects all rows is ordinarily
logged as 100 updates with a begin and commit surrounding it. Start the
distribution agent then check Lumigent's output. The same setup can be used
for interrupted commands.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

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.

Autostart Sql Server Agent

In sql server 2005 how do you change the settings for autostarting the sqlserver agent when the OS starts. For eg in sql server 2000 when you click the server properties you can cha nge it there but what about sql server 2005?right click My Computer and then Manage. Once there, expand Services and Applications, then click on Services. From there, you can find the SQL Server Agent() service, go to properties, and make the startup type Automatic.|||

Hello Tim,

Thanks for this info, but i wanted to know how could you do it from management console. like how you can do it from Enterprise manager in SQL server 2000. This will help my cause but just for better knowledge i wanted to know.

|||

SQL Server Configuration Manager is the tool to be used in sql server 2005 for any administration of Services, protocols etc... You can find it Programs --MSSQLServer 2005 --Configuration Tool.

Right click on any service and do whatever setting you want there.

ref : http://msdn2.microsoft.com/en-us/library/ms174212.aspx

Madhu

|||Thanks a lot Madhu. I appreciate that.|||

Make sure you mark it as "Answered"

yes, SQL Configuration Tool would be the place to configure Service Start type of services

Autostart MS Agent on Win98/Me

Hello,
does anyone know how I could autostart the MSAgent on Win98/Me with a
named instance.
I try with
scm.exe -Action 1 -Service SQLAgent$$" & str_InstanceName
where str_InstanceName is the name of the MSDE Instance.
The password is correct (I exported the crypted password from a computer
with Entreprise manager and the agent start with WinNT...
It can also start manually.
On Winnt, 2K and XP, all is fine, on Win98/Me, I receive the message
Service operation has been completed successfully but the agent did not
start. I can manually start the agent with the MSDE service manager, but
if my custommer forget it then he has no automatic backup of his database.
Thank you
Marc Allard
Allcomp
If you really rely on SQL Server Agent being started and you have not a lot
of control over the machine, start SQL Server Agent from within SQL Server:
-- Create a procedure to start SQL Server Agent
USE master
GO
CREATE PROC usp_start_sqlserveragent
AS
EXEC master..xp_cmdshell 'net start SQLServerAgent'
GO
-- Mark stored procedure to run on SQL Server start
EXEC sp_procoption 'usp_start_sqlserveragent', 'startup', 'true'
Jacco Schalkwijk
SQL Server MVP
"Allcomp" <marc@.nospam.allcomp.be> wrote in message
news:41e279f2$0$2676$ba620e4c@.news.skynet.be...
> Hello,
> does anyone know how I could autostart the MSAgent on Win98/Me with a
> named instance.
> I try with
> scm.exe -Action 1 -Service SQLAgent$$" & str_InstanceName
> where str_InstanceName is the name of the MSDE Instance.
> The password is correct (I exported the crypted password from a computer
> with Entreprise manager and the agent start with WinNT...
> It can also start manually.
> On Winnt, 2K and XP, all is fine, on Win98/Me, I receive the message
> Service operation has been completed successfully but the agent did not
> start. I can manually start the agent with the MSDE service manager, but
> if my custommer forget it then he has no automatic backup of his database.
>
> Thank you
> Marc Allard
> Allcomp
|||That will never work on Windows 9x based OS's since there is no concept of a
real service which gets started with NET START. Only Windows NT based OS's
(and OS/2) have NET START.
You can use SCM.EXE instead
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid > wrote
in message news:eU1Ed3y9EHA.2876@.TK2MSFTNGP12.phx.gbl...
> If you really rely on SQL Server Agent being started and you have not a
> lot of control over the machine, start SQL Server Agent from within SQL
> Server:
> -- Create a procedure to start SQL Server Agent
> USE master
> GO
> CREATE PROC usp_start_sqlserveragent
> AS
> EXEC master..xp_cmdshell 'net start SQLServerAgent'
> GO
> -- Mark stored procedure to run on SQL Server start
> EXEC sp_procoption 'usp_start_sqlserveragent', 'startup', 'true'
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Allcomp" <marc@.nospam.allcomp.be> wrote in message
> news:41e279f2$0$2676$ba620e4c@.news.skynet.be...
>
|||Right. Seems Win9x is a bit too long ago for me. I better not answer any
more questions that involve Win 9x
Jacco Schalkwijk
SQL Server MVP
"Gert E.R. Drapers" <GertD@.SQLDev.Net> wrote in message
news:eyuMfi09EHA.1544@.TK2MSFTNGP11.phx.gbl...
> That will never work on Windows 9x based OS's since there is no concept of
> a real service which gets started with NET START. Only Windows NT based
> OS's (and OS/2) have NET START.
> You can use SCM.EXE instead
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
> Copyright SQLDev.Net 1991-2004 All rights reserved.
> "Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid >
> wrote in message news:eU1Ed3y9EHA.2876@.TK2MSFTNGP12.phx.gbl...
>
|||Hello,
Thank you for your answers, but I already try to start the agent with
scm, but it doesn't start. If I start it manually with SQL Server
Service Manager, then it is working.
Is there something to do an automatic backup without the agent?
Thank you
Marc Allard
Allcomp
Jacco Schalkwijk wrote:
> Right. Seems Win9x is a bit too long ago for me. I better not answer any
> more questions that involve Win 9x
>