February 20, 2009 at 8:06 am
I find extended store procs in all my servers except one why is it so?
I was looking ofr this proc " master.dbo.xp_backup_database"
February 20, 2009 at 8:11 am
Because it's not a standard extended proc. Probably created by a 3rd party backup tool.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 20, 2009 at 8:14 am
Ok now i know. May be LiteSpeed is not installed there on that server. Can i just migrate those procs into my new server and perform by backups as if ido with other servers using LiteSpeed.
If so what is the eacy way to migrate all extended procs in one shot.
thanks
February 20, 2009 at 8:19 am
Mike Levan (2/20/2009)
Can i just migrate those procs into my new server and perform by backups as if ido with other servers using LiteSpeed.
No.
Install LiteSpeed there if you need to, make sure you have enough licences to do so.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 20, 2009 at 8:20 am
Do you think if i migrate those it will not work??
February 20, 2009 at 8:28 am
Mike Levan (2/20/2009)
Do you think if i migrate those it will not work??
How were you planning to migrate, seeing as extended procedures are not SQL code?
What's wrong with installing LiteSpeed on the other server?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 20, 2009 at 8:50 am
Do you have these commands? xp_restore_database ,xp_restore_log and xp_sqllitespeed_version?
If you have these stored procs, xp_backup_database might have got deleted , to get in that extended proc
use this command
use master
go
exec sp_addextendedproc xp_backup_database ,'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xpsls.dll'
By default this is the place where all sql server dll's and executable are located.
February 20, 2009 at 8:59 am
If i cant use those procs then i may have to do regular maintanance plan as i dont have litespeed liscences anymore.
If my sql server is running under local account without any windows service account can i be still able to backup databaase over network drive?
February 20, 2009 at 9:02 am
If my sql server is running under local account without any windows service account can i be still able to backup databaase over network drive?
NO
* Noel
February 20, 2009 at 9:08 am
Mike Levan (2/20/2009)
If i cant use those procs then i may have to do regular maintanance plan as i dont have litespeed liscences anymore.
If you don't have litespeed licences then you can't use litespeed. Any part of litespeed. That includes trying to copy procs to dodge licensing limitations
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 20, 2009 at 11:17 am
If my sql server is running under local account without any windows service account can i be still able to backup databaase over network drive?
is there any work around to backup on a network drive, i tried giving UNC name but didnt work.
thanks
February 20, 2009 at 11:29 am
Not really. The backup runs as the service account, so it needs rights to get across the network.
Note that network backups are not recommended. If there's any network hiccup, the backup will fail. File copies retry a bunch, the SQL backup will not.
Back up locally, copy to a remote location with a script.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply