View Complete Post
We have a database schema with a period in it's name. This is valid as per
http://msdn.microsoft.com/en-us/library/aa224033(SQL.80).aspx. When we create a maintenance plan to update statistics it will succeed if the object property is set to 'Tables and Views'.
If this is set to 'Table' it will fail.
Steps to Reproduce
CREATE SCHEMA [Windows.EventLog] AUTHORIZATION [dbo]
CREATE TABLE [Windows.EventLog].[Computer](
[ComputerId] [smallint] IDENTITY(1,1) NOT NULL,
[ComputerName] [varchar](255) NOT NULL,
CONSTRAINT [PK_Computer] PRIMARY KEY CLUSTERED ([ComputerId] ASC)
) ON [PRIMARY]
I am running a maintenance plan (Sql Server 2008 Enterprise) every night at mid-night. All the plan entails is doing a full backup of one database (about a 3GB database). We are getting timeouts on our site at exactly that point when the database is being backed up and they last up to 20min. I was under the impression that doing backups this way does not take the db down? Or am I wrong about this?
Has anyone else experienced this and if so what steps did you take to rectify it? Sorry if I have not provided other information, just let me know and I will give it to you.
I have a maintenance plan built on a SQL Server 2005 instance that rebuilds indexes, rebuilds statistics, checks for database integrity, performs a maintenance cleanup, and performs a history cleanup. This job runs once per week.
In the "Reporting and Logging" section I have the following options:
- Generate a text file report is checked
- Create a new file is selected
- A valid destination folder is identified
- Send report to an email recipient is checked
- A valid agent operator is selected
- Log extended information is checked
The job seems to complete successfully and a report is created and emailed, but the only information in the report is as follows:
Quest SLSSQLMaint Utility.
Logging on to SQL Server 'DEVSQL01' with Windows Authentication
Logged on to SQL Server 'DEVSQL01'
 Delete old text report files...
 Execution Time: 0 hrs, 0 mins, 0 secs.
 Send DBMail or SendMail report file....
 Execution Time: 0 hrs, 0 mins, 1 secs.
End of maintenance plan 'DB Maintenance Plan (No Backups) [DB Maintenance]' on 9/29/2010 8:40:49 PM (Success)
C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\Binn\slssqlmaint.exe Process Exit Code: 0 (Success)
Where is the information about the rest of the maintenance plan?&nbs
We are running SQL 2005 Standard Edition SP3 on a single server. Anytime I attempt to save a maintenance plan, I get a "Class Not Registered" error. I also got this when attempting to edit or delete Maintenance Plans created previously, when this functionality
was working. On this server there is a SQL Server 2000 as the default instance, and the SQL Server 2005 is a named instance.
Looking at other posts everywhere, installing SP2 or SP3 can break the ability to create or edit Maintenance Plans. I can confirm that SSIS is running and that I can now connect to Integration Services in Mainagement Studio (and I was able to delete my old
plans in the Integration Services). There was a problem with this which was cured by manually registering dts.dll and msDtsSrvrUtil.dll in the DTS/Binn folder. I wonder if I need to manually register any more DLLs.
We are trying to create and edit a Backup Script in Maintenance plans. It is throwing the following error. Please help.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'msddsp, Version=188.8.131.52,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the
File name: 'msddsp, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
sender, ComponentChangedEventArgs chevent)
at System.ComponentModel.Design.ComponentChangedEventHandler.Invoke(Object sender,
ntChanged(Object component, MemberDescriptor member, Object oldValue, Object newValue)
ed(Object component, MemberDescriptor member, Obje
One of my customer db there is one maintenance plan(full backup / Transaction log backup ) schedule time for the full backup is 11:00:00 PM daily and for transaction log backup 12.30 pm Sunday to Friday ,I
checked the job created by maintenance plan there also schedule time is same but when i check the history of the job it shows it happened at 7:00:00 pm every day. why there is time difference ?
Product version is 8.00.2055(SP4)
i checked the MSDB.dbo.sysjobschedules table and the next_run_date is not updated properly,it is showing yesterday 11:00:00 pm
please help me to resolve this issue