Re: corrupt msdb
From: Jacco Schalkwijk (NOSPAMjaccos_at_eurostop.co.uk)
Date: 03/24/04
- Next message: Joseph Geretz: "Re: WHERE clause applies to right-hand table of LEFT JOIN"
- Previous message: Chieko Kuroda: "MS Access performance enhancement?"
- In reply to: Tibor Karaszi: "Re: corrupt msdb"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Mar 2004 15:07:45 -0000
Very good point, and something I totally forgot about. I wasn't the only one
though, see this post http://tinyurl.com/2delc.
-- Jacco Schalkwijk SQL Server MVP "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in message news:%23$Gts2aEEHA.576@TK2MSFTNGP11.phx.gbl... > 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! > > > > > >
- Next message: Joseph Geretz: "Re: WHERE clause applies to right-hand table of LEFT JOIN"
- Previous message: Chieko Kuroda: "MS Access performance enhancement?"
- In reply to: Tibor Karaszi: "Re: corrupt msdb"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
