Restore a database in recovery mode sql server 2005

Please i need some help. My database has been marked in recovery in sql 2005 management studio and i can't connect to it how do i bring it back to normal

if your database is marked in recovery this means that SQL Server is recoverying the database typically after a sql server restart.
If the database is marked restoring, do this restore database databasename with recovery
Otherwise, you need to check the status of the recovery - Check this query: SELECT state_desc FROM sys.databases WHERE name = 'ProblemDatabaseName'; If this returns recovery_pending you have to wait. Check the SQL Server log for messages about the
state of the recovery.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Similar Messages

Migration from of database and app from SQL server 2005 to Oracle 10g

Hello Every body,
Lately, I have been requested to migrate one inhouse developed hub application from SQL server 2005 to Oracle 10g. The objective is to move application and also the database to Oracel 10g.
Here is the current platform:
OS Win 2008 64 bit
JDK 1.4.2
JBoss 3.2.5
EJB 2.1
My question is what kind of issues you guys see in above upgrade. As far I know, Schema and Database migration can be done by Oracle workbench. Oracle 10g supports JDK 1.4. Oracle 10g also supports EJB 2.1.
Anything, I need to take into consideration or any risks or problems. I would like to list down all the risks, and accordingly, I am thinking of start the upgrade.
Thanks in advance.
Regards,
Zeeshan Qureshi

In general the Java/J2EE application needs work in the following categories:
1. Connection Settings: Use Oracle JDBC drivers, create new data sources, connection pools and what not. Disable AUTOCOMMIT for Oracle JDBC Connections.
2. For EJBs, you should regenerate the entity beans because some object names/column names might have changed in oracle.
3. Any custom SQL that is in use in the EJBs will have to be ported to Oracle just as you would do in stored procedures and other applications.
4. For Java front-ends, if you are using callouts to stored procedures and expecting result sets then they will require some changes. You need to modify the stored procedure call signature to include the REF CURSOR variables and process them.
5. Changes to any SQL Server specific database functions manipulating character/date data will be required.
6. CLOB/BLOB/XML apis are different across databases so if you are using those then focus on them as well.
7. Retreiving Auto/generated keys from database also may need changes from what I have seen.
Hope this helps..
Regards
Prakash
NOTE: Not sure why but my posts from yesterday are not visible today. Even worse is that I can see them in one browser (FireFox) but not in Internet explorer. Crazy browser day I am having.

How to Select from Oracle 8i database and insert into Sql Server 2005 datab

Hi how to Select from Oracle 8i and insert into Sql Server 2005.
Source db as Oracle 8i
Target db as Sql Server 2005.
I need to select one table data from Oracle 8i & insert into Sql Server 2005
Thanks

Thanks Khan..
Is there is any query (OPENQUERY) available for that?
Regards..

Restoring an ms access database backup file in sql server 2005

Hello everyone.
I have an ms access database backup file.
Presently i dont have ms access database in my system.
It is high priority to access that ms access database backup file.
So, is there anyway to access that in sql server?
-- Thanks and Regards Srikar Reddy Gondesi, Trainee SQL Server Database Administrator Miracle Software systems, Inc.

Hello sir,
i tried to use import/export wizard to import data from an ms access backup file.
I completed it with some warning's.
Wizard has shown that 2 out of three objects(tables and views) are copied to destination database(empty database which i have created for storing this imported data).
And in that process, wizard made me to create a package.
Now how to access that package?
And my newly created database has no data.(i mean it is supposed to have 2 objects which are copied from source right?)
Sorry if my doubt looks silly i have never used ssis or import/export ever before.
-- Thanks and Regards Srikar Reddy Gondesi, Trainee SQL Server Database Administrator Miracle Software systems, Inc.
-- Thanks and Regards Srikar Reddy Gondesi, Trainee SQL Server Database Administrator Miracle Software systems, Inc.

Database backup strategy(MS sql server 2005, Winodws 2003, SAP ECC 6.00)

Hello gurus,
    I am confused, about the backup system i should go for(backup device, abckup software)?? Fllowing is my SAP Landscape.
1) IDES
2) Solution manager
3) Development
4) BIW
no of users 25 max
modules implemented
MM
HR
FICO
BIW
<b>    I want to implemente before go live, backup system in my company.</b>
We have received backup schedule from our implementation partner. Our backup system is as follows.
Backup device is HP Surestore Autoloader.
Cartridge capacity is 100/200GB
Backup software is Veritas (version 8.6)
Note: Through this we take backup of our legacy system and it takes around 3 1/2 hour to 4 hours to take backup of 60 GB of our legacy data.
     Right now the problem is our backup software version is old and i even believe, the hardware we have is not sufficient to take daily database backup and fortnightly, SAP system backup.
    The only solution to the problem i can see is
1) to go for another backup device exclusively for SAP system
2) Even go for SQL Agent software used to take backup of SAP system thorugh Veritas.
3) Even upgrade my Veritas version.
<b>   Its a request to GURUS</b>
1) Is the solution, i am thinking to this issue is correct.?? If no then please advice me
2) Please tell me the best backup system in your opinion for my above mentioned system.
Thanks Gurus
Rahul

Hello,
A indication of the size of each database would be helpful.
However, its NOT a good idea to take only one on line backup a week. What if you have a tape error and cant recover a TL? You have no chance for recovery. This is not best practice. Can the business except a 4,5 or even 6 days loss of data - id guess not.
This is what id do if you don't want to purchase a new device, I would take an online backups from SQL to disk every night - this would be a separate disk! From the disk you can the pick up the backup to take at a time to suit that wont impact the existing backup. Plus you always have two copies of the backup. One on disk, one on tape.
My normal transaction log strategy is similar, again backup to disk, every hour on a production system. Then after midnight move the existing 24 logs into an archive folder. This folder would also be picked up by the existing device at a suitable time before being moved to a 'saved' folder and deleted the next day. Again you always have multiple copies of the data. two on disk, two on tape.

SQL Server 2005 High Availability and Disaster Recovery options

Hi, We are are working on a High Availability & Disaster Recovery Planning solution for an application database which is on SQL Server 2005. What different options have we got to implement this for SQL Server 2005 and after we have everything setup how
do we test the failover is working?
Thanks in advance.........
Ione

DR : Disaster recovery is the best option for the business to minimize their data loss and downtime. The SQL server has a number of native options. But, everything is depends upon your recovery time objective RTO and recovery point objective RPO.
1. Data center disaster
Geo Clustering
2. Server(Host)/Drive (Except shared drive) disaster
Clustering
3. Database/Drive disaster
Database mirroring
Log shipping
Replication
Log shipping
Log shipping is the process of automating the full database backup and transaction log on a production server and then automatically restores them on to the secondary (standby) server.
Log shipping will work either Full or Bulk logged recovery model.
You can also configure log shipping in the single SQL instance.
The Stand by database can be either restoring or read only (standby).
The manual fail over is required to bring the database online.
Some data can be lost (15 minutes).
Peer-to-Peer Transactional Replication
Peer-to-peer transactional replication is designed for applications that might read or might modify the data in any database that participates in replication. Additionally, if any servers that host the databases are unavailable, you can modify the application
to route traffic to the remaining servers. The remaining servers contain same copies of the data.
Clustering
Clustering is a combination of one or more servers it will automatically allow one physical server to take over the tasks of another physical server that has failed. Its not a real disaster recovery solution because if the shared drive unavailable we cannot
bring the database to online.
Clustering is best option it provides a minimum downtime (like 5 minutes) and data loss in case any data center (Geo) or server failure.
Clustering needs extra hardware/server and it’s more expensive.
Database mirroring
Database mirroring introduced in 2005 onwards. Database Mirroring maintain an exact copy of a database on a different server. It has automatic fail over option and mainly helps to increase the database availability too.
Database mirroring only works FULL recovery model.
This needs two instances.
Mirror database always in restoring state.
http://msdn.microsoft.com/en-us/library/ms151196%28v=sql.90%29.aspx
http://blogs.technet.com/b/wbaer/archive/2008/04/19/high-availability-and-disaster-recovery-with-microsoft-sql-server-2005-database-mirroring-and-microsoft-sql-server-2005-log-shipping-for-microsoft-sharepoint-products-and-technologies.aspx
http://www.slideshare.net/rajib_kundu/disaster-recovery-in-sql-server
HADR Considerations
Need to Understand the business motivations and regulatory requirements that are driving the customer's HA/DR requirements. Understand how your customer categorizes the workload from an HA/DR perspective. There is likely to be an alignment between the needs
and categorization.
Check for both the recovery time objective (RTO) and the recovery point objective (RPO) for different workload categories, for both a failure within a data center (local high availability) and a total data center failure (disaster recovery). While RPO and
RTO vary for different workloads because of business, cost, or technological considerations, customers may prefer a single technical solution for ease in operations. However, a single technical solution may require trade-offs that need to be discussed with
customers so that their expectations are set appropriately.
Check and understand if there is an organizational preference for a particular HA/DR technology. Customers may have a preference because of previous experiences, established operational procedures, or simply the desire for uniformity across databases from
different vendors. Understand the motives behind a preference: A customers' preference for HA/DR may not be because of the functions and features of the HA/DR technology. For example, a customer may decide to adopt a third-party solution for DR to maintain
a single operational procedure. For this reason, using HA/DR technology provided by a SAN vendor (such as EMC SRDF) is a popular approach.
To design and adopt an HA/DR solution it is also important to understand the implications of applying maintenance to both hardware and software (including Windows security patching). Database mirroring is often adopted to minimize the service disruption
to achieve this objective.
HADR Options :
Failover clustering for HA and database mirroring for DR.
Synchronous database mirroring for HA/DR and log shipping for additional DR.
Geo-cluster for HA/DR and log shipping for additional DR.
Failover clustering for HA and storage area network (SAN)-based replication for DR.
Peer-to-peer replication for HA and DR (and reporting).
Backup & Restore ( DR)
keep your server DB backups in network location ( DR)
Always keep your sql server 2005 upto date, in case if you are not getting any official support from MS then you have to take care of any critical issues and more..
Raju Rasagounder Sr MSSQL DBA

Moving from SQL server 2005 to SQL server 2008 ... for a MS/SQL newbie.

Hello,
I am in charge of moving an existing SAP NW BI (SPS20) from a MS SQL Server 2005 database on Windows Server 2003 (x864/64 bit) Platform to a MS SQL Server 2008 database/Windows Server 2008 Platform (x64/64 bit).
The SID of the SAP system will remain the same.
The thing is that I have always worrked so far on Oracle/Unix environements, windows/MSSQL is an entire new world for me,
so I am quite worried.
I have read many sap notes/installation guides/forum posts regarding this operation, I will describe here my understanding
of the techinical operations that I will need to perfrom.
Could you correct me if I am wrong, as well as give me your comments ?
1/ I will need to perform an SQL server database copy within a homogeneous system copy.
2/First ,I'll have to install on the target environnement the SQL server 2008 database. I'll have to install the SQL Server Database Software with SQL4SAP (no need to install the database server software manually, right ?). Afterwards, I'll install on the target environnent, SAP Netweaver 7.0 SR3 with a modified Instalaltion Master DVD.
3/ On the source environement, I'll perfrom a database backup of the SQL Server 2005 system and restore the database on the target environement. since I choose to perfrom a restore of the database , there is no need to follow all the steps described in sap note 151603 :determine the file structure of the source database, create the directory structure for the target database, etc ...
4/ Once the restoration is finished, I use SAPINST and finish the homogeneous copy : >additional sofware->system copy>target system->central system --> Based on AS Abap --central installation
Your comments are welcome.
Thank you for your attention
Best Regards.
Raoul

Hi Raoul,
you also need a modified Kernel DVD for the installation on SQL 2008 (see SAP Note 1152240).
And don't forget to install and patch the Visual Studio c++ Runtime (also described in that note).
I also would recommend to restore the backup and then install SAP NW 7.0 SR3 and use the restored SQL 2008 database.
So the basic steps are:
1. Perform backup and restore to SQL 2008
1.1 Install SQL 2008 with SQL4SAP
1.2 Backup old database
1.3. Restore backup on SQL 2008
2. Install VC runtime on Win 2008
3. Create modified Kernel DVD
4. Create modified Master DVD
5. Perform system copy target installaton with - additional sofware->system copy>target system--->central system --> Based on AS Abap --central installation and use the SQL 2008 database
You could also use SQL Server 2008 R2 which was release last month.
Please also check Note 1476928
Best,
Sebastian Dusch

Error"Failed to open the connection" - Named Instance of SQL Server 2005

"Failed to open the connection" error, when connecting to the Named Instance of SQL Server 2005
The report is throwing error, when changing the logon information dynamically through C#.
Code
     string reportPath = @"D:\NET\TestReport\TestReport.rpt";
     ReportDocument reportDocument = new ReportDocument();
     reportDocument.Load(reportPath);
     foreach(CrystalDecisions.CrystalReports.Engine.Table table in tables)
          TableLogOnInfo tableLogonInfo = table.LogOnInfo;
          tableLogonInfo.ConnectionInfo.ServerName = @"TestServer\Instance1"; //Connnecting to Named instance of SQL Server 2005
          tableLogonInfo.ConnectionInfo.UserID = "sa";
          tableLogonInfo.ConnectionInfo.Password = "password";
          tableLogonInfo.ConnectionInfo.DatabaseName = "TEST_DB";
          table.ApplyLogOnInfo(tableLogonInfo);
     crystalReportViewer1.ReportSource = reportDocument;
Error Message
     Failed to open the connection.
     Failed to open the connection.
     C:\DOCUME1\PUGALE1\LOCALS~1\Temp\{DF9593A5-5C80-4CBC-ABC3-EC4EF204A7EB}.rpt
The error is occuring only whenever i am connecting to the Named Instance of SQL Server 2005.
Thanks in Advance
Edited by: pugalendran p on Feb 2, 2009 10:32 AM
Edited by: pugalendran p on Feb 2, 2009 10:43 AM

Hi,
Following solution might help you to resolve the issue.
Solution1:
Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
Resolution
Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
Import the universe from the designer.
Go to File->Parameters.
Edit Connection.
On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
Change the DSN to new DSN connection
Test the connection.
Save the Universe and Export it to the repository.
Solution2:
I am taking Oracle as an example over here.
This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
Resolution
To resolve,
check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
look for any paths that contain a mapped drive partition
Change the mapped drive letter to a UNC path (
server\folder)
Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
If the path is not updated to the new path
Reboot the server
Regards,
Sarbhjeet Kaur

SQL Server 2005 data pull from Oracle

Hi, I am learning how to use Oracle and I ran into this problem.
My database is running on SQL Server 2005.
I have an ODBC connection to Oracle. I also have a VB .Net script that queries the Oracle table that the data resides in.
When the job is running, and if it stalls, I do not get a timeout error. It locks down my database and no other source systems can feed data to me; these are back logged in the queue.
Is there an easier way for me to make a connection that will pull data on a consistent basis? Please help ...
Student Learner

Learning how to use Oracle does not include taking data from Oracle and putting it into SQL Server.
From your description of what is happening I agree with BluShadow. This is not an Oracle issue. This is a coding in VB .NET issue.
Posting the statements you are executing against some unknown version of Oracle would be a good starting point.

SQL Server 2005 performance decreases with DB size while SQL Server 2012 is fine

Hi,
We have a C# windows service running that polls some files and inserts/updates some fields in database.
The service was tested on a local dev machine with SQL Server 2012 running and performance was quite decent with any number of records. Later on the service was moved to a test stage environment where SQL Server 2005 is installed. At that point database
was still empty and service was running just fine but later on, after some 500k records were written, performance problems came to light. After some more tests we've founds out that, basically, database operation performance in SQL Server 2005 decreases with
a direct correlation with the database size. Here are some testing results:
Run#
1
2
3
4
5
DB size (records)
520k
620k
720k
820k
920k
SQL Server 2005
TotalRunTime
25:25.1
32:25.4
38:27.3
42:50.5
43:51.8
Get1
00:18.3
00:18.9
00:20.1
00:20.1
00:19.3
Get2
01:13.4
01:17.9
01:21.0
01:21.2
01:17.5
Get3
01:19.5
01:24.6
01:28.4
01:29.3
01:24.8
Count1
00:19.9
00:18.7
00:17.9
00:18.7
00:19.1
Count2
00:44.5
00:45.7
00:45.9
00:47.0
00:46.0
Count3
00:21.7
00:21.7
00:21.7
00:22.3
00:22.3
Count4
00:23.6
00:23.9
00:23.9
00:24.9
00:24.5
Process1
03:10.6
03:15.4
03:14.7
03:21.5
03:19.6
Process2
17:08.7
23:35.7
28:53.8
32:58.3
34:46.9
Count5
00:02.3
00:02.3
00:02.3
00:02.3
00:02.1
Count6
00:01.6
00:01.6
00:01.6
00:01.7
00:01.7
Count7
00:01.9
00:01.9
00:01.7
00:02.0
00:02.0
Process3
00:02.0
00:01.8
00:01.8
00:01.8
00:01.8
SQL Server 2012
TotalRunTime
12:51.6
13:38.7
13:20.4
13:38.0
12:38.8
Get1
00:21.6
00:21.7
00:20.7
00:22.7
00:21.4
Get2
01:38.3
01:37.2
01:31.6
01:39.2
01:37.3
Get3
01:41.7
01:42.1
01:35.9
01:44.5
01:41.7
Count1
00:20.3
00:19.9
00:19.9
00:21.5
00:17.3
Count2
01:04.5
01:04.8
01:05.3
01:10.0
01:01.0
Count3
00:24.5
00:24.1
00:23.7
00:26.0
00:21.7
Count4
00:26.3
00:24.6
00:25.1
00:27.5
00:23.7
Process1
03:52.3
03:57.7
03:59.4
04:21.2
03:41.4
Process2
03:05.4
03:06.2
02:53.2
03:10.3
03:06.5
Count5
00:02.8
00:02.7
00:02.6
00:02.8
00:02.7
Count6
00:02.3
00:03.0
00:02.8
00:03.4
00:02.4
Count7
00:02.5
00:02.9
00:02.8
00:03.4
00:02.5
Process3
00:21.7
00:21.0
00:20.4
00:22.8
00:21.5
One more thing is that it's not Process2 table that constantly grows in size but is Process1 table, that gets almost 100k records each run.
After that SQL Server 2005 has also been installed on a dev machine just to test things and we got exactly the same results. Both SQL Server 2005 and 2012 instances are installed using default settings with no changes at all. The same goes for databases
created for the service.
So the question is - why are there such huge differences between performance of SQL Server 2005 and 2012? Maybe there are some settings that are set by default in SQL Server 2012 database that need to be set manually in 2005?
What else can I try to test? The main problem is that production SQL Server will be updated god-knows-when and we can't just wait for that.
Any suggestions/advices are more than welcome.

...One more thing is that it's not Process2 table that constantly grows in size but is
Process1 table, that gets almost 100k records each run....
Hi,
It is not clear to me what is that you are doing, but now we have a better understanding on ONE of your tables an it is obviously you will get worse result as the data become bigger. Actually your table look like a automatic build table by ORM like Entity
Framework, and it's DDL probably do not much your needs. For example if your select query is using a filter on the other column that [setID] then you have no index and the server probably have to scan the entire table in order to find the records that you
need.
Forum is a suitable place to seek advice about a specific system (as I mentioned before we are not familiar with your system), and it is more suitable for general questions. For example the fact that you have no index except the index on the column [setID]
can indicate a problem. Ultimately to optimize the system will need to investigate it more thoroughly (as it is no longer appropriate forum ... but we're not there yet). Another point is that now we can see that you are using [timestamp] column, an this
implies that your are using this column as a filter for selecting the data. If so, then maybe a better DDL will be to use clustered index on this column and if needed a nonclustered index on the [setID] if it is needed at all...
what is obviously is that next is to check if this DDL fit
your specific needs (as i mentioned before).
Next step is to understand what action do you do with this table. (1) what is your query which become slowly in a bigger data set. (2) Are you using ORM (object relational mapping, like Entity Framework
code first), and if so then which one.
[Personal Site] [Blog] [Facebook]

Error in adding PRIMARY Data file of SQL Server 2005

Hi Experts,
I am using SQL 2005 as back end database for SAP ECC6. Due to Space problem in PRD data volume, i have added PRDDATA4.ndf file in SSMS ( SQL Server Management Studio) and saved. But, suddenly i got one more idea and extended the file size of exisiting PRDDATA1.mdf, PRDDATA2.ndf & PRDDATA3.ndf immediately i removed the PRDDATA4.ndf file before starting the service. But, while seeing in SAP using ST04 it showing the PRDDATA4.ndf with error message of file missing. What i have to do now? How can i delete the information showing in ST04. But it is not showing in SSMS.
Please help how to solve this.
Regards,
B.Sudharsan

Hi,
Following solution might help you to resolve the issue.
Solution1:
Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
Resolution
Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
Import the universe from the designer.
Go to File->Parameters.
Edit Connection.
On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
Change the DSN to new DSN connection
Test the connection.
Save the Universe and Export it to the repository.
Solution2:
I am taking Oracle as an example over here.
This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
Resolution
To resolve,
check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
look for any paths that contain a mapped drive partition
Change the mapped drive letter to a UNC path (
server\folder)
Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
If the path is not updated to the new path
Reboot the server
Regards,
Sarbhjeet Kaur

How do I copy a table from Oracle DB to Sql Server 2005 db ?

Hi , can anyone tell me what the SQL syntax would be for me to copy a table from an ORacle Database over to a SQL SERVER 2005 database ?

Hi,
Please look into this link,
Re: Dump data from SQL Server Database to Oracle
Thanks

SQL Server 2005 collation type for the Discovery System?

Greetings,
The SQL Server 2005 Eval 180 day license expired on our Discovery System. I un-installed the Eval copy and installed a licensed SQL Server 2005 EE instance. I searched for the SQL Server collation, and found SAP Note 600027, which recommended Binary order for use with the 850 Multilingual Character Set as the collation.
I attached the existing databases using the script provided with the Discovery system. Started up the SAP ERP instance. I then tried to log into the ERP 300 and got a START_CALL_SICK error message. From the error message details I find, "DB CHECK Wrong Server collation. Perform SQL2005 after upgrade steps. Please see note 126973". Note 126973 seemed to refer me to note 799058. However this talks about upgrading....
It appears to me I simply chose the wrong SQL Server 2005 collation type when installing the licensed coipy of SQL Server.
What collation type should be used?
Thanks,
Jay Warling

After reviewing what I did, it appears I neglected to detach the databases before un-installing SQL Server 2005 evaluation copy.
I did stop the ERP system via the SAP MMC before un-installing but did not detach the databases.
I believe the collation is actually correct, but I am stumped as how to proceed with the START_CALL_SICK error message.
Any ideas?
Thanks,
Jay

DG4MSQL v11.2.0.1 certified with Sql Server 2005 Express Edition?

We are working on a proof of concept and need to use Oracle Database Gateway for MS Sql Server - DG4MSQL version 11.2 - on 64bit Linux to connect to a Windows database that is using SQL Server 2005 Express Edition. I reviewed the certification matrix for the database gateways and it lists that SQL Server 2005 is certified - but does not specify which editions.
We are having some problems connecting to the SQL Server database and want to make sure that we should be able to connect to the express edition.
Thanks.

Yes, DG4MSQL 11 is certified with SQL Server Express Edition.

Issue in rebuilding index after restoring database from sql server 2005 to 2012

Hi All,
We have recently restored a database named DBA_admin from our sql server 2005 instance to sql server 2012 and we have added the database to out weekly maintenance plan. After adding the database to maintenance plan the job is failing every weekend due to
below error message.
Error message from maintenance plan history:
Executing the query "ALTER INDEX [PK_lsttype] ON [dbo].[lstAssign..." failed with the following error: "Invalid object name 'admin.dbo.databaselog'.
ALTER_INDEX - dbo.PK_lsttype". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Below is the code within the maintenance plan which the rebuild index task is using for database dba_admin:
USE [dba_admin]
GO
ALTER INDEX [PK_lstType] ON [dbo].[lstType] REBUILD PARTITION = ALL WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 98, DATA_COMPRESSION = PAGE)
Please let me know if any one knows how to fix this issue.
Thanks in Advance.

Sorry for the confusion.
Here is what is happening.
The query is failing while trying to rebuild index [Pk_lsttype] on table [lstAssign], both these objects belong to database
admin.
I have verified the old instance there is table databaselog within the database
dba_admin, but in new SQL instance within the database dba_admin the table is not present.
Even I'm not sure of what this table databaselog has to do with rebuilding indexes on table
lstAssign within the admin database.
I have manually tried to execute the alter index command within the database
admin and it is failing with the below error.
ALTER_TABLE - dbo.Query_pnb_sms
Msg 208, Level 16, State 1, Procedure ddlDatabaseTriggerLog, Line 39
Invalid object name 'dba_admin.dbo.databaselog'.

Restore a database in recovery mode sql server 2005

Similar Messages

Maybe you are looking for