Several developers have been assigned dbo of a database. Is there a way to
allow all the objects that we create to all have the dbo ownership by
default, rather than our user name?
I'm aware that we could explicitly type ...
create proc dbo.myprocedurename as
but was hoping this could be the default behavior.
Thanks in advance.
Mark
Mark,
I assume you mean they have been assigned the db_owner role? Only one login can be the dbo user. There is a
difference between dbo and db_owner.
Assuming that the logins have their own user names and are indeed db_owner, then you have to qualify the owner
when you create the object. Only way around is to use sp_addalias, but this will disappear in future and
there's no GUI support for this. Be careful to read in BOL whether it is supported or not.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Mark" <mfield@.idonotlikespam.cce.umn.edu> wrote in message news:%23GgYl4dMEHA.1392@.TK2MSFTNGP09.phx.gbl...
> Several developers have been assigned dbo of a database. Is there a way to
> allow all the objects that we create to all have the dbo ownership by
> default, rather than our user name?
> I'm aware that we could explicitly type ...
> create proc dbo.myprocedurename as
> but was hoping this could be the default behavior.
> Thanks in advance.
> Mark
>
|||Mark wrote:
> Several developers have been assigned dbo of a database. Is there a way to
> allow all the objects that we create to all have the dbo ownership by
> default, rather than our user name?
could you put all those developers into a group on the db server and then have
that group be the dbowner of the db?
Showing posts with label objects. Show all posts
Showing posts with label objects. Show all posts
Tuesday, March 27, 2012
default dbo to object names instead of user name
Several developers have been assigned dbo of a database. Is there a way to
allow all the objects that we create to all have the dbo ownership by
default, rather than our user name?
I'm aware that we could explicitly type ...
create proc dbo.myprocedurename as
but was hoping this could be the default behavior.
Thanks in advance.
MarkMark,
I assume you mean they have been assigned the db_owner role? Only one login
can be the dbo user. There is a
difference between dbo and db_owner.
Assuming that the logins have their own user names and are indeed db_owner,
then you have to qualify the owner
when you create the object. Only way around is to use sp_addalias, but this
will disappear in future and
there's no GUI support for this. Be careful to read in BOL whether it is sup
ported or not.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Mark" <mfield@.idonotlikespam.cce.umn.edu> wrote in message news:%23GgYl4dMEHA.1392@.TK2MSFTN
GP09.phx.gbl...
> Several developers have been assigned dbo of a database. Is there a way t
o
> allow all the objects that we create to all have the dbo ownership by
> default, rather than our user name?
> I'm aware that we could explicitly type ...
> create proc dbo.myprocedurename as
> but was hoping this could be the default behavior.
> Thanks in advance.
> Mark
>|||Mark wrote:
> Several developers have been assigned dbo of a database. Is there a way t
o
> allow all the objects that we create to all have the dbo ownership by
> default, rather than our user name?
could you put all those developers into a group on the db server and then ha
ve
that group be the dbowner of the db?sql
allow all the objects that we create to all have the dbo ownership by
default, rather than our user name?
I'm aware that we could explicitly type ...
create proc dbo.myprocedurename as
but was hoping this could be the default behavior.
Thanks in advance.
MarkMark,
I assume you mean they have been assigned the db_owner role? Only one login
can be the dbo user. There is a
difference between dbo and db_owner.
Assuming that the logins have their own user names and are indeed db_owner,
then you have to qualify the owner
when you create the object. Only way around is to use sp_addalias, but this
will disappear in future and
there's no GUI support for this. Be careful to read in BOL whether it is sup
ported or not.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Mark" <mfield@.idonotlikespam.cce.umn.edu> wrote in message news:%23GgYl4dMEHA.1392@.TK2MSFTN
GP09.phx.gbl...
> Several developers have been assigned dbo of a database. Is there a way t
o
> allow all the objects that we create to all have the dbo ownership by
> default, rather than our user name?
> I'm aware that we could explicitly type ...
> create proc dbo.myprocedurename as
> but was hoping this could be the default behavior.
> Thanks in advance.
> Mark
>|||Mark wrote:
> Several developers have been assigned dbo of a database. Is there a way t
o
> allow all the objects that we create to all have the dbo ownership by
> default, rather than our user name?
could you put all those developers into a group on the db server and then ha
ve
that group be the dbowner of the db?sql
default dbo to object names instead of user name
Several developers have been assigned dbo of a database. Is there a way to
allow all the objects that we create to all have the dbo ownership by
default, rather than our user name?
I'm aware that we could explicitly type ...
create proc dbo.myprocedurename as
but was hoping this could be the default behavior.
Thanks in advance.
MarkMark,
I assume you mean they have been assigned the db_owner role? Only one login can be the dbo user. There is a
difference between dbo and db_owner.
Assuming that the logins have their own user names and are indeed db_owner, then you have to qualify the owner
when you create the object. Only way around is to use sp_addalias, but this will disappear in future and
there's no GUI support for this. Be careful to read in BOL whether it is supported or not.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Mark" <mfield@.idonotlikespam.cce.umn.edu> wrote in message news:%23GgYl4dMEHA.1392@.TK2MSFTNGP09.phx.gbl...
> Several developers have been assigned dbo of a database. Is there a way to
> allow all the objects that we create to all have the dbo ownership by
> default, rather than our user name?
> I'm aware that we could explicitly type ...
> create proc dbo.myprocedurename as
> but was hoping this could be the default behavior.
> Thanks in advance.
> Mark
>|||Mark wrote:
> Several developers have been assigned dbo of a database. Is there a way to
> allow all the objects that we create to all have the dbo ownership by
> default, rather than our user name?
could you put all those developers into a group on the db server and then have
that group be the dbowner of the db?
allow all the objects that we create to all have the dbo ownership by
default, rather than our user name?
I'm aware that we could explicitly type ...
create proc dbo.myprocedurename as
but was hoping this could be the default behavior.
Thanks in advance.
MarkMark,
I assume you mean they have been assigned the db_owner role? Only one login can be the dbo user. There is a
difference between dbo and db_owner.
Assuming that the logins have their own user names and are indeed db_owner, then you have to qualify the owner
when you create the object. Only way around is to use sp_addalias, but this will disappear in future and
there's no GUI support for this. Be careful to read in BOL whether it is supported or not.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Mark" <mfield@.idonotlikespam.cce.umn.edu> wrote in message news:%23GgYl4dMEHA.1392@.TK2MSFTNGP09.phx.gbl...
> Several developers have been assigned dbo of a database. Is there a way to
> allow all the objects that we create to all have the dbo ownership by
> default, rather than our user name?
> I'm aware that we could explicitly type ...
> create proc dbo.myprocedurename as
> but was hoping this could be the default behavior.
> Thanks in advance.
> Mark
>|||Mark wrote:
> Several developers have been assigned dbo of a database. Is there a way to
> allow all the objects that we create to all have the dbo ownership by
> default, rather than our user name?
could you put all those developers into a group on the db server and then have
that group be the dbowner of the db?
Sunday, February 19, 2012
Debugging CLR Objects
Hi,
I was able to use SQL Server Project template in VS to debug my CLR-SPs. But
I'd like to know if it is possible to debug those CLR-Objects while
executing from SSMS.
Any help would be greatly appreciated.
Leila
Hi
No, CLR objects must be debugged from within Visual Studio 2005.
From SQL Server 2005 BOL
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-46ad21168319.htm):
"SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio 2005
supports debugging connections to SQL Server. For more information about how
to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
defined types, and aggregates from Visual Studio, see the Visual Studio 2005
documentation."
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Leila" <Leilas@.hotpop.com> wrote in message
news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
> Hi,
> I was able to use SQL Server Project template in VS to debug my CLR-SPs.
> But
> I'd like to know if it is possible to debug those CLR-Objects while
> executing from SSMS.
> Any help would be greatly appreciated.
> Leila
>
|||Thanks,
But what about attaching processes from VS IDE? It seems there are some
facilities for Analysis Services.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecWBBrb#FHA.1332@.tk2msftngp13.phx.gbl...
> Hi
> No, CLR objects must be debugged from within Visual Studio 2005.
> From SQL Server 2005 BOL
>
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
> "SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio
2005
> supports debugging connections to SQL Server. For more information about
how
> to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
> defined types, and aggregates from Visual Studio, see the Visual Studio
2005
> documentation."
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
>
I was able to use SQL Server Project template in VS to debug my CLR-SPs. But
I'd like to know if it is possible to debug those CLR-Objects while
executing from SSMS.
Any help would be greatly appreciated.
Leila
Hi
No, CLR objects must be debugged from within Visual Studio 2005.
From SQL Server 2005 BOL
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-46ad21168319.htm):
"SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio 2005
supports debugging connections to SQL Server. For more information about how
to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
defined types, and aggregates from Visual Studio, see the Visual Studio 2005
documentation."
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Leila" <Leilas@.hotpop.com> wrote in message
news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
> Hi,
> I was able to use SQL Server Project template in VS to debug my CLR-SPs.
> But
> I'd like to know if it is possible to debug those CLR-Objects while
> executing from SSMS.
> Any help would be greatly appreciated.
> Leila
>
|||Thanks,
But what about attaching processes from VS IDE? It seems there are some
facilities for Analysis Services.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecWBBrb#FHA.1332@.tk2msftngp13.phx.gbl...
> Hi
> No, CLR objects must be debugged from within Visual Studio 2005.
> From SQL Server 2005 BOL
>
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
> "SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio
2005
> supports debugging connections to SQL Server. For more information about
how
> to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
> defined types, and aggregates from Visual Studio, see the Visual Studio
2005
> documentation."
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
>
Debugging CLR Objects
Hi,
I was able to use SQL Server Project template in VS to debug my CLR-SPs. But
I'd like to know if it is possible to debug those CLR-Objects while
executing from SSMS.
Any help would be greatly appreciated.
LeilaHi
No, CLR objects must be debugged from within Visual Studio 2005.
From SQL Server 2005 BOL
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
"SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio 2005
supports debugging connections to SQL Server. For more information about how
to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
defined types, and aggregates from Visual Studio, see the Visual Studio 2005
documentation."
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Leila" <Leilas@.hotpop.com> wrote in message
news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
> Hi,
> I was able to use SQL Server Project template in VS to debug my CLR-SPs.
> But
> I'd like to know if it is possible to debug those CLR-Objects while
> executing from SSMS.
> Any help would be greatly appreciated.
> Leila
>|||Thanks,
But what about attaching processes from VS IDE? It seems there are some
facilities for Analysis Services.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecWBBrb#FHA.1332@.tk2msftngp13.phx.gbl...
> Hi
> No, CLR objects must be debugged from within Visual Studio 2005.
> From SQL Server 2005 BOL
>
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
> "SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio
2005
> supports debugging connections to SQL Server. For more information about
how
> to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
> defined types, and aggregates from Visual Studio, see the Visual Studio
2005
> documentation."
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
>
I was able to use SQL Server Project template in VS to debug my CLR-SPs. But
I'd like to know if it is possible to debug those CLR-Objects while
executing from SSMS.
Any help would be greatly appreciated.
LeilaHi
No, CLR objects must be debugged from within Visual Studio 2005.
From SQL Server 2005 BOL
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
"SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio 2005
supports debugging connections to SQL Server. For more information about how
to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
defined types, and aggregates from Visual Studio, see the Visual Studio 2005
documentation."
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Leila" <Leilas@.hotpop.com> wrote in message
news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
> Hi,
> I was able to use SQL Server Project template in VS to debug my CLR-SPs.
> But
> I'd like to know if it is possible to debug those CLR-Objects while
> executing from SSMS.
> Any help would be greatly appreciated.
> Leila
>|||Thanks,
But what about attaching processes from VS IDE? It seems there are some
facilities for Analysis Services.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecWBBrb#FHA.1332@.tk2msftngp13.phx.gbl...
> Hi
> No, CLR objects must be debugged from within Visual Studio 2005.
> From SQL Server 2005 BOL
>
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
> "SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio
2005
> supports debugging connections to SQL Server. For more information about
how
> to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
> defined types, and aggregates from Visual Studio, see the Visual Studio
2005
> documentation."
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
>
Debugging CLR Objects
Hi,
I was able to use SQL Server Project template in VS to debug my CLR-SPs. But
I'd like to know if it is possible to debug those CLR-Objects while
executing from SSMS.
Any help would be greatly appreciated.
LeilaHi
No, CLR objects must be debugged from within Visual Studio 2005.
From SQL Server 2005 BOL
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-46ad21168319.htm):
"SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio 2005
supports debugging connections to SQL Server. For more information about how
to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
defined types, and aggregates from Visual Studio, see the Visual Studio 2005
documentation."
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Leila" <Leilas@.hotpop.com> wrote in message
news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
> Hi,
> I was able to use SQL Server Project template in VS to debug my CLR-SPs.
> But
> I'd like to know if it is possible to debug those CLR-Objects while
> executing from SSMS.
> Any help would be greatly appreciated.
> Leila
>|||Thanks,
But what about attaching processes from VS IDE? It seems there are some
facilities for Analysis Services.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecWBBrb#FHA.1332@.tk2msftngp13.phx.gbl...
> Hi
> No, CLR objects must be debugged from within Visual Studio 2005.
> From SQL Server 2005 BOL
>
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
> "SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio
2005
> supports debugging connections to SQL Server. For more information about
how
> to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
> defined types, and aggregates from Visual Studio, see the Visual Studio
2005
> documentation."
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
> > Hi,
> > I was able to use SQL Server Project template in VS to debug my CLR-SPs.
> > But
> > I'd like to know if it is possible to debug those CLR-Objects while
> > executing from SSMS.
> > Any help would be greatly appreciated.
> > Leila
> >
> >
>
I was able to use SQL Server Project template in VS to debug my CLR-SPs. But
I'd like to know if it is possible to debug those CLR-Objects while
executing from SSMS.
Any help would be greatly appreciated.
LeilaHi
No, CLR objects must be debugged from within Visual Studio 2005.
From SQL Server 2005 BOL
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-46ad21168319.htm):
"SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio 2005
supports debugging connections to SQL Server. For more information about how
to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
defined types, and aggregates from Visual Studio, see the Visual Studio 2005
documentation."
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Leila" <Leilas@.hotpop.com> wrote in message
news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
> Hi,
> I was able to use SQL Server Project template in VS to debug my CLR-SPs.
> But
> I'd like to know if it is possible to debug those CLR-Objects while
> executing from SSMS.
> Any help would be greatly appreciated.
> Leila
>|||Thanks,
But what about attaching processes from VS IDE? It seems there are some
facilities for Analysis Services.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecWBBrb#FHA.1332@.tk2msftngp13.phx.gbl...
> Hi
> No, CLR objects must be debugged from within Visual Studio 2005.
> From SQL Server 2005 BOL
>
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
> "SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio
2005
> supports debugging connections to SQL Server. For more information about
how
> to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
> defined types, and aggregates from Visual Studio, see the Visual Studio
2005
> documentation."
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
> > Hi,
> > I was able to use SQL Server Project template in VS to debug my CLR-SPs.
> > But
> > I'd like to know if it is possible to debug those CLR-Objects while
> > executing from SSMS.
> > Any help would be greatly appreciated.
> > Leila
> >
> >
>
Debugging CLR Objects
Hi,
I was able to use SQL Server Project template in VS to debug my CLR-SPs. But
I'd like to know if it is possible to debug those CLR-Objects while
executing from SSMS.
Any help would be greatly appreciated.
LeilaHi
No, CLR objects must be debugged from within Visual Studio 2005.
From SQL Server 2005 BOL
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
"SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio 2005
supports debugging connections to SQL Server. For more information about how
to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
defined types, and aggregates from Visual Studio, see the Visual Studio 2005
documentation."
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Leila" <Leilas@.hotpop.com> wrote in message
news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
> Hi,
> I was able to use SQL Server Project template in VS to debug my CLR-SPs.
> But
> I'd like to know if it is possible to debug those CLR-Objects while
> executing from SSMS.
> Any help would be greatly appreciated.
> Leila
>|||Thanks,
But what about attaching processes from VS IDE? It seems there are some
facilities for Analysis Services.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecWBBrb#FHA.1332@.tk2msftngp13.phx.gbl...
> Hi
> No, CLR objects must be debugged from within Visual Studio 2005.
> From SQL Server 2005 BOL
>
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
> "SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio
2005
> supports debugging connections to SQL Server. For more information about
how
> to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
> defined types, and aggregates from Visual Studio, see the Visual Studio
2005
> documentation."
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
>
I was able to use SQL Server Project template in VS to debug my CLR-SPs. But
I'd like to know if it is possible to debug those CLR-Objects while
executing from SSMS.
Any help would be greatly appreciated.
LeilaHi
No, CLR objects must be debugged from within Visual Studio 2005.
From SQL Server 2005 BOL
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
"SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio 2005
supports debugging connections to SQL Server. For more information about how
to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
defined types, and aggregates from Visual Studio, see the Visual Studio 2005
documentation."
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Leila" <Leilas@.hotpop.com> wrote in message
news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
> Hi,
> I was able to use SQL Server Project template in VS to debug my CLR-SPs.
> But
> I'd like to know if it is possible to debug those CLR-Objects while
> executing from SSMS.
> Any help would be greatly appreciated.
> Leila
>|||Thanks,
But what about attaching processes from VS IDE? It seems there are some
facilities for Analysis Services.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecWBBrb#FHA.1332@.tk2msftngp13.phx.gbl...
> Hi
> No, CLR objects must be debugged from within Visual Studio 2005.
> From SQL Server 2005 BOL
>
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/denet9/html/1332035c-d6ed-424d-8234-4
6ad21168319.htm):
> "SQL Server 2005 does not ship with a debugger. Microsoft Visual Studio
2005
> supports debugging connections to SQL Server. For more information about
how
> to debug SQL Server 2005 CLR stored procedures, functions, triggers, user
> defined types, and aggregates from Visual Studio, see the Visual Studio
2005
> documentation."
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:eibf7eb%23FHA.600@.tk2msftngp13.phx.gbl...
>
Subscribe to:
Posts (Atom)