Clear Cache sqlrs.ReportingServices2005

I'm using the Reporting Service web service to display my reports to the user.
I've deleted some test reports from the server. I've also gone to the
server, searched the test report names, and deleted those.
When I display the available reports using the Reporting Services web
service, the test reports are still there.
How do I remove Reporting Service reports from the server?
Thanks
--
RandyGo to Report Manager, click on report, properties, delete button.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"randy1200" <randy1200@.newsgroups.nospam> wrote in message
news:F873554A-B145-4800-B93F-65B3F6AFC955@.microsoft.com...
> I'm using the Reporting Service web service to display my reports to the
> user.
> I've deleted some test reports from the server. I've also gone to the
> server, searched the test report names, and deleted those.
> When I display the available reports using the Reporting Services web
> service, the test reports are still there.
> How do I remove Reporting Service reports from the server?
> Thanks
> --
> Randy

Clean up replication data

I have a develop machine for our web site. On this machine I have a copy of a database from the production site. The database on the production site is being replicated. When I copied the database to the develop machine and started testing some new developments I got the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80040e37'

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'sysmergearticles'

This tells me that some replication data is also copied to the develop database.

Can anyone tell me how I can clean this data, or if I should copy the databse in a different way. (Now I create a new databse and do an import of the tables and stored procedures)You could try to remove replication by going under Tools(in EM)-->Replication-->Disable publishing,Distri...If it allows you to do so then it's fine.Or else you could try to first set the replication on your Test system and then remove ot by using the Tools-->Replication.
Or you may try the script below:

USE [DBNAME]
GO

-- Drop all replication triggers from the database
PRINT 'Drop all replication triggers from the database'
SELECT trigs.name AS TriggerName,
trigs.id AS TriggerID,
tables.name AS TableName
INTO #Triggers
FROM sysobjects trigs
INNER JOIN sysobjects tables
ON trigs.parent_obj=tables.id
where trigs.category=2 and trigs.xtype='TR'

DECLARE @.TriggerName varchar(100), @.TriggerID INT, @.TableName varchar(100)

DECLARE cur CURSOR for SELECT * FROM #Triggers
OPEN cur
FETCH NEXT FROM cur INTO @.TriggerName, @.TriggerID, @.TableName
WHILE @.@.FETCH_STATUS=0
BEGIN
EXECUTE ('DROP TRIGGER ' + @.TriggerName)
FETCH NEXT FROM cur INTO @.TriggerName, @.TriggerID, @.TableName
END
CLOSE cur
DEALLOCATE cur
GO

-- Drop all replication constraints from the database
PRINT 'Drop all replication constraints from the database'
DECLARE @.ConstName varchar(100), @.ConstID INT, @.TableName varchar(100)

SELECT CONST.name AS ConstName,
CONST.id AS ConstID,
tables.name AS TableName
INTO #Constraints
FROM sysobjects CONST
INNER JOIN sysobjects tables
ON CONST.parent_obj=tables.id
where CONST.xtype='C'

DECLARE cur CURSOR for SELECT * FROM #Constraints
OPEN cur
FETCH NEXT FROM cur INTO @.ConstName, @.ConstID, @.TableName
WHILE @.@.FETCH_STATUS=0
BEGIN
EXECUTE ('ALTER Table ' + @.TableName + ' DROP CONSTRAINT ' + @.ConstName)
FETCH NEXT FROM cur INTO @.ConstName, @.ConstID, @.TableName
END
CLOSE cur
DEALLOCATE cur

GO

-- Drop all replication User tables
PRINT 'Drop all replication User tables'
DECLARE @.TableName varchar(100), @.TableID INT

SELECT Tables.name AS ConstName,
Tables.id AS ConstID
INTO #Tables
FROM sysobjects Tables
where Tables.xtype='U' AND Status < 0 AND category=2050

DECLARE cur CURSOR for SELECT * FROM #Tables
OPEN cur
FETCH NEXT FROM cur INTO @.TableName, @.TableID
WHILE @.@.FETCH_STATUS=0
BEGIN
EXECUTE ('DROP Table ' + @.TableName)
FETCH NEXT FROM cur INTO @.TableName, @.TableID
END
CLOSE cur
DEALLOCATE cur

GO

-- Drop all replication User procedures
PRINT 'Drop all replication User procedures'
DECLARE @.ProcName varchar(100), @.ProcID INT

SELECT Procs.name AS ConstName,
Procs.id AS ConstID
INTO #Procedures
FROM sysobjects Procs
where procs.xtype='P' AND Status < 0

DECLARE cur CURSOR for SELECT * FROM #Procedures
OPEN cur
FETCH NEXT FROM cur INTO @.ProcName, @.ProcID
WHILE @.@.FETCH_STATUS=0
BEGIN
EXECUTE ('DROP Procedure ' + @.ProcName)
FETCH NEXT FROM cur INTO @.ProcName, @.ProcID
END
CLOSE cur
DEALLOCATE cur

GO

-- Drop all replication User Views
PRINT 'Drop all replication User Views'
DECLARE @.ViewName varchar(100), @.ViewID INT

SELECT MyViews.name AS ConstName,
MyViews.id AS ConstID
INTO #Views
FROM sysobjects MyViews
where MyViews.xtype='V' AND Status < 0 AND Name NOT LIKE 'sys%'

DECLARE cur CURSOR for SELECT * FROM #Views
OPEN cur
FETCH NEXT FROM cur INTO @.ViewName, @.ViewID
WHILE @.@.FETCH_STATUS=0
BEGIN
EXECUTE ('DROP View ' + @.ViewName)
FETCH NEXT FROM cur INTO @.ViewName, @.ViewID
END
CLOSE cur
DEALLOCATE cur

GO

-- Drop all replication rowguids, defaults and indexes
PRINT 'Drop all replication rowguids, defaults and indexes'
SELECT tables.name as TableName,
defaults.name AS DefaultName,
Indexes.IndexName,
cols.name AS ColumnName
INTO #Defaults
FROM sysobjects defaults
INNER JOIN syscolumns cols
ON defaults.ID=cols.cdefault
INNER JOIN sysobjects tables
ON tables.id=cols.id
INNER JOIN
(select sysindexes.name AS IndexName,
Tables.Name AS TableName,
Tables.id as TableID,
cols.Name AS ColumnName
from sysindexes
INNER JOIN sysobjects Tables
ON sysindexes.id=tables.id
INNER JOIN sysindexkeys k
on sysindexes.id=k.id
AND sysindexes.indid=k.indid
INNER JOIN syscolumns cols
ON k.id=cols.id
AND k.colid=cols.colid
where cols.name='rowguid') Indexes
ON Indexes.TableID=tables.id
where cols.name='rowguid'

DECLARE @.DefaultName varchar(100), @.IndexName varchar(100), @.TableName varchar(100), @.ColName varchar(50)

DECLARE cur CURSOR for SELECT * FROM #Defaults
OPEN cur
FETCH NEXT FROM cur INTO @.TableName, @.DefaultName, @.IndexName, @.ColName
WHILE @.@.FETCH_STATUS=0
BEGIN
EXECUTE ('ALTER TABLE ' + @.TableName + ' DROP CONSTRAINT ' + @.DefaultName)
EXECUTE ('DROP INDEX ' + @.TableName + '.' + @.IndexName)
EXECUTE ('ALTER TABLE ' + @.TableName + ' DROP COLUMN rowguid')
FETCH NEXT FROM cur INTO @.TableName, @.DefaultName, @.IndexName, @.ColName
END
CLOSE cur
DEALLOCATE cur
GO|||I've been trying to delete the conflict tables left over after EXEC sp_removereplication

Your script did it!

Clarify the name changes on all SQL Server 2005 CE RC1 pages and give installion help for mobile

Please add some more substantial needed info in ALL the web pages of "SQL Server 2005 Compact Edition RC1, Release Candidate 1", like at:

http://support.microsoft.com/kb/920700

for:
1) Clarifying the confusing name changes of the Mobile Edition to Everywhere Edition then to CE,
2) Giving installion instructions of the RC1 for mobile devices

Thanks,
Alpoge

I can address 1):

Microsoft first started using the name "Microsoft SQL Server 2005 Everywhere Edition" during the alpha and early beta tests. Once Microsoft branding and their legal team completed their work (and negotiations with Sybase) they decided to change the name to "Microsoft SQL Server 2005 Compact Edition". This name change is being propagated into Visual Studio 2005 and SQL Server Management Studio as well as into the OLE DB drivers and .NET providers (as described in my Ebook). Last news in this regard says that the changes will be first seen in January sometime. Since the SqlCe namespace is unchanged, your source code should not have to change.

2) I don't work with Mobile devices, but as I understand it, there is no change in how it's deployed to these devices.

See www.hitchhikerguides.net for more information.

hth

|||See these postings as well

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1038295&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1046958&SiteID=1

Clarify the name changes on all SQL Server 2005 CE RC1 pages and give installion help for mo

Please add some more substantial needed info in ALL the web pages of "SQL Server 2005 Compact Edition RC1, Release Candidate 1", like at:

http://support.microsoft.com/kb/920700

for:
1) Clarifying the confusing name changes of the Mobile Edition to Everywhere Edition then to CE,
2) Giving installion instructions of the RC1 for mobile devices

Thanks,
Alpoge

I can address 1):

Microsoft first started using the name "Microsoft SQL Server 2005 Everywhere Edition" during the alpha and early beta tests. Once Microsoft branding and their legal team completed their work (and negotiations with Sybase) they decided to change the name to "Microsoft SQL Server 2005 Compact Edition". This name change is being propagated into Visual Studio 2005 and SQL Server Management Studio as well as into the OLE DB drivers and .NET providers (as described in my Ebook). Last news in this regard says that the changes will be first seen in January sometime. Since the SqlCe namespace is unchanged, your source code should not have to change.

2) I don't work with Mobile devices, but as I understand it, there is no change in how it's deployed to these devices.

See www.hitchhikerguides.net for more information.

hth

|||See these postings as well

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1038295&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1046958&SiteID=1

Cisco

Is anyone using Cisco ICM and sql server 7.0 ,need some assistance with acount replication on the advanced services web deploymentIm all alone ,nobody here beside me,nobody to deride me...

Is no-one using ICM?

cipher

hi
i'm a web application developer. i am writeing a commercial system. i want to cipher my data. i use microsoft sql server 2000 to store my data.i use ASP to develop my application.
please tell me how i cipher my database and ensure my application security.
thanks.if you're using ASP you're on the wrong site. this is an ASP.NET site. However...

as for 'cipher'ing your data, there's more to security than just ROT13ing the stuff you store in your database. you ought to sit down and read up on web application security rather than just asuming encipherment is your friend (it's not - by definition encipherment is NOT the same as encryption and is inherently breakable)

for a start-out, try www.aspin.com (they have a security section), www.badwebmasters.net, www.securityfocus.com, www.4guysfromrolla.com, www.aspfaq.com, www.developersdex.com and most importantly google. with the right keywords you'll turn up a host of information on ways to secure your ASP code.

j

Choosing DBMS and architecture for ecommerce website

Hi to all

I have to choose a DBMS and a database architecture for an Ebay like
website about to be launched.

The company wants to use a web hosting service and not host the
database on dedicated servers at the office.

The database will contain web-only information and lots of back end
information that is not really needed to be stored on the web host.

I'm wondering how to design that part, should I store all information
on the web host only ? miror that DB every evening on some local DB
server to be able to use the data without eating up lots of bandwith ?
separate the database in 2 parts ? how to sync and assure integrity
then ? having a local DB will also mean the company will have to pay a
licence for the DBMS ...

What DBMS should I pick considering that the database will have to
hold at least 1 million products to sale (eBay like) and all the
information that goes with it. I thought any DBMS weaker than SQL
Server or Sybase or Oracle will not be enough. What do you think ?

Thanks a lot, hope I have made myself clear enough

P.S. I would really like to get lots of different points of view. I
think I'll use Sybase after all, so I wonder if that'sa good choice
and I still want to know your thoughts about the 2 or 1 DB design
(separate Web & Billing information for example, or leave all the info
in the hosted database, what techniques to use to keep the integrity
and to have the latest information in-house)... Thanks a lotOn Mon, 03 Nov 2003 07:08:07 -0800, Alex_Bxl wrote:

> I'm wondering how to design that part, should I store all information
> on the web host only ? miror that DB every evening on some local DB
> server to be able to use the data without eating up lots of bandwith ?
> separate the database in 2 parts ? how to sync and assure integrity
> then ? having a local DB will also mean the company will have to pay a
> licence for the DBMS ...

I'd use Sybase, and I'd use replication server to move data from the
production server (in co-location facility) to the reporting server (in
the office).

But you can do similar things with Oracle, MS-SQL, etc., although I'd
personally stay away from MS-SQL due to its being Microsoft-centric (i.e.
can't scale beyond Intel/Windows type machines)

Michael
--
Michael Peppler Data Migrations, Inc.
mpeppler@.peppler.org http://www.mbay.net/~mpeppler
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or
long term contract positions - http://www.mbay.net/~mpeppler/resume.html|||"Michael Peppler" <mpeppler@.peppler.org> wrote in message news:<pan.2003.11.03.15.33.00.222843@.peppler.org>...
> On Mon, 03 Nov 2003 07:08:07 -0800, Alex_Bxl wrote:
> > I'm wondering how to design that part, should I store all information
> > on the web host only ? miror that DB every evening on some local DB
> > server to be able to use the data without eating up lots of bandwith ?
> > separate the database in 2 parts ? how to sync and assure integrity
> > then ? having a local DB will also mean the company will have to pay a
> > licence for the DBMS ...
> I'd use Sybase, and I'd use replication server to move data from the
> production server (in co-location facility) to the reporting server (in
> the office).
> But you can do similar things with Oracle, MS-SQL, etc., although I'd
> personally stay away from MS-SQL due to its being Microsoft-centric (i.e.
> can't scale beyond Intel/Windows type machines)
> Michael

Dual DB's aren't really necessary.

Points in favor of 2 DB's
*its standard approach Production and Development DB's
*large reports don't hog resources from live interactions.
*new developments/data are staged in development first, in a secure,
isolated environment.

points in favor of 1 DB
*if its accessable from the WEB then developers can work there too.
(schema isolation should be as good as DB isolation)
*web access means you know when the site goes down.

I've seen both.

Check sql table input at certian times and send email

I have a .net web application and need to create a program that needs to check the database every two hours and if data has not been input send the user an email message. I have heard this can be done via SQL Server - events or triggers? Can anyone tell me where I can find example code or more information on this. Thank you in advance.

Hi,

Yes since your whole work is within the database then I think setting up a "SQL job" will be the best possible solution also you can schedule it to run on certain times. Basically you need to create a "stored procedure" which will check the table and will be sending mail and you can call this stored procedure from your job. Mails can be sent by using "SQL Mail" or using .NET framework (if you are using Sql Server 2005).

I have marked the importent terms in the mail. You can get best materials on them in Books Online in Sql Server.

Hope it helps!

Bhaskar!

|||

In a well trafficed website, I usually drop that in the login.aspx page, or if I have enabled cookies, then another often hit page.

You can also do this using sql agent. Write the stored procedure to scan the table, and generate the emails. Then tell sql agent to execute that stored procedure every two hours.

check sql server 2000 or sql server 2005

Hi..

I have a web application(ASP.NET 2.0 + C#). I have sql server 2000 as well as sql server 2005.

Several queries in my application work well with the sql server 2005, and the same query fails in the sql server 2000.

How to check if the database is connected to sql server 2000 or sql server 2005 and then call the queries accordingly through the c# code?

Thanks

That may be happening if you are using built-in stored procedures or the INFORMATION_SCHEMA from 2005. There's stuff in 2005 that doesn't exist in 2000.

You are the one establishing the connection, right? You have to know which one you are connecting to when you do, right? You'll have to have a connection to your 2005 instance and one to your 2000 instance. Although for performance purposes, I'd recommend migrating your db to 2005.

Of course, you can always look at the Database property of your connection object if you are getting it from somewhere deep in the bowels of legacy code.