SQL Server and C#
-
there is debate in my local office as whether or not we would benefit from migrating from C++ to C# to work with our SQL Server database. currently we are using MS SQL Server Express R2 as a test model and making connections and doing some stored procedure work from C++ front end. Eventually, we will work in our customer's environment of the full fledged Microsoft SQL Server. Can I get some feedback/opinions on the pros and cons of each - C++ and C# ? Thank you, JJ Mackey
-
there is debate in my local office as whether or not we would benefit from migrating from C++ to C# to work with our SQL Server database. currently we are using MS SQL Server Express R2 as a test model and making connections and doing some stored procedure work from C++ front end. Eventually, we will work in our customer's environment of the full fledged Microsoft SQL Server. Can I get some feedback/opinions on the pros and cons of each - C++ and C# ? Thank you, JJ Mackey
If you're using ADO.net with either then there shouldn't be much difference. My first experiences with SQL Server was with C++ and ODBC to access SQL Server 6; I hope you're not doing that.
-
If you're using ADO.net with either then there shouldn't be much difference. My first experiences with SQL Server was with C++ and ODBC to access SQL Server 6; I hope you're not doing that.
Currently, i am using C++ with ADO commands. My programming team maintains several thousand lines of code in C++ (Visual Studio 2008) and there are roughly 1K-3K lines that interact with external databases in the Microsoft SQL Server environment. The majority of the system(s) code we maintain don't perform SQL Server interaction - maybe 25% will interact with SQL Server. Maybe i'm missing the difference between ADO and ADO.net. Also, back to the original question, what do i gain if i choose C# over C++ ? Most of the team knows C++/MFC and we are clueless on C#. Thanks.
-
Currently, i am using C++ with ADO commands. My programming team maintains several thousand lines of code in C++ (Visual Studio 2008) and there are roughly 1K-3K lines that interact with external databases in the Microsoft SQL Server environment. The majority of the system(s) code we maintain don't perform SQL Server interaction - maybe 25% will interact with SQL Server. Maybe i'm missing the difference between ADO and ADO.net. Also, back to the original question, what do i gain if i choose C# over C++ ? Most of the team knows C++/MFC and we are clueless on C#. Thanks.
john john mackey wrote:
what do i gain if i choose C# over C++ ?
Undying gratitude from Microsoft?
john john mackey wrote:
Most of the team knows C++/MFC and we are clueless on C#.
Then stick with what you know.
-
there is debate in my local office as whether or not we would benefit from migrating from C++ to C# to work with our SQL Server database. currently we are using MS SQL Server Express R2 as a test model and making connections and doing some stored procedure work from C++ front end. Eventually, we will work in our customer's environment of the full fledged Microsoft SQL Server. Can I get some feedback/opinions on the pros and cons of each - C++ and C# ? Thank you, JJ Mackey
I don't think there is any difference from the database POV, I doubt there is any difference from the connection and interaction POV either. I'd be astonished if changing from C++ to C# made the slightest difference, changing from ADO to ADO.Net "may" make some slight difference.
Never underestimate the power of human stupidity RAH
-
there is debate in my local office as whether or not we would benefit from migrating from C++ to C# to work with our SQL Server database. currently we are using MS SQL Server Express R2 as a test model and making connections and doing some stored procedure work from C++ front end. Eventually, we will work in our customer's environment of the full fledged Microsoft SQL Server. Can I get some feedback/opinions on the pros and cons of each - C++ and C# ? Thank you, JJ Mackey
ADO.net (DataAdapters and suchlike) is quite nice. And you also have the potential of an entity management system like Entity Framework or NHibernate. However, that's not likely to be practical on a large existing database, and once you've written the queries, things aren't that different. If you were starting a new project from scratch I'd advise using C# but the gains are not going to pay back the massive cost of moving an existing system, particularly if your team would have to start learning from the ground up.
-
I don't think there is any difference from the database POV, I doubt there is any difference from the connection and interaction POV either. I'd be astonished if changing from C++ to C# made the slightest difference, changing from ADO to ADO.Net "may" make some slight difference.
Never underestimate the power of human stupidity RAH
Thanks for the insight. Now I must look at the differences/advantages of ADO.net v ADO. Regards, John John
-
ADO.net (DataAdapters and suchlike) is quite nice. And you also have the potential of an entity management system like Entity Framework or NHibernate. However, that's not likely to be practical on a large existing database, and once you've written the queries, things aren't that different. If you were starting a new project from scratch I'd advise using C# but the gains are not going to pay back the massive cost of moving an existing system, particularly if your team would have to start learning from the ground up.
Thank you for your comment and some topics to investigate regarding ADO.net. Yes, the learning curve and porting our existing system is an important consider for staying with C++. - John John
-
there is debate in my local office as whether or not we would benefit from migrating from C++ to C# to work with our SQL Server database. currently we are using MS SQL Server Express R2 as a test model and making connections and doing some stored procedure work from C++ front end. Eventually, we will work in our customer's environment of the full fledged Microsoft SQL Server. Can I get some feedback/opinions on the pros and cons of each - C++ and C# ? Thank you, JJ Mackey
john john mackey wrote:
Can I get some feedback/opinions on the pros and cons of each - C++ and C# ?
That isn't logical. You can't make a technological decision wildly. It needs to be based on your business needs. Some possible considerations. - You have a team of 10 C++ senior developers with no C# experience. And the application meets all of the current business needs. And the C++ developers want do continue using C++. So the ONLY decision is to keep using C++. - You have a team of 10 C++ developers with varying experience levels in C++ and C#. The application meets all of the current business needs. But 5 developers with the most business knowledge are threatening to quit unless you start using C#. So the only decision is to use C#. - Your largest customer produces 80% of your business income and insists that you use either C++ or C#. So that is what you use. - Your largest customer produces 80% of your business income and insists that you implement a feature that can only be implemented in either C++ or C#. So that is what you use. (This is probably a stretch scenario.) - Your business plan calls for you selling the company to Microsoft. Then use C#. - Your business plan calls for you selling the company to Oracle. Then use C++. Or Java. Regardless re-write to use Oracle instead of SQL Server. - Your application is 1000% slower than it should be. You have a design/architecture/requirements problem. It has NOTHING to do with language choice. - etc, etc, etc...