Re: Access or SQL Server?
From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 08/06/04
- Next message: Tazama: "How do I map INSERT parameters to DataTabler Columns?"
- Previous message: William \(Bill\) Vaughn: "Re: Monitoring OleDbConnection pool"
- In reply to: Thomas H: "Re: Access or SQL Server?"
- Next in thread: eWolverine: "Re: Access or SQL Server?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 6 Aug 2004 10:51:25 -0700
I would still not recommend Access/JET for my parent's business. I think
there are too many serious issues that can cripple a small business that
MSDE/SQLExpress just deal with quickly, quietly and efficiently. Access is a
great tool for individuals and single-user databases--I use it myself for
several small databases. It's just not a good choice for business IMHO.
-- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP www.betav.com Please reply only to the newsgroup so that others can benefit. This posting is provided "AS IS" with no warranties, and confers no rights. __________________________________ "Thomas H" <T@H> wrote in message news:u1Yi2F8eEHA.3028@TK2MSFTNGP12.phx.gbl... > "Peter" <zlxmqyt@sina.com> wrote in message > news:%23ooHnG2eEHA.3964@TK2MSFTNGP12.phx.gbl... > > Hi,everybody, > > > > I'm a newbie of .net, I've programed some database code with VB6 and > Access > > . Now,I'm turning to vb.net and can't decide which database tool to use, > > Access or SQL Server? Could somebody give me suggestions? Any suggestions > > will be appreciated ? > > Peter, SQL Server wins without a doubt. Access shouldn't even be in the > contest. Think of Access as a single-user-only database for a very small > business! For example, Mom & Dad have a classic record store, and Mom does > all the recordkeeping on the computer, and Dad only deals with the product > itself. If your application will ever go beyond a > single-user-single-workstation model, don't even install Access on your > computer. Go right to MSDE or SQL Server. > > MSDE is basically a "SQL Server Ultra-Lite". It's a free download from > Microsoft, you're very limited to the # of users that can simultaneously > connect, and you don't get SQL Server Enterprise Manager. All of your > database work needs to be done through straight T-SQL. MSDE is free, and I > believe that Microsoft allows it to be shipped with a production product- so > check the license agreement. That way you could sell your program to a > small 10-employee company, and they wouldn't have to buy SQL Server- chances > are their budget wouldn't allow it. But, you could also sell your product > to a 1000-employee company- who could afford (and would prefer!) SQL Server. > Your application would work with both- it wouldn't know the difference. > > One warning though!! Make sure you change the "sa" user password after > installing MSDE!! That's the sys admin password; it's left blank as > default. If you leave it blank, you can be easily hacked. You should try > to install MSDE with your computer unhooked from the 'net, change the sa > password, and then reconnect your network. > > We have applications at my company that do both. One department is very > small (about 5 employees), and they use MSDE 2000 on an old server. A much > larger department uses SQL Server on a newer box. For both servers, I > manually scripted the backup procedurs. I had no choice with MSDE. But > with SQL Server 2000, which allows fancy maintenance plans, I still chose to > script my own backup/maintenance manually. I believe that you used to be > able to download a trial version of SQL Server 2000, and it would let you > see what Enterprise Manager looks like. Also, http://www.asp.net has > written a web-based clone of SQL Server's EM, you can find it here > http://www.aspenterprisemanager.com/ . I'm not sure how secure their demo > is though, you might want to d/l the source and install it on your own box > first. > > Try to forget anything you learned about Access! Go right to MSDE, and > never look at Access again. I could use it if I had to, but I won't, and > you won't see it on my resume. > > Also, consider buying (or making) an old PC and turning it into a test > server. Don't install your database locally- this way, you'll get the > experience of connecting to a server. Even if the old PC just runs Win2k > and MSDE 2000 (SP3), it'll still simulate a real server. > > Visit http://www.microsoft.com/sql and http://www.microsoft.com/sql/msde for > more info on both products. > > Good luck! > > -Thomas > >
- Next message: Tazama: "How do I map INSERT parameters to DataTabler Columns?"
- Previous message: William \(Bill\) Vaughn: "Re: Monitoring OleDbConnection pool"
- In reply to: Thomas H: "Re: Access or SQL Server?"
- Next in thread: eWolverine: "Re: Access or SQL Server?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
