Backup the database from the old server and restore it to a different database on the new server.

Then you can do a simple outer join between the tables and insert...

If you're brave, you can check the subscription status in the ReportServer database and email when the subscription fires. You could poll the table from a SQL Agent job.

If you're...

Hope you're not trying to create an extract file in Reporting Services. Something like DTS, SSIS or BCP is better suited to that and you can specify your own seperator.

Lester, probably not a good idea to go around modifying system tables directly. Can get you into an awful pickle with Microsoft when you have a problem you want them...

Can't the custom page go into the Control Panel somehow? Maybe a change to add to the long term list 😉

Keep up the great work. Despite the many "little" niggles,...

Haven't found a "default" setting yet. It may be there somewhere.

In the meantime, choose the applicable subscription option in the "Post Options" below the edit pane. Only take one click...

SQL 2005 variant that doesn't use a loop.

http://philcart.blogspot.com/2007/06/split-function.html

Could be easily modified to work with nvarchar(4000)

Hmm ... I found it pretty easy. Just click on your name and then choose "Find All Members Post" from the context menu.

Another option is to click the "Control Panel"...

Top job kudos to all involved.

Now if only the links from the Newsletter would work 😉

I've been working as a "Remote DBA" for the past nine months and we have clients across a very broad spectrum. Retail, Finance, Legal, Automotive, Travel, etc...

Each client has their...

That post doesn't show what version of SQL they're talking about. Without reading up on old documentation, I wouldn't make any absolute statements. I can only make a guess at...

The transaction log is made up of multiple virtual log files (VLF). Without doing a lot of digging through old documentation, my guess would be that it's removing the empty...

Backing up the database is seperate to backing up the log.

Take a look at the following article,

http://msdn2.microsoft.com/en-us/library/ms191253.aspx

It's for SQL 2005, but most of it is applicable to SQL Server in...

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

You're not saving your T-log now. The WITH TRUNCATE_ONLY is throwing it away.

If you want to save the transaction log then you should be backing it up to a file...