Have you ever faced in a scenario where you are required to rename existing database. While dealing with one my client I have installed reporting server and during RS configuration I’ve chosen the default settings while creating the database so it created the reporting server dbname as ReportServer and ReportServerTempdb and RS working fine.
Few days back I was working with one of my colleague with reporting service. I dont have much exposure to RS however its a simple task, he asked me to download a RDL file from the report server, we are using RS2005 and couldnt find download or export button which is supposed to be in different name. In this article we are just going to see how to download or export the RDL from your reporting server.
In my previous webcast we have seen how to install reporting services 2008. Here is my next webcast on configuring reporting services 2008.
In this webcast we are going to install SQL Server reporting services 2008. Watch the video and post your feed back incomments.
In my previous article we have covered installing reporting service. The next step in reporting service is to configure them according to your environment.
There are many options are available in reporting service configuration. You need to configure all these values with respect to your environment. There are two ways to configure reporting service a.) Using Reporting service configuration GUI and b.) Reporting service configuration command line utility (RSConfig.exe located @ C:Program FilesMicrosoft SQL Server90ToolsBinn directory). The reporting service GUI configuration tool is very simple to use and many prefer this. Lets configure reporting service using this GUI too.
RA
| #
Thanks for the script. I had database with space between the names.
I modified to use square brackets:
FROM [?].sys.database_principals a
LEFT OUTER JOIN [?].sys.database_role_members
and
from [?].sys.database_permissions join [?].sys.sysusers U
on grantee_principal_id = uid join [?].sys.sysobjects
Gangadhar NG
| #
This tip is helpful enough for me.
thanks.
Zukunftsmusik
| #
Thanks! That helped my a lot. But there’s a little mistake:
SQL_Latin1_General_CP1_CI_AS stands for “Latin1-General, case-insensitive, accent-sensitive [...]” therefore sort order 52.
If you want to set the sort order to 54 the correct collation would be “SQL_Latin1_General_CP1_CI_AI”
Amit Bhatt
| #
Hi Deepak,
Thanks for such a nice article.
You missed one thing to add in code:
@article = ‘all’,
Hence the script will be like this:
EXEC sp_addsubscription
@publication = ‘mypublication’,
@article = ‘ALL’,
@subscriber = ‘Subscriberservername’,
@destination_db = ‘mydestinationdbname’,
@reserved=’Internal’
Error 18486 | Platformblog
| #
[...] SQL-Articles » Troubleshooting Login failed Error 18456This is one of the infamous error message (and number) that most of the DBAs …. 18486. Login failed for user ‘%.*ls’ because the account is currently locked out. [...]