Sunday, March 25, 2012
Database Backups
the following error message.
Execution failed. See the maintenance plan and SQL Server Agent job history
logs for details.
Job Backup.Subplan_1 was suspended. (SqlManagerUI)
My current operating system structure is this.
OS installed on C: and I have SQL installed on D:
I will appreciate any help on this matter.
Chris Holden
Chris
We need more info about your backup strategy. What did you create?
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:4A06B2C6-D95C-4892-A070-B326C12623D6@.microsoft.com...
> Im trying to backup all my database in SQL server 2005, but I keep
> getting
> the following error message.
> Execution failed. See the maintenance plan and SQL Server Agent job
> history
> logs for details.
> Job Backup.Subplan_1 was suspended. (SqlManagerUI)
> My current operating system structure is this.
> OS installed on C: and I have SQL installed on D:
> I will appreciate any help on this matter.
> --
> Chris Holden
sql
Database Backups
g
the following error message.
Execution failed. See the maintenance plan and SQL Server Agent job history
logs for details.
Job Backup.Subplan_1 was suspended. (SqlManagerUI)
My current operating system structure is this.
OS installed on C: and I have SQL installed on D:
I will appreciate any help on this matter.
Chris HoldenChris
We need more info about your backup strategy. What did you create?
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:4A06B2C6-D95C-4892-A070-B326C12623D6@.microsoft.com...
> Im trying to backup all my database in SQL server 2005, but I keep
> getting
> the following error message.
> Execution failed. See the maintenance plan and SQL Server Agent job
> history
> logs for details.
> Job Backup.Subplan_1 was suspended. (SqlManagerUI)
> My current operating system structure is this.
> OS installed on C: and I have SQL installed on D:
> I will appreciate any help on this matter.
> --
> Chris Holden
Database Backups
the following error message.
Execution failed. See the maintenance plan and SQL Server Agent job history
logs for details.
Job Backup.Subplan_1 was suspended. (SqlManagerUI)
My current operating system structure is this.
OS installed on C: and I have SQL installed on D:
I will appreciate any help on this matter.
--
Chris HoldenChris
We need more info about your backup strategy. What did you create?
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:4A06B2C6-D95C-4892-A070-B326C12623D6@.microsoft.com...
> I?m trying to backup all my database in SQL server 2005, but I keep
> getting
> the following error message.
> Execution failed. See the maintenance plan and SQL Server Agent job
> history
> logs for details.
> Job Backup.Subplan_1 was suspended. (SqlManagerUI)
> My current operating system structure is this.
> OS installed on C: and I have SQL installed on D:
> I will appreciate any help on this matter.
> --
> Chris Holden
Wednesday, March 21, 2012
Database Backup Failed with Timeout Expired from Enterprise Manager
Hi,
I have SQL Server 2000 with SP4. When we take backup from Enterprise manager its fails with error "timeout expired". But when we take backup from query analyzer it works.
It seems that through enterprise manager 30 sec is the non configurable timeout parameter set. Checked sysprocesses table during backup but there was no blocking during that time at least for that spid.
Is there a way to find out which process is blocking the database backup? Also, what are the possible scenarios where database backup can be blocked.
Thanks,
Ramesh
Hi rksingh,
When you run a backup or restore from the Enterprise manager, the querytimeout does not apply.
It timesout because the process is being blocked by another process.
It could be blocked by BACKUP LOG or ALTER DATABASE commands.
Open another QA session and use SP_WHO2 ACTIVE to check for blocking.
regards
Jag
|||Check SQL error log what error it is recorded...all backup info recorded in sql error log.
|||Problem is resolved with the help of Microsoft PSS.
There is query time out setting for SQL Server 2000 Enterprise Manager which was set to 100 in my case whereas set to 0 on other servers.
To change settings
1. Open enterprise Manager.
2. Click on Tools - > Options
3. Goto Advanced Tab
3. Under connection setting change the Query time out value.
Thanks,
Ramesh
Database Backup Failed with Timeout Expired from Enterprise Manager
Hi,
I have SQL Server 2000 with SP4. When we take backup from Enterprise manager its fails with error "timeout expired". But when we take backup from query analyzer it works.
It seems that through enterprise manager 30 sec is the non configurable timeout parameter set. Checked sysprocesses table during backup but there was no blocking during that time at least for that spid.
Is there a way to find out which process is blocking the database backup? Also, what are the possible scenarios where database backup can be blocked.
Thanks,
Ramesh
Hi rksingh,
When you run a backup or restore from the Enterprise manager, the querytimeout does not apply.
It timesout because the process is being blocked by another process.
It could be blocked by BACKUP LOG or ALTER DATABASE commands.
Open another QA session and use SP_WHO2 ACTIVE to check for blocking.
regards
Jag
|||Check SQL error log what error it is recorded...all backup info recorded in sql error log.
|||Problem is resolved with the help of Microsoft PSS.
There is query time out setting for SQL Server 2000 Enterprise Manager which was set to 100 in my case whereas set to 0 on other servers.
To change settings
1. Open enterprise Manager.
2. Click on Tools - > Options
3. Goto Advanced Tab
3. Under connection setting change the Query time out value.
Thanks,
Ramesh
sqlMonday, March 19, 2012
Database backup
In EM, right click Northwind, select All Tasks, Backup a database...
Enter Description, select complete backup, Add a destination to a location,
set the shedule.
But there is not backup after the schedule time.
Anything I missed ?Check inside Management, SQL Agent, Jobs and see if there is a n error
associated with the job
"Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
news:uTPM1$rpEHA.3300@.TK2MSFTNGP12.phx.gbl...
>I tried to backup a database but failed:
> In EM, right click Northwind, select All Tasks, Backup a database...
> Enter Description, select complete backup, Add a destination to a
> location,
> set the shedule.
> But there is not backup after the schedule time.
> Anything I missed ?
>
>|||Ah, may be the SQL Server Agent has not started.
"Mary Bray" <no@.spam.com> wrote in message
news:%231pAMcspEHA.2764@.TK2MSFTNGP11.phx.gbl...
> Check inside Management, SQL Agent, Jobs and see if there is a n error
> associated with the job
> "Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
> news:uTPM1$rpEHA.3300@.TK2MSFTNGP12.phx.gbl...
> >I tried to backup a database but failed:
> >
> > In EM, right click Northwind, select All Tasks, Backup a database...
> > Enter Description, select complete backup, Add a destination to a
> > location,
> > set the shedule.
> >
> > But there is not backup after the schedule time.
> >
> > Anything I missed ?
> >
> >
> >
>
Database attach failed
*.mdb and *.ldf) from a 'reputable' source on the net. But when I
attempted to attach it to my sql server 2000 with SP3 with EM, it
failed complaining "Could not find row in sysindexes for database ID
10, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes."
Then, I attempted to command line attach (thought it may have some
option...), same outcome. Then, ran a search on this NG, and found
the following thread, the question is, MS most likely would not
support something like this, so now what? Also thought about
manually adding a row to sysindexes table to 'fool the attach process'
but after looking at some sample data in this table, I don't think
it's a good idea to try, what can I do? Thanks.
http://groups.google.com/group/comp...3bee910fa30aa9atime management (tatata9999@.gmail.com) writes:
Quote:
Originally Posted by
Here's the scoop, I got a generic-purpose database (in the form of
*.mdb and *.ldf) from a 'reputable' source on the net. But when I
attempted to attach it to my sql server 2000 with SP3 with EM, it
failed complaining "Could not find row in sysindexes for database ID
10, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes."
That message appears familiar. I seem to recall that is what happens
if you try to attach an SQL 2005 database on SQL 2000. As far as
SQL 2000 that is a database that is alien, and for which it cannot
really have any graceful handling off.
Quote:
Originally Posted by
Then, I attempted to command line attach (thought it may have some
option...), same outcome. Then, ran a search on this NG, and found
the following thread,
Which is from 1998, and applies to really old versions of SQL Server.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||On Nov 19, 5:32 pm, Erland Sommarskog <esq...@.sommarskog.sewrote:
Quote:
Originally Posted by
time management (tatata9...@.gmail.com) writes:
Quote:
Originally Posted by
Here's the scoop, I got a generic-purpose database (in the form of
*.mdb and *.ldf) from a 'reputable' source on the net. But when I
attempted to attach it to my sql server 2000 with SP3 with EM, it
failed complaining "Could not find row in sysindexes for database ID
10, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes."
>
That message appears familiar. I seem to recall that is what happens
if you try to attach an SQL 2005 database on SQL 2000. As far as
SQL 2000 that is a database that is alien, and for which it cannot
really have any graceful handling off.
>
Quote:
Originally Posted by
Then, I attempted to command line attach (thought it may have some
option...), same outcome. Then, ran a search on this NG, and found
the following thread,
>
Which is from 1998, and applies to really old versions of SQL Server.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Thanks for the follow-up, Erland. I tried to attach it with sql
server 2005 as well, the restored db seemed weired with "D:\aName
\blakdsm\blad..", empty, not workable. Now, suppose I can get a
clean/good copy for server 2005, what are the chances of success of
using DUMB database then BACKUP or LOAD back into server 2000? These
two boxes are not connected and they can't.
Don|||time management (tatata9999@.gmail.com) writes:
Quote:
Originally Posted by
Thanks for the follow-up, Erland. I tried to attach it with sql
server 2005 as well, the restored db seemed weired with "D:\aName
\blakdsm\blad..", empty, not workable. Now, suppose I can get a
clean/good copy for server 2005, what are the chances of success of
using DUMB database then BACKUP or LOAD back into server 2000? These
two boxes are not connected and they can't.
If you need to move a database from SQL 2005 to SQL 2000 you need to
create from scripts and copy data to file with bulk copy. If the database
uses features that do not exist in SQL 2000, you will have to make some
compromises.
You cannot restore a backup from SQL 2005 on SQL 2000. For quite obvious
reasons: there are features in SQl 2005 for which SQL 2000 is not prepared.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||On Nov 20, 5:31 pm, Erland Sommarskog <esq...@.sommarskog.sewrote:
Quote:
Originally Posted by
time management (tatata9...@.gmail.com) writes:
Quote:
Originally Posted by
Thanks for the follow-up, Erland. I tried to attach it with sql
server 2005 as well, the restored db seemed weired with "D:\aName
\blakdsm\blad..", empty, not workable. Now, suppose I can get a
clean/good copy for server 2005, what are the chances of success of
using DUMB database then BACKUP or LOAD back into server 2000? These
two boxes are not connected and they can't.
>
If you need to move a database from SQL 2005 to SQL 2000 you need to
create from scripts and copy data to file with bulk copy. If the database
uses features that do not exist in SQL 2000, you will have to make some
compromises.
>
You cannot restore a backup from SQL 2005 on SQL 2000. For quite obvious
reasons: there are features in SQl 2005 for which SQL 2000 is not prepared.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Thanks, Erland, bcp is clumsy or because I'm not an expert of it :)
Viable options for the task all seem to consume quite a bit of time
but hey got to do the job. Once again I appreciate it.
Don