I know access is not made for web. I am using access 2000 database in my website. At this time site is getting about 50000 pageviews permonth. Should I think to convert my access databases into MS SQL Server 2005? How much traffic an access database can hold. I know the limitation of access. But I want to know it in terms of page views or data transfer. Off topic question: Can I install windows server 2003 on my winxp pro machine? Can I use msoffice2007, adobeCS3, coreldraw, tuneup utilities, norton 2008, vs2008 etc software in it? I have P4 2.93GHz 1GB RAM system. At this time I update the database manually by using access2007 and upload it to the server. If I move to MSSQL then can I do the same thing? or should I think to create a joomla, .netnuke or blogger like control panel to update database online? Please Help.
How big (Disk Size) is your current database? Comparing MSSQL and Access is like comparing a hand generator to a nuclear power plant. Access is a database by it's own definition, but in reality it's basically a pumped up version of Excel. You aren't going to be able to manually update MSSQL like you are doing with access. (I'm assuming that you aren't using a command line to work with Access.) It's a completely different system. With that being said, I personally would switch just for the ability to use a real database. The performance and stability differences between the two are huge. Also, data backup, restoring, and portability is way better with MSSQL. You can run MSSQL express on the current XP machine. It's free, and should be signifigantly better than Access. It also has a free GUI editor, but it's somewhat limited, and doesn't resemble what you see with access at all. If you do decide to switch, you will want to migrate your database to MSSQL. There are several programs out there that will do it. The ease of this really depends on how complex your access database is. I've seen some that were very easy, and I've seen some that were near impossible. To address your Server 2003 question, yes you can run most of those on there. Server 2003 typically has more strict security settings than XP, but most of these can be worked through. Server 2003 is very similar to XP from the user's perspective. The RAM is probably going to end up being a limiting factor. But, if it's just your personal computer and not being used for hosting, there would be no reason to go to Windows Server. XP is fine with MSSQL and would be perfectly sufficient for testing and development. I would try SQL 2005 Express and see if it is something you currently want to work with. Once you get used to it, you can make a formal migration over to it. If you're interested in MSSQL express: http://www.microsoft.com/sql/editions/express/default.mspx I didn't address the updating question. Normally you would only update your online database. I'm don't understand how you are doing it now, upload the whole thing to the server? With MSSQL you could edit the database on the server in real time, which would be much more efficient than uploading the whole thing. You can do this from the GUI editor, or by command line, or through a web admin area. There's several possibilities depending on what's easiest and most efficient for you.
WOW jestep, Thank you so much. You given me great info. You asked me that what is size of my access db . I am using multiple db for different sections of my website. e.g. for wallpapers there is a seperate db and for computer tips and tricks section there is another db. I have about 5 databases. In which database of maximum size is about 1MB. total size will be about under 4mb.
I never used MSSQL Server therefore I am asking few questions: *How can I edit the database in real time? What type of gui editor? Do helix or plesk control panel provide editing of database?
Editing would need to be done through the management console. It's available in the download for the database. It's not like editing an access database, as the access to the data is very different. The Business Intelligence Developer Studio may be something a little more user friendly. Probably the best way to start out is to get a beginning MSSQL 2005 book. Another option you could look into is using mysql instead of mssql. It runs on more systems and there is a lot more community support for it than with mssql. You can also use a GUI program like Navicat, which would give you the ability to edit everything in real-time, but using a visual table editor. MySQL is generally a lot more friendly than MSSQL, and it's free and very well supported.
Will MYSQL Work with ASP.NET 3.5 ? If yes how we can start? I am asking this because in VS2008 we can easily create MSSql DB. I don't have any idea for using MySql. Can I merge and convert my all access dbs into MySql DB?
It will work with it but there isnt native support.... basically if your using .net then ms sql is the best option. There are plenty of GUIs for all the SQL dbs but the majority are more aimed at SQL pro's than Access which is much more home user based. That said if your used to VS then much of the interface with SQL Management Suite Express is very similar and it isnt until you really get into writing stored procedures etc that it does start to feel much more programmer tool