Can’t a client easily register an instance of MSDE using any third party GUI
or EM and get hold of our data structure? How can I over come this issue, if
I am installing MSDE on client computer?
thanx
hi,
"Job Lot" <JobLot@.discussions.microsoft.com> ha scritto nel messaggio
news:7002631C-B28D-4785-8C16-2EFE5D74BD50@.microsoft.com
> Can’t a client easily register an instance of MSDE using any third
> party GUI or EM and get hold of our data structure? How can I over
> come this issue, if I am installing MSDE on client computer?
> thanx
a MSDE instance can be easly registered as a linked server or in EM, from
remote (as long as the required network protocols are enabled) or local pc,
or using third party tools... as long as login privileges are set to the
logged user or a valid SQL Server login is known...
to access the databases, another issue must be granted (quite easy), that's
to say the logged user (login) is mapped to a valid database user...
if the login (both NT [trusted connections] or SQL Server [requiring "user"
and "pwd" credentials]) is member of WinNT administrators group (and thus)
or sysadmins server roles, he/she can actually do whatever he/she wants as
that membership grants illimitate privileges...
this design is part of the SQL Server security and can not be cut... so you
have to grant minimal privileges (server side) to logins in order to allow
only to specific logins the ability to access you databases..
a good article about security model is presented at
http://www.sql-server-performance.co...l_security.asp and
http://www.microsoft.com/technet/pro.../sp3sec03.mspx
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Showing posts with label third. Show all posts
Showing posts with label third. Show all posts
Monday, March 12, 2012
Saturday, February 25, 2012
MSDE incomplete install
I have SQL 2000 running on a Windows 2000 server.
A third party product attempted to install MSDE onto the same server, but
failed to complete its install.
At random it appears as though the MSDE attempts to run and complete its
install, which increases the processor upto approx 100%.
Since the MSDE is in an incomplete state, what is the best approach at
attempting to remove the failing component and leave SQL intact.
MSDE does not show up in the add/remove programs.
Regardshi,
Ray wrote:
> I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server,
> but failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete
> its install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
>
first identify the named instance name, perhaps looking in the \Program
Files\Microsoft SQL Server\ folder... as you already have a SQL Server 2000
installed (probably as default instance, check it first), you could have
something like MSSQL$InstanceName...
you can then manually clean up the failed install following
http://support.microsoft.com/defaul...b;EN-US;Q290991 ...
this procedure does not clean up Windows Installer MSDE related registry
entries, and you have to use (if you want to) MSIZap.exe, part of the
Windows Installer SDK as exposed in
http://support.microsoft.com/defaul...kb;en-us;320873
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||The reason MSDE doesn't appear in add/remove programs is that the third
party product installed it as a merge module which means as far as the
installer is concerned, it is part of the product you're installing. Try
removing the third party product with add/remove programs.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ray" <Ray@.test.com> wrote in message
news:%23g62vrfiGHA.1600@.TK2MSFTNGP04.phx.gbl...
>I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server, but
> failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete its
> install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
> Regards
>
A third party product attempted to install MSDE onto the same server, but
failed to complete its install.
At random it appears as though the MSDE attempts to run and complete its
install, which increases the processor upto approx 100%.
Since the MSDE is in an incomplete state, what is the best approach at
attempting to remove the failing component and leave SQL intact.
MSDE does not show up in the add/remove programs.
Regardshi,
Ray wrote:
> I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server,
> but failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete
> its install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
>
first identify the named instance name, perhaps looking in the \Program
Files\Microsoft SQL Server\ folder... as you already have a SQL Server 2000
installed (probably as default instance, check it first), you could have
something like MSSQL$InstanceName...
you can then manually clean up the failed install following
http://support.microsoft.com/defaul...b;EN-US;Q290991 ...
this procedure does not clean up Windows Installer MSDE related registry
entries, and you have to use (if you want to) MSIZap.exe, part of the
Windows Installer SDK as exposed in
http://support.microsoft.com/defaul...kb;en-us;320873
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||The reason MSDE doesn't appear in add/remove programs is that the third
party product installed it as a merge module which means as far as the
installer is concerned, it is part of the product you're installing. Try
removing the third party product with add/remove programs.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ray" <Ray@.test.com> wrote in message
news:%23g62vrfiGHA.1600@.TK2MSFTNGP04.phx.gbl...
>I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server, but
> failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete its
> install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
> Regards
>
MSDE incomplete install
I have SQL 2000 running on a Windows 2000 server.
A third party product attempted to install MSDE onto the same server, but
failed to complete its install.
At random it appears as though the MSDE attempts to run and complete its
install, which increases the processor upto approx 100%.
Since the MSDE is in an incomplete state, what is the best approach at
attempting to remove the failing component and leave SQL intact.
MSDE does not show up in the add/remove programs.
Regardshi,
Ray wrote:
> I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server,
> but failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete
> its install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
>
first identify the named instance name, perhaps looking in the \Program
Files\Microsoft SQL Server\ folder... as you already have a SQL Server 2000
installed (probably as default instance, check it first), you could have
something like MSSQL$InstanceName...
you can then manually clean up the failed install following
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 ...
this procedure does not clean up Windows Installer MSDE related registry
entries, and you have to use (if you want to) MSIZap.exe, part of the
Windows Installer SDK as exposed in
http://support.microsoft.com/default.aspx?scid=kb;en-us;320873
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||The reason MSDE doesn't appear in add/remove programs is that the third
party product installed it as a merge module which means as far as the
installer is concerned, it is part of the product you're installing. Try
removing the third party product with add/remove programs.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ray" <Ray@.test.com> wrote in message
news:%23g62vrfiGHA.1600@.TK2MSFTNGP04.phx.gbl...
>I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server, but
> failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete its
> install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
> Regards
>
A third party product attempted to install MSDE onto the same server, but
failed to complete its install.
At random it appears as though the MSDE attempts to run and complete its
install, which increases the processor upto approx 100%.
Since the MSDE is in an incomplete state, what is the best approach at
attempting to remove the failing component and leave SQL intact.
MSDE does not show up in the add/remove programs.
Regardshi,
Ray wrote:
> I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server,
> but failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete
> its install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
>
first identify the named instance name, perhaps looking in the \Program
Files\Microsoft SQL Server\ folder... as you already have a SQL Server 2000
installed (probably as default instance, check it first), you could have
something like MSSQL$InstanceName...
you can then manually clean up the failed install following
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 ...
this procedure does not clean up Windows Installer MSDE related registry
entries, and you have to use (if you want to) MSIZap.exe, part of the
Windows Installer SDK as exposed in
http://support.microsoft.com/default.aspx?scid=kb;en-us;320873
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||The reason MSDE doesn't appear in add/remove programs is that the third
party product installed it as a merge module which means as far as the
installer is concerned, it is part of the product you're installing. Try
removing the third party product with add/remove programs.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ray" <Ray@.test.com> wrote in message
news:%23g62vrfiGHA.1600@.TK2MSFTNGP04.phx.gbl...
>I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server, but
> failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete its
> install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
> Regards
>
Subscribe to:
Posts (Atom)