SQL Enterprise Manager - Sudden problems

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Development (2000)

SQL Enterprise Manager - Sudden problems

Author

Topic

MaverickUK
Yak Posting Veteran

89 Posts

Posted - 2003-12-19 : 10:45:39

Hi guys

Since last week I've noticed that SQL Server Enterprise manager has started to generate a number of errors

* When editting a table and clicking on the dropdown for the data type, I get the error "ODBC error:[Microsoft][ODBC SQL Server Driver]Communication link failure"
and then the dropdown is left blank

* Editting a table again, if I try and save changes, I get another error "ODBC error: [Microsoft][ODBC SQL Server Driver]Communication link failure"

When these errors are produced, they appear to also cause SQL Server to spit out a SQLxxxxx.dmp file in the MSSQL/LOG folder.

The info in the top of this .dmp file consists of this


*   Exception Address = 00800A9F (RowsetSS::Init(class IMemObj *,class BaseXact
 *,int,int,int,struct IRowset *,class RowsetUsageDescriptor *,class RowsetExecC
ontext const *,int) + 000003E9 Line 0+00000000)                                
*   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION                    
*   Access Violation occurred reading address 00000148                         
* Input Buffer 1152 bytes -                                                    
*  select xp.name, cast(xp.[value] as nvarchar(4000)), cast(SQL_VARIANT_PRO    
*  PERTY(xp.[value], 'BaseType') as nvarchar(256)), cast(SQL_VARIANT_PROPER    
*  TY(xp.[value], 'MaxLength') as int), cast(SQL_VARIANT_PROPERTY(xp.[value    
*  ], 'Precision') as int), cast(SQL_VARIANT_PROPERTY(xp.[value], 'Scale')     
*  as int)from ::fn_listextendedproperty(NULL, N'user', N'dbo', N'table', N    
*  'Survey', NULL, NULL) xp where xp.name in (N'MS_Description', N'MS_Filte    
*  r', N'MS_OrderBy', N'MS_SubdatasheetName', N'MS_LinkChildFields', N'MS_L    
*  inkMasterFields', N'MS_SubdatasheetHeight', N'MS_SubdatasheetExpanded')

all these problems *appear* to have all started since a certain Microsoft security mini-update was added... I'm stuck in the middle, as a developer, as I'm not really meant to deal with the service packs etc... but our support team is just shrugging when it comes to solving this issue :/
Please... anyone have any idea about this?

X002548
Not Just a Number

15586 Posts

Posted - 2003-12-19 : 11:08:30

Have you done a DBCC CHECKDB?

Also why are you doing all of this in EM?

Brett

8-)

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2003-12-19 : 11:43:02

Are you on Win2003?

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.

MaverickUK
Yak Posting Veteran

89 Posts

Posted - 2003-12-19 : 12:02:32

X002548

* I considered doing a DBCC CHECKDB, but I wanted to investigate to see if I could find a simpler cause of the problems, before doing this.
* Why shouldn't I edit db tables through EM? It's very impressive writing the commands out through QA, but using EM is alot faster and easier.

DerrickLeggitt
Nope, sorry I should have said.
W2K SP2, SQL Server 2000, currently it has not been patched...
I'm hoping I can talk the powers that be into getting SQL Server service packed up to date next week.

MaverickUK
Yak Posting Veteran

89 Posts

Posted - 2003-12-19 : 12:04:05

Just to let you know...
I've run a DBCC CHECKDB on a few random databases, plus the master, no problems

CHECKDB found 0 allocation errors and 0 consistency errors in database 'master'.

X002548
Not Just a Number

15586 Posts

Posted - 2003-12-19 : 12:18:02

I just find EM to be quirky...

What happens if you do the same thing in QA?

Plus, if you write code, you can see what you did...not really so in EM...plus you can save the code and is repeatable if need be...

My Own opinion

MOO

Brett

8-)

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-12-19 : 12:27:19

Applying service pack 3a will most fix your problem.

Also, when you make the change in EM, do not save the change but rather hit the save change script button, then copy that code into Query Analyzer, then close EM without saving the change. Now run the code in Query Analyzer. This will allow you to make the table change without getting the EM error. It will also help you learn the code that it takes to modify tables.

Tara

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2003-12-19 : 12:56:35

I think we all agree on this one. Get the latest SPs (on SQL Server and W2K). Any admin who has SQL Server and hasn't put the latest SP on should be talked to. :) Also, don't use EM for any modification. The code that thing gens to do simple mods is crazy. Just script it out and use what you need.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.

robvolk
Most Valuable Yak

15732 Posts

Posted - 2003-12-20 : 18:01:32

Yet another reason not to use EM for data editing/browsing:

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=31410

This might appear to be just a simple quirk, but there are a number of them, and it doesn't make sense to just work around them when you can do everything correctly in Query Analyzer.

MaverickUK
Yak Posting Veteran

89 Posts

Posted - 2003-12-22 : 04:38:48

I was worried this might turn into an old DOS command line VS visual DOS shell style debate

But anyway, I've managed to talk the powers that be into allowing me to update our database server to the latest service pack.
If only the developers were in charge!

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources