Add-in for SQL Server Mnagement Studio 2005

Hi,
I notice that a few third party SQL Server tool developers (RedGate
for example) have started to sell utilities that appear as add-ins
to
SQL Server Management Studio 2005 (with additional menu's and
dialogs).
I cant find any documentation on how you do this. Is it an
unsupported hack ? If so, can anyone point me in the right direction
on how I would work out how to do this.
(Sorry for the cross post, I posted the same message in
microsoft.public.sqlserver.server by mistake).
Thanks in advance,
Matt
Asked and answered in .server. Please refrain from multiposting.

Adam Machanic
SQL Server MVP - http://sqlblog.com
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
<matt_randle@.yahoo.com> wrote in message
news:1183902073.740953.145580@.22g2000hsm.googlegro ups.com...
> Hi,
> I notice that a few third party SQL Server tool developers (RedGate
> for example) have started to sell utilities that appear as add-ins
> to
> SQL Server Management Studio 2005 (with additional menu's and
> dialogs).
>
> I cant find any documentation on how you do this. Is it an
> unsupported hack ? If so, can anyone point me in the right direction
> on how I would work out how to do this.
> (Sorry for the cross post, I posted the same message in
> microsoft.public.sqlserver.server by mistake).
> Thanks in advance,
>
> Matt
>
|||Adam Machanic (amachanic@.IHATESPAMgmail.com) writes:
> Asked and answered in .server. Please refrain from multiposting.
Hey, he did after all say:
[vbcol=seagreen]
And this groups is certainly the appropriate one for the topic.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||Ok. Thanks for your reply (in the other group). If I can work out
how to do it, ill put up a blog post explaining it. I notice that it
will be a supported feature in the next release of SSMS though so may
just wait for that.
Thanks.
On 8 Jul, 16:09, "Adam Machanic" <amacha...@.IHATESPAMgmail.com> wrote:
> Asked and answered in .server. Please refrain from multiposting.
> --
> Adam Machanic
> SQL Server MVP -http://sqlblog.com
> Author, "Expert SQL Server 2005 Development"http://www.apress.com/book/bookDisplay.html?bID=10220
> <matt_ran...@.yahoo.com> wrote in message
> news:1183902073.740953.145580@.22g2000hsm.googlegro ups.com...
>

add an sql 2000 instance to a production server

Hi,
If I add an sql 2000 instance to a existing prod sql box used as a
developping sql instance.
The developers don't need to tough the production box..
Is it feasible? it will reduce the production performance?
What's the side effect?
What about creating a virtual server -- 2-3 virtual sql servers in a one
physical box.
Thanksmecn wrote:
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
Don't do that. Production and developing (or test) environment should be
separated. Separation means that there is no influence between them.
Unfortunately, when two instances are installed on the same server, one
instance can easily affect performance of other instance.
> What's the side effect?
When you add another (dev) instance, it will use common system
resources. Dev instance will consume RAM memory potentially available
for prod instance, it will also utilize processor(s) and IO.
IMHO it's a risky move.
> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
Better idea, because virtualization introduces much higher separation
level, but I think that's still not enough. Let production SQL Server
work on dedicated machine.
Best regards,
Marcin Guzowski
http://guzowski.info|||Thanks. I got it.
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ufol$grr$1@.news.onet.pl...
> mecn wrote:
>> Hi,
>> If I add an sql 2000 instance to a existing prod sql box used as a
>> developping sql instance.
>> The developers don't need to tough the production box..
>> Is it feasible? it will reduce the production performance?
> Don't do that. Production and developing (or test) environment should be
> separated. Separation means that there is no influence between them.
> Unfortunately, when two instances are installed on the same server, one
> instance can easily affect performance of other instance.
>> What's the side effect?
> When you add another (dev) instance, it will use common system resources.
> Dev instance will consume RAM memory potentially available for prod
> instance, it will also utilize processor(s) and IO.
> IMHO it's a risky move.
>> What about creating a virtual server -- 2-3 virtual sql servers in a one
>> physical box.
> Better idea, because virtualization introduces much higher separation
> level, but I think that's still not enough. Let production SQL Server work
> on dedicated machine.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info|||Do I need more sql licenses for virtual servers
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uWMC86OuHHA.1184@.TK2MSFTNGP04.phx.gbl...
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
> What's the side effect?
> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
> Thanks
>|||mecn wrote:
> Do I need more sql licenses for virtual servers
I don't know if it is true for SQL Server 2000 (probably not), but in
SQL Server 2005 it depends on SQL Server version (edition). If you have
SQL Server 2005 Enterprise Edition, you don't need additional licenses
for each virtual server.
In other cases, you must buy new licenses.
Best regards,
Marcin Guzowski
http://guzowski.info|||Thanks a lot dfor your help!!
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ui6o$pu8$1@.news.onet.pl...
> mecn wrote:
>> Do I need more sql licenses for virtual servers
> I don't know if it is true for SQL Server 2000 (probably not), but in SQL
> Server 2005 it depends on SQL Server version (edition). If you have SQL
> Server 2005 Enterprise Edition, you don't need additional licenses for
> each virtual server.
> In other cases, you must buy new licenses.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info

add an sql 2000 instance to a production server

Hi,
If I add an sql 2000 instance to a existing prod sql box used as a
developping sql instance.
The developers don't need to tough the production box..
Is it feasible? it will reduce the production performance?
What's the side effect?
What about creating a virtual server -- 2-3 virtual sql servers in a one
physical box.
Thanks
mecn wrote:
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
Don't do that. Production and developing (or test) environment should be
separated. Separation means that there is no influence between them.
Unfortunately, when two instances are installed on the same server, one
instance can easily affect performance of other instance.

> What's the side effect?
When you add another (dev) instance, it will use common system
resources. Dev instance will consume RAM memory potentially available
for prod instance, it will also utilize processor(s) and IO.
IMHO it's a risky move.

> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
Better idea, because virtualization introduces much higher separation
level, but I think that's still not enough. Let production SQL Server
work on dedicated machine.
Best regards,
Marcin Guzowski
http://guzowski.info
|||Thanks. I got it.
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ufol$grr$1@.news.onet.pl...
> mecn wrote:
> Don't do that. Production and developing (or test) environment should be
> separated. Separation means that there is no influence between them.
> Unfortunately, when two instances are installed on the same server, one
> instance can easily affect performance of other instance.
>
> When you add another (dev) instance, it will use common system resources.
> Dev instance will consume RAM memory potentially available for prod
> instance, it will also utilize processor(s) and IO.
> IMHO it's a risky move.
>
> Better idea, because virtualization introduces much higher separation
> level, but I think that's still not enough. Let production SQL Server work
> on dedicated machine.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info
|||Do I need more sql licenses for virtual servers
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uWMC86OuHHA.1184@.TK2MSFTNGP04.phx.gbl...
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
> What's the side effect?
> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
> Thanks
>
|||mecn wrote:
> Do I need more sql licenses for virtual servers
I don't know if it is true for SQL Server 2000 (probably not), but in
SQL Server 2005 it depends on SQL Server version (edition). If you have
SQL Server 2005 Enterprise Edition, you don't need additional licenses
for each virtual server.
In other cases, you must buy new licenses.
Best regards,
Marcin Guzowski
http://guzowski.info
|||Thanks a lot dfor your help!!
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ui6o$pu8$1@.news.onet.pl...
> mecn wrote:
> I don't know if it is true for SQL Server 2000 (probably not), but in SQL
> Server 2005 it depends on SQL Server version (edition). If you have SQL
> Server 2005 Enterprise Edition, you don't need additional licenses for
> each virtual server.
> In other cases, you must buy new licenses.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info

add an sql 2000 instance to a production server

Hi,
If I add an sql 2000 instance to a existing prod sql box used as a
developping sql instance.
The developers don't need to tough the production box..
Is it feasible? it will reduce the production performance?
What's the side effect?
What about creating a virtual server -- 2-3 virtual sql servers in a one
physical box.
Thanksmecn wrote:
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
Don't do that. Production and developing (or test) environment should be
separated. Separation means that there is no influence between them.
Unfortunately, when two instances are installed on the same server, one
instance can easily affect performance of other instance.

> What's the side effect?
When you add another (dev) instance, it will use common system
resources. Dev instance will consume RAM memory potentially available
for prod instance, it will also utilize processor(s) and IO.
IMHO it's a risky move.

> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
Better idea, because virtualization introduces much higher separation
level, but I think that's still not enough. Let production SQL Server
work on dedicated machine.
Best regards,
Marcin Guzowski
http://guzowski.info|||Thanks. I got it.
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ufol$grr$1@.news.onet.pl...
> mecn wrote:
> Don't do that. Production and developing (or test) environment should be
> separated. Separation means that there is no influence between them.
> Unfortunately, when two instances are installed on the same server, one
> instance can easily affect performance of other instance.
>
> When you add another (dev) instance, it will use common system resources.
> Dev instance will consume RAM memory potentially available for prod
> instance, it will also utilize processor(s) and IO.
> IMHO it's a risky move.
>
> Better idea, because virtualization introduces much higher separation
> level, but I think that's still not enough. Let production SQL Server work
> on dedicated machine.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info|||Do I need more sql licenses for virtual servers
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uWMC86OuHHA.1184@.TK2MSFTNGP04.phx.gbl...
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
> What's the side effect?
> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
> Thanks
>|||mecn wrote:
> Do I need more sql licenses for virtual servers
I don't know if it is true for SQL Server 2000 (probably not), but in
SQL Server 2005 it depends on SQL Server version (edition). If you have
SQL Server 2005 Enterprise Edition, you don't need additional licenses
for each virtual server.
In other cases, you must buy new licenses.
Best regards,
Marcin Guzowski
http://guzowski.info|||Thanks a lot dfor your help!!
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ui6o$pu8$1@.news.onet.pl...
> mecn wrote:
> I don't know if it is true for SQL Server 2000 (probably not), but in SQL
> Server 2005 it depends on SQL Server version (edition). If you have SQL
> Server 2005 Enterprise Edition, you don't need additional licenses for
> each virtual server.
> In other cases, you must buy new licenses.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info