Hello there,
i have a great doubt: does MSDE run on XP Tablet Edition? I bought a beautiful notebook but didn't notice that it runs XP tablet...
Thanks in advance
Yes it does
Showing posts with label msde. Show all posts
Showing posts with label msde. Show all posts
Thursday, March 29, 2012
Sunday, March 25, 2012
Does SQL Express have a Simultaneous Connections Limit?
I have used MSDE in the past & it had a limit on the number of simultaneous
connections per the Microsoft paid support folks. I found various articles
on SQL Express with the limitations but nothing referencing the number of
connections. Has anyone already found this out?"BCW" <nospam@.cfl.rr.com> wrote in message
news:uiyafD9PGHA.2912@.tk2msftngp13.phx.gbl...
>I have used MSDE in the past & it had a limit on the number of
>simultaneous
> connections per the Microsoft paid support folks. I found various
> articles
> on SQL Express with the limitations but nothing referencing the number of
> connections. Has anyone already found this out?
There is no limitation on connections in MSDE or in SQL Express. MSDE was
optimized for a "typical" load of upto 25 users I believe but this wasn't a
hard limit it was just a potential throttle on scalability. AFAIK there is
no such constraint on SQL Express. If you check out the feature comparison
however you'll see that Express supports only a single processor and 1GB
RAM. So those are the limits you have to work within:
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
connections per the Microsoft paid support folks. I found various articles
on SQL Express with the limitations but nothing referencing the number of
connections. Has anyone already found this out?"BCW" <nospam@.cfl.rr.com> wrote in message
news:uiyafD9PGHA.2912@.tk2msftngp13.phx.gbl...
>I have used MSDE in the past & it had a limit on the number of
>simultaneous
> connections per the Microsoft paid support folks. I found various
> articles
> on SQL Express with the limitations but nothing referencing the number of
> connections. Has anyone already found this out?
There is no limitation on connections in MSDE or in SQL Express. MSDE was
optimized for a "typical" load of upto 25 users I believe but this wasn't a
hard limit it was just a potential throttle on scalability. AFAIK there is
no such constraint on SQL Express. If you check out the feature comparison
however you'll see that Express supports only a single processor and 1GB
RAM. So those are the limits you have to work within:
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Does SQL Express have a Simultaneous Connections Limit?
I have used MSDE in the past & it had a limit on the number of simultaneous
connections per the Microsoft paid support folks. I found various articles
on SQL Express with the limitations but nothing referencing the number of
connections. Has anyone already found this out?
"BCW" <nospam@.cfl.rr.com> wrote in message
news:uiyafD9PGHA.2912@.tk2msftngp13.phx.gbl...
>I have used MSDE in the past & it had a limit on the number of
>simultaneous
> connections per the Microsoft paid support folks. I found various
> articles
> on SQL Express with the limitations but nothing referencing the number of
> connections. Has anyone already found this out?
There is no limitation on connections in MSDE or in SQL Express. MSDE was
optimized for a "typical" load of upto 25 users I believe but this wasn't a
hard limit it was just a potential throttle on scalability. AFAIK there is
no such constraint on SQL Express. If you check out the feature comparison
however you'll see that Express supports only a single processor and 1GB
RAM. So those are the limits you have to work within:
http://www.microsoft.com/sql/prodinf...-features.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
connections per the Microsoft paid support folks. I found various articles
on SQL Express with the limitations but nothing referencing the number of
connections. Has anyone already found this out?
"BCW" <nospam@.cfl.rr.com> wrote in message
news:uiyafD9PGHA.2912@.tk2msftngp13.phx.gbl...
>I have used MSDE in the past & it had a limit on the number of
>simultaneous
> connections per the Microsoft paid support folks. I found various
> articles
> on SQL Express with the limitations but nothing referencing the number of
> connections. Has anyone already found this out?
There is no limitation on connections in MSDE or in SQL Express. MSDE was
optimized for a "typical" load of upto 25 users I believe but this wasn't a
hard limit it was just a potential throttle on scalability. AFAIK there is
no such constraint on SQL Express. If you check out the feature comparison
however you'll see that Express supports only a single processor and 1GB
RAM. So those are the limits you have to work within:
http://www.microsoft.com/sql/prodinf...-features.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
Does SQL Express have a Simultaneous Connections Limit?
I have used MSDE in the past & it had a limit on the number of simultaneous
connections per the Microsoft paid support folks. I found various articles
on SQL Express with the limitations but nothing referencing the number of
connections. Has anyone already found this out?"BCW" <nospam@.cfl.rr.com> wrote in message
news:uiyafD9PGHA.2912@.tk2msftngp13.phx.gbl...
>I have used MSDE in the past & it had a limit on the number of
>simultaneous
> connections per the Microsoft paid support folks. I found various
> articles
> on SQL Express with the limitations but nothing referencing the number of
> connections. Has anyone already found this out?
There is no limitation on connections in MSDE or in SQL Express. MSDE was
optimized for a "typical" load of upto 25 users I believe but this wasn't a
hard limit it was just a potential throttle on scalability. AFAIK there is
no such constraint on SQL Express. If you check out the feature comparison
however you'll see that Express supports only a single processor and 1GB
RAM. So those are the limits you have to work within:
http://www.microsoft.com/sql/prodin...e-features.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
connections per the Microsoft paid support folks. I found various articles
on SQL Express with the limitations but nothing referencing the number of
connections. Has anyone already found this out?"BCW" <nospam@.cfl.rr.com> wrote in message
news:uiyafD9PGHA.2912@.tk2msftngp13.phx.gbl...
>I have used MSDE in the past & it had a limit on the number of
>simultaneous
> connections per the Microsoft paid support folks. I found various
> articles
> on SQL Express with the limitations but nothing referencing the number of
> connections. Has anyone already found this out?
There is no limitation on connections in MSDE or in SQL Express. MSDE was
optimized for a "typical" load of upto 25 users I believe but this wasn't a
hard limit it was just a potential throttle on scalability. AFAIK there is
no such constraint on SQL Express. If you check out the feature comparison
however you'll see that Express supports only a single processor and 1GB
RAM. So those are the limits you have to work within:
http://www.microsoft.com/sql/prodin...e-features.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Monday, March 19, 2012
Does MSDE support roles and views?
Hello,
I'm trying to figure out whether we need to go with MSDE or SQL Server. Can someone tell me if views are available in MSDE and if so, are they done the same as in SQL Server? Thanks so much.
Debbie
Yes.
Some of the differences between MSDE 2000 and SQL Server 2000 Standard
Edition are:
MSDE 2000 does not include the GUI tools.
MSDE 2000 has a workload governor that limits performance when more than a
few people connect.
MSDE 2000 databases are limited to 2GB of data per database.
MSDE 2000 does not support features primarily intended to support large
servers, such as failover clustering.
A list of the features supported by each edition of SQL Server 2000 is at:
http://msdn.microsoft.com/library/?u...asp?frame=true
You can find a lot of information about MSDE 2000 at
www.microsoft.com\sql\msde
There is a description of the workload governor starting at this location:
http://msdn.microsoft.com/library/?u...asp?frame=true
Much of the documentation in the SQL Server 2000 Books Online applies to
MSDE 2000. This topic describes which parts apply:
http://msdn.microsoft.com/library/?u...asp?frame=true
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
|||On Tue, 15 Jun 2004 19:35:49 -0700, Alan Brewer [MSFT] wrote:
>MSDE 2000 has a workload governor that limits performance when more than a
>few people connect.
Hi Alan,
That's not entirely accurate. The workload governor will only limit
performance if the number of active operations gets too high (over 8, 3 of
which are for system internal use).
One connection may execute several operations simultaneously. But on the
other hand, in a typical data entry situation, one can have 50 to 100
people connected without ever hitting the workload governor's limitations,
as the connections are inactive while the data entry typist is hammering
his/her keyboard and only active for a short time when data is sent to the
server and stored.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||Thank you both. What I need to get at is that views in SQL Server will help us limit the access to a centralized data by remote location. This means that a location will only see their data. I'm wondering if that capability exists in MSDE 2000. Thanks
,
Debbie
"Hugo Kornelis" wrote:
> On Tue, 15 Jun 2004 19:35:49 -0700, Alan Brewer [MSFT] wrote:
>
> Hi Alan,
> That's not entirely accurate. The workload governor will only limit
> performance if the number of active operations gets too high (over 8, 3 of
> which are for system internal use).
> One connection may execute several operations simultaneously. But on the
> other hand, in a typical data entry situation, one can have 50 to 100
> people connected without ever hitting the workload governor's limitations,
> as the connections are inactive while the data entry typist is hammering
> his/her keyboard and only active for a short time when data is sent to the
> server and stored.
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)
>
|||On Wed, 16 Jun 2004 03:52:01 -0700, Debbie wrote:
>Thank you both. What I need to get at is that views in SQL Server will help us limit the access to a centralized data by remote location. This means that a location will only see their data. I'm wondering if that capability exists in MSDE 2000. Thank
s,
>Debbie
>
Hi Debbie,
Yes, you can do that, if you include a location column in the table
design. Simplified example:
CREATE VIEW ViewForLocationA
SELECT ColumnA, ColmunB, ...
FROM CompleteTable
WHERE Location = 'A'
Make sure that people at location A get rights to this view but no rights
to other views and the underlying table. This will work for both SQL
Server and MSDE.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||Yes, which is why I included the link to the more in-depth description of
the governor so Debbie could get a better idea of exactly how the governor
worked.
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
|||Thank you again so much, that was a huge help!
Debbie
"Alan Brewer [MSFT]" wrote:
> Yes, which is why I included the link to the more in-depth description of
> the governor so Debbie could get a better idea of exactly how the governor
> worked.
> --
> Alan Brewer [MSFT]
> Lead Programming Writer
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
>
>
I'm trying to figure out whether we need to go with MSDE or SQL Server. Can someone tell me if views are available in MSDE and if so, are they done the same as in SQL Server? Thanks so much.
Debbie
Yes.
Some of the differences between MSDE 2000 and SQL Server 2000 Standard
Edition are:
MSDE 2000 does not include the GUI tools.
MSDE 2000 has a workload governor that limits performance when more than a
few people connect.
MSDE 2000 databases are limited to 2GB of data per database.
MSDE 2000 does not support features primarily intended to support large
servers, such as failover clustering.
A list of the features supported by each edition of SQL Server 2000 is at:
http://msdn.microsoft.com/library/?u...asp?frame=true
You can find a lot of information about MSDE 2000 at
www.microsoft.com\sql\msde
There is a description of the workload governor starting at this location:
http://msdn.microsoft.com/library/?u...asp?frame=true
Much of the documentation in the SQL Server 2000 Books Online applies to
MSDE 2000. This topic describes which parts apply:
http://msdn.microsoft.com/library/?u...asp?frame=true
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
|||On Tue, 15 Jun 2004 19:35:49 -0700, Alan Brewer [MSFT] wrote:
>MSDE 2000 has a workload governor that limits performance when more than a
>few people connect.
Hi Alan,
That's not entirely accurate. The workload governor will only limit
performance if the number of active operations gets too high (over 8, 3 of
which are for system internal use).
One connection may execute several operations simultaneously. But on the
other hand, in a typical data entry situation, one can have 50 to 100
people connected without ever hitting the workload governor's limitations,
as the connections are inactive while the data entry typist is hammering
his/her keyboard and only active for a short time when data is sent to the
server and stored.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||Thank you both. What I need to get at is that views in SQL Server will help us limit the access to a centralized data by remote location. This means that a location will only see their data. I'm wondering if that capability exists in MSDE 2000. Thanks
,
Debbie
"Hugo Kornelis" wrote:
> On Tue, 15 Jun 2004 19:35:49 -0700, Alan Brewer [MSFT] wrote:
>
> Hi Alan,
> That's not entirely accurate. The workload governor will only limit
> performance if the number of active operations gets too high (over 8, 3 of
> which are for system internal use).
> One connection may execute several operations simultaneously. But on the
> other hand, in a typical data entry situation, one can have 50 to 100
> people connected without ever hitting the workload governor's limitations,
> as the connections are inactive while the data entry typist is hammering
> his/her keyboard and only active for a short time when data is sent to the
> server and stored.
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)
>
|||On Wed, 16 Jun 2004 03:52:01 -0700, Debbie wrote:
>Thank you both. What I need to get at is that views in SQL Server will help us limit the access to a centralized data by remote location. This means that a location will only see their data. I'm wondering if that capability exists in MSDE 2000. Thank
s,
>Debbie
>
Hi Debbie,
Yes, you can do that, if you include a location column in the table
design. Simplified example:
CREATE VIEW ViewForLocationA
SELECT ColumnA, ColmunB, ...
FROM CompleteTable
WHERE Location = 'A'
Make sure that people at location A get rights to this view but no rights
to other views and the underlying table. This will work for both SQL
Server and MSDE.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||Yes, which is why I included the link to the more in-depth description of
the governor so Debbie could get a better idea of exactly how the governor
worked.
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
|||Thank you again so much, that was a huge help!
Debbie
"Alan Brewer [MSFT]" wrote:
> Yes, which is why I included the link to the more in-depth description of
> the governor so Debbie could get a better idea of exactly how the governor
> worked.
> --
> Alan Brewer [MSFT]
> Lead Programming Writer
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
>
>
Does MSDE run ok on Windows XP Home, Media Edition?
We can't seem to get TCP/IP working...
Hi Jon,
Have you enabled tcp/ip using svrnetcn.exe?
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jon Brunson" <JonBrunson@.NOSPAMinnovationsoftwareDOTcoPERIODuk> wrote in
message news:%23QouccA6EHA.3708@.TK2MSFTNGP14.phx.gbl...
> We can't seem to get TCP/IP working...
|||Yep, and Named Pipes. It's listening on the default port of 1433, but
when SQL starts, in the log, it doesn't say it's listening on TCP. There
are no warnings/errors either.
The PC does have a firewall on it, would that make any difference?
Greg Low [MVP] wrote:
> Hi Jon,
> Have you enabled tcp/ip using svrnetcn.exe?
> HTH,
>
|||Hi Jon,
Yep, sure would. Have you put an exception for port 1433 (assuming you're
using the default port) ?
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jon Brunson" <JonBrunson@.NOSPAMinnovationsoftwareDOTcoPERIODuk> wrote in
message news:e24tD0M6EHA.3376@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Yep, and Named Pipes. It's listening on the default port of 1433, but when
> SQL starts, in the log, it doesn't say it's listening on TCP. There are no
> warnings/errors either.
> The PC does have a firewall on it, would that make any difference?
> Greg Low [MVP] wrote:
Hi Jon,
Have you enabled tcp/ip using svrnetcn.exe?
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jon Brunson" <JonBrunson@.NOSPAMinnovationsoftwareDOTcoPERIODuk> wrote in
message news:%23QouccA6EHA.3708@.TK2MSFTNGP14.phx.gbl...
> We can't seem to get TCP/IP working...
|||Yep, and Named Pipes. It's listening on the default port of 1433, but
when SQL starts, in the log, it doesn't say it's listening on TCP. There
are no warnings/errors either.
The PC does have a firewall on it, would that make any difference?
Greg Low [MVP] wrote:
> Hi Jon,
> Have you enabled tcp/ip using svrnetcn.exe?
> HTH,
>
|||Hi Jon,
Yep, sure would. Have you put an exception for port 1433 (assuming you're
using the default port) ?
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jon Brunson" <JonBrunson@.NOSPAMinnovationsoftwareDOTcoPERIODuk> wrote in
message news:e24tD0M6EHA.3376@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Yep, and Named Pipes. It's listening on the default port of 1433, but when
> SQL starts, in the log, it doesn't say it's listening on TCP. There are no
> warnings/errors either.
> The PC does have a firewall on it, would that make any difference?
> Greg Low [MVP] wrote:
Does MSDE listen on 1433 by default?
Does a default installation of MSDE listen for connections on TCP/IP port
1433 by default or do I need to explicitly turn the TCP/IP listener on using
svrnetcn.exe?
(I'm using W2kR4 (v5.00.2195) and MSDE v8.000.761)
hi,
sparky62 wrote:
> Does a default installation of MSDE listen for connections on TCP/IP
> port 1433 by default or do I need to explicitly turn the TCP/IP
> listener on using svrnetcn.exe?
> (I'm using W2kR4 (v5.00.2195) and MSDE v8.000.761)
if network protocols have been enabled at install time
(DISABLENETWORKPROTOCOLS=0 parameter) TCP/IP port 1433 is assigned by
default to a default instance, where named instances use by default
dynamically assigned port, and thus UDP 1434 is needed to..
The SQL Server Resolution Service, which operates on UDP port 1434, provides
a way for clients to query for the appropriate network endpoints to use for
a particular SQL Server instance... this handshake is provided at connection
time via MDAC stack (MDAC must be at 2.6 level at least) , the SQL Server
Resolution Service queries the SQL Server instance for the port it is
listening to and transfer that info to the client redirecting the dialog to
that port...
if a static port has been assigned, the SQL Server Resolution Service is no
longer needed but you have to define an Alias pointing to the server on the
correct port on each remote client..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
1433 by default or do I need to explicitly turn the TCP/IP listener on using
svrnetcn.exe?
(I'm using W2kR4 (v5.00.2195) and MSDE v8.000.761)
hi,
sparky62 wrote:
> Does a default installation of MSDE listen for connections on TCP/IP
> port 1433 by default or do I need to explicitly turn the TCP/IP
> listener on using svrnetcn.exe?
> (I'm using W2kR4 (v5.00.2195) and MSDE v8.000.761)
if network protocols have been enabled at install time
(DISABLENETWORKPROTOCOLS=0 parameter) TCP/IP port 1433 is assigned by
default to a default instance, where named instances use by default
dynamically assigned port, and thus UDP 1434 is needed to..
The SQL Server Resolution Service, which operates on UDP port 1434, provides
a way for clients to query for the appropriate network endpoints to use for
a particular SQL Server instance... this handshake is provided at connection
time via MDAC stack (MDAC must be at 2.6 level at least) , the SQL Server
Resolution Service queries the SQL Server instance for the port it is
listening to and transfer that info to the client redirecting the dialog to
that port...
if a static port has been assigned, the SQL Server Resolution Service is no
longer needed but you have to define an Alias pointing to the server on the
correct port on each remote client..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Does MSDE fit my need?
I am creating an application that need store data locally (the new data
are downloaded from my webserver daily). Here is what I want:
1. Secure - Only my application can read the database. I don't want the
user be able to look at the data using other tools, or be able to
export the data for other purpose.
2. Handle large amount of data and be very fast.
3. How MSDE is distributed?
Thanks
John
hi,
Q. John Chen wrote:
> I am creating an application that need store data locally (the new
> data are downloaded from my webserver daily). Here is what I want:
> 1. Secure - Only my application can read the database. I don't want
> the user be able to look at the data using other tools, or be able to
> export the data for other purpose.
>
SQL Server/MSDE is secure as long as you provide an accurate login logic...
SQL Server uses a so called "2 phase" authentication policy:
first an SQL Server Login or a Windows login must be created of granted
access to the SQL Server instance... at the server level a login can be made
member of none, 1 or all of the fixed server roles, which include "sysadmin"
role and so on...
the second authentication phase is at database level, where each login will
be granted database access mapping to a database user... here access
permissions are set, as granting user/role SELECT/DELETE/EXECUTE (and so on)
privileges at an object level (or column level for tables and views)..
the mapping is performed in the JOIN database..sysusers.sid =
master..syslogins.sid , so the only link is the provided Login's sid, it's
Security IDentification number
so, the second phase regards a database security implementation... in order
to access a specified database the simple login existance does not provide
database access, but a (database) user must be mapped to the corresponding
login.. and is about verifying that at each object level (including
database, tables, views, columns, procedures and so on) the Login/User
association is permitted access to... please go on reading at
http://msdn.microsoft.com/library/de...urity_05bt.asp ,
http://msdn.microsoft.com/library/de...ar_da_0n77.asp
and following chapters..
but, back to the first phase, you can choose between 2 authentication modes:
WinNT (trusted) connections or SQL Server authenticated connections... the
latter always requires full user's credential such as "User
Id=sa;Password=pwd", the password can be NULL so it must not be specified,
but I strongly advise you always to ensure strong passwords are present...
WindowsNT authentication, on the contrary, does not requires user's
credential becouse it's directly provided by Windows via the logins'ID
(sid), which authenticate user's login at the windows login step... SQL
Server only needs to verify that the corresponding login and/or group is
granted to log on the instance...
Microsoft recommends to use the Windows NT (trusted) model as it grants more
and reliable security patterns
you can start reading about authentication modes at
other articles worth reading can be found at
http://www.sql-server-performaXnce.c...l_security.asp
http://www.microsoft.com/technet/pro.../sp3sec03.mspx
http://www.microsoft.com/technet/pro.../sp3sec00.mspx
> 2. Handle large amount of data and be very fast.
about large amount of data, MSDE is limited to 2gb data file per database..
> 3. How MSDE is distributed?
I do not understand this question... if it's about legal permissions, MSDE
is free to download and use, where you have to register (for free) at
http://www.microsoft.com/sql/msde/ho...stregister.asp for
redistribution rights...
frmo a technical point of view, it isa provided as a package including a
boostrap installer based on Windows Installer technology, to be run from a
command line prompt in order to provide all the required parameters
http://msdn.microsoft.com/library/de...stsql_84xl.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||About security the OP asked. His intention is not allowing user to see his
database design and data. On this regard, login logic only guard very
innocent users. For any reasonably knowledgable network/computer
administrator, who allows MSDE being installed or who does his own MSDE
installation (thanks to MSDE, many non-database administrators know how to
do it now), can install/uninstall, attach/detach your *.mdf , then be able
to see the database, unless some sort of encryption is applied. After all,
you cannot prevent an Administrator to install/uninstall MSDE. Say, your app
installs MSDE with SQL Security only with a long SA password. The user can
easily enable Win Security by going to Registry, or simply uninstall the
MSDE (note, user database *.mdf does not get erased during uninstallation)
and re-install it with Windows security. And he can create whatever login
and give the login whatever role he wants and then attach your database and
open it.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3drhk9F6n6b9nU1@.individual.net...
> hi,
> Q. John Chen wrote:
> SQL Server/MSDE is secure as long as you provide an accurate login
logic...
> SQL Server uses a so called "2 phase" authentication policy:
> first an SQL Server Login or a Windows login must be created of granted
> access to the SQL Server instance... at the server level a login can be
made
> member of none, 1 or all of the fixed server roles, which include
"sysadmin"
> role and so on...
>
> the second authentication phase is at database level, where each login
will
> be granted database access mapping to a database user... here access
> permissions are set, as granting user/role SELECT/DELETE/EXECUTE (and so
on)
> privileges at an object level (or column level for tables and views)..
> the mapping is performed in the JOIN database..sysusers.sid =
> master..syslogins.sid , so the only link is the provided Login's sid, it's
> Security IDentification number
> so, the second phase regards a database security implementation... in
order
> to access a specified database the simple login existance does not provide
> database access, but a (database) user must be mapped to the corresponding
> login.. and is about verifying that at each object level (including
> database, tables, views, columns, procedures and so on) the Login/User
> association is permitted access to... please go on reading at
>
http://msdn.microsoft.com/library/de...urity_05bt.asp ,
>
http://msdn.microsoft.com/library/de...ar_da_0n77.asp
> and following chapters..
>
> but, back to the first phase, you can choose between 2 authentication
modes:
> WinNT (trusted) connections or SQL Server authenticated connections... the
> latter always requires full user's credential such as "User
> Id=sa;Password=pwd", the password can be NULL so it must not be specified,
> but I strongly advise you always to ensure strong passwords are
present...
> WindowsNT authentication, on the contrary, does not requires user's
> credential becouse it's directly provided by Windows via the logins'ID
> (sid), which authenticate user's login at the windows login step... SQL
> Server only needs to verify that the corresponding login and/or group is
> granted to log on the instance...
>
> Microsoft recommends to use the Windows NT (trusted) model as it grants
more
> and reliable security patterns
> you can start reading about authentication modes at
>
> other articles worth reading can be found at
> http://www.sql-server-performaXnce.c...l_security.asp
>
http://www.microsoft.com/technet/pro.../sp3sec03.mspx
>
http://www.microsoft.com/technet/pro.../sp3sec00.mspx
>
> about large amount of data, MSDE is limited to 2gb data file per
database..
>
> I do not understand this question... if it's about legal permissions, MSDE
> is free to download and use, where you have to register (for free) at
> http://www.microsoft.com/sql/msde/ho...stregister.asp for
> redistribution rights...
> frmo a technical point of view, it isa provided as a package including a
> boostrap installer based on Windows Installer technology, to be run from a
> command line prompt in order to provide all the required parameters
>
http://msdn.microsoft.com/library/de...stsql_84xl.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||It seems that I can not use MSDE for my application thanks to you
answer. (unless I can find a way to remove your post :-))
Any recommendation on a local database that provide the security I
wanted. (not a good place to ask for an alternative here though).
Thanks
John
|||hi Norman,
I do not understand if you are just claiming for security...
Norman Yuan wrote:
> About security the OP asked. His intention is not allowing user to
> see his
> database design and data.
and of course you have to manage your WinNT users/groups accordingly to your
security needs and policy.. never give permissions your user is not
interested/accorded with..
and again, of course, we are dealing with SQL Server security and not OS
security, you should already know and manage accordingly to your needs
> On this regard, login logic only guard very
> innocent users. For any reasonably knowledgable network/computer
> administrator, who allows MSDE being installed or who does his own
> MSDE
> installation (thanks to MSDE, many non-database administrators know
> how to
> do it now), can install/uninstall, attach/detach your *.mdf , then be
> able
> to see the database, unless some sort of encryption is applied. After
> all,
> you cannot prevent an Administrator to install/uninstall MSDE.
do not understand this point... you can actually prevent your administrators
from logging in SQL Server... but you can not prevent them to uninstall SQL
Server... that's ok... but, what kind of employee do you have in your
organization? usually, if you can not trust your (fews) administrator, I
really think you have to fire them... the very same applys to SQL Server
(not os) administrator(s)..
>Say,
> your app
> installs MSDE with SQL Security only with a long SA password. The
> user can
> easily enable Win Security by going to Registry,
not the user, the local administrator...
>or simply uninstall the
> MSDE (note, user database *.mdf does not get erased during
> uninstallation)
> and re-install it with Windows security. And he can create whatever
> login
> and give the login whatever role he wants and then attach your
> database and
> open it.
again... I think you should fire your employees :D
as a local admin can do whatever operation he likes to do, you can not
prevent him to stop the server and trash your data.. he can perhaps even
eventually log on SQL Server, if you did not remove the
BUILTIN\Administrator login group (as I usually do) from the MSDE istance,
and of course, as part of the sysamin server role, even access the company
database and increase his salary by 20%...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||The original OP are concerned about protecting his software, including the
database design and data the software used. He does not want the software
user, be it individual or organization, to peek into his software logic by
openning database on MSDE. So my point is the software user has the power to
open a SQL Server database installed on his computer unless some encryption
is implemented on the database. It has nothing to do with how the employee
is behaves and is regulated.
Actually, from the point of view of pretecting software, lot of your unique
business logic are reflected on the database design. And when using MSDE in
your application, we are educated to use as much stroed procedures as
possible, meaning more business logic in the DB. Obviously, there is need to
protect them (I know and you know there are tools for encypting SPs). In
most cases of SQL Server being used in a organization, it is most likely
that app used there are custom-developed, so protecting software wouldn't be
a problem. But when you are developing a stand-alone app for sale, with MSDE
integrided, concerns on user peeking into the DB is understandable.
I developed a windows app package a couple of years ago and used MSDE with
tons of SPs in it. It was aimed to small business in certain business. There
is nothing to prevent them to find a knowledgable guy to get into the
database and uses those Tables/SPs and develop there new UI app, although
they did not do that. Since MSDE is a powerful data engine and very easy to
be integrited into your app, protecting software resulted in by this should
be a concern. How to safyly regulating SQL Server/MSDE in a organization is
not my topic here.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3dsa5rF6tlqnqU1@.individual.net...
> hi Norman,
> I do not understand if you are just claiming for security...
> Norman Yuan wrote:
> and of course you have to manage your WinNT users/groups accordingly to
your
> security needs and policy.. never give permissions your user is not
> interested/accorded with..
> and again, of course, we are dealing with SQL Server security and not OS
> security, you should already know and manage accordingly to your needs
>
> do not understand this point... you can actually prevent your
administrators
> from logging in SQL Server... but you can not prevent them to uninstall
SQL
> Server... that's ok... but, what kind of employee do you have in your
> organization? usually, if you can not trust your (fews) administrator, I
> really think you have to fire them... the very same applys to SQL Server
> (not os) administrator(s)..
>
> not the user, the local administrator...
>
> again... I think you should fire your employees :D
> as a local admin can do whatever operation he likes to do, you can not
> prevent him to stop the server and trash your data.. he can perhaps even
> eventually log on SQL Server, if you did not remove the
> BUILTIN\Administrator login group (as I usually do) from the MSDE istance,
> and of course, as part of the sysamin server role, even access the company
> database and increase his salary by 20%...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Norman,
You read my mind. The software I developed is an application analyzing
commodity trading data. The user is not of a single organization but in
different organization or individuals all over the world. What we are
selling is the data not the software ifself. So protect the data is the
first priority.
Still, I want thank Andrea for giving me all the information about
MSDE.
Again, thanks both.
John
|||Q. John Chen wrote:
> Norman,
> You read my mind. The software I developed is an application analyzing
> commodity trading data. The user is not of a single organization but in
> different organization or individuals all over the world. What we are
> selling is the data not the software ifself. So protect the data is the
> first priority.
> Still, I want thank Andrea for giving me all the information about
> MSDE.
> Again, thanks both.
> John
>
Hi,
My company sells data and ships an MSDE application. What we ended up
doing was coding in application encryption logic. Numbers are not
encrypted but databae column with anything in text (like say
COMPANYNAME) was encrypted.
We can't stop the end-users looking at the database through Access, but
what they do see is a garbled mess !
|||Encrypt the data before storing it in the database, and decrypt it on the
application side when you read it. Of course this will affect overall
performance, but if security is your primary concern, performance is going
to take a hit no matter what.
"Q. John Chen" <qjchen@.email.com> wrote in message
news:1115221772.287953.148830@.o13g2000cwo.googlegr oups.com...
> It seems that I can not use MSDE for my application thanks to you
> answer. (unless I can find a way to remove your post :-))
> Any recommendation on a local database that provide the security I
> wanted. (not a good place to ask for an alternative here though).
> Thanks
> John
>
are downloaded from my webserver daily). Here is what I want:
1. Secure - Only my application can read the database. I don't want the
user be able to look at the data using other tools, or be able to
export the data for other purpose.
2. Handle large amount of data and be very fast.
3. How MSDE is distributed?
Thanks
John
hi,
Q. John Chen wrote:
> I am creating an application that need store data locally (the new
> data are downloaded from my webserver daily). Here is what I want:
> 1. Secure - Only my application can read the database. I don't want
> the user be able to look at the data using other tools, or be able to
> export the data for other purpose.
>
SQL Server/MSDE is secure as long as you provide an accurate login logic...
SQL Server uses a so called "2 phase" authentication policy:
first an SQL Server Login or a Windows login must be created of granted
access to the SQL Server instance... at the server level a login can be made
member of none, 1 or all of the fixed server roles, which include "sysadmin"
role and so on...
the second authentication phase is at database level, where each login will
be granted database access mapping to a database user... here access
permissions are set, as granting user/role SELECT/DELETE/EXECUTE (and so on)
privileges at an object level (or column level for tables and views)..
the mapping is performed in the JOIN database..sysusers.sid =
master..syslogins.sid , so the only link is the provided Login's sid, it's
Security IDentification number
so, the second phase regards a database security implementation... in order
to access a specified database the simple login existance does not provide
database access, but a (database) user must be mapped to the corresponding
login.. and is about verifying that at each object level (including
database, tables, views, columns, procedures and so on) the Login/User
association is permitted access to... please go on reading at
http://msdn.microsoft.com/library/de...urity_05bt.asp ,
http://msdn.microsoft.com/library/de...ar_da_0n77.asp
and following chapters..
but, back to the first phase, you can choose between 2 authentication modes:
WinNT (trusted) connections or SQL Server authenticated connections... the
latter always requires full user's credential such as "User
Id=sa;Password=pwd", the password can be NULL so it must not be specified,
but I strongly advise you always to ensure strong passwords are present...
WindowsNT authentication, on the contrary, does not requires user's
credential becouse it's directly provided by Windows via the logins'ID
(sid), which authenticate user's login at the windows login step... SQL
Server only needs to verify that the corresponding login and/or group is
granted to log on the instance...
Microsoft recommends to use the Windows NT (trusted) model as it grants more
and reliable security patterns
you can start reading about authentication modes at
other articles worth reading can be found at
http://www.sql-server-performaXnce.c...l_security.asp
http://www.microsoft.com/technet/pro.../sp3sec03.mspx
http://www.microsoft.com/technet/pro.../sp3sec00.mspx
> 2. Handle large amount of data and be very fast.
about large amount of data, MSDE is limited to 2gb data file per database..
> 3. How MSDE is distributed?
I do not understand this question... if it's about legal permissions, MSDE
is free to download and use, where you have to register (for free) at
http://www.microsoft.com/sql/msde/ho...stregister.asp for
redistribution rights...
frmo a technical point of view, it isa provided as a package including a
boostrap installer based on Windows Installer technology, to be run from a
command line prompt in order to provide all the required parameters
http://msdn.microsoft.com/library/de...stsql_84xl.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||About security the OP asked. His intention is not allowing user to see his
database design and data. On this regard, login logic only guard very
innocent users. For any reasonably knowledgable network/computer
administrator, who allows MSDE being installed or who does his own MSDE
installation (thanks to MSDE, many non-database administrators know how to
do it now), can install/uninstall, attach/detach your *.mdf , then be able
to see the database, unless some sort of encryption is applied. After all,
you cannot prevent an Administrator to install/uninstall MSDE. Say, your app
installs MSDE with SQL Security only with a long SA password. The user can
easily enable Win Security by going to Registry, or simply uninstall the
MSDE (note, user database *.mdf does not get erased during uninstallation)
and re-install it with Windows security. And he can create whatever login
and give the login whatever role he wants and then attach your database and
open it.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3drhk9F6n6b9nU1@.individual.net...
> hi,
> Q. John Chen wrote:
> SQL Server/MSDE is secure as long as you provide an accurate login
logic...
> SQL Server uses a so called "2 phase" authentication policy:
> first an SQL Server Login or a Windows login must be created of granted
> access to the SQL Server instance... at the server level a login can be
made
> member of none, 1 or all of the fixed server roles, which include
"sysadmin"
> role and so on...
>
> the second authentication phase is at database level, where each login
will
> be granted database access mapping to a database user... here access
> permissions are set, as granting user/role SELECT/DELETE/EXECUTE (and so
on)
> privileges at an object level (or column level for tables and views)..
> the mapping is performed in the JOIN database..sysusers.sid =
> master..syslogins.sid , so the only link is the provided Login's sid, it's
> Security IDentification number
> so, the second phase regards a database security implementation... in
order
> to access a specified database the simple login existance does not provide
> database access, but a (database) user must be mapped to the corresponding
> login.. and is about verifying that at each object level (including
> database, tables, views, columns, procedures and so on) the Login/User
> association is permitted access to... please go on reading at
>
http://msdn.microsoft.com/library/de...urity_05bt.asp ,
>
http://msdn.microsoft.com/library/de...ar_da_0n77.asp
> and following chapters..
>
> but, back to the first phase, you can choose between 2 authentication
modes:
> WinNT (trusted) connections or SQL Server authenticated connections... the
> latter always requires full user's credential such as "User
> Id=sa;Password=pwd", the password can be NULL so it must not be specified,
> but I strongly advise you always to ensure strong passwords are
present...
> WindowsNT authentication, on the contrary, does not requires user's
> credential becouse it's directly provided by Windows via the logins'ID
> (sid), which authenticate user's login at the windows login step... SQL
> Server only needs to verify that the corresponding login and/or group is
> granted to log on the instance...
>
> Microsoft recommends to use the Windows NT (trusted) model as it grants
more
> and reliable security patterns
> you can start reading about authentication modes at
>
> other articles worth reading can be found at
> http://www.sql-server-performaXnce.c...l_security.asp
>
http://www.microsoft.com/technet/pro.../sp3sec03.mspx
>
http://www.microsoft.com/technet/pro.../sp3sec00.mspx
>
> about large amount of data, MSDE is limited to 2gb data file per
database..
>
> I do not understand this question... if it's about legal permissions, MSDE
> is free to download and use, where you have to register (for free) at
> http://www.microsoft.com/sql/msde/ho...stregister.asp for
> redistribution rights...
> frmo a technical point of view, it isa provided as a package including a
> boostrap installer based on Windows Installer technology, to be run from a
> command line prompt in order to provide all the required parameters
>
http://msdn.microsoft.com/library/de...stsql_84xl.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||It seems that I can not use MSDE for my application thanks to you
answer. (unless I can find a way to remove your post :-))
Any recommendation on a local database that provide the security I
wanted. (not a good place to ask for an alternative here though).
Thanks
John
|||hi Norman,
I do not understand if you are just claiming for security...
Norman Yuan wrote:
> About security the OP asked. His intention is not allowing user to
> see his
> database design and data.
and of course you have to manage your WinNT users/groups accordingly to your
security needs and policy.. never give permissions your user is not
interested/accorded with..
and again, of course, we are dealing with SQL Server security and not OS
security, you should already know and manage accordingly to your needs
> On this regard, login logic only guard very
> innocent users. For any reasonably knowledgable network/computer
> administrator, who allows MSDE being installed or who does his own
> MSDE
> installation (thanks to MSDE, many non-database administrators know
> how to
> do it now), can install/uninstall, attach/detach your *.mdf , then be
> able
> to see the database, unless some sort of encryption is applied. After
> all,
> you cannot prevent an Administrator to install/uninstall MSDE.
do not understand this point... you can actually prevent your administrators
from logging in SQL Server... but you can not prevent them to uninstall SQL
Server... that's ok... but, what kind of employee do you have in your
organization? usually, if you can not trust your (fews) administrator, I
really think you have to fire them... the very same applys to SQL Server
(not os) administrator(s)..
>Say,
> your app
> installs MSDE with SQL Security only with a long SA password. The
> user can
> easily enable Win Security by going to Registry,
not the user, the local administrator...
>or simply uninstall the
> MSDE (note, user database *.mdf does not get erased during
> uninstallation)
> and re-install it with Windows security. And he can create whatever
> login
> and give the login whatever role he wants and then attach your
> database and
> open it.
again... I think you should fire your employees :D
as a local admin can do whatever operation he likes to do, you can not
prevent him to stop the server and trash your data.. he can perhaps even
eventually log on SQL Server, if you did not remove the
BUILTIN\Administrator login group (as I usually do) from the MSDE istance,
and of course, as part of the sysamin server role, even access the company
database and increase his salary by 20%...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||The original OP are concerned about protecting his software, including the
database design and data the software used. He does not want the software
user, be it individual or organization, to peek into his software logic by
openning database on MSDE. So my point is the software user has the power to
open a SQL Server database installed on his computer unless some encryption
is implemented on the database. It has nothing to do with how the employee
is behaves and is regulated.
Actually, from the point of view of pretecting software, lot of your unique
business logic are reflected on the database design. And when using MSDE in
your application, we are educated to use as much stroed procedures as
possible, meaning more business logic in the DB. Obviously, there is need to
protect them (I know and you know there are tools for encypting SPs). In
most cases of SQL Server being used in a organization, it is most likely
that app used there are custom-developed, so protecting software wouldn't be
a problem. But when you are developing a stand-alone app for sale, with MSDE
integrided, concerns on user peeking into the DB is understandable.
I developed a windows app package a couple of years ago and used MSDE with
tons of SPs in it. It was aimed to small business in certain business. There
is nothing to prevent them to find a knowledgable guy to get into the
database and uses those Tables/SPs and develop there new UI app, although
they did not do that. Since MSDE is a powerful data engine and very easy to
be integrited into your app, protecting software resulted in by this should
be a concern. How to safyly regulating SQL Server/MSDE in a organization is
not my topic here.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3dsa5rF6tlqnqU1@.individual.net...
> hi Norman,
> I do not understand if you are just claiming for security...
> Norman Yuan wrote:
> and of course you have to manage your WinNT users/groups accordingly to
your
> security needs and policy.. never give permissions your user is not
> interested/accorded with..
> and again, of course, we are dealing with SQL Server security and not OS
> security, you should already know and manage accordingly to your needs
>
> do not understand this point... you can actually prevent your
administrators
> from logging in SQL Server... but you can not prevent them to uninstall
SQL
> Server... that's ok... but, what kind of employee do you have in your
> organization? usually, if you can not trust your (fews) administrator, I
> really think you have to fire them... the very same applys to SQL Server
> (not os) administrator(s)..
>
> not the user, the local administrator...
>
> again... I think you should fire your employees :D
> as a local admin can do whatever operation he likes to do, you can not
> prevent him to stop the server and trash your data.. he can perhaps even
> eventually log on SQL Server, if you did not remove the
> BUILTIN\Administrator login group (as I usually do) from the MSDE istance,
> and of course, as part of the sysamin server role, even access the company
> database and increase his salary by 20%...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Norman,
You read my mind. The software I developed is an application analyzing
commodity trading data. The user is not of a single organization but in
different organization or individuals all over the world. What we are
selling is the data not the software ifself. So protect the data is the
first priority.
Still, I want thank Andrea for giving me all the information about
MSDE.
Again, thanks both.
John
|||Q. John Chen wrote:
> Norman,
> You read my mind. The software I developed is an application analyzing
> commodity trading data. The user is not of a single organization but in
> different organization or individuals all over the world. What we are
> selling is the data not the software ifself. So protect the data is the
> first priority.
> Still, I want thank Andrea for giving me all the information about
> MSDE.
> Again, thanks both.
> John
>
Hi,
My company sells data and ships an MSDE application. What we ended up
doing was coding in application encryption logic. Numbers are not
encrypted but databae column with anything in text (like say
COMPANYNAME) was encrypted.
We can't stop the end-users looking at the database through Access, but
what they do see is a garbled mess !
|||Encrypt the data before storing it in the database, and decrypt it on the
application side when you read it. Of course this will affect overall
performance, but if security is your primary concern, performance is going
to take a hit no matter what.
"Q. John Chen" <qjchen@.email.com> wrote in message
news:1115221772.287953.148830@.o13g2000cwo.googlegr oups.com...
> It seems that I can not use MSDE for my application thanks to you
> answer. (unless I can find a way to remove your post :-))
> Any recommendation on a local database that provide the security I
> wanted. (not a good place to ask for an alternative here though).
> Thanks
> John
>
Does MSDE allow cascaded deletes
I just wanted to make sure there is no limitation here, since I have
cascaded deletes in my table relationships.
Thanks
Norton
MSDE 2000 does support cascading deletes. MSDE 1.0, as it was based on SQL
Server 7, doesn't.
Jacco Schalkwijk
SQL Server MVP
"TheNortonZ" <thenortonz@.hotmail.com> wrote in message
news:%23pa0URZzEHA.1932@.TK2MSFTNGP09.phx.gbl...
>I just wanted to make sure there is no limitation here, since I have
>cascaded deletes in my table relationships.
> Thanks
> Norton
>
cascaded deletes in my table relationships.
Thanks
Norton
MSDE 2000 does support cascading deletes. MSDE 1.0, as it was based on SQL
Server 7, doesn't.
Jacco Schalkwijk
SQL Server MVP
"TheNortonZ" <thenortonz@.hotmail.com> wrote in message
news:%23pa0URZzEHA.1932@.TK2MSFTNGP09.phx.gbl...
>I just wanted to make sure there is no limitation here, since I have
>cascaded deletes in my table relationships.
> Thanks
> Norton
>
Does MSDE (SP4) support Full Text Research?
How can i install eand run Full text research Service in Windows xp Sp2
hi,
S. Luca wrote:
> How can i install eand run Full text research Service in Windows xp
> Sp2
MSDE does not support (and provide) Full Text engine..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
hi,
S. Luca wrote:
> How can i install eand run Full text research Service in Windows xp
> Sp2
MSDE does not support (and provide) Full Text engine..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Sunday, February 26, 2012
Does anyone know a utility/batch script to Warn when close to Max DB size
Hello Group
Does anyone know of a utility or Batch script (osql or Windows cmd or mix)
to Warn an Admin when a MSDE DB is closing in on 2 GB in size (or 2005
Express closes in on 4 GB).
Any leads or tips will be appriciated highly
Best regards
Uffe
hi Uffe,
Uffe Bak wrote:
> Hello Group
> Does anyone know of a utility or Batch script (osql or Windows cmd or
> mix) to Warn an Admin when a MSDE DB is closing in on 2 GB in size
> (or 2005 Express closes in on 4 GB).
> Any leads or tips will be appriciated highly
> Best regards
> Uffe
in MSDE you can perhaps schedule a job defined to include a way to gather
that kind of data, using direct access to the sysfiles database table or via
DBCC SHOWFILESTATS..
you can then validate that data against a userdefined treshold and notify
someone via NET SEND or mail via SMPT alternative, like exploded in
http://www.karaszi.com/sqlserver/info_no_mapi.asp,
http://www.dbmaint.com/SmtpAlerter.asp , thus defining a kind of alert..
PRINT 'MSDE';
PRINT '--';
USE Northwind;
PRINT 'sp_spaceused';
EXEC sp_spaceused @.updateusage = 'TRUE';
PRINT '--';
PRINT 'DBCC SHOWFILESTATS';
CREATE TABLE #tmp_sfs (
fileid int,
filegroup int,
totalextents int,
usedextents int,
name varchar(1024),
filename varchar(1024)
);
INSERT INTO #tmp_sfs
EXECUTE('DBCC SHOWFILESTATS');
SELECT LEFT(DB_NAME(),10), (SUM(totalextents) * 64) / 1024 AS [totalextents
in MB], (SUM(usedextents) * 64) /1024 AS [usedextents in MB]
FROM #tmp_sfs;
DROP TABLE #tmp_sfs;
PRINT '--';
PRINT 'sysdatabase query';
SELECT LEFT(DB_NAME(),10) AS [Database], sum(convert(float,size)) * (8192.0
/1024.0) /1024.0 AS [Size in MB for Data files]
FROM dbo.sysfiles
WHERE (status & 0x40) <> 0x40;
SQLExpress does not provide the SQL Server Agent, so you can perhaps rely on
the native OS scheduler for something similar.. as regards the SMPT
integration, you have to (possibly) write your own CLR based mailer
solution.. I personally will... then, from the OS scheduler, you'll execute
SqlCmd command line tool to perform the SQLExpress connection and data
retrival...
just an idea..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks to Andrea and Satya for quick answers
I will look into your suggestions and return if I find a solution.
I also looked up some Scripting options, so there are as usual more than one
road to Rome
Best regards
Uffe Bak
Does anyone know of a utility or Batch script (osql or Windows cmd or mix)
to Warn an Admin when a MSDE DB is closing in on 2 GB in size (or 2005
Express closes in on 4 GB).
Any leads or tips will be appriciated highly
Best regards
Uffe
hi Uffe,
Uffe Bak wrote:
> Hello Group
> Does anyone know of a utility or Batch script (osql or Windows cmd or
> mix) to Warn an Admin when a MSDE DB is closing in on 2 GB in size
> (or 2005 Express closes in on 4 GB).
> Any leads or tips will be appriciated highly
> Best regards
> Uffe
in MSDE you can perhaps schedule a job defined to include a way to gather
that kind of data, using direct access to the sysfiles database table or via
DBCC SHOWFILESTATS..
you can then validate that data against a userdefined treshold and notify
someone via NET SEND or mail via SMPT alternative, like exploded in
http://www.karaszi.com/sqlserver/info_no_mapi.asp,
http://www.dbmaint.com/SmtpAlerter.asp , thus defining a kind of alert..
PRINT 'MSDE';
PRINT '--';
USE Northwind;
PRINT 'sp_spaceused';
EXEC sp_spaceused @.updateusage = 'TRUE';
PRINT '--';
PRINT 'DBCC SHOWFILESTATS';
CREATE TABLE #tmp_sfs (
fileid int,
filegroup int,
totalextents int,
usedextents int,
name varchar(1024),
filename varchar(1024)
);
INSERT INTO #tmp_sfs
EXECUTE('DBCC SHOWFILESTATS');
SELECT LEFT(DB_NAME(),10), (SUM(totalextents) * 64) / 1024 AS [totalextents
in MB], (SUM(usedextents) * 64) /1024 AS [usedextents in MB]
FROM #tmp_sfs;
DROP TABLE #tmp_sfs;
PRINT '--';
PRINT 'sysdatabase query';
SELECT LEFT(DB_NAME(),10) AS [Database], sum(convert(float,size)) * (8192.0
/1024.0) /1024.0 AS [Size in MB for Data files]
FROM dbo.sysfiles
WHERE (status & 0x40) <> 0x40;
SQLExpress does not provide the SQL Server Agent, so you can perhaps rely on
the native OS scheduler for something similar.. as regards the SMPT
integration, you have to (possibly) write your own CLR based mailer
solution.. I personally will... then, from the OS scheduler, you'll execute
SqlCmd command line tool to perform the SQLExpress connection and data
retrival...
just an idea..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks to Andrea and Satya for quick answers
I will look into your suggestions and return if I find a solution.
I also looked up some Scripting options, so there are as usual more than one
road to Rome
Best regards
Uffe Bak
Friday, February 24, 2012
Does "MSDE 2000 Release A" only can support 2GB database?
It is very important to me. thank you.
Hi
Yes. Built in limitation for MSDE 2000.
For anything bigger, you need to use Standard Edition.
Regards
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/
"kingou" <kingou@.huawei.com> wrote in message
news:262a01c4e991$c5827f10$a401280a@.phx.gbl...
> It is very important to me. thank you.
Hi
Yes. Built in limitation for MSDE 2000.
For anything bigger, you need to use Standard Edition.
Regards
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/
"kingou" <kingou@.huawei.com> wrote in message
news:262a01c4e991$c5827f10$a401280a@.phx.gbl...
> It is very important to me. thank you.
Documenting the Database
Hi all,
I need some asistance. I use the MSDE SQL server inside the Web matrix project. I am trying to print the database and its SQL commands in order to add it to my project's documentation.
Can any body tell me how to do this?
Thanx a lot in advace.You might want to try this -http://www.eggheadcafe.com/articles/20040913.asp.
s/Don
Sunday, February 19, 2012
Documenting MSDE
Can anyone tell me what methods are there for documenting the tables created
in MSDE.
I would like something that would give me the field names, data type, size
etc and also be able to list the indices.
Any suggestions?
June
FMS (http://www.fmsinc.com) makes a reporting tool called Total SQL
Analyzer. They're a reputable company and have been around for a
while. There may be other third-party solutions as well if you don't
want to write your own.
--Mary
On Wed, 26 May 2004 13:12:02 +0100, "June Macleod"
<junework@.hotmail.com> wrote:
>Can anyone tell me what methods are there for documenting the tables created
>in MSDE.
>I would like something that would give me the field names, data type, size
>etc and also be able to list the indices.
>Any suggestions?
>June
>
|||hi June,
"June Macleod" <junework@.hotmail.com> ha scritto nel messaggio
news:%23c4RHpxQEHA.3744@.TK2MSFTNGP10.phx.gbl...
> Can anyone tell me what methods are there for documenting the tables
created
> in MSDE.
> I would like something that would give me the field names, data type, size
> etc and also be able to list the indices.
you can have a look at a free prj of mine, at the link following my sign.,
which provide a way to produce an HTML documentation with cross references
for this kind of thing...
or commercial tools like http://www.ag-software.com/ags_scribe_index.aspx
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea
Obviously I am going blind in my old age <g>
This is a cracker of a tool! The documentation is exactly what I am looking
for and will save me hours of time.
Much appreciated.
June
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2i1kskFi58j8U1@.uni-berlin.de...[vbcol=seagreen]
> hi June,
> "June Macleod" <junework@.hotmail.com> ha scritto nel messaggio
> news:OXGnIywREHA.3056@.TK2MSFTNGP11.phx.gbl...
documentaion[vbcol=seagreen]
was
> select the databese you want to document in the left pane treeview...
> right-click... select the "Database documentation" menu item...
> hope will meet your requirements..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
in MSDE.
I would like something that would give me the field names, data type, size
etc and also be able to list the indices.
Any suggestions?
June
FMS (http://www.fmsinc.com) makes a reporting tool called Total SQL
Analyzer. They're a reputable company and have been around for a
while. There may be other third-party solutions as well if you don't
want to write your own.
--Mary
On Wed, 26 May 2004 13:12:02 +0100, "June Macleod"
<junework@.hotmail.com> wrote:
>Can anyone tell me what methods are there for documenting the tables created
>in MSDE.
>I would like something that would give me the field names, data type, size
>etc and also be able to list the indices.
>Any suggestions?
>June
>
|||hi June,
"June Macleod" <junework@.hotmail.com> ha scritto nel messaggio
news:%23c4RHpxQEHA.3744@.TK2MSFTNGP10.phx.gbl...
> Can anyone tell me what methods are there for documenting the tables
created
> in MSDE.
> I would like something that would give me the field names, data type, size
> etc and also be able to list the indices.
you can have a look at a free prj of mine, at the link following my sign.,
which provide a way to produce an HTML documentation with cross references
for this kind of thing...
or commercial tools like http://www.ag-software.com/ags_scribe_index.aspx
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea
Obviously I am going blind in my old age <g>
This is a cracker of a tool! The documentation is exactly what I am looking
for and will save me hours of time.
Much appreciated.
June
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2i1kskFi58j8U1@.uni-berlin.de...[vbcol=seagreen]
> hi June,
> "June Macleod" <junework@.hotmail.com> ha scritto nel messaggio
> news:OXGnIywREHA.3056@.TK2MSFTNGP11.phx.gbl...
documentaion[vbcol=seagreen]
was
> select the databese you want to document in the left pane treeview...
> right-click... select the "Database documentation" menu item...
> hope will meet your requirements..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Subscribe to:
Posts (Atom)