SSMS 2008 Super Buggy

microsoft.public.sqlserver.tools

17 Mar 2009 9:48 PM

Chuck P

We updated some servers from 05 to 08.
We soon found out you couldn't do queries in 05 to an 08 server.
So the DBAs installed SSMS on their xpp sp2 boxes. Only SSMS not the
database.

Well if you try to edit a proc you get nothing but error squiggleys.
The sprocs complile but all the invalid error messages are very annoying.

If you go to the linked severs and click on an 05 box and try to see the
catalogs, the request times out after about 5 minutes.

If you try to debug a sproc, SSMS locks up and can only be killed through
task manger.

This is happening on multiple machines.
Any suggestions?

17 Mar 2009 11:17 PM

Erland Sommarskog

Chuck P (Chuck@newsgroup.nospam) writes:

> We updated some servers from 05 to 08.
> We soon found out you couldn't do queries in 05 to an 08 server.

It is possible to connect to SQL 2008 with SSMS 2005, if you have
installed SP3 of SQL 2005.

> Well if you try to edit a proc you get nothing but error squiggleys.
> The sprocs complile but all the invalid error messages are very annoying.

Intellisense is indeed very annoying. But you can turn it off.
Tools->Options->Text Editor->Transact-SQL->Intellisense.

> If you try to debug a sproc, SSMS locks up and can only be killed through
> task manger.

I have found in previous versions of SQL Server that came with a debugger,
that debugging is really only an option if you run against an instance
on the same machine. Debugging against other servers means struggling
with a lot og read time.

> If you go to the linked severs and click on an 05 box and try to see the
> catalogs, the request times out after about 5 minutes.

That does indeed seem to be slow, but I would say to me that this is
something I do very often.

--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Are all your drivers up to date? click for free checkup

18 Mar 2009 1:22 PM

Chuck P

I'd like to use the intellisence it worked fine in the other versions. Don't
understand why it highlights 10-20 words in the sproc and says they are all
bad.

Debugging in previous versions I would get errors but not complete lockups
of SSMS

When we looked at linked servers in previous versions we could look at the
catalogs, It would take under 2 seconds. Now it just locks up.

Show quoteHide quote

"Erland Sommarskog" wrote:

> Chuck P (Chuck@newsgroup.nospam) writes:
> > We updated some servers from 05 to 08.
> > We soon found out you couldn't do queries in 05 to an 08 server.
>
> It is possible to connect to SQL 2008 with SSMS 2005, if you have
> installed SP3 of SQL 2005.
>
> > Well if you try to edit a proc you get nothing but error squiggleys.
> > The sprocs complile but all the invalid error messages are very annoying.
>
> Intellisense is indeed very annoying. But you can turn it off.
> Tools->Options->Text Editor->Transact-SQL->Intellisense.
>
> > If you try to debug a sproc, SSMS locks up and can only be killed through
> > task manger.
>
> I have found in previous versions of SQL Server that came with a debugger,
> that debugging is really only an option if you run against an instance
> on the same machine. Debugging against other servers means struggling
> with a lot og read time.
>
> > If you go to the linked severs and click on an 05 box and try to see the
> > catalogs, the request times out after about 5 minutes.
>
> That does indeed seem to be slow, but I would say to me that this is
> something I do very often.
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Links for SQL Server Books Online:
> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>

18 Mar 2009 10:50 PM

Erland Sommarskog

Chuck P (Chuck@newsgroup.nospam) writes:

> I'd like to use the intellisence it worked fine in the other versions.

SSMS 2008 is the first version of SSMS to provide intellisense.

> Debugging in previous versions I would get errors but not complete
> lockups of SSMS

Again, SSMS 2008 is the first version of SSMS to provide debugging. But
it is true that it was also available in QA 2000.

I should that I have been able to use debugger, but admittedly it is a
fairly slow starter. Personally, I find the debugger to be a quite
over-rated feature.

> When we looked at linked servers in previous versions we could look at the
> catalogs, It would take under 2 seconds. Now it just locks up.

This may also be due to network issues. Linked servers often means headache.

18 Mar 2009 7:22 AM

Mark Han[MSFT]

Hi Chuck,

Thank you for using Microsoft MSDN Managed Newsgroup. My name is Mark Han.
I am glad to work with you on this issue.

From your description, I understand that there are 2 issues you meet now.
1 when you try to connect to the linked server (SQL 2005)created on the SQL
Server 2008, an error about(time out) appears.

2 when using SQL 2008 SSMS to dubug a sprocs, it seems that the SSMS hangs.
If I have misunderstood, please let me know.

in order to address you concern, I would like to explain the following
1 we have to update the SQL 2005 to SP3 so that we can use SSMS 2005 to
connect to the SQL 2008. Based on your description, I know that you have
installed the SSMS 2008. it is great and suggested.

2 I understand your concerns on the Intellisense feature. So, if it is
convenient to you, please close it. Tools->Options->Text
Editor->Transact-SQL->Intellisense.

3 In the post, I will help to focus on 2 different issues. So, generally, I
will seperate my response to 2 parts in the future.

For linked server time out issue.
To further diagnose the issue, we need to understand the scenario first. So
please help to confirm the following and send me an email. after receiving
your mail, I will create a workspace for you to upload the required
informatin and list the next troubleshooting step.
my email address is v-fathan@online. microsoft.com (remove online)
1 how is the linked server built?

2 on the machine where the SSMS hangs, could we connect to the SQL 2005 by
SSMS directly?

3 on the machine where 2008 is installed, please try to use SSMS to
connect the SQL 2005.

For SSMS hang issue.
The issue is a client tool problem. So, please do the following to narrow
down the issue
1 please involve another machine where the SSMS 2008 is installed and then
try to use the SSMS to debug the sprocs to check if the issue will still
happen

2 please create a simple code. For example "select * from table_name". and
try to debug the query and see if the issue will occur again.

If there is anything unclear, please do not hesitate to let me know. Have a
nice day!

Best regards,
Mark Han
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msd***@microsoft.com.
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or
a Microsoft Support Engineer within 2 business day is acceptable. Please
note that each follow up response may take approximately
2 business days as the support professional working with you may need
further investigation to reach the most efficient resolution.
The offering is not appropriate for situations that require urgent,
real-time or phone-based interactions. Issues of this nature are
best handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx

============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================

18 Mar 2009 1:57 PM

Chuck P

I would say the real problem I am trying to solve is we upgraded SSMS to the
08 version and within 5 minutes pretty much found out it is bug ridden. I am
sure as the day wears on we will find more problems. I spent some time
describing how we installed with the hopes that maybe the way we did it
results in bugs that could be fixed by reinstalling or doing something else.

Debugging: All of our 05 servers are on sp2 or sp3.
I will get the remaining ones on sp3 tonight.

I would like to use intellisence, is their a way to get it to not report
that 15 items are in error when none of them are?

Show quoteHide quote

"Mark Han[MSFT]" wrote:

> Hi Chuck,
>
> Thank you for using Microsoft MSDN Managed Newsgroup. My name is Mark Han.
> I am glad to work with you on this issue.
>
> From your description, I understand that there are 2 issues you meet now.
> 1 when you try to connect to the linked server (SQL 2005)created on the SQL
> Server 2008, an error about(time out) appears.
>
> 2 when using SQL 2008 SSMS to dubug a sprocs, it seems that the SSMS hangs.
> If I have misunderstood, please let me know.
>
> in order to address you concern, I would like to explain the following
> 1 we have to update the SQL 2005 to SP3 so that we can use SSMS 2005 to
> connect to the SQL 2008. Based on your description, I know that you have
> installed the SSMS 2008. it is great and suggested.
>
> 2 I understand your concerns on the Intellisense feature. So, if it is
> convenient to you, please close it. Tools->Options->Text
> Editor->Transact-SQL->Intellisense.
>
> 3 In the post, I will help to focus on 2 different issues. So, generally, I
> will seperate my response to 2 parts in the future.
>
> For linked server time out issue.
> To further diagnose the issue, we need to understand the scenario first. So
> please help to confirm the following and send me an email. after receiving
> your mail, I will create a workspace for you to upload the required
> informatin and list the next troubleshooting step.
> my email address is v-fathan@online. microsoft.com (remove online)
> 1 how is the linked server built?
>
> 2 on the machine where the SSMS hangs, could we connect to the SQL 2005 by
> SSMS directly?
>
> 3 on the machine where 2008 is installed, please try to use SSMS to
> connect the SQL 2005.
>
> For SSMS hang issue.
> The issue is a client tool problem. So, please do the following to narrow
> down the issue
> 1 please involve another machine where the SSMS 2008 is installed and then
> try to use the SSMS to debug the sprocs to check if the issue will still
> happen
>
> 2 please create a simple code. For example "select * from table_name". and
> try to debug the query and see if the issue will occur again.
>
> If there is anything unclear, please do not hesitate to let me know. Have a
> nice day!
>
>
> Best regards,
> Mark Han
> Microsoft Online Community Support
> ===========================================================
> Delighting our customers is our #1 priority. We welcome your
> comments and suggestions about how we can improve the
> support we provide to you. Please feel free to let my manager
> know what you think of the level of service provided. You can
> send feedback directly to my manager at: msd***@microsoft.com.
> ===========================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
> Note: MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or
> a Microsoft Support Engineer within 2 business day is acceptable. Please
> note that each follow up response may take approximately
> 2 business days as the support professional working with you may need
> further investigation to reach the most efficient resolution.
> The offering is not appropriate for situations that require urgent,
> real-time or phone-based interactions. Issues of this nature are
> best handled working with a dedicated Microsoft Support Engineer by
> contacting Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
>
> ============================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> =========================================================
>
>

18 Mar 2009 3:25 PM

Ekrem_Ã–nsoy

Take a look at this feedback (about intellisense):
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=311967

--
Ekrem Ã–nsoy

Show quoteHide quote

"Chuck P" <Chuck@newsgroup.nospam> wrote in message
news:0E6FE28F-6964-4416-B985-7FDD81579000@microsoft.com...
>I would say the real problem I am trying to solve is we upgraded SSMS to
>the
> 08 version and within 5 minutes pretty much found out it is bug ridden. I
> am
> sure as the day wears on we will find more problems. I spent some time
> describing how we installed with the hopes that maybe the way we did it
> results in bugs that could be fixed by reinstalling or doing something
> else.
>
> Debugging: All of our 05 servers are on sp2 or sp3.
> I will get the remaining ones on sp3 tonight.
>
> I would like to use intellisence, is their a way to get it to not report
> that 15 items are in error when none of them are?
>
> "Mark Han[MSFT]" wrote:
>
>> Hi Chuck,
>>
>> Thank you for using Microsoft MSDN Managed Newsgroup. My name is Mark
>> Han.
>> I am glad to work with you on this issue.
>>
>> From your description, I understand that there are 2 issues you meet now.
>> 1 when you try to connect to the linked server (SQL 2005)created on the
>> SQL
>> Server 2008, an error about(time out) appears.
>>
>> 2 when using SQL 2008 SSMS to dubug a sprocs, it seems that the SSMS
>> hangs.
>> If I have misunderstood, please let me know.
>>
>> in order to address you concern, I would like to explain the following
>> 1 we have to update the SQL 2005 to SP3 so that we can use SSMS 2005 to
>> connect to the SQL 2008. Based on your description, I know that you have
>> installed the SSMS 2008. it is great and suggested.
>>
>> 2 I understand your concerns on the Intellisense feature. So, if it is
>> convenient to you, please close it. Tools->Options->Text
>> Editor->Transact-SQL->Intellisense.
>>
>> 3 In the post, I will help to focus on 2 different issues. So, generally,
>> I
>> will seperate my response to 2 parts in the future.
>>
>> For linked server time out issue.
>> To further diagnose the issue, we need to understand the scenario first.
>> So
>> please help to confirm the following and send me an email. after
>> receiving
>> your mail, I will create a workspace for you to upload the required
>> informatin and list the next troubleshooting step.
>> my email address is v-fathan@online. microsoft.com (remove online)
>> 1 how is the linked server built?
>>
>> 2 on the machine where the SSMS hangs, could we connect to the SQL 2005
>> by
>> SSMS directly?
>>
>> 3 on the machine where 2008 is installed, please try to use SSMS to
>> connect the SQL 2005.
>>
>> For SSMS hang issue.
>> The issue is a client tool problem. So, please do the following to narrow
>> down the issue
>> 1 please involve another machine where the SSMS 2008 is installed and
>> then
>> try to use the SSMS to debug the sprocs to check if the issue will still
>> happen
>>
>> 2 please create a simple code. For example "select * from table_name".
>> and
>> try to debug the query and see if the issue will occur again.
>>
>> If there is anything unclear, please do not hesitate to let me know. Have
>> a
>> nice day!
>>
>>
>> Best regards,
>> Mark Han
>> Microsoft Online Community Support
>> ===========================================================
>> Delighting our customers is our #1 priority. We welcome your
>> comments and suggestions about how we can improve the
>> support we provide to you. Please feel free to let my manager
>> know what you think of the level of service provided. You can
>> send feedback directly to my manager at: msd***@microsoft.com.
>> ===========================================================
>> Get notification to my posts through email? Please refer to
>> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
>> ications.
>>
>> Note: MSDN Managed Newsgroup support offering is for non-urgent issues
>> where an initial response from the community or
>> a Microsoft Support Engineer within 2 business day is acceptable. Please
>> note that each follow up response may take approximately
>> 2 business days as the support professional working with you may need
>> further investigation to reach the most efficient resolution.
>> The offering is not appropriate for situations that require urgent,
>> real-time or phone-based interactions. Issues of this nature are
>> best handled working with a dedicated Microsoft Support Engineer by
>> contacting Microsoft Customer Support Services (CSS) at
>> http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
>>
>> ============================================================
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> =========================================================
>>
>>

18 Mar 2009 3:34 PM

Chuck P

Interesting,
We didn't do any table changes.
But if you just do a select with 5 column name 3 of them will be squiggled.
Our cache is probably corrupted or maybe not even created.

Show quoteHide quote

"Ekrem Ã–nsoy" wrote:

> Take a look at this feedback (about intellisense):
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=311967
>
> --
> Ekrem Ã–nsoy
>
>
>
> "Chuck P" <Chuck@newsgroup.nospam> wrote in message
> news:0E6FE28F-6964-4416-B985-7FDD81579000@microsoft.com...
> >I would say the real problem I am trying to solve is we upgraded SSMS to
> >the
> > 08 version and within 5 minutes pretty much found out it is bug ridden. I
> > am
> > sure as the day wears on we will find more problems. I spent some time
> > describing how we installed with the hopes that maybe the way we did it
> > results in bugs that could be fixed by reinstalling or doing something
> > else.
> >
> > Debugging: All of our 05 servers are on sp2 or sp3.
> > I will get the remaining ones on sp3 tonight.
> >
> > I would like to use intellisence, is their a way to get it to not report
> > that 15 items are in error when none of them are?
> >
> > "Mark Han[MSFT]" wrote:
> >
> >> Hi Chuck,
> >>
> >> Thank you for using Microsoft MSDN Managed Newsgroup. My name is Mark
> >> Han.
> >> I am glad to work with you on this issue.
> >>
> >> From your description, I understand that there are 2 issues you meet now.
> >> 1 when you try to connect to the linked server (SQL 2005)created on the
> >> SQL
> >> Server 2008, an error about(time out) appears.
> >>
> >> 2 when using SQL 2008 SSMS to dubug a sprocs, it seems that the SSMS
> >> hangs.
> >> If I have misunderstood, please let me know.
> >>
> >> in order to address you concern, I would like to explain the following
> >> 1 we have to update the SQL 2005 to SP3 so that we can use SSMS 2005 to
> >> connect to the SQL 2008. Based on your description, I know that you have
> >> installed the SSMS 2008. it is great and suggested.
> >>
> >> 2 I understand your concerns on the Intellisense feature. So, if it is
> >> convenient to you, please close it. Tools->Options->Text
> >> Editor->Transact-SQL->Intellisense.
> >>
> >> 3 In the post, I will help to focus on 2 different issues. So, generally,
> >> I
> >> will seperate my response to 2 parts in the future.
> >>
> >> For linked server time out issue.
> >> To further diagnose the issue, we need to understand the scenario first.
> >> So
> >> please help to confirm the following and send me an email. after
> >> receiving
> >> your mail, I will create a workspace for you to upload the required
> >> informatin and list the next troubleshooting step.
> >> my email address is v-fathan@online. microsoft.com (remove online)
> >> 1 how is the linked server built?
> >>
> >> 2 on the machine where the SSMS hangs, could we connect to the SQL 2005
> >> by
> >> SSMS directly?
> >>
> >> 3 on the machine where 2008 is installed, please try to use SSMS to
> >> connect the SQL 2005.
> >>
> >> For SSMS hang issue.
> >> The issue is a client tool problem. So, please do the following to narrow
> >> down the issue
> >> 1 please involve another machine where the SSMS 2008 is installed and
> >> then
> >> try to use the SSMS to debug the sprocs to check if the issue will still
> >> happen
> >>
> >> 2 please create a simple code. For example "select * from table_name".
> >> and
> >> try to debug the query and see if the issue will occur again.
> >>
> >> If there is anything unclear, please do not hesitate to let me know. Have
> >> a
> >> nice day!
> >>
> >>
> >> Best regards,
> >> Mark Han
> >> Microsoft Online Community Support
> >> ===========================================================
> >> Delighting our customers is our #1 priority. We welcome your
> >> comments and suggestions about how we can improve the
> >> support we provide to you. Please feel free to let my manager
> >> know what you think of the level of service provided. You can
> >> send feedback directly to my manager at: msd***@microsoft.com.
> >> ===========================================================
> >> Get notification to my posts through email? Please refer to
> >> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> >> ications.
> >>
> >> Note: MSDN Managed Newsgroup support offering is for non-urgent issues
> >> where an initial response from the community or
> >> a Microsoft Support Engineer within 2 business day is acceptable. Please
> >> note that each follow up response may take approximately
> >> 2 business days as the support professional working with you may need
> >> further investigation to reach the most efficient resolution.
> >> The offering is not appropriate for situations that require urgent,
> >> real-time or phone-based interactions. Issues of this nature are
> >> best handled working with a dedicated Microsoft Support Engineer by
> >> contacting Microsoft Customer Support Services (CSS) at
> >> http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
> >>
> >> ============================================================
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> =========================================================
> >>
> >>
>

18 Mar 2009 3:28 PM

Aaron Bertrand [SQL Server MVP]

> I would say the real problem I am trying to solve is we upgraded SSMS to the
> 08 version and within 5 minutes pretty much found out it is bug ridden.

I have been using it since it was in very early beta and I find SSMS 2005
much more tedious to use and has several more bugs that have gone unfixed
that simply don't exist in the 2008 version of the tool. With that said:

(a) I turn IntelliSense off, though with it on I only see red squigglies for
things it can't resolve, such as column names in a table that are referenced
via synonym or linked server. I'd be interested to see a screen shot that
shows where you get all kinds of red squigglies that shouldn't be there,
along with a way to tell that you are right, as I am sure there is an
explanation.

(b) I will likely never use any "debug" tools against the database... this
is what unit tests / test harnesses are for. If I am simply modifying a
procedure I can use TRY/CATCH, RAISERROR, PRINT, etc. if I really need that
type of debugging. (Since debugging doesn't work for remote SQL auth on 05
SP2, which is where I spend 90+% of my time these days.) In fact the first
thing I do when I set up a new client tools installation is customize the
toolbar by removing the debug icon (since I hit it accidentally several
times, as it looks like the old Query Analyzer's "execute" icon). This
shouldn't really be a loss to you when compared to 2005 SSMS, since there
was no debug option, so you're no worse off... just don't use it.
(Patient: "It hurts when I jump off the roof." Doctor: "Stop jumping off the
roof.")

(c) I have installed the SP1 CTP; not sure how much has affected stability,
debugging or IntelliSense issues in SSMS specifically, but you may want to
install that on all your clients, or at least CU4, which was released
earlier this week.

CU4:
http://is.gd/nSeS

SP1 CTP:
http://is.gd/kFmq

You can also look for SSMS fixes that might help you out by searching for
cumulative updates 1, 2 and 3 (those fixes are all included in CU4).