December 16, 2003 at 9:43 am
Does anyone know of a way to change the default view for servers and databases in Enterprise Manager to taskpad rather than Large Icons?
December 16, 2003 at 10:27 am
If you change each DB, it should get saved fo the next time.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
December 16, 2003 at 2:09 pm
In most cases this is true, unless EM decides otherwise and resets itself.
However, I haven't found out yet where this information is stored.
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
December 16, 2003 at 2:14 pm
Frank, That's what I'm finding out as well. We have over 30 SQL2000 servers each with a number of databases. I am trying to change to taskpad view whenever I go into a server or database. After changing a number of servers and databases, Enterprise Manager seems to revert to the default view of large icons.
December 16, 2003 at 2:24 pm
Yes, it's magic!
In the past there were some issues with taskpad view.
That was the time I decided to use EM only when necessary.
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
December 17, 2003 at 4:14 am
I think taskpad view is perfect - if only it worked properly all the time. Half the time when I click on the database name in the object browser I get an error dialog like this...
An error has occurred in the script on this page
Line: 307
Char: 2
Error: Unspecified error
Code: 0
URL: res://C:\Program%Files\Microsoft%20 etc.blah.blah.blah./tabs.html
If I then select large icons then taskpad, it works OK. This is really frustrating - is there anything I can do?
December 17, 2003 at 6:06 am
Sorry, I guess nothing you really want to hear, but I had the same problems.
I have a mixture of german and english SQL installation here, and I bet it must have something to do with the installation sequence, because the first time I had the same problem like you. But the second time (a totally new installation) I haven't encountered this problems yet.
Knock on wood.
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy