Is there any limitations in SQL Server 2005 express ? Can I use it for my database at my job ?
Printable View
Is there any limitations in SQL Server 2005 express ? Can I use it for my database at my job ?
It depends what you mean by limitations.. if you mean "am I allowed to use it for business use" the answer is Yes.
If you mean the software limitations... there is a maximum database size of 4GB, and some other limitations that you probably wont care about. More details can be found here (from the "SQL Server 2005 useful info" sticky thread).
What is the limitation for business use ?
Other than the maximum size, none. Do you think you database will exceed 4 gig?
Did you look at si_the_geeks link?
Nothing - you are allowed to use it, as stated in my previous post.
The limitations are essentially software based.. if those limits are too restrictive you'll need a full version, rather than the Express Edition.
I currently have a 75 Mb Access database and I would like to convert it to SQL server to speed up the queries
75 Mb is less practically less than nothing. :)Quote:
Originally Posted by Gensor
You shouldn't have a problem.
Is this conversion cleared with your management?
You do realize that you will have to recode and recompile and reroll out the application after the conversion. You also realize that you will need to put together a migration process that will take the records from your Access database and put them into your SQL Server database, right? And, that this will need to be run a few times during your recoding.
I would suggest you create a Test platform and production platform on SQL Server as well.
The conversion may or may not alter the speed, it depends on various factors. For example:
If the database is only accessed by one user (and the database is store on their computer) then SQL Server Express will be slightly slower, but not too much.
If the database is on a network, SQL Server is likely to be faster (but this is not guaranteed).
The more users that are connected, the faster it becomes compared to Access.
..the chances are that making sure the table design (and indexes etc) are correct will have a bigger impact on the speed.
I think that in SQL Server, I can do stored procedure which I can't with Access
Correct.. and they are very useful tools (especially for security, or if you have multiple applications that work with the same database).
I thought is was to speed up the queries !
Potentially they can (and often do), but that depends entirely on the queries.