Sunday, February 19, 2012

Enterprise Manager 2/ Me 0

Ahoy All!
Say I come in, bright-eyed-and-bushy-tailed in the AM and say "Hey! I think
I'll add a field to a table this Bright and Glorious morning!" so I fire up
Enterprise Manager (v 2.0) with the SQL Enterprise Manager (v 8.0) (running
on XP SP2 hitting a SQL Server 2000 SP4 DB running on W2k3 Server) and go to
design view, add my tiny little field (this time an int, default 0), click
Apply, click Yes Please (actually OK), and then, lo and behold, I get this
little gem:
17310 :
SqlDumpExceptionHandler: Process 848 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
No further access via EM or QA at that point.
So I stop the SQLService on the server, count to 10 and sprinkle a little
pixie dust about, restart the SQLService, and voila! sometimes my field is
in the table, sometimes it isn't, and if it isn't, I add it in, click Apply,
click Yes Please, and double-viola! It works like a charm - then, for the
rest of the day, all is well (can add fields, update sprocs, modify triggers
,
you-name-it).
Any thoughts and suggestions would be appreciated. Haven't tried it via QA,
though, next time I think I'll give 'er a whirl.
ThanksType, don't click. :)
ML
http://milambda.blogspot.com/|||Ha ha! I agree, but Dang! Why would the EM cause such dismay?
"ML" wrote:

> Type, don't click. :)
>
> ML
> --
> http://milambda.blogspot.com/|||> Any thoughts and suggestions would be appreciated.
Use Query Analyzer and ALTER TABLE commands. In addition to not being
mystified by voodoo (and often worse things) that Enterprise Manager is
going "for you" behind the scenes, you can just click a button to save the
script, maybe to store in sourcesafe, and you can also wrap your command(s)
in a transaction and roll it back quite easily if things go south (granted,
as long as what you are doing doesn't somehow cause an AV and shut down the
service, which definitely sounds like a bug).
What is @.@.VERSION? 8.00.2039? You should move to at least .2040 and maybe
better still 2187.
A|||I meant to add the suggestion to make sure your client tools are at the same
build/patch level as the server, if your client tools are connecting to a
non-local server.
And it gives me another chance to stress using QA, not EM, for managing
schema / data.
A
"B@.DJJ" <BDJJ@.discussions.microsoft.com> wrote in message
news:579A20A3-FC31-4901-AD39-7A141B76DBE8@.microsoft.com...
> Ahoy All!
> Say I come in, bright-eyed-and-bushy-tailed in the AM and say "Hey! I
> think
> I'll add a field to a table this Bright and Glorious morning!" so I fire
> up
> Enterprise Manager (v 2.0) with the SQL Enterprise Manager (v 8.0)
> (running
> on XP SP2 hitting a SQL Server 2000 SP4 DB running on W2k3 Server) and go
> to
> design view, add my tiny little field (this time an int, default 0), click
> Apply, click Yes Please (actually OK), and then, lo and behold, I get this
> little gem:
> 17310 :
> SqlDumpExceptionHandler: Process 848 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> No further access via EM or QA at that point.
> So I stop the SQLService on the server, count to 10 and sprinkle a little
> pixie dust about, restart the SQLService, and voila! sometimes my field
> is
> in the table, sometimes it isn't, and if it isn't, I add it in, click
> Apply,
> click Yes Please, and double-viola! It works like a charm - then, for the
> rest of the day, all is well (can add fields, update sprocs, modify
> triggers,
> you-name-it).
> Any thoughts and suggestions would be appreciated. Haven't tried it via
> QA,
> though, next time I think I'll give 'er a whirl.
> Thanks
>|||> Why would the EM cause such dismay?
It's hard to say, because we don't know enough about the table. Maybe it's
in a circular reference with a chain of 18 indexed views? It could be
pretty much anything, i fmoving to 2187 doesn't alleviate the issue, you
should talk to PSS and maybe they can help you take a SQLDUMP of the error
and figure it out.
Or, if it hurts when you scratch your left knee with your right hand, then
like I suggested before, don't do that... try using your left hand instead.|||Thanks Aaron - the plan is to bring us up to 2187 in the next day or so - bu
t
I think it's going to be QA from now on fer this here gunshy fellah.
"Aaron Bertrand [SQL Server MVP]" wrote:

> I meant to add the suggestion to make sure your client tools are at the sa
me
> build/patch level as the server, if your client tools are connecting to a
> non-local server.
> And it gives me another chance to stress using QA, not EM, for managing
> schema / data.
> A
>
>
> "B@.DJJ" <BDJJ@.discussions.microsoft.com> wrote in message
> news:579A20A3-FC31-4901-AD39-7A141B76DBE8@.microsoft.com...
>
>|||Gunshy today, a darn good DBA tomorow.
ML
http://milambda.blogspot.com/|||Within EM, add your new column, and then (instead of clicking Save) click
the Save Change Script button to view the T-SQL that EM us generting to
alter the table. Depending on the cirscumstances, it may copy the data to a
temporary table first.
"B@.DJJ" <BDJJ@.discussions.microsoft.com> wrote in message
news:579A20A3-FC31-4901-AD39-7A141B76DBE8@.microsoft.com...
> Ahoy All!
> Say I come in, bright-eyed-and-bushy-tailed in the AM and say "Hey! I
> think
> I'll add a field to a table this Bright and Glorious morning!" so I fire
> up
> Enterprise Manager (v 2.0) with the SQL Enterprise Manager (v 8.0)
> (running
> on XP SP2 hitting a SQL Server 2000 SP4 DB running on W2k3 Server) and go
> to
> design view, add my tiny little field (this time an int, default 0), click
> Apply, click Yes Please (actually OK), and then, lo and behold, I get this
> little gem:
> 17310 :
> SqlDumpExceptionHandler: Process 848 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> No further access via EM or QA at that point.
> So I stop the SQLService on the server, count to 10 and sprinkle a little
> pixie dust about, restart the SQLService, and voila! sometimes my field
> is
> in the table, sometimes it isn't, and if it isn't, I add it in, click
> Apply,
> click Yes Please, and double-viola! It works like a charm - then, for the
> rest of the day, all is well (can add fields, update sprocs, modify
> triggers,
> you-name-it).
> Any thoughts and suggestions would be appreciated. Haven't tried it via
> QA,
> though, next time I think I'll give 'er a whirl.
> Thanks
>

No comments:

Post a Comment