I have multiple applications that will use the same named instance of MSDE. When I try to setup my second application using the MSDE Deployment addin it thinks that MSDE needs to be installed again. According to the flowchart it should bypass this and
just install my appliation. Any suggestions as to why my setup insists in needs to install another instance? My instance name is the same for all applications.
Thanks,
Bill
Bill in one of the previous messages someone from Microsoft mentioned that it is a known bug in the beta version of the toolkit. Hopefully it will be fixed.
goodluck
dev
|||Thanks for the info. Does anyone know when the full release will be out?
sql
Showing posts with label applications. Show all posts
Showing posts with label applications. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
MSDE Security (aka users looking at my apps database)
Is there a way to secure a database on MSDE so that my users cannot be
poking around my applications database? I've been reading up on it and see
that MSDE installs with a mixed security mode.
Does that mean if I secure my database with sql security someone who is an
admin on the machine can look at my database regardless of what I set?
I am concerned that my users (and competition) will try to hack into my
instance and steal my data & data structures so I'm trying to figure out
how I can prevent that. I understand I can encrypt my stored procedure at
least I hope that is still the case with MSDE.
Any thoughts?
Thanks.
This is a desktop app and not a web app btw.
hi Jason,
"Jason" <yo@.yo.com> ha scritto nel messaggio
news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
> This is a desktop app and not a web app btw.
you can only protect stored procedures, views and user define function with
WITH ENCRYPTION in order to hide their text, but for base table you are out
of luck... there's actually non way for preventing sysadmins role members to
dig into your metaschema...
as regard data, that can only be encripted using third parties tools like
http://www.activecrypt.com/index.htm or tools like that
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello,
It is also possible to use SQL autentification, then create only one login
that the user doesn't know.
After that, your application connect as the login you 've just created. (for
example Log = marc PWD = marc)
In you database, you make a login table. This table contain the login of the
user and his password, and your application will test this table to see if
the user can connect. With this method you can even forbid a part of the
application or a time to connect ... easily.
For example UID Andre PWD Andre.
After that, your user will enter the login and password to your application
(Andre/ Andre).
your application connect as marc, see if Andre can login and if Andre can
login, your application can work with the user name marc with the database
(and show the user the login Andre)
So your user will never be able to work on the database as his login is not
a database login
Marc Allard
"Jason" <yo@.yo.com> a crit dans le message de
news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
>
> This is a desktop app and not a web app btw.
>
|||The only way you can lock the data down is to encrypt it. If a user has
Local Admin rights in the OS (NT/2K/XP), then they can see the data anyway,
irrespective of SQL Auth as NT Auth is always available.
Administrator ALWAYS gets to the data!
On Fri, 6 Aug 2004 11:05:29 +0200, Allcomp wrote:
[vbcol=seagreen]
> Hello,
> It is also possible to use SQL autentification, then create only one login
> that the user doesn't know.
> After that, your application connect as the login you 've just created. (for
> example Log = marc PWD = marc)
> In you database, you make a login table. This table contain the login of the
> user and his password, and your application will test this table to see if
> the user can connect. With this method you can even forbid a part of the
> application or a time to connect ... easily.
> For example UID Andre PWD Andre.
> After that, your user will enter the login and password to your application
> (Andre/ Andre).
> your application connect as marc, see if Andre can login and if Andre can
> login, your application can work with the user name marc with the database
> (and show the user the login Andre)
> So your user will never be able to work on the database as his login is not
> a database login
> Marc Allard
>
> "Jason" <yo@.yo.com> a crit dans le message de
> news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
|||Hello,
I didn't know it was possible to connect as Administrator in a sql server
when the installation was mado to allow only SQL autentification. How can
you make it?
Thank you
Marc Allard
"Paul Buxton" <psb@.NOSPAMspireite.demon.co.uk> a crit dans le message de
news:1opgizeso0jib$.ywf1zot73zdg.dlg@.40tude.net...
> The only way you can lock the data down is to encrypt it. If a user has
> Local Admin rights in the OS (NT/2K/XP), then they can see the data
anyway,[vbcol=seagreen]
> irrespective of SQL Auth as NT Auth is always available.
> Administrator ALWAYS gets to the data!
> On Fri, 6 Aug 2004 11:05:29 +0200, Allcomp wrote:
login[vbcol=seagreen]
(for[vbcol=seagreen]
the[vbcol=seagreen]
if[vbcol=seagreen]
application[vbcol=seagreen]
can[vbcol=seagreen]
database[vbcol=seagreen]
not[vbcol=seagreen]
see[vbcol=seagreen]
an[vbcol=seagreen]
out[vbcol=seagreen]
at[vbcol=seagreen]
|||hi,
"Allcomp" <fa097770@.nospam.skynet.be> ha scritto nel messaggio
news:41136323$0$296$ba620e4c@.news.skynet.be...
> Hello,
> I didn't know it was possible to connect as Administrator in a sql server
> when the installation was mado to allow only SQL autentification. How can
> you make it?
just log in in Windows as a member of sysadmins; sysadmis are member of
Builtin\Administrator SQL Server role, which has administrative privileges
by default...
the method you previously exposed only prevents user of YOUR application not
to access that data, but using ad-hoc query tools like QA, oSql or simply
Visual Data Manager (VB3 to VB6 <g>) an administrator can perform whatever
activity...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Only One JASON, FORGET IT.
I have been called in more than once to untangle all sorts of developer
installed security, I do it and will continue to do it.
Developers who think that business data should be locked up from the
Business should be locked up themselves. If your data is proprietary,
then I suggest you create your own encrypted storage system! But give up on
trying to lock the rightful owners of data out from it by denying them
access to the database.
Your schema etc. Might be your work, but locking out legitimate uses of
the data is in my opinion about as quick a way to get your application
dumped as you can get. Companies expect to be able to throw a copy of
Crystal Reports onto a machine and interogate the database for the
information that they want, in the manner that they want it, when they want
it.
As foir competitors using your schema in their own products, you must be
joking! They might however write conversion routines to 'upgrade' from your
product. This is a fairly normal business practice.
You sound like Apple complaining about Real Networks, or an IBM salesman
from the 1970s, telling the customer that MS-Dos on a compatible PC is just
not as good as an IBM PC-XT with PC-Dos for running Lotus 1-2-3
Matt
|||hi Matt,
"Unicorn" <unicorn@.somewhere.com> ha scritto nel messaggio
news:epy96HEfEHA.2604@.TK2MSFTNGP12.phx.gbl...
> Only One JASON, FORGET IT.
> I have been called in more than once to untangle all sorts of developer
> installed security, I do it and will continue to do it.
> Developers who think that business data should be locked up from the
> Business should be locked up themselves. If your data is proprietary,
> then I suggest you create your own encrypted storage system! But give up
on
> trying to lock the rightful owners of data out from it by denying them
> access to the database.
not to start a flame, but just a consideration...
I think it really depends... if you "sell" data, that's to say an aggregated
and/or particular kind of sensible data, perhaps having it not accessible to
external application but your(s), could be a legitimated pray for a
particular protection system, and perhaps external encryption is a way to go
for, as you already pointed out... perhaps not the best as it will be not
integrated.. but acceptable...
the same is true for sensible code you provide in form of stored
procedures/udf/views...
let's think about a genious tool, RAC by SQL Server MVP Thanh Ngo (AKA OJ)..
my understanding is it provides a set of stored procedures to manipulate
data, with unique features like CROSSTAB rotations and so on... this is
valuable code and think is provided as encrypted code... as it should
but you actually have no way to protect your metaschema(s) the same way...
even if SQL Server encryption has been defeated... I do personally think
this could be a valuable feature in some scenario...
> Your schema etc. Might be your work, but locking out legitimate uses of
> the data is in my opinion about as quick a way to get your application
> dumped as you can get. Companies expect to be able to throw a copy of
> Crystal Reports onto a machine and interogate the database for the
> information that they want, in the manner that they want it, when they
want
> it.
this could violate certain EULAs and/or rules, both private and/or
legislative...
recently I've been asked to buy a mailing for german (potential)
customers... the selling company provided a well defined license for 1 use,
n uses of the same data... don't know what kind of database they would
provide as our choice went to mailing labels directly, just for one shot...
but this scenario certainly does not grant you the possibility for multi
server analysis and or use...
another issue... think to privacy protection for sensible data... medical
data... there are both european and USA (as other countries too..) acts that
state and (strictly) discipline the use of this kind of data...
a recent article by Sean Maloney on SQL Server Magazine
(http://www.winnetmag.com/SQLServer/A...731/42731.html for
subscribers only) presents a way to protect data from unlegitimated users
with row level security granularity.. but if you manually bypass that kind
of security (which you can, as a syasdmin) you are elegible for legal
repercussions...
> As foir competitors using your schema in their own products, you must be
> joking! They might however write conversion routines to 'upgrade' from
your
> product. This is a fairly normal business practice.
>
agree =;-D
again... not to flame but just my 2 (euro)cents
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you for your answer
Marc Allard
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> a crit dans le message de
news:2nhjgsFud2mU1@.uni-berlin.de...[vbcol=seagreen]
> hi,
> "Allcomp" <fa097770@.nospam.skynet.be> ha scritto nel messaggio
> news:41136323$0$296$ba620e4c@.news.skynet.be...
server[vbcol=seagreen]
can
> just log in in Windows as a member of sysadmins; sysadmis are member of
> Builtin\Administrator SQL Server role, which has administrative privileges
> by default...
> the method you previously exposed only prevents user of YOUR application
not
> to access that data, but using ad-hoc query tools like QA, oSql or simply
> Visual Data Manager (VB3 to VB6 <g>) an administrator can perform whatever
> activity...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||A possible solution may be to use dbLockdown. It will encrypt ALL (or
selected) database object scripts for stored procedures, triggers, user
defined functions and views in your MSDE database using the WITH
ENCRYPTION clause. The tool will also automatically archive the script
source so you can restore it again at any time. Check out
http://www.ecatenate.com/dblockdown_product_info.html
Regards, Simon
"Jason" <yo@.yo.com> wrote in message news:<#4bvqLoeEHA.3016@.tk2msftngp13.phx.gbl>...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
>
> This is a desktop app and not a web app btw.
poking around my applications database? I've been reading up on it and see
that MSDE installs with a mixed security mode.
Does that mean if I secure my database with sql security someone who is an
admin on the machine can look at my database regardless of what I set?
I am concerned that my users (and competition) will try to hack into my
instance and steal my data & data structures so I'm trying to figure out
how I can prevent that. I understand I can encrypt my stored procedure at
least I hope that is still the case with MSDE.
Any thoughts?
Thanks.
This is a desktop app and not a web app btw.
hi Jason,
"Jason" <yo@.yo.com> ha scritto nel messaggio
news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
> This is a desktop app and not a web app btw.
you can only protect stored procedures, views and user define function with
WITH ENCRYPTION in order to hide their text, but for base table you are out
of luck... there's actually non way for preventing sysadmins role members to
dig into your metaschema...
as regard data, that can only be encripted using third parties tools like
http://www.activecrypt.com/index.htm or tools like that
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello,
It is also possible to use SQL autentification, then create only one login
that the user doesn't know.
After that, your application connect as the login you 've just created. (for
example Log = marc PWD = marc)
In you database, you make a login table. This table contain the login of the
user and his password, and your application will test this table to see if
the user can connect. With this method you can even forbid a part of the
application or a time to connect ... easily.
For example UID Andre PWD Andre.
After that, your user will enter the login and password to your application
(Andre/ Andre).
your application connect as marc, see if Andre can login and if Andre can
login, your application can work with the user name marc with the database
(and show the user the login Andre)
So your user will never be able to work on the database as his login is not
a database login
Marc Allard
"Jason" <yo@.yo.com> a crit dans le message de
news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
>
> This is a desktop app and not a web app btw.
>
|||The only way you can lock the data down is to encrypt it. If a user has
Local Admin rights in the OS (NT/2K/XP), then they can see the data anyway,
irrespective of SQL Auth as NT Auth is always available.
Administrator ALWAYS gets to the data!
On Fri, 6 Aug 2004 11:05:29 +0200, Allcomp wrote:
[vbcol=seagreen]
> Hello,
> It is also possible to use SQL autentification, then create only one login
> that the user doesn't know.
> After that, your application connect as the login you 've just created. (for
> example Log = marc PWD = marc)
> In you database, you make a login table. This table contain the login of the
> user and his password, and your application will test this table to see if
> the user can connect. With this method you can even forbid a part of the
> application or a time to connect ... easily.
> For example UID Andre PWD Andre.
> After that, your user will enter the login and password to your application
> (Andre/ Andre).
> your application connect as marc, see if Andre can login and if Andre can
> login, your application can work with the user name marc with the database
> (and show the user the login Andre)
> So your user will never be able to work on the database as his login is not
> a database login
> Marc Allard
>
> "Jason" <yo@.yo.com> a crit dans le message de
> news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
|||Hello,
I didn't know it was possible to connect as Administrator in a sql server
when the installation was mado to allow only SQL autentification. How can
you make it?
Thank you
Marc Allard
"Paul Buxton" <psb@.NOSPAMspireite.demon.co.uk> a crit dans le message de
news:1opgizeso0jib$.ywf1zot73zdg.dlg@.40tude.net...
> The only way you can lock the data down is to encrypt it. If a user has
> Local Admin rights in the OS (NT/2K/XP), then they can see the data
anyway,[vbcol=seagreen]
> irrespective of SQL Auth as NT Auth is always available.
> Administrator ALWAYS gets to the data!
> On Fri, 6 Aug 2004 11:05:29 +0200, Allcomp wrote:
login[vbcol=seagreen]
(for[vbcol=seagreen]
the[vbcol=seagreen]
if[vbcol=seagreen]
application[vbcol=seagreen]
can[vbcol=seagreen]
database[vbcol=seagreen]
not[vbcol=seagreen]
see[vbcol=seagreen]
an[vbcol=seagreen]
out[vbcol=seagreen]
at[vbcol=seagreen]
|||hi,
"Allcomp" <fa097770@.nospam.skynet.be> ha scritto nel messaggio
news:41136323$0$296$ba620e4c@.news.skynet.be...
> Hello,
> I didn't know it was possible to connect as Administrator in a sql server
> when the installation was mado to allow only SQL autentification. How can
> you make it?
just log in in Windows as a member of sysadmins; sysadmis are member of
Builtin\Administrator SQL Server role, which has administrative privileges
by default...
the method you previously exposed only prevents user of YOUR application not
to access that data, but using ad-hoc query tools like QA, oSql or simply
Visual Data Manager (VB3 to VB6 <g>) an administrator can perform whatever
activity...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Only One JASON, FORGET IT.
I have been called in more than once to untangle all sorts of developer
installed security, I do it and will continue to do it.
Developers who think that business data should be locked up from the
Business should be locked up themselves. If your data is proprietary,
then I suggest you create your own encrypted storage system! But give up on
trying to lock the rightful owners of data out from it by denying them
access to the database.
Your schema etc. Might be your work, but locking out legitimate uses of
the data is in my opinion about as quick a way to get your application
dumped as you can get. Companies expect to be able to throw a copy of
Crystal Reports onto a machine and interogate the database for the
information that they want, in the manner that they want it, when they want
it.
As foir competitors using your schema in their own products, you must be
joking! They might however write conversion routines to 'upgrade' from your
product. This is a fairly normal business practice.
You sound like Apple complaining about Real Networks, or an IBM salesman
from the 1970s, telling the customer that MS-Dos on a compatible PC is just
not as good as an IBM PC-XT with PC-Dos for running Lotus 1-2-3
Matt
|||hi Matt,
"Unicorn" <unicorn@.somewhere.com> ha scritto nel messaggio
news:epy96HEfEHA.2604@.TK2MSFTNGP12.phx.gbl...
> Only One JASON, FORGET IT.
> I have been called in more than once to untangle all sorts of developer
> installed security, I do it and will continue to do it.
> Developers who think that business data should be locked up from the
> Business should be locked up themselves. If your data is proprietary,
> then I suggest you create your own encrypted storage system! But give up
on
> trying to lock the rightful owners of data out from it by denying them
> access to the database.
not to start a flame, but just a consideration...
I think it really depends... if you "sell" data, that's to say an aggregated
and/or particular kind of sensible data, perhaps having it not accessible to
external application but your(s), could be a legitimated pray for a
particular protection system, and perhaps external encryption is a way to go
for, as you already pointed out... perhaps not the best as it will be not
integrated.. but acceptable...
the same is true for sensible code you provide in form of stored
procedures/udf/views...
let's think about a genious tool, RAC by SQL Server MVP Thanh Ngo (AKA OJ)..
my understanding is it provides a set of stored procedures to manipulate
data, with unique features like CROSSTAB rotations and so on... this is
valuable code and think is provided as encrypted code... as it should
but you actually have no way to protect your metaschema(s) the same way...
even if SQL Server encryption has been defeated... I do personally think
this could be a valuable feature in some scenario...
> Your schema etc. Might be your work, but locking out legitimate uses of
> the data is in my opinion about as quick a way to get your application
> dumped as you can get. Companies expect to be able to throw a copy of
> Crystal Reports onto a machine and interogate the database for the
> information that they want, in the manner that they want it, when they
want
> it.
this could violate certain EULAs and/or rules, both private and/or
legislative...
recently I've been asked to buy a mailing for german (potential)
customers... the selling company provided a well defined license for 1 use,
n uses of the same data... don't know what kind of database they would
provide as our choice went to mailing labels directly, just for one shot...
but this scenario certainly does not grant you the possibility for multi
server analysis and or use...
another issue... think to privacy protection for sensible data... medical
data... there are both european and USA (as other countries too..) acts that
state and (strictly) discipline the use of this kind of data...
a recent article by Sean Maloney on SQL Server Magazine
(http://www.winnetmag.com/SQLServer/A...731/42731.html for
subscribers only) presents a way to protect data from unlegitimated users
with row level security granularity.. but if you manually bypass that kind
of security (which you can, as a syasdmin) you are elegible for legal
repercussions...
> As foir competitors using your schema in their own products, you must be
> joking! They might however write conversion routines to 'upgrade' from
your
> product. This is a fairly normal business practice.
>
agree =;-D
again... not to flame but just my 2 (euro)cents
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you for your answer
Marc Allard
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> a crit dans le message de
news:2nhjgsFud2mU1@.uni-berlin.de...[vbcol=seagreen]
> hi,
> "Allcomp" <fa097770@.nospam.skynet.be> ha scritto nel messaggio
> news:41136323$0$296$ba620e4c@.news.skynet.be...
server[vbcol=seagreen]
can
> just log in in Windows as a member of sysadmins; sysadmis are member of
> Builtin\Administrator SQL Server role, which has administrative privileges
> by default...
> the method you previously exposed only prevents user of YOUR application
not
> to access that data, but using ad-hoc query tools like QA, oSql or simply
> Visual Data Manager (VB3 to VB6 <g>) an administrator can perform whatever
> activity...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||A possible solution may be to use dbLockdown. It will encrypt ALL (or
selected) database object scripts for stored procedures, triggers, user
defined functions and views in your MSDE database using the WITH
ENCRYPTION clause. The tool will also automatically archive the script
source so you can restore it again at any time. Check out
http://www.ecatenate.com/dblockdown_product_info.html
Regards, Simon
"Jason" <yo@.yo.com> wrote in message news:<#4bvqLoeEHA.3016@.tk2msftngp13.phx.gbl>...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
>
> This is a desktop app and not a web app btw.
MSDE running on same machine as SQL Sever 2000?
Hi,
I currently have 2 instances of MSDE running on a server to support two
different applications. We have decided to obtain the full SQL 2000 std for
another project. Can SQL Server 2000 run on the same machine as Server MSDE?
Will I need to migrate the existing databases that are currently using MSDE
to SQL Server 2000 once it is installed?
Thanks
You CAN run MSDE and another edition on the same machine.
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Jedi Dave" <Jedi Dave@.discussions.microsoft.com> wrote in message
news:748798E1-F1A2-4F2B-8C81-30CD70B19F68@.microsoft.com...
> Hi,
> I currently have 2 instances of MSDE running on a server to support two
> different applications. We have decided to obtain the full SQL 2000 std
> for
> another project. Can SQL Server 2000 run on the same machine as Server
> MSDE?
> Will I need to migrate the existing databases that are currently using
> MSDE
> to SQL Server 2000 once it is installed?
> Thanks
sql
I currently have 2 instances of MSDE running on a server to support two
different applications. We have decided to obtain the full SQL 2000 std for
another project. Can SQL Server 2000 run on the same machine as Server MSDE?
Will I need to migrate the existing databases that are currently using MSDE
to SQL Server 2000 once it is installed?
Thanks
You CAN run MSDE and another edition on the same machine.
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Jedi Dave" <Jedi Dave@.discussions.microsoft.com> wrote in message
news:748798E1-F1A2-4F2B-8C81-30CD70B19F68@.microsoft.com...
> Hi,
> I currently have 2 instances of MSDE running on a server to support two
> different applications. We have decided to obtain the full SQL 2000 std
> for
> another project. Can SQL Server 2000 run on the same machine as Server
> MSDE?
> Will I need to migrate the existing databases that are currently using
> MSDE
> to SQL Server 2000 once it is installed?
> Thanks
sql
Wednesday, March 21, 2012
MSDE on a Dedicated Webserver
Hi, our company is running a couple of java based applications on a dedicated webserver. We are interested in running the Rainbow Portal on this server as well (as a public website), but the actual owner of the server doesn't want to outlay the cash for S
QL Server at the moment. Would it be legal for us to install MSDE on this webserver to use as the database engine for the Rainbow Portal? (bearing in mind that it's a dedicated webserver, and that there would only be one instance of MSDE, and probably onl
y one database)
Sounds like it would be ok, but check the information at this link.
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
Jim
"Nicholas Smeaton" <nsmeaton@.footbag.org> wrote in message
news:89AA18C5-9A3B-47CE-914B-9DC0263196BD@.microsoft.com...
> Hi, our company is running a couple of java based applications on a
dedicated webserver. We are interested in running the Rainbow Portal on this
server as well (as a public website), but the actual owner of the server
doesn't want to outlay the cash for SQL Server at the moment. Would it be
legal for us to install MSDE on this webserver to use as the database engine
for the Rainbow Portal? (bearing in mind that it's a dedicated webserver,
and that there would only be one instance of MSDE, and probably only one
database)
|||Thanks Jim, but I'm still a bit hazy on the details. The "Appropriate Uses of MSDE FAQ" page says it's appropriate to use it as a database for a website, but the EULA says: "NO RENTAL/COMMERCIAL HOSTING". Seems a bit contradictory, and I need to be absolu
tely sure. I guess it'll be the owner of the dedicated webserver that'll be offering it to our company, but they won't be charging us to use it, and we'll be the only one's using it. It *sounds* like it should be ok, but can someone give me a definitive y
ea or nay?
|||IMHO u cant legally use MSDE in this situation
"Nicholas Smeaton" <nsmeaton@.footbag.org> wrote in message
news:89AA18C5-9A3B-47CE-914B-9DC0263196BD@.microsoft.com...
> Hi, our company is running a couple of java based applications on a
dedicated webserver. We are interested in running the Rainbow Portal on this
server as well (as a public website), but the actual owner of the server
doesn't want to outlay the cash for SQL Server at the moment. Would it be
legal for us to install MSDE on this webserver to use as the database engine
for the Rainbow Portal? (bearing in mind that it's a dedicated webserver,
and that there would only be one instance of MSDE, and probably only one
database)
|||John,
MS changed licensing for MSDE a while ago. Nowadays, it is "free". As far as I can read below URL, using MSDE
in the scenario described would be OK...
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"John Smith" <a__@.abv.bg> wrote in message news:uEW7yg0NEHA.3672@.TK2MSFTNGP11.phx.gbl...
> IMHO u cant legally use MSDE in this situation
>
> "Nicholas Smeaton" <nsmeaton@.footbag.org> wrote in message
> news:89AA18C5-9A3B-47CE-914B-9DC0263196BD@.microsoft.com...
> dedicated webserver. We are interested in running the Rainbow Portal on this
> server as well (as a public website), but the actual owner of the server
> doesn't want to outlay the cash for SQL Server at the moment. Would it be
> legal for us to install MSDE on this webserver to use as the database engine
> for the Rainbow Portal? (bearing in mind that it's a dedicated webserver,
> and that there would only be one instance of MSDE, and probably only one
> database)
>
|||but what about this: "
Q. How do I acquire rights to deploy MSDE throughout my company?
A. The following products allow you to deploy MSDE throughout your
organization:
a.. MSDN Universal, Enterprise, and Professional subscriptions
b.. SQL Server 2000 Developer, Standard, and Enterprise Editions
c.. Visual Studio .NET Architect, Developer, and Professional
Editions
d.. Visual FoxPro 7.0 or 8.0
Note: Microsoft Access only provides rights to use MSDE on the device
on which Microsoft Access is installed.
"
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oxouso0NEHA.3264@.tk2msftngp13.phx.gbl...
> John,
> MS changed licensing for MSDE a while ago. Nowadays, it is "free". As far
as I can read below URL, using MSDE
> in the scenario described would be OK...
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "John Smith" <a__@.abv.bg> wrote in message
news:uEW7yg0NEHA.3672@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
this[vbcol=seagreen]
be[vbcol=seagreen]
engine[vbcol=seagreen]
webserver,
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Yes, I asked MS to clarify that point, something they apparently didn't do. My assumption is that it is either
a leftover or it refers to re-distributing within your own organization...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"John Smith" <a__@.abv.bg> wrote in message news:eYfrXi%23NEHA.3348@.TK2MSFTNGP09.phx.gbl...
> but what about this: "
> Q. How do I acquire rights to deploy MSDE throughout my company?
> A. The following products allow you to deploy MSDE throughout your
> organization:
> a.. MSDN Universal, Enterprise, and Professional subscriptions
> b.. SQL Server 2000 Developer, Standard, and Enterprise Editions
> c.. Visual Studio .NET Architect, Developer, and Professional
> Editions
> d.. Visual FoxPro 7.0 or 8.0
> Note: Microsoft Access only provides rights to use MSDE on the device
> on which Microsoft Access is installed.
> "
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:Oxouso0NEHA.3264@.tk2msftngp13.phx.gbl...
> as I can read below URL, using MSDE
> news:uEW7yg0NEHA.3672@.TK2MSFTNGP11.phx.gbl...
> this
> be
> engine
> webserver,
>
>
|||if u get an answer post it here plz
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OB2Hqx%23NEHA.3012@.tk2msftngp13.phx.gbl...
> Yes, I asked MS to clarify that point, something they apparently didn't
do. My assumption is that it is either
> a leftover or it refers to re-distributing within your own organization...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
|||I asked again last week, but I didn't get a reply yet. Probably an MS representative or below is the best bet:
"To speak to someone regarding licensing:
You can call 1-800-426-9400 (select option 4), Monday through Friday, 6:00
A.M. to 6:00 P.M. (PST) to speak directly to a Microsoft licensing
specialist for licensing problem. Worldwide customers can use the Guide to
Worldwide Microsoft Licensing Sites
http://www.microsoft.com/licensing/index/worldwide.asp to find contact
information in their locations."
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Smith" <a__@.abv.bg> wrote in message news:%23aOzQ0%23NEHA.4036@.TK2MSFTNGP12.phx.gbl...
> if u get an answer post it here plz
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:OB2Hqx%23NEHA.3012@.tk2msftngp13.phx.gbl...
> do. My assumption is that it is either
>
QL Server at the moment. Would it be legal for us to install MSDE on this webserver to use as the database engine for the Rainbow Portal? (bearing in mind that it's a dedicated webserver, and that there would only be one instance of MSDE, and probably onl
y one database)
Sounds like it would be ok, but check the information at this link.
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
Jim
"Nicholas Smeaton" <nsmeaton@.footbag.org> wrote in message
news:89AA18C5-9A3B-47CE-914B-9DC0263196BD@.microsoft.com...
> Hi, our company is running a couple of java based applications on a
dedicated webserver. We are interested in running the Rainbow Portal on this
server as well (as a public website), but the actual owner of the server
doesn't want to outlay the cash for SQL Server at the moment. Would it be
legal for us to install MSDE on this webserver to use as the database engine
for the Rainbow Portal? (bearing in mind that it's a dedicated webserver,
and that there would only be one instance of MSDE, and probably only one
database)
|||Thanks Jim, but I'm still a bit hazy on the details. The "Appropriate Uses of MSDE FAQ" page says it's appropriate to use it as a database for a website, but the EULA says: "NO RENTAL/COMMERCIAL HOSTING". Seems a bit contradictory, and I need to be absolu
tely sure. I guess it'll be the owner of the dedicated webserver that'll be offering it to our company, but they won't be charging us to use it, and we'll be the only one's using it. It *sounds* like it should be ok, but can someone give me a definitive y
ea or nay?
|||IMHO u cant legally use MSDE in this situation
"Nicholas Smeaton" <nsmeaton@.footbag.org> wrote in message
news:89AA18C5-9A3B-47CE-914B-9DC0263196BD@.microsoft.com...
> Hi, our company is running a couple of java based applications on a
dedicated webserver. We are interested in running the Rainbow Portal on this
server as well (as a public website), but the actual owner of the server
doesn't want to outlay the cash for SQL Server at the moment. Would it be
legal for us to install MSDE on this webserver to use as the database engine
for the Rainbow Portal? (bearing in mind that it's a dedicated webserver,
and that there would only be one instance of MSDE, and probably only one
database)
|||John,
MS changed licensing for MSDE a while ago. Nowadays, it is "free". As far as I can read below URL, using MSDE
in the scenario described would be OK...
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"John Smith" <a__@.abv.bg> wrote in message news:uEW7yg0NEHA.3672@.TK2MSFTNGP11.phx.gbl...
> IMHO u cant legally use MSDE in this situation
>
> "Nicholas Smeaton" <nsmeaton@.footbag.org> wrote in message
> news:89AA18C5-9A3B-47CE-914B-9DC0263196BD@.microsoft.com...
> dedicated webserver. We are interested in running the Rainbow Portal on this
> server as well (as a public website), but the actual owner of the server
> doesn't want to outlay the cash for SQL Server at the moment. Would it be
> legal for us to install MSDE on this webserver to use as the database engine
> for the Rainbow Portal? (bearing in mind that it's a dedicated webserver,
> and that there would only be one instance of MSDE, and probably only one
> database)
>
|||but what about this: "
Q. How do I acquire rights to deploy MSDE throughout my company?
A. The following products allow you to deploy MSDE throughout your
organization:
a.. MSDN Universal, Enterprise, and Professional subscriptions
b.. SQL Server 2000 Developer, Standard, and Enterprise Editions
c.. Visual Studio .NET Architect, Developer, and Professional
Editions
d.. Visual FoxPro 7.0 or 8.0
Note: Microsoft Access only provides rights to use MSDE on the device
on which Microsoft Access is installed.
"
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oxouso0NEHA.3264@.tk2msftngp13.phx.gbl...
> John,
> MS changed licensing for MSDE a while ago. Nowadays, it is "free". As far
as I can read below URL, using MSDE
> in the scenario described would be OK...
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "John Smith" <a__@.abv.bg> wrote in message
news:uEW7yg0NEHA.3672@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
this[vbcol=seagreen]
be[vbcol=seagreen]
engine[vbcol=seagreen]
webserver,
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Yes, I asked MS to clarify that point, something they apparently didn't do. My assumption is that it is either
a leftover or it refers to re-distributing within your own organization...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"John Smith" <a__@.abv.bg> wrote in message news:eYfrXi%23NEHA.3348@.TK2MSFTNGP09.phx.gbl...
> but what about this: "
> Q. How do I acquire rights to deploy MSDE throughout my company?
> A. The following products allow you to deploy MSDE throughout your
> organization:
> a.. MSDN Universal, Enterprise, and Professional subscriptions
> b.. SQL Server 2000 Developer, Standard, and Enterprise Editions
> c.. Visual Studio .NET Architect, Developer, and Professional
> Editions
> d.. Visual FoxPro 7.0 or 8.0
> Note: Microsoft Access only provides rights to use MSDE on the device
> on which Microsoft Access is installed.
> "
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:Oxouso0NEHA.3264@.tk2msftngp13.phx.gbl...
> as I can read below URL, using MSDE
> news:uEW7yg0NEHA.3672@.TK2MSFTNGP11.phx.gbl...
> this
> be
> engine
> webserver,
>
>
|||if u get an answer post it here plz
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OB2Hqx%23NEHA.3012@.tk2msftngp13.phx.gbl...
> Yes, I asked MS to clarify that point, something they apparently didn't
do. My assumption is that it is either
> a leftover or it refers to re-distributing within your own organization...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
|||I asked again last week, but I didn't get a reply yet. Probably an MS representative or below is the best bet:
"To speak to someone regarding licensing:
You can call 1-800-426-9400 (select option 4), Monday through Friday, 6:00
A.M. to 6:00 P.M. (PST) to speak directly to a Microsoft licensing
specialist for licensing problem. Worldwide customers can use the Guide to
Worldwide Microsoft Licensing Sites
http://www.microsoft.com/licensing/index/worldwide.asp to find contact
information in their locations."
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Smith" <a__@.abv.bg> wrote in message news:%23aOzQ0%23NEHA.4036@.TK2MSFTNGP12.phx.gbl...
> if u get an answer post it here plz
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:OB2Hqx%23NEHA.3012@.tk2msftngp13.phx.gbl...
> do. My assumption is that it is either
>
Monday, March 19, 2012
MSDE management
When I install msde on a W2K professional and go into My Computer/manage and
click on Services and Applications, it shows a MS Sql Server entry from which
I can manage msde. When I install on W2003 server, it's not there. Is this
by design ?
hi,
Dave Mc wrote:
> When I install msde on a W2K professional and go into My
> Computer/manage and click on Services and Applications, it shows a MS
> Sql Server entry from which I can manage msde. When I install on
> W2003 server, it's not there. Is this by design ?
Start -> Administrative Tools-> Services
Start -> Control Panel-> Administrative Tools-> Services
Start -> All Programs-> Administrative Tools-> Services
Start -> My Computer-> Change a setting-> Administrative Tools-> Services
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I guess I didn't make it clear. The service is there on my W2003 server.
What's different is on my W2k pro, under My Computer/Manage/Services and
Applications, It shows Microsoft SQL Servers/MYLOCALSERVER/ then all the
"normal" Enterprise Manager items -- Databases, Maintenance Plans, etc. As
far as I know, MSDE is the only SQL ever installed on my workstation. When I
do an MSDE install on the server, though, the service is there and running
but I don't get the management tools as above. I was surprised when I saw
them on my workstation because I thought to manage msde, you were either
stuck with command line osql statements or third party "Enterprise Manager
like" management tools. So, I'm a little confused.
Thanks
"Andrea Montanari" wrote:
> hi,
> Dave Mc wrote:
> Start -> Administrative Tools-> Services
> Start -> Control Panel-> Administrative Tools-> Services
> Start -> All Programs-> Administrative Tools-> Services
> Start -> My Computer-> Change a setting-> Administrative Tools-> Services
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Dave,
Dave Mc wrote:
> I guess I didn't make it clear. The service is there on my W2003
> server. What's different is on my W2k pro, under My
> Computer/Manage/Services and Applications, It shows Microsoft SQL
> Servers/MYLOCALSERVER/ then all the "normal" Enterprise Manager
> items -- Databases, Maintenance Plans, etc. As far as I know, MSDE
> is the only SQL ever installed on my workstation. When I do an MSDE
> install on the server, though, the service is there and running but
> I don't get the management tools as above. I was surprised when I
> saw them on my workstation because I thought to manage msde, you were
> either stuck with command line osql statements or third party
> "Enterprise Manager like" management tools. So, I'm a little
> confused.
> Thanks
MSDE comes with no management tool but oSql.exe, the command line tool, full
stop.
if you find them on your pc(s), they have been arbitrarily installed by the
SQL Server CD-Rom and no other way..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||You are right. I did some more checking and found that someone had been
doing development on this pc and installed sql 2000 from their msdn cd. Now,
my question is, am I violating a license agreement if I just install Client
Tools from a SQL cd even though I am only installing msde ?
Thanks
"Andrea Montanari" wrote:
> hi Dave,
> Dave Mc wrote:
> MSDE comes with no management tool but oSql.exe, the command line tool, full
> stop.
> if you find them on your pc(s), they have been arbitrarily installed by the
> SQL Server CD-Rom and no other way..
>
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Dave,
Dave Mc wrote:
> You are right. I did some more checking and found that someone had
> been doing development on this pc and installed sql 2000 from their
> msdn cd. Now, my question is, am I violating a license agreement if
> I just install Client Tools from a SQL cd even though I am only
> installing msde ?
AFAIK, unfortunately YES...
in order to manage MSDE instance, you can only rely on self made tools or
third arty tools, but not on SQL Server Client Tools..
please have a look at this post, http://tinyurl.com/4u2zh , by a Microsoft
representative
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
click on Services and Applications, it shows a MS Sql Server entry from which
I can manage msde. When I install on W2003 server, it's not there. Is this
by design ?
hi,
Dave Mc wrote:
> When I install msde on a W2K professional and go into My
> Computer/manage and click on Services and Applications, it shows a MS
> Sql Server entry from which I can manage msde. When I install on
> W2003 server, it's not there. Is this by design ?
Start -> Administrative Tools-> Services
Start -> Control Panel-> Administrative Tools-> Services
Start -> All Programs-> Administrative Tools-> Services
Start -> My Computer-> Change a setting-> Administrative Tools-> Services
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I guess I didn't make it clear. The service is there on my W2003 server.
What's different is on my W2k pro, under My Computer/Manage/Services and
Applications, It shows Microsoft SQL Servers/MYLOCALSERVER/ then all the
"normal" Enterprise Manager items -- Databases, Maintenance Plans, etc. As
far as I know, MSDE is the only SQL ever installed on my workstation. When I
do an MSDE install on the server, though, the service is there and running
but I don't get the management tools as above. I was surprised when I saw
them on my workstation because I thought to manage msde, you were either
stuck with command line osql statements or third party "Enterprise Manager
like" management tools. So, I'm a little confused.
Thanks
"Andrea Montanari" wrote:
> hi,
> Dave Mc wrote:
> Start -> Administrative Tools-> Services
> Start -> Control Panel-> Administrative Tools-> Services
> Start -> All Programs-> Administrative Tools-> Services
> Start -> My Computer-> Change a setting-> Administrative Tools-> Services
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Dave,
Dave Mc wrote:
> I guess I didn't make it clear. The service is there on my W2003
> server. What's different is on my W2k pro, under My
> Computer/Manage/Services and Applications, It shows Microsoft SQL
> Servers/MYLOCALSERVER/ then all the "normal" Enterprise Manager
> items -- Databases, Maintenance Plans, etc. As far as I know, MSDE
> is the only SQL ever installed on my workstation. When I do an MSDE
> install on the server, though, the service is there and running but
> I don't get the management tools as above. I was surprised when I
> saw them on my workstation because I thought to manage msde, you were
> either stuck with command line osql statements or third party
> "Enterprise Manager like" management tools. So, I'm a little
> confused.
> Thanks
MSDE comes with no management tool but oSql.exe, the command line tool, full
stop.
if you find them on your pc(s), they have been arbitrarily installed by the
SQL Server CD-Rom and no other way..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||You are right. I did some more checking and found that someone had been
doing development on this pc and installed sql 2000 from their msdn cd. Now,
my question is, am I violating a license agreement if I just install Client
Tools from a SQL cd even though I am only installing msde ?
Thanks
"Andrea Montanari" wrote:
> hi Dave,
> Dave Mc wrote:
> MSDE comes with no management tool but oSql.exe, the command line tool, full
> stop.
> if you find them on your pc(s), they have been arbitrarily installed by the
> SQL Server CD-Rom and no other way..
>
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Dave,
Dave Mc wrote:
> You are right. I did some more checking and found that someone had
> been doing development on this pc and installed sql 2000 from their
> msdn cd. Now, my question is, am I violating a license agreement if
> I just install Client Tools from a SQL cd even though I am only
> installing msde ?
AFAIK, unfortunately YES...
in order to manage MSDE instance, you can only rely on self made tools or
third arty tools, but not on SQL Server Client Tools..
please have a look at this post, http://tinyurl.com/4u2zh , by a Microsoft
representative
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Monday, March 12, 2012
MSDE Lockdown scripts
We are installing MSDE along with one of our applications.
But with the current security threats, we want to make sure
that the installed MSDE is secure. So is there any lock
down scripts available publicly that can be used for the same.
Thanks in Advance.
hi,
"Arunkumar Viswanathan" <anonymous@.discussions.microsoft.com> ha scritto nel
messaggio news:012101c4904c$0eea0af0$a401280a@.phx.gbl...
> We are installing MSDE along with one of our applications.
> But with the current security threats, we want to make sure
> that the installed MSDE is secure. So is there any lock
> down scripts available publicly that can be used for the same.
not that I'm aware of... anyway, MSDE installs by default disabling network
protocols and with Windows NT authentication only... you only have to set a
strong "sa" password...
this is the *standard*, and should be quite secure... but usually you will
need remote connections (which require TCP/IP or other preferred network
protocol to be enabled) ... if you do not need SQL Server authenticated
connections, you can go with the default "trusted" only...
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
|||Hi Andrea,
Thanks for replying. As you rightly said the we have to
provide a strong password to the sa user. But generally in
a stand alone MSDE installation some stored procedures are
given public previleges and that can cause problems with
advanced users. So if you of know of any lock down scripts
pls post the link here.
Thanks
Arunkumar
>--Original Message--
>not that I'm aware of... anyway, MSDE installs by default
disabling network
>protocols and with Windows NT authentication only... you
only have to set a
>strong "sa" password...
>this is the *standard*, and should be quite secure... but
usually you will
>need remote connections (which require TCP/IP or other
preferred network
>protocol to be enabled) ... if you do not need SQL Server
authenticated
>connections, you can go with the default "trusted" only...
>--
>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
>.
>
|||hi Arunkumar,
<anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:452d01c49052$8853d550$a601280a@.phx.gbl...
> Hi Andrea,
> Thanks for replying. As you rightly said the we have to
> provide a strong password to the sa user. But generally in
> a stand alone MSDE installation some stored procedures are
> given public previleges and that can cause problems with
> advanced users. So if you of know of any lock down scripts
> pls post the link here.
again... unfortunately I do not know one :-(
but, again, it all depends on what you want to secure...
if you mean system stored procedures, usually (at least the problematic,
like xp_cmdshell and so on) they are "protected" requiring sysadmins
privileges
on the other side, if you mena your own procedures, it' up to you to remove
"guest" permission to them =;-D
so I usually remove guest login and deny public involvement... and I do
manage privileges in user's groups...
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
But with the current security threats, we want to make sure
that the installed MSDE is secure. So is there any lock
down scripts available publicly that can be used for the same.
Thanks in Advance.
hi,
"Arunkumar Viswanathan" <anonymous@.discussions.microsoft.com> ha scritto nel
messaggio news:012101c4904c$0eea0af0$a401280a@.phx.gbl...
> We are installing MSDE along with one of our applications.
> But with the current security threats, we want to make sure
> that the installed MSDE is secure. So is there any lock
> down scripts available publicly that can be used for the same.
not that I'm aware of... anyway, MSDE installs by default disabling network
protocols and with Windows NT authentication only... you only have to set a
strong "sa" password...
this is the *standard*, and should be quite secure... but usually you will
need remote connections (which require TCP/IP or other preferred network
protocol to be enabled) ... if you do not need SQL Server authenticated
connections, you can go with the default "trusted" only...
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
|||Hi Andrea,
Thanks for replying. As you rightly said the we have to
provide a strong password to the sa user. But generally in
a stand alone MSDE installation some stored procedures are
given public previleges and that can cause problems with
advanced users. So if you of know of any lock down scripts
pls post the link here.
Thanks
Arunkumar
>--Original Message--
>not that I'm aware of... anyway, MSDE installs by default
disabling network
>protocols and with Windows NT authentication only... you
only have to set a
>strong "sa" password...
>this is the *standard*, and should be quite secure... but
usually you will
>need remote connections (which require TCP/IP or other
preferred network
>protocol to be enabled) ... if you do not need SQL Server
authenticated
>connections, you can go with the default "trusted" only...
>--
>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
>.
>
|||hi Arunkumar,
<anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:452d01c49052$8853d550$a601280a@.phx.gbl...
> Hi Andrea,
> Thanks for replying. As you rightly said the we have to
> provide a strong password to the sa user. But generally in
> a stand alone MSDE installation some stored procedures are
> given public previleges and that can cause problems with
> advanced users. So if you of know of any lock down scripts
> pls post the link here.
again... unfortunately I do not know one :-(
but, again, it all depends on what you want to secure...
if you mean system stored procedures, usually (at least the problematic,
like xp_cmdshell and so on) they are "protected" requiring sysadmins
privileges
on the other side, if you mena your own procedures, it' up to you to remove
"guest" permission to them =;-D
so I usually remove guest login and deny public involvement... and I do
manage privileges in user's groups...
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
Wednesday, March 7, 2012
MSDE Installation Confusion
I recently obtained Visual C++ .NET 2003, and am under the impression that I
have to install MSDE to provide SQL support for applications I write.
Do I need to install SQLServer as well? (None of the documentation I have
read so far says so, but some comments I have read make me want
confirmation).
Regards
Dave
Hi Dave,
If you have SQL Server, you have no need to install the MSDE. The MSDE is
basically a cut-down SQL Server mostly used for deployment with apps where
the client doesn't have SQL Server. For development, you should use the
Developer Edition of SQL Server.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Dave Bolt" <dave@.NO_SPAM_PLEASE_davebolt.fsnet.co.uk> wrote in message
news:usPPlBk5EHA.2012@.TK2MSFTNGP15.phx.gbl...
>I recently obtained Visual C++ .NET 2003, and am under the impression that
>I have to install MSDE to provide SQL support for applications I write.
> Do I need to install SQLServer as well? (None of the documentation I have
> read so far says so, but some comments I have read make me want
> confirmation).
> Regards
> Dave
>
|||Thanks lots for that clarification.
Regards
Dave
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:%23wWf3Xl5EHA.1264@.TK2MSFTNGP12.phx.gbl...
> Hi Dave,
> If you have SQL Server, you have no need to install the MSDE. The MSDE is
> basically a cut-down SQL Server mostly used for deployment with apps where
> the client doesn't have SQL Server. For development, you should use the
> Developer Edition of SQL Server.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Dave Bolt" <dave@.NO_SPAM_PLEASE_davebolt.fsnet.co.uk> wrote in message
> news:usPPlBk5EHA.2012@.TK2MSFTNGP15.phx.gbl...
>
have to install MSDE to provide SQL support for applications I write.
Do I need to install SQLServer as well? (None of the documentation I have
read so far says so, but some comments I have read make me want
confirmation).
Regards
Dave
Hi Dave,
If you have SQL Server, you have no need to install the MSDE. The MSDE is
basically a cut-down SQL Server mostly used for deployment with apps where
the client doesn't have SQL Server. For development, you should use the
Developer Edition of SQL Server.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Dave Bolt" <dave@.NO_SPAM_PLEASE_davebolt.fsnet.co.uk> wrote in message
news:usPPlBk5EHA.2012@.TK2MSFTNGP15.phx.gbl...
>I recently obtained Visual C++ .NET 2003, and am under the impression that
>I have to install MSDE to provide SQL support for applications I write.
> Do I need to install SQLServer as well? (None of the documentation I have
> read so far says so, but some comments I have read make me want
> confirmation).
> Regards
> Dave
>
|||Thanks lots for that clarification.
Regards
Dave
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:%23wWf3Xl5EHA.1264@.TK2MSFTNGP12.phx.gbl...
> Hi Dave,
> If you have SQL Server, you have no need to install the MSDE. The MSDE is
> basically a cut-down SQL Server mostly used for deployment with apps where
> the client doesn't have SQL Server. For development, you should use the
> Developer Edition of SQL Server.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Dave Bolt" <dave@.NO_SPAM_PLEASE_davebolt.fsnet.co.uk> wrote in message
> news:usPPlBk5EHA.2012@.TK2MSFTNGP15.phx.gbl...
>
Monday, February 20, 2012
MSDE for web applications
Hi, I am needing help on which MSDE version support 25 concurrent users. Can anyone help?
Creating an intranet that I would like to run on msde. My problem is that it wont allow more than one person to access the intranet at a time.
MSDE is running on windows 2000 with IIS.How do you know that MSDE is only allowing one person to access your intranet? Is there an error message it is throwing? If so what is it and how are you calling the data (maybe show us some code samples)?
Subscribe to:
Posts (Atom)