I am little bit scared that if i upgrade reporting server db to 2005, My report won't work. I just wanna test with some reports in SQL 2005 reporting services.
1) what should i do( I have already installed Reporting services in 2005 (64-bit)?
2) Can i backup Report server db and Report Tempdb database and restore in SQL 2005 but these database already exists in SQL 2005.?
3) If i upgrade these database , Will it effect my 2000 Production Reports?
I'm migrating SQl Server Reporting Services from 2000 to 2005.The reports are generated normally in 2000 but it seems that it is taking more time in 2005 or sometimes it does not generate the report at all.Could you kindly suggest a solution?
hello good afternoon, I am having this issue, I need to move reporting services from one server to another, but I need that credentials, roles and reports stay the same. But as the reporting services is integrated with sharepoint, dont know if I can move both at the same or it has to be done one at a time. this is just data migration, but still I will like to Know how it can be done having the same structure with the roles and credentials. or it is prefered to do a ghost?? but the issue will be that we have the reporting services in one place and the data in another... donīt know how this will affect. thanks in advanced for the help.
I am trying to migrate my reports from SQL server 2000 reporting services 32bit to 2005 64bit. I am following the migration steps that MS specified. Restored my Reportserver and ReportserverTempDB databases Then I was using the configure Report services to upgrade these databases but I always end up getting the follwoing exception when I run the upgrade on the "Database Setup" configuration for 'ReportServerTempDB' database System.Data.SqlClient.SqlException: Could not locate entry in sysdatabases for database 'ReportServerTempDBTempDB'. No entry found with that name. Make sure that the name is entered correctly. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script) at ReportServicesConfigUI.SqlClientTools.SqlTools.ApplyScript(String connectionString, String script)
It's driving me crazy, why is it looking for 'ReportServerTempDBTempDB' in the catalog instead of 'ReportServerTempDB'? Is it possible to migrate from 32bit to 64bit?
I'm trying to create reports in RS2005 using AS2000 as my data source. I understand that if I use RS2005 on AS2000, I wont be able to enjoy the OLAP based parameters as in using AS2005. Does anyone know an easy way to easily use Parameters in RS2005 while still using AS2000?
i have a small problem with the data sources in the reporting services, maybe you can clarify the situation... I have a MS CRM 3 solution with the reporting services 2005 installed. From an other vendor we have a arcplan solution on the 2000 analysis services. I would like to get access from the 2005 reporting services to the 2000 cube. Is this possible? Ive read that the SSMS cant connect to the 2000 cubes. Can i connect from the reporting services??
i am working in vs.net 2005 (c#.net & asp.net), my application need reporting functionality, for that i am using Sql Reporting Services 2000 in vs.net 2005, and i am not able to generate the report, can any pls tell me how to use sql reporting services 2000 in vs.net 2005 and configuration setting etc...
it would really help more to build my applications in sophisticated way
I am migrating our reporting services from 2000 to 2005. I am following the instructions in http://msdn2.microsoft.com/en-us/library/ms143724.aspx. I am currently using the Report Server Configuration tool to restore the encryption key. I click "Restore", point to the backup that I created at the beginning of the process, enter the password, and the process begins. I get a check mark and a message saying "Restoring Encryption Key." The problem is that it never comes back from this. I let it run for over an hour and finally clicked one of the previous steps to abort this. I went back and started it over. Again, it has been running for over an hour. I get no errors; it just does not complete. How do I proceed? Thanks in advance for any assistance.
How can I get the 2000 and 2005 versions of SQL Server Reporting Servicesboth working on my development laptop ?????I have ASP.NET 1.1 and 2.0 installed on my laptop.I have Visual Studio 2003 and 2005 installed on my laptop.I have my default website configured for ASP.NET 2.0.I have the developer edition of SQL Server 2000 installed on my laptop asinstance RMK006 in the MSSQL folder. I have the developer edition of SQLServer installed on my laptop as instance RMK0062005 in the MSSQL.1 folder.I have the corresponding versions of SQL Server Reporting Services installedon my laptop.I have the Reports web site and the Reports web site and ReportServer website configured to ASP.NET 1.1I have the Report$RMK0062005 web site and the ReportsServer$RMK0052006configured to ASP.NET 2.0Entering http://localhost/reports$rmk0062005 in my web browser works fine.Entering http://localhost/reportserver in my web browser generates thefollowing error:Reporting Services Error--------------------------------------------------------------------------------The report server cannot decrypt the symmetric key used to access sensitiveor encrypted data in a report server database. You must either restore abackup key or delete all encrypted content and then restart the service.Check the documentation for more information. (rsReportServerDisabled) GetOnline HelpBad Data.--------------------------------------------------------------------------------Microsoft Reporting ServicesEntering http://localhost/Reports in my web browser generates the followingerror:The report server cannot decrypt the symmetric key used to access sensitiveor encrypted data in a report server database. You must either restore abackup key or delete all encrypted content and then restart the service.Check the documentation for more information. (rsReportServerDisabled) GetOnline Help Bad Data.The only way I can seem to get 2000 Reporting Services working is to do thefollowing:- run C:WINDOWSMicrosoft.NETFrameworkv2.0.50727aspn et_regiis.exe -u- uninstall 2000 Reporting Services- run C:WINDOWSMicrosoft.NETFrameworkv1.1.4322aspne t_regiis.exe -i- install 2000 Reporting ServicesBut once I've done that Visual Studio 2005 etc no longer work.The utlimate goal is an ASP.NET 2.0 application developed in Visual Studio2005; the application is based on a SQL Server 2000 database and needs toinvoke SQL Server 2000 Reporting Services to run reports.What am I doing wrong?ANY HELP WOULD BE GREATLY APPRECIATED - I'M DIEING HERE AND MY CLIENT ISLOSING PATIENCE !!!!!
Hi friends, i have some questions about Reporting Services 2005:
Can i use RS 2005 with a SQL 2000 Database? Can i create a report with RS 2005 (with a SQL 2K Database) a show it in a webform? What do i need to install (in the webserver and in the Database server) in order to start designing reports in RS 2005 against a SQL 2K DB?Thanks in advance. Regards Eduardo
Is there any way to pass a dataset parameter in RS 2000? Basicly, I have some data in my web page and want to print it. But I don't want to create another page to pass parameters to RS. I want to print the page as it is with the data already in the page, so if there is a way I can send the data through a dataset to the report directly, would be great. Is there?
Hello, We want the reporting tool to be integrated with visual studio 2005. From my understanding SQL reporting services 2000 can be integrated only with visual studio 2003 (Please correct me if I am wrong) . Hence we have decided to go for SQL reporting services 2005 I understand that SQL reporting services 2005 can be used with SQL server 2000 database. I want to know if SQL reporting services 2005 and SQL server 2000 database are on a single machine, would a single license for SQL server 2000 suffice or should we have a license for sql server 2005 (since we use SQL reporting services 2005) as well.
I successfully got SQL 2005 Express with reporting services running under VISTA. Developed some reports in the VISTA environment. However, my target system is a Windows 2000 server. We installed SQL 2005 w/reporting services onto the Windows 2000 server. SQL2005 Database is up and running. Reporting Services are running, IIS RRS virtual directories are built, RRS databases are built. I can do everything except deploy reports from Business Intelligent Studio. I can preview reports, just cannot deploy. The Reporting Services indicate 1 failure in its configuration; the Web Service Identity. It is loaded with <server>ASPNET. I cannot get rid of this error. I assume this is the problem. After digging around I found that Windows 2000 does not have an ASPNET user, it uses the IWAM user instead. Reporting services did not run at all till I changed the rs config file and put the IWAM user in as <WebServiceAccount>.
Does anyone have Reporting services 2005 running on Windows 2000 server? Anyone know how to fix the Web Service Identity error I am getting?
We currently have a report generated weekly running script which creates an excel file and pivot tables. Using pivot tables we can drag and drop the various required fields and the report changes instantly. But i was told there is a limitation of size while using pivot tables.
Can this report be easily created with almost all the flexibility in reporting services, if so could you please guide me with some sample report or tutorials.
currently there is a some store procedures thats run every week using a DTS manually, is there a way of automating this.
I am in the middle of migrating all Crystal Reports over to SSRS and am having some troubles converting formulas used in Crystal Reports to functional expressions in SSRS. For example: My formula for one of the crystal reports is the following. Very simple logic but how would I build it as an expression to work in my SSRS report?
IF {CUST_ORDER_LINE.ORDER_QTY}-{CUST_ORDER_LINE.TOTAL_SHIPPED_QTY} < 0 THEN 0 ELSE {CUST_ORDER_LINE.ORDER_QTY}-{CUST_ORDER_LINE.TOTAL_SHIPPED_QTY}
Hi, I'm wondering if I can use SQL 2005 Reporting Services with SQL Server 2000, SQL Express or MSDE, or I need to install SQL Server 2005 in order to use Reporting Services 2005? Thank you in advance.
I apologize for not doing the legwork to see if i can answer my own question, but I am close to a loosely planned SQL 2005 migration and don't have time and resources to test my own theories.
Is there a way for a Reporting Services 2000 server to connect to SQL server 2005 databases? I've tried creating a new data source and changing a report to this data source, but it seems like the report is still using the old data source. I'm guessing i might need to register new data providers on the 2000 RS server and then change the existsing data sources.
Is there any way to deploy reports to a Report Manager in SQL Server Reporting Services 2005 if the reports query SQL Server 2000 databases? Or are only 2005 databases able to deploy to the web?
Also, if I have a report that queries both, can I deploy it to the web on the 2005 Report Manager with a linked server to the 2000 server?
I had to migrate my report server (2008R2) to a new domain. I built new server and restored the old ReportServer and ReportServerTempDB into new server and also restored the certificate from old server. The Report Server is running but I don't have full access to all server futures anymore, looks like it's AD authentication messed up. My new account is Admin on new server but I can't see all options, like New Data Source, or wehn going on report level to manage to see all option such as Parameters, Subscriptions, Data Source.
I am currently migrating several Crystal Reports that have charts. The chart series is set to use the TopN values in a count, and combine the rest of the series into one series titled "Other". I see how to filter the chart using TopN, however I need to still show the rest of the data grouped as "Other". I think the solution I need is to create a group expression that uses some sort of IIF function to create the "Other" group, but I haven't found a function that I can use to get the results I need. Any ideas?
I'm in need of migrating DB's from a SQL 2000 server to a new SQL 2005 server. Has anyone had any success in this or does anyone know of a process which would be best for this situation?
Here's my setup...
SQL2000 SERVER....OS - Server 2000 MDF's/LDF's reside on D:MSSQLData Backups reside on D:MSSQLBackup
SQL2005 SERVER....OS - Server 2003 MDF's/LDF's reside on E:MSSQLData Backups reside on E:MSSQLBackup
Any information on how to get these DB from 2000 to 2005 will be greatly appreciated.
Hi, since havenot done migration yet, my company is planning to migrate from sql 2000 to sql 2005 server. and i am in group for capacity planning. can anybody suggest me the steps i should be really taking in order to migrate to 2005, if anyone has done the it in real world with database up to 50g. thanks Derek
Guys! Very very junior in this migration part. Hope the seniors can help out....PLEASE!!!!!! Don't get me wrong asking you guys to spoon feed me. I have read a lot of articles and even BOL and also not to forget read millions of books on this. But just wanted to make sure that I am in the right path and want to do this without any problem. That's why I have decided to ask the Gurus here who have done this in past.
I have this machine now:
Microsoft SQL Server 2000 - 8.00.2040 (Intel X86) Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: )
Migrating to this machine:
Microsoft SQL Server 2005 - (X64) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
I have these in the SQL Server 2000 box: 1. Databases, tables (of course) 2. Views 3. Securities(Logins, Roles, Password) 4. DTS packages 5. Jobs 6. Replications 7. Linked Servers 8. Stored Procedures
Every article is different. I was confused at a point of time. Please show me the right way guys!
Yesterday I started this topic and I came step by step higher and now I have finalized my steps to migrate.
Seniors and Gurus and who has done this before, please review and correct me where I am wrong and/or add some tips for me to have this one going on successfully! Thanking all of you guys in advance! Here is what I have:
Before Migrating: 1. Install Service Packs, Security Patches and Hot Fixes 2. Install DTS Designer Tool from Microsoft to prevent conflict and failure of migrating current DTS packages to SQL Server 2005 3. Backup EACH and EVERY Database and double check the .bak files whether it exist and backup was successful 4. Just before migrating, reboot the server to clarify that the SQL Server Services and SQL Server Agent is working When you are ready to migrate: 5. Make sure there are no users trying to connect to the OLD AND the NEW SQL Server. Inform them well in advance about the downtime. Shutdown any applications or websites that might be accessing the SQL Server. 6. Stop the SQL Server, SQL Agent and MS Search Services on the NEW SQL Server If downtime is not possible: 7. For ever changing OLTP database, by the time you restore the backup onto the new server, the old server would have received more changes. To avoid this problem, you need to resort to log shipping. Log shipping is nothing but an automated process of backup and restore. The following steps will explain the process of log shipping (Note that SQL Server 2000 Enterprise Edition provides inbuilt logs hipping. We don't need that for this purpose. We can simply create a job that backs up and restores the databases 8. Create a job on the old server, with two steps. The first steps backs up the transaction log of the OLTP database. The second step restores this transaction log backup file onto the new server, using WITH STANDBY or WITH NORECOVERY option of the RESTORE command. Schedule this job to run every 10 minutes or 15 minutes, depending on the volume of transactions your OLTP database receives 9. This job will take care of shipping all new transactions since the full database backup, to the database on the new server. Let this job run until you can afford some downtime on your production database (that is, mid-night, or early morning, or a planned maintenance window) 10. Now to be doubly sure, no new transactions are coming in, set the database in 'single user' or 'dbo use only' mode. Take one last transaction log backup of the production OLTP database, and restore it onto the database on new server. This time use the WITH RECOVERY option of the RESTORE command 11. Run UPDATE_STATISTIC on User Database to reorganize all indexes Considerations: 12. Security - The security model changed along with object ownership, but users that own objects will be turned into schemas and all of the object and role permissions will come over. These you will want to look over afterwards, but they should be ok. 13. Unless you have hundreds of them, it is always better to re-create them after upgrading. You cannot detach an MSDB database on a 2000 server and attach it on a 2005 server and have it work. Fortunate in this, we can script out the jobs from SQL Server 2000 and run it on the new SQL Server 2005 14. Typically you will have to re-create your replication too. Again, the good news is that you can generate the scripts for replication on a 2000 server and execute them on a 2005 server and it will create the appropriate articles and publications 15. For DTS packages, it is always recommended to use the Package Migration wizard to do this so that less or no problems will be encountered. Consider about the jobs previously set. 16. Logins can be created by using sp_hexadecimal and sp_revlogin2005
Hello guys, I have vry basic question. I'm migrating from 2000 to 2005. MY question is do we have to recode all packages or just migrating of old 2000 DTS is fine. If so, then I can see only small icon of DTS package in 2005, whihc is not showing the details of DTS. Kindly, explain me what do i really do, migrating old one or re-creating new in 2005. Thanks in Advance
Has anyone had experience of migrating from 2000 to 2005 on the same box , and maintaining the SERVERNAMEINSTANCE_NAME. What are some effective ways of migrating and retaining the same servername/instance name ?
The issue revolves around minimising the use of extra boxes , as I would like to do the migration on the same server and keep the name the same .
Jack Vamvas -------------------- Search IT jobs from multiple sources- http://www.ITjobfeed.com
Hi, I have a database on a SQL Server 2000, and would like to migrate it to a new server machine that has SQL Server 2005. has anyone already tried this, and can you please provide the steps to follow.
We are migrating from SQL Server 2000 to 2005. We currently use ADO.Net to make connection to sql server. I just want to know after migration to sql server 2005 do we have to make any changes in code in the way we make connection to use ADO.Net2 which is part of sql server 2005. ??
