Monday, February 20, 2012

MSDB Corrupt?

[298] SQLServer Error: 446, Cannot resolve collation conflict for equal
to operation. [SQLSTATE 42000]
I keep getting this from SQL Agent. I restored an msdb database from an
old SQL Server and i am now finding out that it had a different
collation on it. how do i fix the msdb?in sql2000 you can change the collation of a column and
database. Read "changing collations" in sql BOL.
>--Original Message--
>[298] SQLServer Error: 446, Cannot resolve collation
conflict for equal
>to operation. [SQLSTATE 42000]
>I keep getting this from SQL Agent. I restored an msdb
database from an
>old SQL Server and i am now finding out that it had a
different
>collation on it. how do i fix the msdb?
>.
>|||Is there anyway to completely rebuild msdb (get a fresh one?)
anonymous@.discussions.microsoft.com wrote:
> in sql2000 you can change the collation of a column and
> database. Read "changing collations" in sql BOL.
>
>>--Original Message--
>>[298] SQLServer Error: 446, Cannot resolve collation
> conflict for equal
>>to operation. [SQLSTATE 42000]
>>I keep getting this from SQL Agent. I restored an msdb
> database from an
>>old SQL Server and i am now finding out that it had a
> different
>>collation on it. how do i fix the msdb?
>>.|||I know there was a rebuildmsdb utility in SQL &. You could drop msdb
and create msdb again, then run a utility to create all the tables and
procedures. is there one for sql 2000?
anonymous@.discussions.microsoft.com wrote:
> in sql2000 you can change the collation of a column and
> database. Read "changing collations" in sql BOL.
>
>>--Original Message--
>>[298] SQLServer Error: 446, Cannot resolve collation
> conflict for equal
>>to operation. [SQLSTATE 42000]
>>I keep getting this from SQL Agent. I restored an msdb
> database from an
>>old SQL Server and i am now finding out that it had a
> different
>>collation on it. how do i fix the msdb?
>>.|||the following article should also apply to sql2000.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;238822
>--Original Message--
>I know there was a rebuildmsdb utility in SQL &. You
could drop msdb
>and create msdb again, then run a utility to create all
the tables and
>procedures. is there one for sql 2000?
>
>anonymous@.discussions.microsoft.com wrote:
>> in sql2000 you can change the collation of a column and
>> database. Read "changing collations" in sql BOL.
>>
>>--Original Message--
>>[298] SQLServer Error: 446, Cannot resolve collation
>> conflict for equal
>>to operation. [SQLSTATE 42000]
>>I keep getting this from SQL Agent. I restored an msdb
>> database from an
>>old SQL Server and i am now finding out that it had a
>> different
>>collation on it. how do i fix the msdb?
>>.
>.
>|||> the following article should also apply to sql2000.
That is only the repository, not the whole msdb.
instmsdb.sql will build msdb. But search KB and the net on instruction on how to use it first.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
<anonymous@.discussions.microsoft.com> wrote in message
news:037f01c39e5c$ff4a5ff0$a301280a@.phx.gbl...
> the following article should also apply to sql2000.
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;238822
> >--Original Message--
> >I know there was a rebuildmsdb utility in SQL &. You
> could drop msdb
> >and create msdb again, then run a utility to create all
> the tables and
> >procedures. is there one for sql 2000?
> >
> >
> >anonymous@.discussions.microsoft.com wrote:
> >
> >> in sql2000 you can change the collation of a column and
> >> database. Read "changing collations" in sql BOL.
> >>
> >>
> >>
> >>--Original Message--
> >>[298] SQLServer Error: 446, Cannot resolve collation
> >>
> >> conflict for equal
> >>
> >>to operation. [SQLSTATE 42000]
> >>
> >>I keep getting this from SQL Agent. I restored an msdb
> >>
> >> database from an
> >>
> >>old SQL Server and i am now finding out that it had a
> >>
> >> different
> >>
> >>collation on it. how do i fix the msdb?
> >>
> >>.
> >>
> >
> >.
> >

No comments:

Post a Comment