Just couple of questions.

How sure are you that you do not have any embedded SQL's in the applications that might not work in 2005?

Did you by any chance test all...

Maybe this is not what you want, but did you check the article posted here about the Page viewer?

http://www.sqlservercentral.com/articles/Product+Reviews/3200/

Maybe it could help. But I am not sure.

I agree with Jeff. Get rid of the cursor. My personnel belief is that cursors are the tools invented by the evil....;)

colin Leversuch-Roberts (12/31/2007)

---

you should not name user stored procedures...

We made sure that Phantom objects does not get created by going for a two prong security measure.

1. All Objects that need to be created should be Scheama Qualified....

Since it is going to be large DB, make sure you keep an eye on the Indexes. Keep an eye on Statistics.

I came across an issue where a Stored...

Indexing is something that you have to do carefuly. Study the Data and first try to find out what is the main criterea in almost all the queries. If it...

You can have an App that takes the Text as DB Name and pass it to the Stored Proc.

The stored proc should have the Restore command in Dynamic SQL.

You should...

The SQL Query would be like this...

Select CustomerID, col2, col3 from tbCustomerTbl1

where CustomerID = @parameter

If (@rowcount = 0)

Select CustomerID, col2, col3 from tbCustomerTbl2

where CustomerID = @parameter

That should retrieve the rows....

This is possible.

If you have the Back up of the MainDB and script for all Jobs it is quite possible.

You can restore the DB into the new machine with...

I am not sure what you want to see... Or what help you need. You say it is complex. So why not just copy the body of the Stored proc...

Is your DB set to Auto Close? That could be the reason for the errors shown on the sql server log files.

Also I read somewhere that if you have DBCC...

Are you calling a stored Proc to query the DB from your form? Or is it Raw SQL?

If Stored Proc you can do it quite easily with an IF Statement.

Either...

That is the best news I have...

Did you by any chance check the SQL Server Log? Was there any thing strange there?

Also check the Event viewer to see if it was throwing some IO errors. Nothing...

From BOL.

USE AdventureWorks;

GO

DECLARE @SQLString NVARCHAR(500);

/* Set column list. CHAR(13) is a carriage return, line feed.*/

SET @SQLString = N'SELECT FirstName, LastName, JobTitle' + CHAR(13);

/* Set FROM clause with carriage return, line...