Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
marot_r
Starting Member
2 Posts |
 Posted - 2007-03-02 : 10:06:50
|
| Hello and thanks for your time.I hope I am in the right forum, if not please let me know wher I should have post.I am currently looking for a solution for a client of mine. He does not have IT internal ressorce just a mild power user and I don't plan to be with hime every day.I was wondering if SQL Express was a good solution for him.I am expert in Access but SQL Express looks a lot more complicated. I am sure I can master SQL Express it in not too much time but will you recommand it for a comagny that does not have a permanent DBA ?Thanks for your advice.Have all a nice day.A+ |
|
|
mikewa
Microsoft SQL Server Product Team
84 Posts |
Posted - 2007-03-02 : 11:09:48
|
| The answer, of course, is it depends...I won't kid you, SQL Server is a lot more complicated that Access, but it also offers some significant advantages under the right circumstances. Many people use SQL Express with very little official DBA interaction and it works fine. Others seem to strugle with it. Much depends on how good of a job is done in the initial configuration and what type of application you are writting.I'm an advocate of using the right product for the right application. If your application would benefit from the improved security and scalability of SQL Express, then you should consider using it. If the application is a single user application you might want to consider an alternative engine such as SQL CE or stick with Access/Jet. For multi-user applications you really need to consider how many people are going to use the application now and in the future. If this will be used by five people and never grow, then Access is probably a reasonable choice, but if you plan on eventually having many more users, (50, 100, 150...) you will probably find SQL a more scalable solution.If you choose to use SQL Express, remember that you can still use Access as your development platform if you like. Access support linked tables to SQL Server which gives a little bit of the best of both worlds, especially since you already have experience as an Access developer. There are some tricks you should know when developing an Access application against a SQL database since you need to do certain things differently when working against a server type database such as SQL Server. I recomend you read Andy Baron's excelent article about Access development against SQL Server, which you can fine at http://msdn2.microsoft.com/en-us/library/bb188204.aspx.Regards,Mike WachalSQL ExpressThis posting is provided "AS IS" with no warranties, and confers no rights.Use of included script samples are subject to the terms specified athttp://www.microsoft.com/info/cpyright.htm |
 |
|
|
marot_r
Starting Member
2 Posts |
Posted - 2007-03-02 : 11:30:01
|
| Thanks, SQL Express looks appeling and it will give me an opportunity to put a hand in SQL Server wich is a good thing for my CV but an the other hand I wish my customer can easily manage and back-up or restore his database and not depends on external ressources to do so. They will also be the final owner of the application, so it should be easy to maintain without me.The FREE factor is also appealing, using others Express tools I should be able to build them a good application, using modern tools, without having to buy software even if they will have to pay for my time.My customer is small company, 15 peoples max and not all using the data (currently 5 users max) and they do not like they will grow much in the near future. I should asks just to be sure but that my current perception so scalabilty should not be a huge problem and security also can be light.As mentionned my main concern is on day-to-day opperations.Thanks again for your insight.A+ |
|
|
|
|
|
|
|
|
Shall I use SQL Expess without a permanet DBA ?