Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm thinking of using ASP.NET and MySQL together on a large project. Does anyone have any experience in using these two on a large scale and are there any aspects I should be wary of? If there is a chance that there could be compatibility issues, then I may be prepared to purchase an MSSQL license, but I'd rather go the free route right now. In theory it's possible, but how easy is it to transfer a MySQL database to and MSSQL database in the future?
Thanks
(I'll make this a CW if requested).
Mysql is quite capable as a database engine, although the performance optimization techniques that apply to mysql are obviously different from those that apply to SQL Server.
Some of the largest sites in the world use mysql - last I checked, YouTube ran mysql. So you definitely don't need a commercial product to get good performance.
You will have a lot of trouble porting a non-trivial mysql database to SQL Server or any other DBMS. There are major differences between platforms. I think you'll be much better off picking one platform and sticking to it.
As for ASP.NET, well, in my experience WebForms can be a bit slow, although the ASP.NET backend itself is also very efficient, as evidenced by the numerous large ASP.NET MVC apps out there (such as StackOverflow!)
Edit - are there problems with the combination of ASP.NET and mysql? Well, that depends. The mysql ADO.NET connector is solid and performs just as well as the SQL Server connector. Linq to SQL doesn't support mysql out of the box, although there are 3rd-party products such as LightSpeed which are supposed to do it well, and of course NHibernate supports it (although documentation is a bit harder to find, but that only matters when you're getting started).
In general you'll probably find less support for mysql-related issues in .NET, you might find that mysql is a second-class citizen in the .NET community, but both technologies are solid and both are perfectly capable of talking to each other.
If you have the money, I'd probably spring for SQL Server on account of the support factor alone, or even start out with SQL Express if it's a very small site, but again, there are no serious problems using .NET with mysql.
I dont have any info on the scalabilty, however to make your transition as smoothe as possible from MySql to MS SQL, you'll want to make sure your using either the Db abstract classes, or the IDB type interfaces on your data access layer. Probably best to only use ANSI SQL while you are at it.
Go ahead with SQL Server 2012 Express Edition ( which is free) and then the migration will be made on the fly in case you need to upgrade to SQL Server 2012 Standard Edition.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have a BI project to be carried out using SQL Server 2008 and Cognos 8. Client seems to be using legendary adhoc/home grown applications. Where as some reports have been using an older version of Cognos. Client has no plan or what so ever as of now but in a real hurry to migrate all older version of Cognos reports to Cognos 8 (which they consider as the brand new version). Going forward Client also want to make reports available on Sharepoint with presently migrating .Net platform.
Given past exposure, I think, looking at all the underlying data/data sources required by the business users/their reports would be a better place to start, then followed by ETL, Data Warehousing to settle Database layer. That will give full performance management control over to BI platform. Where we can proceed with a prototype engaging meta data and presentation layers for a given business user object/department.
This is more of a brain-storming question that highly appreciates relevant ideas in terms of:
Better approach/better practice for planning a BI project on SQL Server/Cognos
Does it make sense to migrate old reports to new version of Cognos using IT resources or start on data sourcing/massaging with requirements gathering from business users? (as client is thinking out loud to integrate all other departments data/reporting into this BI platform in the future.) If latter is more inlined a successful project planning, how to convince the client?
Or should I share with the client that SQL Server 2008, specially 2012 MS BI is competent in BI, so wouldn't it be a huge cost cutting to use SQL Server/MS BI package totally instaed of mixing it with Cognos? (Client had not disclose any reason why they want to use Cognos at all)
Anyone who had used Cognos/SQL Server combo for BI, please provide with suggestions/tips/watch-outs/software-barriers(limits)/tips../2cents :)
Seems like a rather subjective question but here are some suggestions. Take them all with a grain of salt, as your situation and client situation is not, and cannot be fully described here.
Requirements drive technology choice, not the other way around. Consider the scalability requirements, maintainability (industry profesional availability and rates), etc. These are your "ilities" consider them carefully, and ask for clarification from the business where needed.
Consider additional or hidden costs/savings. SQL Server comes with analysis services, integration services, and integrates well with SharePoint.
Start small and move out. Agile methodology can work wonders, even though it has its own pitfalls. Find a project sponsor, someone in the business whose needs you can meet in a timely fashion. Deliver a quick, capable and competent solution. Other business units and users will take note, and you'll get buy-in much quicker and easier than just trying to convince people with charts and promises. Start creating value as quickly as possible.
You really don't want to waterfall a massive upgrade, in a single swoop. It's extremely difficult and likely to end in failure, at least in some form. Look up some of the SAP implementations undertaken by massive companies and the lawsuits and losses that follow (just as example, not out to get SAP).
Don't be afraid of a multi-phase project. It's easier to move from somewhat disjointed individual projects that were all built off SQL Server, SSIS, SSRS, and competent, modern, design to a unified whole, in a year, when the business loves you, than from multiple languages, platforms, architects and the array of data issues that come with that.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
I'm about to start a fresh project and I'm good on normalization of the data. My question is the business I'm working for has a number of tables on MS Sql Server and some version of Oracle. Access to create temporary or even use temporary tables may be limited. We might be able to setup our own tables but chances are 50/50. The approach taken in the past has been to create temporary tables as needed for data dumps into MS Access.
If I can edit / create tables on the SQL server then I'm good, but if not I was thinking about setting up one of the spare machines as a MySQL or MS Sql Express server rather than using Access as a number of these types of projects have been completed in the past and push towards a gig in size due to the amount of data downloaded for preparing reports. Would this be a reasonable approach if I'm locked out of MS Sql server or Oracle? What would you do if your hands were tied in a similar fashion?
To provide a little more insight here, the data dumps are often used to build dozens of excel reports (mostly charts). I was thinking if I can use the MS Sql or Oracle to do all the work via triggers / stored procedures / etc. then perhaps I can eliminate the need for Access and just download the data via VBA using Excel only to reduce the amount of time it takes to build the reports.
Maybe I can use an ORM and some kind of VB.net code rather than excel to build the charts faster?
I'm open to suggestions, let me know what you all think and any questions I'll try to answer the best I can
Although setting up a PC with something like SQL Server Express or MySQL often sounds like a great idea, I strongly suggest that you get the backing of your boss before doing something of this nature. Installing unapproved software on inappropriate/unmaintained workstations is often frowned upon with extreme prejudice. Were I to do this at my current place of employment I'm confident I'd be looking for a job as soon as it was uncovered. I completely agree that just about anything is better than MS Access - however, supporting an architecture such as the one you describe, at least temporarily until you can find a better gig, is probably better than unemployment. YMMV.
Share and enjoy.
Actually the most easy solution here would be to continue to use access as a front end, and simply link to the tables on the particular server database system in question. That way you save all the money time and resources of having to pull down and build temporary local tables.
The end result is you get to continue to use Access as a great RAD tool, but enjoy the benefits of the security, performance and scalability of the server based system in question.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Hi I am interested in learning SQL databases something I should have done a long time ago but I kept avoiding it for some reason.I realized that there are diferent versions of SQL(MySQL , SQL-Server etc.)and now I am prety confused on witch one to learn.I would like to start learning SQL from w3school but to be honest I dont really know what to use for writing SELECT , DELETE statements and more importantly how to run it.I know that in order to create databases you need tables and I used Microsoft Acces for that but after creating the tables I don't know what to do next.I should mention that there are 2 reasons why I wana learn SQL:
1.For using it with PHP web development
2.I have a course at coledge in witch we study C# and I need to be able to learn how to create SQL databases so I can connect to them
Can you tell me what are the diferences beetween MySQL and SQL-Server?
What should I use for creating and manipulating databases?
And what resources or book could you recomend for learning SQL ?
Thanx in advance and sorry if my statements are vague I have never had anything to do with databases before
Both MySQL and Micorosoft SQL Server are so called Relational Database Management Systems (RDBMS). Data is structured in tables of rows and columns, and relations are made between the tables. MySQL is an open source solution, while SQL Server is not. There is however a free edition of Sql Server available called "Sql Server Express". You manage it through the software "Management Console", which I think is included in the download. http://www.microsoft.com/express
Both uses the SQL-language to interact with the stored data, they do have some differences though. SQL Server uses a variant called "T-SQL" while MySQL uses "SQL/PSM". The basics are however the same.
Good luck!
First, check out RDBMS in Wikipedia for a comparison of DBs. Things change regularly, but this can give you a good idea.
Second, you can use PHP w/ MSSQL.
Third, you can use C# with MySQL, but in Visual Studio, it is very easy to use MSSQL and much more feature support.
As a student you can download all of the MS products you need from Dreamspark plus you can get a free subscription to PluralSight which is online video tutorials from beginner to advanced use of MS products.
PHP is fun and I've had more success using MySQL with PHP, but if you will have a class learning C# and MSSQL, you might as well start learning there.
since you use PHP, the best way you start is Mysql.
Check http://www.apachefriends.org/pt_br/xampp.html
With XAMPP you can run your php apps and user PHP mysqladmin to learn more bout SQL syntax.
Good Luck
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I'm looking into whether a move from SQL Server is a viable option. To help me with this decision, I have some questions:
Is it possible to use asp.net membership on a MySQL server ?
Are there many/any useful tools to migrate tables/databases/etc and which ones are the best?
What are the Main disadvantages in moving to MySQL from SQL Server?
As it stands I have a large enough project but it doesn't avail of many MS features so if it's possible I'd like to move.
My company did this a couple years ago with a pretty big project. On thing that made it easier for us is that we mostly used very plain standards compliant SQL. No Linq, no Entity Framework, only a little T-SQL, and only a few stored procedures.
As far as getting your data into MySQL, We ended up creating our own tool for doing this. None of the existing stuff including "MySQL Migration Assistant" can anywhere close to being fully functional. Once you can recreate the schema on MySQL, Getting the data back in, is a matter of exporting to CSV and importing with LOAD DATA INFILE. Tranferring the schema was actually the hardest part. With so many tables, we couldn't just do it by hand. We wrote some code in .Net by starting off using this VBScript that we found, and upgraded it to use the tools in "Microsoft.SqlServer.Management" Namespace available for .Net.
For functions that exist in SQL Server but don't exist in MySQL, such as GetDate, it's easy enough to write your own functions in MySQL that map to these functions, instead of trying to find all the instances of this stuff in the code. There are quite a few syntax differences between MySQL and SQL Server, even with just using basic SQL. For instance MSSQL allows DELETE TABLENAME WHERE ...., but MySQL insists you use DELETE FROM TABLENAME WHERE..... That's just one, there are many other differences.
Anyway, it was quite an adventure, but it worked out well for us. It is do-able, but you have to be committed, and not be afraid to write your own migration tools.
Couple of things off the top of my head.
MySQL doesn't support CHECK constraints. Usually, if your dbms does support CHECK constraints, your tables use them.
Depending on the constraint, you might be able to rewrite it in one of these ways.
As a foreign key to a new table
As a trigger
As a daily (or hourly, whatever) exception report
As a module in application code (which could be part of an exception report)
Something else I haven't thought of.
MySQL's timestamps have a resolution of one second.
Microsoft has a SQL Server Migration Assistant but, naturally, it is designed to help users move in the other direction.
You may want to check out this whitepaper from the MySQL site (you'll need to register - I did not, so I don't know how valuable the paper will be compared to the knowledge you already possess):
http://www.mysql.com/why-mysql/white-papers/mysql_wp_mssql2mysql.php
There are also some products and guides that can be found with a fairly simple search, e.g.
http://www.spectralcore.com/fullconvert/tutorials/convert-mssql-sql-server-to-mysql.php
http://www.haidongji.com/2009/02/23/moving-data-from-sql-server-to-mysql/
I don't know that the ASP.NET Membership can be ported directly to MySQL but I am confident you could replicate its functionality (it is more a question of how much effort it will take, not whether or not it is possible).
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Hi what are the preferred mysql tools with professional developers. I am a recent computing graduate and have used the query browser and administrator from mysql throughout university and i have found them to be very useful.
I start a new job in a couple of weeks though as a web developer and was wondering whether they would be exepcting me to use the command line or some other mysql tools.
What do the professional developers generally use for interacting with mysql databses i.e. creating new schemas, tables etc.
This is the tool to generate MySQL queries. There you can find MySQL generator for different commands, like drop table, create table, rename database, create database etc.
mysqladmin should be sufficient for most of the tasks if not all of them.
For windows, HeidiSQL is fantastic. It might work on Linux through Wine, but I've never tried it.
I occasionally use MySQL Workbench, as it can help speed up schema design (and the price is right). A cursory knowledge of phpMyAdmin is useful as it is often the admin tool of choice on web hosting servers. Most of the time, however, I just use the command line interface from Linux.
Understanding what goes on beneath the GUI is a very useful (dare I say essential) skill to have. Just look here on SO, where you'll find a vast number of SQL scripts that would be difficult to explain or implement if a GUI had to be factored in.
The CLI is available almost everywhere. If you ever have to work on a computer other than your own, be it on site or in your office, you can be fairly certain that CLI access will be available. The same cannot be said for your GUI of choice.
SQLyog is what I turned to after trying to use HeidiSQL. I liked HeidiSQL but I loved SQLyog. There is a free version somewhere.
Probably
Navicat
phpMyAdmin
DB Forge Studio for MySQL
For the Mac for development I use Querious. The application is very well written and supports connecting to local and remote databases.
Both of the tools you point out are good, and they would probably expect you to have some familiarity with them. Usually I will use a tool such as Query Browser or pgAdmin (for PostGreSQL) to run simple queries.
Once you have more experience you might find the command-line tools helpful as well. It's only going to help you by learning them.
For most big companies, you usually use Microsoft Visio to develop and plot the database as well as the web layout.