I have just done an in-place upgrade of a sql2000 SP4 instance to SQL 2005. After the upgrade I applied SP2 and cumulative hotfix rollup 4, plus the SQL 2000 DTS designer components for backward compatibility.
all went well with the upgrade.
I then migrated the maintenance plan for the system databases to 2005 SSIS version, and find it includes tempdb! This causes the jobs to fail.
Have I come across anther maintenance plan issue or have I done something wrong? Should I have applied GDR2 before the cumulative roll up?
In maint. plan when reorg is selected for a user db, it will also work on sys tables in user database. Is it a good thing to do ? How do I avoid sys tables in a user database not to be part of maint optimization plan ? Some script would be helpful !
I need to set up a Maintenance Plan on a 6.5 DB. I know the version is old but the customer cannot upgrade at this time. When I try and run the wizard to set it up I get a warning about running a plan on a DB that is larger that 400MB. Whats the deal? Thanks for the help!!
(1) Maint plan is setup to backup the databases that users actually use to update company information (2) diffrent databases. (2) maint plan backs up the master database this is setup to run by itself. (3) maint plan is setup to backup the model - msdb databases together.
I setup the email notification option to inform me if my backups were successfull. below is an example that I'm recieving everymorning on every database. Something about the single user mode is causing the problem. can somone explain this to? Maybe give me a direction to follow to correct this problem. Below is an example error message that I'm recieving.
I can backup any database by right clicking selecting all tasks then backup database and I get a complete backup to problem. Why is my Maint. Plan not going through. the rebuilding of indexs is successful.
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server 'My Server name' as 'My_Domain_NameMy_SQL_Admin_Account (trusted) Starting maintenance plan 'LEO-SLCBOM Full Nightly' on 4/13/2004 11:15:00 PM [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070: [Microsoft][ODBC SQL Server Driver][SQL Server]Database state cannot be changed while other users are using the database 'Leo' [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement failed. [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed. [1] Database Leo: Check Data and Index Linkage... [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not processed. Database needs to be in single user mode.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not processed. Database needs to be in single user mode. ** Execution Time: 0 hrs, 0 mins, 1 secs **
[2] Database SlcBom: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'LEO-SLCBOM Full Nightly' on 4/13/2004 11:15:01 PM SQLMAINT.EXE Process Exit Code: 1 (Failed)
I have a maint plan for a single database to backup the database, thats it, very simple. It fails every time.
When I do a view history of the maint plan, it is empty as if it has never run. When I do a view history of the job, it shows it has failed after 13 seconds. With this message. "Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed."
Any help would be great as I cannot get any backups to run. I am worried to say the least right now.
I am creating a sql 2005 maintenance plan backup job. How can i specify 'write log files to some particular drive'. I am new to sql server 2005 Please advice
It seems there are at least 3 ways to back up my databases in SQL2000
1) Veritas BackupExec 2) SQL Sever Backup 3) SQL Maintenance Plan
I don't quite see what the difference is between 2 & 3.
I'm currently using Veritas to do a full backup to tape, and a separate full backup to disk via a Maint Plan (a complete backup & trans log backup). It looks as though I've finally got my trans log to stop getting bigger (it started a new one) .... can I delete the huge one I don't need anymore. Does "truncate" mean the log is deleted, or just inactive as a new log gets created. I been reading up on this, but apparently it hasn't sunk in yet.
Please give me any long winded, but clear help you might have
Trying to create a new job from sql server 2005 Management Studio. The nifty wizard under Management provides options to create backups, and clean history, but I cant seem to find out how to create a job to purge old backups.
Looking at the commnand line Sql Server Agent Job shows:
Dear All, With SQL Server 7 SP2 Maint. Plan, Integrity, Attempt to repair minor problems - there was a feature that sometimes left databases in single user mode.
I have recently updated to SQL Server 2000 with a production database (option set OFF) - does this feature still apply to SQL Server 2000?
I created a single step plan that does integrity checks. It fails with the error below. I created a new connection using our clusters virtual sql name.
Executed as user: ACCTCOMsqlagent. ...n 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:10:06 PM Error: 2008-02-15 13:10:49.02 Code: 0xC00291EC Source: {0CF32F3D-A8D1-492A-9C0F-AD4E0FC67D14} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2008-02-15 13:10:49.02 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2008-02-15 13:11:31.26 Code: 0xC0024104 Source: Check Database Integrity Ta... The package execution fa... The step failed.
The agent and db are running under domain accounts and the job is owned by sa.
In SQL 7, a single table cannot be restored. What if a week later one found out that a table was corrupted few days and no one realized, then how to address this ? Restoring entire db from a tape few days old would't be a solution since all other tables have changed meantime.
I am using the Database maintenance on a database that is about 4gb. The database optiiztion is running about an hour. Does this job only do an update stats? If I run the stored procedure sp_updatestats on the database it only takes a couple of minutes. Are thes two processes doin the same thing? Do I need them if the create, update statistics are turned on?
Just two days ago, I noticed none of the scheduled maintenance jobs (backups) are running. I can run them manually successfully, but they are not running according to the maintenance schedule. There are no errors thrown.
Just prior to this happening, our anti-virus detected and deleted what it described as a virus [trojan]. The file was named sqlmaint.rll. I have done extensive searching and have not found anything definitive for this file. Obviously, this has something to do with maintenance not running, but how can I resolve this?
When I use Enterprise Manager to Maint views it basically brought up the view in simple text editor, where I could put in comments as to what the view was for.
I did this by just double clicking the view, but now in SQL Studio express when I modify the view it just brings it up in a query editor. I don't see my comments for my old SQL2000 views.
Is this just the way it is, and I need to get used to it. Or I am just missing something.
"tempdb is skipped. You cannot run a query that requires tempdb"?
We're running a .Net web application with a SQL Server 2000 backend, and we get the error intermittently. Restarting the SQL Server service seems to fix it, as it causes tempdb to be rebuilt, but this isn't a long term solution. Any direction or hints would be greatly appreciated. Thanks! - Mike
Ques; can "both" files the db backup (.bak) file "and" the (.txt)report file in a maint plan object be cleaned up at same time?
The object is working ok but trying to setup and match backup text reports to the db, I have way more .bak files than text files.
Created from/after db maint plan (which is working ok) from/in the object Maintenance Cleanup Task and the object selections are
Delete files of the following type: _backup files _maintenance plan text reports
File location: _delte specific file File name: __ _search folder and delete files based on an extension Folder:__ File extension:__ File age: _Delete files based on the age of the file at task run time... delete files oder than the following. . . .
Does anyone know an easier way to create DB Maint Plans instead of having to create each one manually? i.e. Copy Maint Plans from 1 server to another automatically. Does anyone know of a quick export method.
I have setup a Maint plan that backs up the user and system databases and the transaction Logs on my user databases.
Does optimises and integrity checks on those databases as well. I am not attempting to repair any minor problems. I am not performing integrity checks before backing up the database and transaction logs.
All of the databases that I am doing a transaction log backup on have recovery mode of full.
When the jobs run they fail instantly with error code 22029. Sqlmaint.exe failed to run. This was working up until the end of the day on the Thursday before Good Friday. (last week) The transaction log backup ran fine at 4:00 PM the same job failed at 8:00 PM. No changes were made to the server during that time. Another issue that started at the same time. I have a web page used to grab data from a text file export and pull it into an AS400. I use this server to house the DTS packages and stored procedures that the process needs. I suddenly quit working when the jobs quit running.
We are in a mixed enviroment with most clients on AD and this server and most others still in a NT 4 domain. We have been like this for at least 3 months and everything has worked fine. I setup the various users and systems the way the need to be, to work.
Originally the SQL Agent was running as a generic NT 4 Domain user with local administrator rights to the local box and server role of system administrator. The MSSQLSERVER and DTC services were running as the built in system account.
Everything was happy then it broke.
When I reboot the server the jobs and the website work fine. Then after a period of time that I have not figured out yet, but more than 15 minutes and less than 2 hours. Everything quits working.
I have changed all the services to run as a domain admin with SQL system adminsitrator server role. Still same thing.
I have changed all the services to run as the built in system account. Still same thing.
I run the sqlmaint from command line with the switches that I am using in the maint jobs and it runs fine.
I have run dbcc checkdb on all the databases and they are fine.
The DTS packages and the stored procedures used by the website run fine from with in Query analyzer.
Any help you can provide would be greatly appreciated.
We have an application that uses MS SQL 2005 to stored information related to user internet usage. It is storing a large amout of data on a daily bases. The application is set to create a new logging database, when the current database reaches 10GB, then it will start logging to the new database.
A new database is getting created at the rate of about 1 new db every 48hrs and the backup maintenance plan for the user databases, is not picking up the new database. I have to remember to refresh the maintenance job so, the new database gets picked up and is included in the daily backup.
Is there a way to have the backup maintenance job refesh itself? Or possibly a stored procedure or some sort of scripting option to do this?
Please provide information if you have a way of doing this. Thanks.
We have a debate in our team about embedded SQL vs. Stored Procs.
The argument is why use SP's if you can embed the SQL in the code and SQL2K will cache it on the fly?
I can't find any definitive information on pros and cons between the two methods.
If there are no major performance issues, or gotchas, I guess it comes down to developer preference.
SP Pros: - Great SQL support in VS.NET (dev, debug, integration) - Seperation of database specific code from middle tier. - Less lines of code in middle tier - VS.NET support for .xsd dataset definitions. - Logic closer to data for more demanding processes.
Embedded SQL Pros: - Less artifacts for version control - Better encapsulation of logic
I am running 2005 SP2 (It is the SP2 refresh as I downloaded the SP2 on 3/15/07) and I can't get the .txt maint plans to delete. The job completes successfully; however, the old .txt files are still there. I found this technote: http://support.microsoft.com/kb/938085 although I don't receive the error message in the KB. The report does have "New Component Output" as the 1st line in the report. I still don't see how deleting the 1st line of an already run job (the report) will affect a new run of the job.
Also, I checked the version of the Microsoft.SqlServer.MaintenancePlanTasks.dll and it is at 9.00.3043.00 (which is the SP2 Refresh) in KB 933508 ( http://support.microsoft.com/kb/933508 ).
I have several SQL/2005 servers and they all have this problem. Any help would be appreicated...
We are working on converting to SQL 2005 database. During the conversion we are having to rewrite a lot of code and doing a lot of intital testing and development on development data. This is causing our transaction logs to really big. I have created a maint plan that runs nightly that does a back up of database and tran log but throughtout the day the tran logs are getting really big and eating up a ton of disk space. Does anyone have suggestions on what sort of maint plan I can setup to run on my developement data where as at this point I am not concened about being able to roll back the database just keep is small as possible and "healthly"
Hi fellow techs! I am getting to know SQL 2000 intimately and it's been a fun ride with the top down!
My question is, are there any gotchas that I should be aware of in SQL 2000 if I want to change 3 of my databases running on one 2000 SQL server from simple to full recovery model? I want to begin backing up the log file for point in time purposes, but don't want anything to break by disregarding the gotchas, if there are any.
I've just set up a maintenance plan that backs up all user databases daily and logs hourly. I've just noticed that the plan history is giving the following error -
Database 'BizTalkEDIDb' is not valid to be included in the maintenance plan.
Has anyone seen this before or know how to resolve it?
I'm using sys.dm_db_missing_index_details to find missing indexes on a database that is currently in testing. After running a bunch of our reports, there are several suggested indexes on 3 or 4 columns that have 15 - 20 included columns. The included columns are mostly varchars ranging from 1 to 150 characters along with a couple of date columns. My index size on that table is already nearly twice the size of the data.
I don't think it's a good idea to add an index with that many columns, but the information I've read on included columns is very general. I'm wondering if there is something about them that I don't understand that would make this a good idea.
I use an XML configuration file for my SSIS package, and I have "Enable package configurations" checked. When I build the package, however, there is no dtsConfig file in the output (set to in) or the Deployment folder, and the config file is not included in the SSISDeploymentManifest file. There are no build errors or warnings.
This was working fine the last time I worked on this package (~9 months ago), but not now. I have since installed SP2, but can't confirm if the problem is related to a "fix" in SP2.
I have created reports in 'Projects'. What I would like to know is that if can transfer these reports into a report model?
As per my knowledge, a report model contains datasources, datasource views, report models itself and doesn't allow to transfer reports. Please , let me know if my understanding is correct?
