Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 rows affected? where are they from?

Author  Topic 

funketekun
Constraint Violating Yak Guru

491 Posts

Posted - 2008-05-06 : 16:19:56
After executing a restore command. I got the following result.
Anyone know why is displaying rows affected. I saw the executiong plan and it shows several execution plans? Its the first time i see it. Can anyone explain what is going on?


restore database test_GG_ATRECORDING_QAT2
from disk = 'f:\a.bak'
with move 'a' to 'f:\MSSQL$INAQAT\data\a2.mdf',
move 'a_log' to 'f:\MSSQL$INAQAT\data\a2_log.LDF'



Processed 11016 pages for database 'test_GG_ATRECORDING_QAT2', file 'a' on file 1.
Processed 1 pages for database 'test_GG_ATRECORDING_QAT2', file 'a_log' on file 1.

(1 row(s) affected)


(7 row(s) affected)


(5 row(s) affected)


(5 row(s) affected)


(5 row(s) affected)


(11 row(s) affected)


(7 row(s) affected)


(5 row(s) affected)


(5 row(s) affected)


(5 row(s) affected)


(5 row(s) affected)


(5 row(s) affected)


(5 row(s) affected)


(5 row(s) affected)

RESTORE DATABASE successfully processed 11017 pages in 2.330 seconds (38.732 MB/sec).

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-05-06 : 16:22:53
It probably had to roll forward some transactions.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Database maintenance routines:
http://weblogs.sqlteam.com/tarad/archive/2004/07/02/1705.aspx
Go to Top of Page

funketekun
Constraint Violating Yak Guru

491 Posts

Posted - 2008-05-06 : 17:18:02
i found what is going on. It's firing
sp_restoredbreplication
sp_msrepl_backup_start

But i have no replication implemented and i dont know how to remove them. I googled it but no results.
Go to Top of Page

funketekun
Constraint Violating Yak Guru

491 Posts

Posted - 2008-05-07 : 14:18:21
looks like restarting the server solved the issue.
Go to Top of Page
   

- Advertisement -