Link to home
Start Free TrialLog in
Avatar of Thomasian
ThomasianFlag for Philippines

asked on

SQL Server Express

I am new to SQL Server so I'm not familiar on how this really works. I have originally decided to use SQL Server Compact Edition for my database, but I'm wondering if it will be better to use SQL Server Express instead. I need to know a few things before I can decide if I can switch to SQL Server Express.

1. Deployment: SQL Server CE can be silently distrubuted along with my application and the user doesn't even have to know that a database exists. While I know that distributing SQL Server Express is more complicated, I want to know how difficult it is for the user. Does it need the user to have knowledge in SQL Server to install and run my application?

2. Maintenance: With SQL Server CE, I can create backups and compact the database from time to time automatically. In SQL Server Express, will it need a database administrator to configure(or to do anything) from time to time?

TIA
ASKER CERTIFIED SOLUTION
Avatar of RiteshShah
RiteshShah
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Thomasian

ASKER

>>yes either you or your client has to install SQL Express, it doesn't mean that your client has to know SQL Server.
I have tried installing SQL Server Express and it requires me to enter the user, authentication mode, instance name, etc.. So I have to provide my user (who will do the installing) all the settings for it to work properly with my application? I was hoping for a ClickOnce deployment where there is no room for user error in the installation.


>>Well, you can set automise process, no need for database administrator.
Does that mean that the user will not actually see any difference whether I use SQL Server CE/Express other than during the installation?
>>Does that mean that the user will not actually see any difference whether I use SQL Server CE/Express other than during the installation?<<

yes, you set process and it used to take backup on specific time, store it somewhere and delete old backups.
So when will we need a database administrator? If everything can be done automatically through code, what do they actually do?
database administrator is not only for backing up database. the process automisation I told you is for backing up DB only.
>>I have tried installing SQL Server Express and it requires me to enter the user, authentication mode, instance name, etc.. So I have to provide my user (who will do the installing) all the settings for it to work properly with my application? I was hoping for a ClickOnce deployment where there is no room for user error in the installation.
<<

this link might help:

http://msdn.microsoft.com/en-us/library/bb264562%28SQL.90%29.aspx
Ok. So when will I need to have a database administrator?

Thanks for the link. I will check on the code after I have decided to use SQL Server Express. For now, I only need to know if it will be better for me to use Compact or Express Edition.
DBA's job is not only limited to installing, backup databases etc. they are responsible for uptime, performance tuning, optimisation, high availability of server and much more. all these things couldn't be managed without monitoring. it needs DBA.
As long as backup and some simple task concern, you can do it with automise script. everything has its own pro and cons, now you have to decide which way you want to go.