SQL Server Express

[JString]

Hello.

For anyone who's willing to answer, I have a few questions about replacing
the Jet engine with SQL Express...

The company I work for is fairly small and it outsources all of its computer
needs to private contractors. They would not be able to hire a full time DB
administrator. Would SQL Express require an administrator on site much like
the full SQL Server?

Does SQL Express have the same security issues as SQL full? I've heard that
it is susceptible to worms, etc.

Can our existing front end interface be easily modifed to work with SQL
Express?

I know that SQL Express can be downloaded for free but can it be freely
distributed?

 

[Stefan Hoffmann]

Would SQL Express require an administrator on site much like
the full SQL Server?

The needs for a DBA are determined by the amount of data, availability,
recovery, but not by the SQL Server version.

Does SQL Express have the same security issues as SQL full? I've heard that
it is susceptible to worms, etc.

That's not true.

Can our existing front end interface be easily modifed to work with SQL
Express?

Normally, yes. But there are some traps.

I know that SQL Express can be downloaded for free but can it be freely
distributed?

Yes.



mfG
--> stefan <--

 

[George]

Having done that few months ago for a client, I can say with some certainty
that you won't need a full-time DBA. In fact, after the migration my hours
their dropped considerably. I do some ad-hoc reporting now and a couple of
monthly tasks that no one else there wants to do.

SQL Express is, if all else remains equal, more secure, but that comes with
a small price. You'll need to be on your P's and Q's to set it up properly.

I invested some time migrating the Access Front End to take advantage of SQL
Servers. For example, most of the queries were converted to pass-thrus and
we added stored procedures to move much of the "heavy lifting" to the server
where it is done more efficiently. However, a lot of parts did just stay as
they were because they still work just fine in the Access FE.

I also took advantage of the migration work to implement some long overdue
changes in the basic table design. but that would have been a good idea in
either case.

I am not sure on licensing issues, but I don't think you'll run into
anything there unless you're packaging shrink-wrap for sale and then you
would be wise to look at MS sites for more details.

All in all, I would say that the move from Jet to SQL Express is not simple
if you take the time to do it correctly. but it's not all that complex
either. If you have sound database design skills, you can learn what you
need to handle the migration.

The most important thing is to understand that SQL Express is NOT just Jet
on steroids and that a sound database design is the single most important
aspect of getting it done right. ( Did I make that point enough?)

George