Showing posts with label contained. Show all posts
Showing posts with label contained. Show all posts

Tuesday, March 20, 2012

copy database via tapefile no SQL 2005

Hello,

if you got a tape file how can you restore the contained database onto a
newly installed server? I choose Restore Database From Device then I choose
DB and select same DB in combobox "To Database" but error occured:

TITLE: Microsoft SQL Server Management Studio
Restore failed for Server '...'. (Microsoft.SqlServer.Smo)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: Directory lookup for the file "C:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\KidDatabase.mdf" failed with
the operating system error 3(error not found). (Microsoft.SqlServer.Smo)

what can I do to handle this problem?

regards
MarkMark (Scollop027@.gmx.net) writes:

Quote:

Originally Posted by

if you got a tape file how can you restore the contained database onto a
newly installed server? I choose Restore Database From Device then I
choose DB and select same DB in combobox "To Database" but error
occured:
>
TITLE: Microsoft SQL Server Management Studio
Restore failed for Server '...'. (Microsoft.SqlServer.Smo)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: Directory lookup for the file "C:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\KidDatabase.mdf" failed with
the operating system error 3(error not found). (Microsoft.SqlServer.Smo)
>
what can I do to handle this problem?


First do

RESTORE FILELISTONLY FROM TAPE = 'tapedevice'

this will give you the logical names of the files of the database. Then
do:

RESTORE DATABASE db FROM TAPE = 'tapedevice' WITH
MOVE 'datafile' TO
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\KidDatabase.mdf',
MOVE 'logfile' TO
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\KidDatabase.ldf',
REPLACE

Here I've used the path from your error message. Howver, the error message
indicates that this is a non-existing path, so you may have to examine
where there is place on the server to put the databases.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Hello Erland,
good tip, thank you very much !
I havent seen it :-/
regards Mark

"Erland Sommarskog" <esquel@.sommarskog.seschrieb im Newsbeitrag
news:Xns98203142E059Yazorman@.127.0.0.1...

Quote:

Originally Posted by

Mark (Scollop027@.gmx.net) writes:

Quote:

Originally Posted by

if you got a tape file how can you restore the contained database onto a
newly installed server? I choose Restore Database From Device then I
choose DB and select same DB in combobox "To Database" but error
occured:

TITLE: Microsoft SQL Server Management Studio
Restore failed for Server '...'. (Microsoft.SqlServer.Smo)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: Directory lookup for the file


"C:\Program

Quote:

Originally Posted by

Quote:

Originally Posted by

Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\KidDatabase.mdf" failed


with

Quote:

Originally Posted by

Quote:

Originally Posted by

the operating system error 3(error not found). (Microsoft.SqlServer.Smo)

what can I do to handle this problem?


>
First do
>
RESTORE FILELISTONLY FROM TAPE = 'tapedevice'
>
this will give you the logical names of the files of the database. Then
do:
>
RESTORE DATABASE db FROM TAPE = 'tapedevice' WITH
MOVE 'datafile' TO
C:\Program Files\Microsoft SQL


Server\MSSQL.1\MSSQL\DATA\KidDatabase.mdf',

Quote:

Originally Posted by

MOVE 'logfile' TO
C:\Program Files\Microsoft SQL


Server\MSSQL.1\MSSQL\DATA\KidDatabase.ldf',

Quote:

Originally Posted by

REPLACE
>
Here I've used the path from your error message. Howver, the error message
indicates that this is a non-existing path, so you may have to examine
where there is place on the server to put the databases.
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Sunday, February 12, 2012

converting RS2000 reports to 2005

I am trying to convert reports from reporting services 2000 to 2005. I did not open the solution that contained the reports because I wanted to start fresh with a new structure. I added the projects and brought the existing reports in. My question is, I am findingt the only way to convert the reports is to open them in design view and specify that I want to convert them at the prompt. After a little digging, it appeared the only different was the report declaration at the top:

2005:
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefini..."xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">

2003:
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefini..."xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">

Since it is about ten times faster to open the report in xml (code) view, I thought maybe I could just do a search and replace on the two lines above, or at least copy over them, and then save all. I have over 100 reports and it would be pretty time consuming to do a conversion on each. Anyway, my question is is this the only thing I need to do to convert a report or will I screw up my reports doing it this way. I did one and it seemed to work.

Any advice is appreciated.

The RS 2005 Report Server can run RS 2000 RDLs. You can just publish them to the Report Server - they will be auto-upgraded during publishing. Note: when you retrieve it from the report server, you’ll get the original RS 2000 RDL you published to the server.

From that point of view it is not mandatory to upgrade old RDLs to the new schema definition.

BTW: there are a few more changes in the new schema than just the namespace change.

-- Robert

Converting reports from 2000 to 2005

I am trying to convert reports from reporting services 2000 to 2005. I
did not open the solution that contained the reports because I wanted
to start fresh with a new structure. I added the projects and brought
the existing reports in. My question is, I am findingt the only way to
convert the reports is to open them in design view and specify that I
want to convert them at the prompt. After a little digging, it
appeared the only different was the report declaration at the top:
2005:
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition"
xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
2003:
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
Since it is about ten times faster to open the report in xml (code)
view, I thought maybe I could just do a search and replace on the two
lines above, or at least copy over them, and then save all. I have
over 100 reports and it would be pretty time consuming to do a
conversion on each. Anyway, my question is is this the only thing I
need to do to convert a report or will I screw up my reports doing it
this way. I did one and it seemed to work.
Any advice is appreciated.I don't know. I think you are playing with fire. What if one of your reports
has something different that requires more. I would think you could do a 100
reports in about an hour. A boring hour but it is the safest way.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stephen" <switter@.enpathmed.com> wrote in message
news:1142439465.876284.160770@.p10g2000cwp.googlegroups.com...
>I am trying to convert reports from reporting services 2000 to 2005. I
> did not open the solution that contained the reports because I wanted
> to start fresh with a new structure. I added the projects and brought
> the existing reports in. My question is, I am findingt the only way to
> convert the reports is to open them in design view and specify that I
> want to convert them at the prompt. After a little digging, it
> appeared the only different was the report declaration at the top:
> 2005:
> <Report
> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition"
> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> 2003:
> <Report
> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> Since it is about ten times faster to open the report in xml (code)
> view, I thought maybe I could just do a search and replace on the two
> lines above, or at least copy over them, and then save all. I have
> over 100 reports and it would be pretty time consuming to do a
> conversion on each. Anyway, my question is is this the only thing I
> need to do to convert a report or will I screw up my reports doing it
> this way. I did one and it seemed to work.
> Any advice is appreciated.
>