Now when I go to SQL 2K EM .. And then right click on database and select
properties.. it crashes.. Have any of you observed that ? Let me know how I
can fix it.. I even tried rebooting and it doesnt help
ThanksThis is a multi-part message in MIME format.
--=_NextPart_000_02A4_01C4877F.250CD1D0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hassan,
If the database in question is one of the SQL Server 2005 databases, =you are probably out of luck. Some pre-2005 tools will simply not work =with SQL Server 2005 because they can't support features that didn't =exist when they were developed. If EM is broken when used with SQL =Server 2000 databases, see if this advice from Microsoft about a =different EM problem helps.
Like the rest of the current version of SQL Express this is a =pre-release version, the permissions problem is a bug which we have =resolved in the B2 build of SQL Server 2005. If you need to use EM =before we update SQLDMO and Express, then go to the version of =SQLDMO.dll thats in SQL Server 2000 directory and execute regsvr32 =sqldmo.dll. This should enable EM to work as it was before against SQL =Server 2000 but neither EM nor DMO will work against SQL Express in this =case. If things like this didn't happen, it wouldn't be beta software...
Steve Kass
Drew University
"Hassan" <fatima_ja@.hotmail.com> wrote in message =news:OqF$jH6hEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Ive got SQL 2005 Beta 2 installed along with my SQL 2K on my XP PC
> > Now when I go to SQL 2K EM .. And then right click on database and =select
> properties.. it crashes.. Have any of you observed that ? Let me know =how I
> can fix it.. I even tried rebooting and it doesnt help
> > Thanks
> >
--=_NextPart_000_02A4_01C4877F.250CD1D0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hassan,
If the database in question is one of the SQL =Server 2005 databases, you are probably out of luck. Some pre-2005 tools =will simply not work with SQL Server 2005 because they can't support features =that didn't exist when they were developed. If EM is broken when used =with SQL Server 2000 databases, see if this advice from Microsoft about a =different EM problem helps.
Like the rest of the =current version of SQL Express this is a pre-release version, the permissions =problem is a bug which we have resolved in the B2 build of SQL Server 2005. If =you need to use EM before we update SQLDMO and Express, then go to the =version of SQLDMO.dll thats in SQL Server 2000 directory and execute regsvr32 =sqldmo.dll. This should enable EM to work as it was before against SQL Server 2000 =but neither EM nor DMO will work against SQL Express in this case. If things like this didn't happen, it wouldn't be =beta software...
Steve Kass
Drew University
"Hassan"
--=_NextPart_000_02A4_01C4877F.250CD1D0--
No comments:
Post a Comment