Deleting Reports in Report Server without stopping Report Service

I'd just like to know if it's okay to delete reports in the report server without having to stop the reporting service or without having to restart it? Has anybody tried this?

Thanks.SUre this is one of the administrative tasks that can be done via the Web UI.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

DeleteSubscription leaves job in SQL Server

Has anyone else noticed that if you create a timed subscription using

the web service and then delete it using the DeleteSubscription method,

there is a job (id'ed by a guid) left in SQL Server Jobs?

Consequently we now have hundres of "orphaned" jobs in our database :-(

A bit more investigation appears to reveal this:

I use data driven subscriptions and create them using CreateDataDrivenSubscription. Therefore I retrieve them using GetDataDrivenSubscriptionProperties. The matchData returned does not contain a scheduleId. Is that correct? Well calling ListSchedules returns an empty row, indicating that the schedules created are not shared, so cannot be deleted using DeleteSchedule anyway. However, and this is where the bug appears to be, the schedules are in the ReportSchedule table and the jobs are in SQL Server. Calling DeleteSubscription does not delete the SQL Server Job, nor does it delete the row from ReportSchedule. Is this a bug? Is there a fix or do I have to delete the row myself and delete the job from SQL Server using DMO or some such hack.

|||

The SQL Agent jobs should be deleted when the associated subscription is deleted. There appears to be a problem with your system.

Can you take a peek at Event Viewer and SQLAgent log files and see if there is any incriminating evidence?

Delete sys.Transmission_Queue

I have seen this buried deep with the questions on Service Broker, but I am looking for it again. How do you delete all records from your sys.Transmission_Queue. This is on a test server and I want to clean it before some more test.

alter database foo set new_broker;

Delete query in Linked server

Hi,
I have a pair of SQL Server 2005 (SQL Server 2005 - 9.00.3054.00 Build 3790:
Service Pack 2) running on Windows 2K OS. Linked server is established and
working fine for all type of queries except the following delete query.
DELETE A from ttdb1.sasixp.sasi.aprn7030 A
WHERE
not EXISTS ( SELECT stulink
FROM ttdb1.sasixp.sasi.astu7030 B
WHERE B.stulink = A.stulink )
But the same query is working fine in test server. Test SQL Server 2005
version is SQL Server 2005 - 9.00.3042.00 Build 3790: Service Pack 2). But
production server ver is SQL Server 2005 - 9.00.3054.00 Build 3790: Service
Pack 2. This is the only difference between test server env & production
env.
When I run this query got the following error:
OLE DB provider "SQLNCLI" for linked server "ttdb1" returned message
"Multiple-step OLE DB operation generated errors. Check each OLE DB status
value, if available. No work was done.".
Msg 7202, Level 11, State 2, Line 1
Could not find server 'TTDB1' in sys.servers. Verify that the correct server
name was specified. If necessary, execute the stored procedure
sp_addlinkedserver to add the server to sys.servers.
Any idea what causes this problem?
Thanks in advance for your help.
VenkatPlease read the post below, I had the same issue and got it fixed by changing
the servername.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=274270&SiteID=1
Regards,
Henry
"Venkat N" wrote:
> Hi,
> I have a pair of SQL Server 2005 (SQL Server 2005 - 9.00.3054.00 Build 3790:
> Service Pack 2) running on Windows 2K OS. Linked server is established and
> working fine for all type of queries except the following delete query.
> DELETE A from ttdb1.sasixp.sasi.aprn7030 A
> WHERE
> not EXISTS ( SELECT stulink
> FROM ttdb1.sasixp.sasi.astu7030 B
> WHERE B.stulink = A.stulink )
> But the same query is working fine in test server. Test SQL Server 2005
> version is SQL Server 2005 - 9.00.3042.00 Build 3790: Service Pack 2). But
> production server ver is SQL Server 2005 - 9.00.3054.00 Build 3790: Service
> Pack 2. This is the only difference between test server env & production
> env.
> When I run this query got the following error:
> OLE DB provider "SQLNCLI" for linked server "ttdb1" returned message
> "Multiple-step OLE DB operation generated errors. Check each OLE DB status
> value, if available. No work was done.".
> Msg 7202, Level 11, State 2, Line 1
> Could not find server 'TTDB1' in sys.servers. Verify that the correct server
> name was specified. If necessary, execute the stored procedure
> sp_addlinkedserver to add the server to sys.servers.
> Any idea what causes this problem?
> Thanks in advance for your help.
> Venkat
>
>