 |
|
|
|
Next: Create XML file from query
|
| Author |
Message |
External
Since: Oct 11, 2006
Posts: 6
|
(Msg. 1) Posted: Mon Nov 24, 2008 3:54 pm
Post subject: 2nd Post: MSDN Subscriber - Sql Server 2005 Restore from tape fails ...
Archived from groups: microsoft>public>sqlserver>tools (more info?)
|
|
|
We're using Sql Server 2005, Win2003 and writing backups to an HP Ultrium2
tape drive.
I can get a File List from the tape with no problems. I'm backing up 14
individual databases to the tape.
I want to create a copy of the "sec" database that has a full backup in
position #11 on the tape. I want to recover the "sec" database as
"sec_2008-11-24". I've successfully created this type of restore many
times when the .bak file is physically on the server harddrive.
However, when I use the following script I get the error message listed
below the script. ANY HELP OR SUGGESTIONS WOULD BE GREATLY APPRECIATED !!
Thanks in advance !
Barry in Oregon
== RESTORE SCRIPT ==
RESTORE DATABASE [sec_2008-11-08]
FROM [HP-Ultrium2-Tape] WITH FILE = 11,
MOVE N'sec_data_001.mdf' TO N'C:\Sql Server
2005\owrd\MSSQL.1\MSSQL\DATA\sec_data_2008-11-08.mdf',
MOVE N'sec_log_001.ldf' TO N'C:\Sql Server
2005\owrd\MSSQL.1\MSSQL\DATA\sec_log_2008-11-08.ldf',
NOUNLOAD,
STATS = 10
GO
== RESULTING ERROR MESSAGE ==
Msg 3234, Level 16, State 2, Line 1
Logical file 'sec_data_001.mdf' is not part of database 'sec_2008-11-08'.
Use RESTORE FILELISTONLY to list the logical file names.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally. |
|
| Back to top |
|
 | |
External
Since: Apr 10, 2008
Posts: 60
|
(Msg. 2) Posted: Mon Nov 24, 2008 7:35 pm
Post subject: Re: 2nd Post: MSDN Subscriber - Sql Server 2005 Restore from tape [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
The error message says it all:
Msg 3234, Level 16, State 2, Line 1
Logical file 'sec_data_001.mdf' is not part of database 'sec_2008-11-08'.
Use RESTORE FILELISTONLY to list the logical file names.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
This message is telling you that you cannot MOVE the database with a
logical file name 'sec_2008-11-08.mdf'. Modify the MOVE statement to
reference the actual logical file name that is defined for that backup.
As the error message states - Use RESTORE FILELISTONLY to identify the
actual logical file names for the database you are restoring. Note: you
cannot rename or modify the logical names until after the database has
been restored (and, you can have the same logical file names pointing to
different databases).
Jeff
frostbb wrote:
> We're using Sql Server 2005, Win2003 and writing backups to an HP Ultrium2
> tape drive.
>
> I can get a File List from the tape with no problems. I'm backing up 14
> individual databases to the tape.
>
> I want to create a copy of the "sec" database that has a full backup in
> position #11 on the tape. I want to recover the "sec" database as
> "sec_2008-11-24". I've successfully created this type of restore many
> times when the .bak file is physically on the server harddrive.
>
> However, when I use the following script I get the error message listed
> below the script. ANY HELP OR SUGGESTIONS WOULD BE GREATLY APPRECIATED !!
>
> Thanks in advance !
>
> Barry in Oregon
>
> == RESTORE SCRIPT ==
> RESTORE DATABASE [sec_2008-11-08]
> FROM [HP-Ultrium2-Tape] WITH FILE = 11,
> MOVE N'sec_data_001.mdf' TO N'C:\Sql Server
> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_data_2008-11-08.mdf',
> MOVE N'sec_log_001.ldf' TO N'C:\Sql Server
> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_log_2008-11-08.ldf',
> NOUNLOAD,
> STATS = 10
> GO
>
> == RESULTING ERROR MESSAGE ==
>
> Msg 3234, Level 16, State 2, Line 1
> Logical file 'sec_data_001.mdf' is not part of database 'sec_2008-11-08'.
> Use RESTORE FILELISTONLY to list the logical file names.
> Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
> |
|
| Back to top |
|
| |
External
Since: Oct 11, 2006
Posts: 6
|
(Msg. 3) Posted: Tue Nov 25, 2008 8:00 am
Post subject: Re: 2nd Post: MSDN Subscriber - Sql Server 2005 Restore from tape fails ... [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Jeff,
Thanks for the quick response. Its very much appreciated.
Unfortunately, I'm confused about what you're saying specially about the
part about you can have the same logical file names pointing to different
databases.
Also unfortunately, I don't want to restore over the existing "sec"
database. I want to restore a >> copy of << the "sec" database so that I
can retrieve some lost information from the "sec" copy and put it back into
the existing production "sec" database.
I obviously don't understand the mechanics of restoring a database from tape
as opposed to restoring from a set of .bak files on the hard drive. And this
is NOT something I can screw up. Overwriting the existing production sec db
is definitely off the table.
Anyway, thanks again for the effort. Its very much appreciated. However, I
think it's time to burn one of my "MSDN life line calls" 
Best wishes !!
Barry in Oregon
"Jeffrey Williams" wrote in message
> The error message says it all:
>
> Msg 3234, Level 16, State 2, Line 1
> Logical file 'sec_data_001.mdf' is not part of database 'sec_2008-11-08'.
> Use RESTORE FILELISTONLY to list the logical file names.
> Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
> This message is telling you that you cannot MOVE the database with a
> logical file name 'sec_2008-11-08.mdf'. Modify the MOVE statement to
> reference the actual logical file name that is defined for that backup.
>
> As the error message states - Use RESTORE FILELISTONLY to identify the
> actual logical file names for the database you are restoring. Note: you
> cannot rename or modify the logical names until after the database has
> been restored (and, you can have the same logical file names pointing to
> different databases).
>
> Jeff
>
> frostbb wrote:
>> We're using Sql Server 2005, Win2003 and writing backups to an HP
>> Ultrium2 tape drive.
>>
>> I can get a File List from the tape with no problems. I'm backing up 14
>> individual databases to the tape.
>>
>> I want to create a copy of the "sec" database that has a full backup in
>> position #11 on the tape. I want to recover the "sec" database as
>> "sec_2008-11-24". I've successfully created this type of restore many
>> times when the .bak file is physically on the server harddrive.
>>
>> However, when I use the following script I get the error message listed
>> below the script. ANY HELP OR SUGGESTIONS WOULD BE GREATLY APPRECIATED !!
>>
>> Thanks in advance !
>>
>> Barry in Oregon
>>
>> == RESTORE SCRIPT ==
>> RESTORE DATABASE [sec_2008-11-08]
>> FROM [HP-Ultrium2-Tape] WITH FILE = 11,
>> MOVE N'sec_data_001.mdf' TO N'C:\Sql Server
>> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_data_2008-11-08.mdf',
>> MOVE N'sec_log_001.ldf' TO N'C:\Sql Server
>> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_log_2008-11-08.ldf',
>> NOUNLOAD,
>> STATS = 10
>> GO
>>
>> == RESULTING ERROR MESSAGE ==
>>
>> Msg 3234, Level 16, State 2, Line 1
>> Logical file 'sec_data_001.mdf' is not part of database 'sec_2008-11-08'.
>> Use RESTORE FILELISTONLY to list the logical file names.
>> Msg 3013, Level 16, State 1, Line 1
>> RESTORE DATABASE is terminating abnormally.
>>
>>
> >> Stay informed about: 2nd Post: MSDN Subscriber - Sql Server 2005 Restore from t.. |
|
| Back to top |
|
| |
External
Since: Jan 10, 2008
Posts: 111
|
(Msg. 4) Posted: Tue Nov 25, 2008 3:43 pm
Post subject: Re: 2nd Post: MSDN Subscriber - Sql Server 2005 Restore from tape fails ... [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
SQL uses logical file names that are separate from physical file names. You
are using the physical file name instead of the logical file name in the
"WITH MOVE clause. The ".mdf" extension is a physical name artifact. Use
the logical name and supply a physical destination and everything will work
just fine.
--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP
"frostbb" wrote in message
> Jeff,
>
> Thanks for the quick response. Its very much appreciated.
>
> Unfortunately, I'm confused about what you're saying specially about the
> part about you can have the same logical file names pointing to different
> databases.
>
> Also unfortunately, I don't want to restore over the existing "sec"
> database. I want to restore a >> copy of << the "sec" database so that I
> can retrieve some lost information from the "sec" copy and put it back
> into the existing production "sec" database.
>
> I obviously don't understand the mechanics of restoring a database from
> tape as opposed to restoring from a set of .bak files on the hard drive.
> And this is NOT something I can screw up. Overwriting the existing
> production sec db is definitely off the table.
>
> Anyway, thanks again for the effort. Its very much appreciated. However,
> I think it's time to burn one of my "MSDN life line calls"
>
> Best wishes !!
>
> Barry in Oregon
>
>
>
> "Jeffrey Williams" wrote in message
>
>> The error message says it all:
>>
>> Msg 3234, Level 16, State 2, Line 1
>> Logical file 'sec_data_001.mdf' is not part of database 'sec_2008-11-08'.
>> Use RESTORE FILELISTONLY to list the logical file names.
>> Msg 3013, Level 16, State 1, Line 1
>> RESTORE DATABASE is terminating abnormally.
>>
>> This message is telling you that you cannot MOVE the database with a
>> logical file name 'sec_2008-11-08.mdf'. Modify the MOVE statement to
>> reference the actual logical file name that is defined for that backup.
>>
>> As the error message states - Use RESTORE FILELISTONLY to identify the
>> actual logical file names for the database you are restoring. Note: you
>> cannot rename or modify the logical names until after the database has
>> been restored (and, you can have the same logical file names pointing to
>> different databases).
>>
>> Jeff
>>
>> frostbb wrote:
>>> We're using Sql Server 2005, Win2003 and writing backups to an HP
>>> Ultrium2 tape drive.
>>>
>>> I can get a File List from the tape with no problems. I'm backing up 14
>>> individual databases to the tape.
>>>
>>> I want to create a copy of the "sec" database that has a full backup in
>>> position #11 on the tape. I want to recover the "sec" database as
>>> "sec_2008-11-24". I've successfully created this type of restore many
>>> times when the .bak file is physically on the server harddrive.
>>>
>>> However, when I use the following script I get the error message listed
>>> below the script. ANY HELP OR SUGGESTIONS WOULD BE GREATLY APPRECIATED
>>> !!
>>>
>>> Thanks in advance !
>>>
>>> Barry in Oregon
>>>
>>> == RESTORE SCRIPT ==
>>> RESTORE DATABASE [sec_2008-11-08]
>>> FROM [HP-Ultrium2-Tape] WITH FILE = 11,
>>> MOVE N'sec_data_001.mdf' TO N'C:\Sql Server
>>> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_data_2008-11-08.mdf',
>>> MOVE N'sec_log_001.ldf' TO N'C:\Sql Server
>>> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_log_2008-11-08.ldf',
>>> NOUNLOAD,
>>> STATS = 10
>>> GO
>>>
>>> == RESULTING ERROR MESSAGE ==
>>>
>>> Msg 3234, Level 16, State 2, Line 1
>>> Logical file 'sec_data_001.mdf' is not part of database
>>> 'sec_2008-11-08'.
>>> Use RESTORE FILELISTONLY to list the logical file names.
>>> Msg 3013, Level 16, State 1, Line 1
>>> RESTORE DATABASE is terminating abnormally.
>>>
>>>
>>
>
> >> Stay informed about: 2nd Post: MSDN Subscriber - Sql Server 2005 Restore from t.. |
|
| Back to top |
|
| |
External
Since: Oct 11, 2006
Posts: 6
|
(Msg. 5) Posted: Tue Nov 25, 2008 5:11 pm
Post subject: Re: 2nd Post: MSDN Subscriber - Sql Server 2005 Restore from tape fails ... [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Geoff,
You and Jeff are exactly correct. After following Jeff's advice and
executing a RESTORE FILELISTONLY I realized that the logical file names on
the tapes did not have the .mdf / .ldf suffixes. I removed the suffixes and
the RESTORE worked great! I had been trying to work from the SMS Backup
Device Media Contents list.
Many thanks to both you and Jeff. Your time and patience are very much
appreciated !!
===== The successful restore renamed database script ====
RESTORE DATABASE [sec_2008-11-08]
FROM [HP-Ultrium2-Tape] WITH FILE = 11,
MOVE N'sec_data_001' TO N'C:\Sql Server
2005\owrd\MSSQL.1\MSSQL\DATA\sec_data_2008-11-08.mdf',
MOVE N'sec_log_001' TO N'C:\Sql Server
2005\owrd\MSSQL.1\MSSQL\DATA\sec_log_2008-11-08.ldf',
NOUNLOAD,
STATS = 10
GO
Barry in Oregon
"Geoff N. Hiten" wrote in message
> SQL uses logical file names that are separate from physical file names.
> You are using the physical file name instead of the logical file name in
> the "WITH MOVE clause. The ".mdf" extension is a physical name artifact.
> Use the logical name and supply a physical destination and everything will
> work just fine.
>
>
> --
> Geoff N. Hiten
> Principal SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
>
> "frostbb" wrote in message
>
>> Jeff,
>>
>> Thanks for the quick response. Its very much appreciated.
>>
>> Unfortunately, I'm confused about what you're saying specially about the
>> part about you can have the same logical file names pointing to
>> different databases.
>>
>> Also unfortunately, I don't want to restore over the existing "sec"
>> database. I want to restore a >> copy of << the "sec" database so that I
>> can retrieve some lost information from the "sec" copy and put it back
>> into the existing production "sec" database.
>>
>> I obviously don't understand the mechanics of restoring a database from
>> tape as opposed to restoring from a set of .bak files on the hard drive.
>> And this is NOT something I can screw up. Overwriting the existing
>> production sec db is definitely off the table.
>>
>> Anyway, thanks again for the effort. Its very much appreciated. However,
>> I think it's time to burn one of my "MSDN life line calls"
>>
>> Best wishes !!
>>
>> Barry in Oregon
>>
>>
>>
>> "Jeffrey Williams" wrote in message
>>
>>> The error message says it all:
>>>
>>> Msg 3234, Level 16, State 2, Line 1
>>> Logical file 'sec_data_001.mdf' is not part of database
>>> 'sec_2008-11-08'.
>>> Use RESTORE FILELISTONLY to list the logical file names.
>>> Msg 3013, Level 16, State 1, Line 1
>>> RESTORE DATABASE is terminating abnormally.
>>>
>>> This message is telling you that you cannot MOVE the database with a
>>> logical file name 'sec_2008-11-08.mdf'. Modify the MOVE statement to
>>> reference the actual logical file name that is defined for that backup.
>>>
>>> As the error message states - Use RESTORE FILELISTONLY to identify the
>>> actual logical file names for the database you are restoring. Note: you
>>> cannot rename or modify the logical names until after the database has
>>> been restored (and, you can have the same logical file names pointing to
>>> different databases).
>>>
>>> Jeff
>>>
>>> frostbb wrote:
>>>> We're using Sql Server 2005, Win2003 and writing backups to an HP
>>>> Ultrium2 tape drive.
>>>>
>>>> I can get a File List from the tape with no problems. I'm backing up
>>>> 14 individual databases to the tape.
>>>>
>>>> I want to create a copy of the "sec" database that has a full backup in
>>>> position #11 on the tape. I want to recover the "sec" database as
>>>> "sec_2008-11-24". I've successfully created this type of restore many
>>>> times when the .bak file is physically on the server harddrive.
>>>>
>>>> However, when I use the following script I get the error message listed
>>>> below the script. ANY HELP OR SUGGESTIONS WOULD BE GREATLY APPRECIATED
>>>> !!
>>>>
>>>> Thanks in advance !
>>>>
>>>> Barry in Oregon
>>>>
>>>> == RESTORE SCRIPT ==
>>>> RESTORE DATABASE [sec_2008-11-08]
>>>> FROM [HP-Ultrium2-Tape] WITH FILE = 11,
>>>> MOVE N'sec_data_001.mdf' TO N'C:\Sql Server
>>>> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_data_2008-11-08.mdf',
>>>> MOVE N'sec_log_001.ldf' TO N'C:\Sql Server
>>>> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_log_2008-11-08.ldf',
>>>> NOUNLOAD,
>>>> STATS = 10
>>>> GO
>>>>
>>>> == RESULTING ERROR MESSAGE ==
>>>>
>>>> Msg 3234, Level 16, State 2, Line 1
>>>> Logical file 'sec_data_001.mdf' is not part of database
>>>> 'sec_2008-11-08'.
>>>> Use RESTORE FILELISTONLY to list the logical file names.
>>>> Msg 3013, Level 16, State 1, Line 1
>>>> RESTORE DATABASE is terminating abnormally.
>>>>
>>>>
>>>
>>
>>
> >> Stay informed about: 2nd Post: MSDN Subscriber - Sql Server 2005 Restore from t.. |
|
| Back to top |
|
| |
External
Since: Apr 10, 2008
Posts: 60
|
(Msg. 6) Posted: Tue Nov 25, 2008 10:06 pm
Post subject: Re: 2nd Post: MSDN Subscriber - Sql Server 2005 Restore from tape [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
frostbb wrote:
> Geoff,
>
> You and Jeff are exactly correct. After following Jeff's advice and
> executing a RESTORE FILELISTONLY I realized that the logical file names on
> the tapes did not have the .mdf / .ldf suffixes. I removed the suffixes and
> the RESTORE worked great! I had been trying to work from the SMS Backup
> Device Media Contents list.
>
> Many thanks to both you and Jeff. Your time and patience are very much
> appreciated !!
>
> ===== The successful restore renamed database script ====
> RESTORE DATABASE [sec_2008-11-08]
> FROM [HP-Ultrium2-Tape] WITH FILE = 11,
> MOVE N'sec_data_001' TO N'C:\Sql Server
> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_data_2008-11-08.mdf',
> MOVE N'sec_log_001' TO N'C:\Sql Server
> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_log_2008-11-08.ldf',
> NOUNLOAD,
> STATS = 10
> GO
>
> Barry in Oregon
>
>
> "Geoff N. Hiten" wrote in message
>
>> SQL uses logical file names that are separate from physical file names.
>> You are using the physical file name instead of the logical file name in
>> the "WITH MOVE clause. The ".mdf" extension is a physical name artifact.
>> Use the logical name and supply a physical destination and everything will
>> work just fine.
>>
>>
>> --
>> Geoff N. Hiten
>> Principal SQL Infrastructure Consultant
>> Microsoft SQL Server MVP
>>
>>
>>
>> "frostbb" wrote in message
>>
>>> Jeff,
>>>
>>> Thanks for the quick response. Its very much appreciated.
>>>
>>> Unfortunately, I'm confused about what you're saying specially about the
>>> part about you can have the same logical file names pointing to
>>> different databases.
>>>
>>> Also unfortunately, I don't want to restore over the existing "sec"
>>> database. I want to restore a >> copy of << the "sec" database so that I
>>> can retrieve some lost information from the "sec" copy and put it back
>>> into the existing production "sec" database.
>>>
>>> I obviously don't understand the mechanics of restoring a database from
>>> tape as opposed to restoring from a set of .bak files on the hard drive.
>>> And this is NOT something I can screw up. Overwriting the existing
>>> production sec db is definitely off the table.
>>>
>>> Anyway, thanks again for the effort. Its very much appreciated. However,
>>> I think it's time to burn one of my "MSDN life line calls"
>>>
>>> Best wishes !!
>>>
>>> Barry in Oregon
>>>
>>>
>>>
>>> "Jeffrey Williams" wrote in message
>>>
>>>> The error message says it all:
>>>>
>>>> Msg 3234, Level 16, State 2, Line 1
>>>> Logical file 'sec_data_001.mdf' is not part of database
>>>> 'sec_2008-11-08'.
>>>> Use RESTORE FILELISTONLY to list the logical file names.
>>>> Msg 3013, Level 16, State 1, Line 1
>>>> RESTORE DATABASE is terminating abnormally.
>>>>
>>>> This message is telling you that you cannot MOVE the database with a
>>>> logical file name 'sec_2008-11-08.mdf'. Modify the MOVE statement to
>>>> reference the actual logical file name that is defined for that backup.
>>>>
>>>> As the error message states - Use RESTORE FILELISTONLY to identify the
>>>> actual logical file names for the database you are restoring. Note: you
>>>> cannot rename or modify the logical names until after the database has
>>>> been restored (and, you can have the same logical file names pointing to
>>>> different databases).
>>>>
>>>> Jeff
>>>>
>>>> frostbb wrote:
>>>>> We're using Sql Server 2005, Win2003 and writing backups to an HP
>>>>> Ultrium2 tape drive.
>>>>>
>>>>> I can get a File List from the tape with no problems. I'm backing up
>>>>> 14 individual databases to the tape.
>>>>>
>>>>> I want to create a copy of the "sec" database that has a full backup in
>>>>> position #11 on the tape. I want to recover the "sec" database as
>>>>> "sec_2008-11-24". I've successfully created this type of restore many
>>>>> times when the .bak file is physically on the server harddrive.
>>>>>
>>>>> However, when I use the following script I get the error message listed
>>>>> below the script. ANY HELP OR SUGGESTIONS WOULD BE GREATLY APPRECIATED
>>>>> !!
>>>>>
>>>>> Thanks in advance !
>>>>>
>>>>> Barry in Oregon
>>>>>
>>>>> == RESTORE SCRIPT ==
>>>>> RESTORE DATABASE [sec_2008-11-08]
>>>>> FROM [HP-Ultrium2-Tape] WITH FILE = 11,
>>>>> MOVE N'sec_data_001.mdf' TO N'C:\Sql Server
>>>>> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_data_2008-11-08.mdf',
>>>>> MOVE N'sec_log_001.ldf' TO N'C:\Sql Server
>>>>> 2005\owrd\MSSQL.1\MSSQL\DATA\sec_log_2008-11-08.ldf',
>>>>> NOUNLOAD,
>>>>> STATS = 10
>>>>> GO
>>>>>
>>>>> == RESULTING ERROR MESSAGE ==
>>>>>
>>>>> Msg 3234, Level 16, State 2, Line 1
>>>>> Logical file 'sec_data_001.mdf' is not part of database
>>>>> 'sec_2008-11-08'.
>>>>> Use RESTORE FILELISTONLY to list the logical file names.
>>>>> Msg 3013, Level 16, State 1, Line 1
>>>>> RESTORE DATABASE is terminating abnormally.
>>>>>
>>>>>
>>>
>
>
That is good to know - glad you were able to get this done. >> Stay informed about: 2nd Post: MSDN Subscriber - Sql Server 2005 Restore from t.. |
|
| Back to top |
|
| |
| Related Topics: | sql server 2005 database in restore mode - Hi folks I was restoring a database in SQL Server 2005 express edition. Due to a malfunction, system restarted. Now when I try to access the database, the status shows as "Restoring Database". I have tried to restart SQL Server and PC, but ...
restore sql 2000 backup.bak to sql 2005 database fail - Any one konw the step how to restore sql 2000 database to sql 2005 i got error when i restore backup.bak(backup from sql 2000) file to sql 2005 i right click then choose task , restore
Manage SQL Server 2005 while keeping SQL Server 2000 - I've got SQL Server 2000 running on my PC, and I want to continue doing so. But now I also need to manage a remote SQL Server 2005 database. I think that I need to install SQL Server Management Studio to do so. (Please correct me if that's wrong.) Can...
sp_OACreate + Sql Server 2005 problem! - Hi folks, I am having some dificulties with the extended procedure sp_OACreate, only when using the SQL Server 2005. I am using some COM+ objects inside a procedure, and to access these objects and create them I was using these extended procedures :...
Where get SQL Server Management Studio 2005 - Where can I get SQL Server Management Studio 2005? I have SQL Server 2005 installed (from my MSDN CD). Thanks! |
|
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Search
Profile
Private Messages
Log in
