Re: corrupt msdb

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 03/24/04 

Date: Wed, 24 Mar 2004 15:38:27 +0100

Or rebuilding (rebuildm.exe).

One thing, though. The original files has the "default" collation. If some other collation was selected
(explicitly by user or implicitly by setup program), then you would end up with model having a different
collation than the other system databases. A no-no. 

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Jacco Schalkwijk" <NOSPAMjaccos@eurostop.co.uk> wrote in message
news:%23%23aWmbaEEHA.3040@TK2MSFTNGP12.phx.gbl...
> You can actually get the msdb data and log files out of the installation
> files, they are in there. I did use this a while ago to fix a corrupted
> model db. Stop SQL Server, rename the msdb data and log files and put the
> extracted files in their place. I don't guarantee that this will work
> correctly if you have applied a service pack already, or to more precise,
> I'm not sure if you can reinstall the service pack just to apply the changes
> to msdb. In that case you might be better off reinstalling.
>
> -- 
> Jacco Schalkwijk
> SQL Server MVP
>
>
> "Jim" <jromano@phs-us.com> wrote in message
> news:e1e1a687.0403240514.7c410d93@posting.google.com...
> > We recently upgraded from version 6.5 to 2000. During the process the
> > Wizard did not complete. It apparently build all selected databases
> > but did not migrate the data. The last line in the summary log reads
> > "Preparing SQL-DMO for upgrade=0". We decided to press on with the
> > upgrade by using DTS to port over all non-system databases/tables. We
> > did not port over the master or msdb data as it looked like the wizard
> > did do this work. However I just discovered that I cannot scheudle a
> > job using enterprise manager. The following error is given when
> > creating a new job:
> >
> > Microsoft SQL-DMO (ODBC SQLSTATE: 42s22)
> > Error 207: Invalid column 'category id'
> > Invalid column  ' netsend_address'
> > Invalid column  'last_netsend_date'
> > Invalid column  'last_netsend_time'
> >
> > I know that columns did not get created on several msdb tables when we
> > upgraded to 2000. The columns referenced above are supposed to be in
> > the sysoperator table but they did not get created. I am sure that
> > there are several tables that are not up to date now. So here is my
> > question: What is the best way to get msdb up to date with all the
> > appropriate tables and columns? I did try to DTS the msdb from another
> > instance of SQL but that operation was not successful. I was thinking
> > of installing another instance of SQL (thus creating clean master and
> > msdb databases) and then use DTS to port over non-system databases to
> > the new instance. Does this sound like a good plan? Are there better
> > ways to accomplish my goal? If I do use the instance, can I then
> > rename it to make it the default instance? Thanks!
>
>

Relevant Pages

  • corrupt msdb
    ... It apparently build all selected databases ... upgrade by using DTS to port over all non-system databases/tables. ... Error 207: Invalid column 'category id' ... I know that columns did not get created on several msdb tables when we ...
    (microsoft.public.sqlserver.server)
  • corrupted msdb
    ... all selected databases but did not migrate the data. ... upgrade by using DTS to port over all non-system ... Error 207: Invalid column 'category id' ... I know that columns did not get created on several msdb ...
    (microsoft.public.sqlserver.setup)
  • Re: Periodic maintenance like sp_delete_backuphistory?
    ... Have a look at the sizes of your system databases. ... msdb on one of my servers ... Administrative Tools outside of SQL Server. ...
    (microsoft.public.sqlserver.server)
  • Re: error 207 when trying to add a new job
    ... Did you upgraded your SQL server from older version. ... If yes then the MSDB ... upgrade was not done fully. ... > invalid column name 'netsend_address' ...
    (microsoft.public.sqlserver.server)
  • Re: Stored Packages - MSDB Access
    ... I have written the SSIS Project and created the ... I have successfully deploy the package to MSDB, ... can not browse MSDB either locally on the server from SQL Server Management ... why is it saying that anything about remote ...
    (microsoft.public.sqlserver.dts)