DOT NET MSSQL and windows 2008 server

Dear Experts:

We are implementing the Sugar CRM for our business now that are going live .in this stage management has asked me to look for the ERP so that sugar crm to be integrated with the ERP,  based on our budget one of the vendor have given the near matching proposal almost we can go with them as they have agreed for the sugar crm interfacing with the ERP. sugar crm runs  on the linux  server LAMP. ERP is on windows platform with the below  prequistes :

1.Win2008 enterprise server
2.ms sql 2012 enterprise
3. Dot.Net v 2.0
4. Crystal components

can you please help me on the below points:

1.Dot.Net V2.0 can it be the one of the best choice of application.  I had asked them for the java but the deleoper says they have expertise in Dot.Net and this is does all the job , java not required.

Please suggest me can we go with the Dot.Net

2. developer says we need not procure Crystal reports application they will be installing the crystal components , first does crystal components be a good choice or asking better than this will be a better choice , please suggest,  also iam still confused whether license will be required for the crystal components.

3. Devloper says Windows 2008 STANDARD SERVER will be sufficient but MS SQL required is enterprise edition , please suggest is it recommended practice for windows 2008 enterprsie and MS SQL enterprsie as both will be of enterprise class.

Please help me with the above 03 points
D_wathiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Marten RuneSQL Expert/Infrastructure ArchitectCommented:
1.  .Dot Net is a good choise for application development. I would not care for Jave if it's note neccesary with cross platform application.

2. Crystal Reports is a de facto standard for creating reports for a variety of applications. It works as a database/Data reader, and then it takes it's query and out comes a formatted print. What you have to do is create these reports, i e whats the datasource, how should header and footer look like, a different header for the first page, different odd and even pages and so forth. This is the streangth of Crystal Reports.

3. Editions and versions. Yes thats a difficult one. I cant tell you what to use, but I can tell you what theyr'e fore. Starting with the OS. Enterprise is demanded if you plan to cluster your SQL or Application. Otherwise I would go with standard. The price difference isn't that huge, but it's still big enough to be considered. I don't thing you should buy enterprise windows as a default choice, rather standard as a default choice, and if needed choose enterprice when it's needed. Download comparison guide from here:
http://www.microsoft.com/en-us/server-cloud/windows-server/2008-r2-editions.aspx
and it'll help you choose.
SQL versions, ah thats more my turf. Well the enterprise has very good features, but if they are not used, standard should be the choice, unless a roadmap for the application states that a SQL Enterprise feature is going to be implementetd, such as partitioned tables, always on (demands Enterprise on the OS also since MSCS clustering is used). Comparision can be made from this link:
http://www.microsoft.com/sqlserver/en/us/sql-2012-editions.aspx
Ask what features demand the Enterprise flavour of SQL Server, and then you can choose. Observe that the price difference between the editions is quite big. So choosing the right licensing and version is well worth its time.

Yes licensing, I generally dont advice, but basically it comes down to how many are benefitting/using the system. For example if you have a system for doorpassage. Every employee has a accesscard, and one adminstrator administers the door system. One could argue that its only one user against the database. The way Microsoft sees it is that every cardholder is a database user, and should be licenced. And when you start to think about it their way of reasoning is logical. Now in your case look at how many users will use the system. Then you can look att licensing and its flavours.
Licensing information here: http://www.microsoft.com/sqlserver/en/us/get-sql-server/licensing.aspx

Regards Marten
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.