Question related to Reporting Services vs Crystal Report

I am migrating my reports from crystal 8 to reporting services 2005 but before this my client wants answers of following question.Can anybody provide me answer or link related to mentioned question...

1 -Will there be any performance improvement when the same Report (considering big data) is being run with Sql-Server reporting services compared to the one with Crystal report engine?

2- Is it possible to make the labels which are part of Top Palette like “1 of 1”, “Find”, “Next”, “Select a format”, ‘Export” according to the Account language?

3- Can both Versions of Reporting Tools (SQL-Reporting service and Crystal Report) run on the same machine?

4- What are the limitations of this Tools like whether there are any additional load on Database Server because of the involvement of Reporting services which are installed on DB Server.

5- Whether there are additional (to Crystal Report) types of Graph formats, Export file types available?

6- How is the licensing done for SQL-Server Report services?

Please provide me the answers ASAP.

This link might help. It is a white sheet on migrating from CR to RS... http://www.microsoft.com/sql/techinfo/whitepapers/migrate-crystal-to-reporting-services.mspx

We have CR and RS on the same machine and there were no problems.

Hope this helps.

|||

WOndering how someone would get the title of "Sr. Software Engineer, SIEMENS Sr. Software Engineer, SIEMENS " and not be able to do his own homework.

Sounded to me like a school report question.

|||

hey mainiac,

If you are not aware about the things then these type of comments doesn't suits on you.

I am a pure C# and VC++ developer and currently working on three tasks simultaniously.

I am putting fresh hand on CR & RS and due to time constraint I wanted quick & exact

solution of mentioned questions.

If we can save our time by this then i think its good approach...

Although if you are not able to answer such queries then don't waste your time

here by commenting like this because this is Information Sharing Plateform for

all of us.There is no place for you and your comments in this technical word.

I hope you will understand the things.

Take care next time...

byee

|||

hi guyinkalamazoo3,

very many thanks to you for your quick reply...

Its great information..

sql

Question on SSIS and .NET 1.1

We are migrating our databases from SQL Server 2000 on Win2k to SQL Server 2005 on Win 2k3 machines. Our applications useDTS packages , like creating dynamically in the (application) front end dynamically and sometimes just passing global parameters.

Now with SQL Server 2005 , we have decided to move to SSIS, as SQL Server 2005 has limited support for DTS. Now we were using a com+ assembly from microsoft for using these DTS packages from the front-end(Application). Can we accomplish the same with SSIS using applications developed in .Net Framework 1.1? Are there any work arounds? If not how can we accomplish this in 1.1 framework. Does SSIS expose any API that can be leveraged using .NET 1.1?

Did anyone face any other problems apart from these trying to make 1.1 apps talk to SQL 2005?

I guess this is more of a question to Microsoft experts, or programmers who already had similar experience already migrating to 2005.

It is hard to find information online on this subject. If anyone has valuable information regarding this, please reply with links..

Thanks in advance,

S

My understanding is that a .NET 1.1 application cannot interoperate directly with .NET 2.0 libraries such as the SSIS API. A web service should fit the bill nicely, though as far as just executing packages and passing in variables. If you're actually generating packages, that logic would probably need to be moved completely into the service which would also help insulate your application against future SSIS API changes. Your .NET 1.1 app could talk to the .NET 2.0 service, which could in turn automate the SSIS APIs.

In general, a .NET 1.1 application should not have much trouble making the switch from SQL Server 2000 to 2005, especially if you're using managed providers and calling stored procedures. If the app is calling the database with direct SQL queries, then you may have some minor syntax issues. If you're using procedures the Upgrade Advisor should be able to notify you of any problems, otherwise you'll have to test thoroughly.|||

In addition to nice Jay's wrap up, some mode ideas:

http://blogs.msdn.com/michen/archive/2007/03/22/running-ssis-package-programmatically.aspx

|||Thanks for all the replies..