Personal vs MSDE

Besides the extra storage space. Why would I want to use
the Personal Edition(not free) instead of MSDE (free). I
have read the "Choosing an Edition" related information
but besides space issues, is there any reason not to use
MSDE in favor of the Personal Edition?
Thanks,
MikeHi MT,
With MSDE you don't get "tools". We supply some (details at our site).
Google for others.
HTH,
--
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"MT" <miketownsend33@.yahoo.com> wrote in message
news:07e001c34b6b$1c866720$a401280a@.phx.gbl...
> Besides the extra storage space. Why would I want to use
> the Personal Edition(not free) instead of MSDE (free). I
> have read the "Choosing an Edition" related information
> but besides space issues, is there any reason not to use
> MSDE in favor of the Personal Edition?
> Thanks,
> Mike|||Which "Tools"
Mike
>--Original Message--
>Hi MT,
>With MSDE you don't get "tools". We supply some (details
at our site).
>Google for others.
>HTH,
>--
>Greg Low (MVP)
>MSDE Manager SQL Tools
>www.whitebearconsulting.com
>"MT" <miketownsend33@.yahoo.com> wrote in message
>news:07e001c34b6b$1c866720$a401280a@.phx.gbl...
>> Besides the extra storage space. Why would I want to
use
>> the Personal Edition(not free) instead of MSDE (free).
I
>> have read the "Choosing an Edition" related information
>> but besides space issues, is there any reason not to
use
>> MSDE in favor of the Personal Edition?
>> Thanks,
>> Mike
>
>.
>|||hi MT,
"MT" <MikeTownsend33@.yahoo.com> ha scritto nel messaggio
news:0a4901c34b8d$230f8f00$a301280a@.phx.gbl...
> Which "Tools"
all the client graphical tools to manage SQL Server like Enterpise Manager,
Query Analyzer, Profiler...
MSDE only provides oSql.exe, a command line utility by which you can almost
do the same things but the hard way... via T-SQL statements... =;-) rather
then via a nifty user interface...
for your convenience you can have a look at a prj of mine, at the link
following my sign., that provides a fee user interface similar to Enterprise
Manager..
hth
Andrea Montanari
montanari_andrea@.virgilio.it
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.4.0 - DbaMgr ver 0.50.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||MSDE is just the relational data engine from within the entire SQL Server
product. That's why its name is Microsoft SQL Server 2000 Desktop ENGINE.
Personal Edition is a full EDITION of SQL Server including:
- Tools: Query Analyzer, Enterprise Manager, Profiler, Index Tuning Wizard,
etc.
- Analysis Services: OLAP, Data Mining
- Various bits and pieces of development libraries, legacy utilities, etc.
In general the scenarios for MSDE vs Personal Edition are very different.
MSDE is intended for use embedded within an application, not as a
multi-application database server. Personal Edition is intended primarily
as a client-side store for an application that runs both on the desktop and
on a server. Since the clients already require a CAL (or the SQL Server
server has Processor Licenses) there is no additional cost to use Personal
Edition in this scenario.
Personal Edition has a secondary use, which is as a way to install a full
edition of SQL Server 2000 on a Windows Desktop OS. So if you purchase
Standard Edition but want to install on Windows XP, you have to install
Personal Edition. You are paying a lot for a server product and then
crippling it (both in the OS selection and the database edition you need to
install), but some people are willing to do that. They save some $ on the
OS, and they get the full SQL Server product other than the governor. If it
meets their needs, great.
MSDE technically isn't free. The MSDE model is that you buy a development
tool and you receive the right to redistributed MSDE at no charge with (and
as part of) applications that you develop USING THAT TOOL. Microsoft has one
no cost development tool, ASP.NET Web Matrix, that includes MSDE as well.
But the no cost redistribution of MSDE in that case is limited to
applications developed with Web Matrix. There is another scenario where you
purchase a SQL Server 2000 edition and get MSDE redistribution rights. In
this case the SQL Server 2000 edition takes on the role of the development
tool.
Hal Berenson, SQL Server MVP
True Mountain Group LLC
"MT" <miketownsend33@.yahoo.com> wrote in message
news:07e001c34b6b$1c866720$a401280a@.phx.gbl...
> Besides the extra storage space. Why would I want to use
> the Personal Edition(not free) instead of MSDE (free). I
> have read the "Choosing an Edition" related information
> but besides space issues, is there any reason not to use
> MSDE in favor of the Personal Edition?
> Thanks,
> Mike|||Thanks!! Much clearer now.
As we have purchased several processor licenses for the
Standard Edition of SQL Server and in some cases we have
installed MSDE on a few laptops so that users could use
the same applications that the Standard Edition is using
to test/develop or in one case subscribe to.
We now have one user who wishes to have a copy of the
Personal Edition installed for the same purpose, and
we're reluctant to do so.. is there a reason that you
could think of why they would need to use the Personal
Edition as opposed to MSDE?
MT
>--Original Message--
>MSDE is just the relational data engine from within the
entire SQL Server
>product. That's why its name is Microsoft SQL Server
2000 Desktop ENGINE.
>Personal Edition is a full EDITION of SQL Server
including:
>- Tools: Query Analyzer, Enterprise Manager, Profiler,
Index Tuning Wizard,
>etc.
>- Analysis Services: OLAP, Data Mining
>- Various bits and pieces of development libraries,
legacy utilities, etc.
>In general the scenarios for MSDE vs Personal Edition
are very different.
>MSDE is intended for use embedded within an application,
not as a
>multi-application database server. Personal Edition is
intended primarily
>as a client-side store for an application that runs both
on the desktop and
>on a server. Since the clients already require a CAL
(or the SQL Server
>server has Processor Licenses) there is no additional
cost to use Personal
>Edition in this scenario.
>Personal Edition has a secondary use, which is as a way
to install a full
>edition of SQL Server 2000 on a Windows Desktop OS. So
if you purchase
>Standard Edition but want to install on Windows XP, you
have to install
>Personal Edition. You are paying a lot for a server
product and then
>crippling it (both in the OS selection and the database
edition you need to
>install), but some people are willing to do that. They
save some $ on the
>OS, and they get the full SQL Server product other than
the governor. If it
>meets their needs, great.
>MSDE technically isn't free. The MSDE model is that you
buy a development
>tool and you receive the right to redistributed MSDE at
no charge with (and
>as part of) applications that you develop USING THAT
TOOL. Microsoft has one
>no cost development tool, ASP.NET Web Matrix, that
includes MSDE as well.
>But the no cost redistribution of MSDE in that case is
limited to
>applications developed with Web Matrix. There is
another scenario where you
>purchase a SQL Server 2000 edition and get MSDE
redistribution rights. In
>this case the SQL Server 2000 edition takes on the role
of the development
>tool.
>
>--
>Hal Berenson, SQL Server MVP
>True Mountain Group LLC
>
>"MT" <miketownsend33@.yahoo.com> wrote in message
>news:07e001c34b6b$1c866720$a401280a@.phx.gbl...
>> Besides the extra storage space. Why would I want to
use
>> the Personal Edition(not free) instead of MSDE (free).
I
>> have read the "Choosing an Edition" related information
>> but besides space issues, is there any reason not to
use
>> MSDE in favor of the Personal Edition?
>> Thanks,
>> Mike
>
>.
>

Permissions to data source in Report Manager

I'm deploying some reports to a customer box and am having some quirks
in getting the right permissions to the data source. Instead of going
into detail about my specific problem (which I don't think I can even
give a good description of since I can't see what groups the accounts
I'm using are members of because I don't have access to their AD), can
someone give a list of the permissions required on an account in order
to access a data source? SQL permissions? Report Server permissions? If
I were to create an account purely for accessing the data source for
the reports, is there a complete checklist that I could follow to
ensure all the proper permissions?
Thanks.Oh, btw, I'm concerned about permissions to standard sql database
tables/views, and possibly OLAP cubes.
Thanks!|||Anybody?|||Bueller?
Bueller?
Bueller?|||All right, well I figured it out, at least for SQL Server access. I
guess all a domain account needs is public and db_datareader access to
the db you're getting data out of. Any ideas if it's pretty much the
same if trying to get data from an OLAP cube?|||What you are doing here is using the users account for accessing the
database. I think this is a mistake. First, it makes management of the users
more difficult. Now, every time there is a user that needs to run a report
you have to mess with DB access. Also, by doing this your RS will not be
able to take advantage of connection pooling (connection pooling only works
if everything is exactly the same, which includes the user). What I do is
have a special user that is used only for RS data access and is given
readonly rights to the data. I use RS roles to determine who gets to run
which reports.
The other thing I do is add domain groups and users to a local group on the
server and use that local group with RS roles.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Wannabe_Kiwi" <amkessel@.gmail.com> wrote in message
news:1150908395.063069.70970@.c74g2000cwc.googlegroups.com...
> All right, well I figured it out, at least for SQL Server access. I
> guess all a domain account needs is public and db_datareader access to
> the db you're getting data out of. Any ideas if it's pretty much the
> same if trying to get data from an OLAP cube?
>|||I'm using a single, special domain account to access all the data
sources for all the reports, not using a bunch of individual user
accounts.
I'm still stuck on getting access to the SQL Analysis OLAP cubes, tho.
I can easily set permissions for SQL databases in Enterprise Manager,
but there doesn't seem to be an equivalent in Analysis Manager. Ideas?

permissions granted to an application intead of a user

I have an application that talks to an access db located on a 2000 server. I would like grant permissions to the application instead of a specific user. Any help would be great...

Such capability is not available - permissions are grantable to accounts, not to applications.

Thanks
Laurentiu

|||

I am including a link to a related entry in this forum where we have a detailed discussion on this topic:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=786513&SiteID=1

I hope this information will be useful.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||

let me restate:

the db is on a mapped drive on the 2000 server.

i want the prgm to have access to it but not to the general public.

i need a way to limit access to myself and the prgm only....

i have admin rights and would like to give the prgm the same...

|||

Answer is the same - Windows security works by assigning permissions to users - permissions cannot be assigned to applications.

You should read the post that Raul pointed out. You can attempt to use application roles or have the application connect with specific credentials to the database, but a smart user can reverse-engineer the application and figure out how to connect directly to the database, hence there is no security guarantee of the type you seek.

Thanks
Laurentiu