Fulldatabase backup query

SQL Server full backup displays the following message on successful
completion of the full database backup.
Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
MB/sec).
I understand SQL Server manages data files in the form of pages and thats
the reason on completion of backup it display message "Processed 1136 pages
for database 'MyDB', file 'MyDB' on file 1". But why does it display message
"Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when the
transaction log files are not managed in the form of pages.
Hi
When BACKUP started , it reads (backups) all data pages and last step it
goes to LOG file and reads/backups all the data in the LOG from the point
the BACKUP was started
"Balaji" <Balaji@.discussions.microsoft.com> wrote in message
news:CA26E224-37C4-4C61-8F37-579C7A357DE7@.microsoft.com...
> SQL Server full backup displays the following message on successful
> completion of the full database backup.
> Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
> Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
> BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
> MB/sec).
> I understand SQL Server manages data files in the form of pages and thats
> the reason on completion of backup it display message "Processed 1136
> pages
> for database 'MyDB', file 'MyDB' on file 1". But why does it display
> message
> "Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when
> the
> transaction log files are not managed in the form of pages.
>
sql

Fulldatabase backup query

SQL Server full backup displays the following message on successful
completion of the full database backup.
Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
MB/sec).
I understand SQL Server manages data files in the form of pages and thats
the reason on completion of backup it display message "Processed 1136 pages
for database 'MyDB', file 'MyDB' on file 1". But why does it display message
"Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when the
transaction log files are not managed in the form of pages.Hi
When BACKUP started , it reads (backups) all data pages and last step it
goes to LOG file and reads/backups all the data in the LOG from the point
the BACKUP was started
"Balaji" <Balaji@.discussions.microsoft.com> wrote in message
news:CA26E224-37C4-4C61-8F37-579C7A357DE7@.microsoft.com...
> SQL Server full backup displays the following message on successful
> completion of the full database backup.
> Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
> Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
> BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
> MB/sec).
> I understand SQL Server manages data files in the form of pages and thats
> the reason on completion of backup it display message "Processed 1136
> pages
> for database 'MyDB', file 'MyDB' on file 1". But why does it display
> message
> "Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when
> the
> transaction log files are not managed in the form of pages.
>|||The backup database process includes the log records produced while the back
up was running. When you
do RESTORE, the log records are used to give you a consistent view of the da
ta (by doing REDO and
UNDO of those log records, just as each time the database is started),.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Balaji" <Balaji@.discussions.microsoft.com> wrote in message
news:CA26E224-37C4-4C61-8F37-579C7A357DE7@.microsoft.com...
> SQL Server full backup displays the following message on successful
> completion of the full database backup.
> Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
> Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
> BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
> MB/sec).
> I understand SQL Server manages data files in the form of pages and thats
> the reason on completion of backup it display message "Processed 1136 page
s
> for database 'MyDB', file 'MyDB' on file 1". But why does it display messa
ge
> "Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when th
e
> transaction log files are not managed in the form of pages.
>

Fulldatabase backup query

SQL Server full backup displays the following message on successful
completion of the full database backup.
Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
MB/sec).
I understand SQL Server manages data files in the form of pages and thats
the reason on completion of backup it display message "Processed 1136 pages
for database 'MyDB', file 'MyDB' on file 1". But why does it display message
"Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when the
transaction log files are not managed in the form of pages.Hi
When BACKUP started , it reads (backups) all data pages and last step it
goes to LOG file and reads/backups all the data in the LOG from the point
the BACKUP was started
"Balaji" <Balaji@.discussions.microsoft.com> wrote in message
news:CA26E224-37C4-4C61-8F37-579C7A357DE7@.microsoft.com...
> SQL Server full backup displays the following message on successful
> completion of the full database backup.
> Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
> Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
> BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
> MB/sec).
> I understand SQL Server manages data files in the form of pages and thats
> the reason on completion of backup it display message "Processed 1136
> pages
> for database 'MyDB', file 'MyDB' on file 1". But why does it display
> message
> "Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when
> the
> transaction log files are not managed in the form of pages.
>|||The backup database process includes the log records produced while the backup was running. When you
do RESTORE, the log records are used to give you a consistent view of the data (by doing REDO and
UNDO of those log records, just as each time the database is started),.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Balaji" <Balaji@.discussions.microsoft.com> wrote in message
news:CA26E224-37C4-4C61-8F37-579C7A357DE7@.microsoft.com...
> SQL Server full backup displays the following message on successful
> completion of the full database backup.
> Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
> Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
> BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
> MB/sec).
> I understand SQL Server manages data files in the form of pages and thats
> the reason on completion of backup it display message "Processed 1136 pages
> for database 'MyDB', file 'MyDB' on file 1". But why does it display message
> "Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when the
> transaction log files are not managed in the form of pages.
>

Full text stuck in a rut - error msg 7619

I have a full-text index on a production db. The catalog is currently empty. When I try to populate it, I get a message saying I must enable full text for this database. When I try to run sp_fulltext_database 'enable', I get the following message:
Server: Msg 7619, Level 16, State 1, Procedure sp_fulltext_database, Line 61
Execution of a full-text operation failed. The process cannot access the file because it is being used by another process.
Our OS team could not find any processes other than sqlserver.exe using files in the FTData dir. MSSearch is currently owned by the localsystem account, and ownership has not been changed since the SQL Server install.
I am using SQL 2000 EE. on a Windows 2000 cluster. SP3A is installed.
Has anyone else come across this error? Any advice would be appreciated!

Quote:

Originally posted by lisanova22
I have a full-text index on a production db. The catalog is currently empty. When I try to populate it, I get a message saying I must enable full text for this database. When I try to run sp_fulltext_database 'enable', I get the following message:
Server: Msg 7619, Level 16, State 1, Procedure sp_fulltext_database, Line 61
Execution of a full-text operation failed. The process cannot access the file because it is being used by another process.
Our OS team could not find any processes other than sqlserver.exe using files in the FTData dir. MSSearch is currently owned by the localsystem account, and ownership has not been changed since the SQL Server install.
I am using SQL 2000 EE. on a Windows 2000 cluster. SP3A is installed.
Has anyone else come across this error? Any advice would be appreciated!

full text searching...

This is a multi-part message in MIME format.
--=_NextPart_000_0006_01C64DEE.B57F4590
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I am working on a system where we wish toc reat a full text catalog in = sql server 2000. I created a test catalog and started a 'full = population' but it failed. After several attempts I restarted the = 'Mircosoft Search' service and it is failing with the following error:
"The Gatherer property mapping file cannot be opened. Error: 80070003. = The default values are being used. You may have to copy the property = mapping file from the setup CD, or reinstall the application".
I have little knowledge about MS seraching and the relationship with = full text catalogs in sql server 2000. I have been able from google to = find the following MS knowledge base article:
http://support.microsoft.com/?kbid=3D827449
Is this the best solution for my problem?
The system I am working on is not a clustered database and has the sql = installtion on the 'C:' drive with the log and data files fdor the = database seperated oput onto to seperate physical drives
Cheers
Ollie Riches
--=_NextPart_000_0006_01C64DEE.B57F4590
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
I am = working on a system where we wish toc reat a full text catalog in sql server 2000. I = created a test catalog and started a 'full population' but it failed. After = several attempts I restarted the 'Mircosoft Search' service and it is failing = with the following error:"The Gatherer property mapping file cannot be = opened. Error: 80070003. The default values are being used. You may have to copy = the property mapping file from the setup CD, or reinstall the = application".I have little knowledge about MS seraching and the relationship with full = text catalogs in sql server 2000. I have been able from google to find the = following MS knowledge base article:http://support.microsoft.com/?kbid=3D827449Is = this the best solution for my problem?The system I am working on is not a = clustered database and has the sql installtion on the 'C:' drive with = the log and data files fdor the database seperated oput onto to seperate = physical drivesCheersOllie Riches
--=_NextPart_000_0006_01C64DEE.B57F4590--I think this kb article is the best choice for you.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ollie Riches" <ollie.riches@.phoneanalyser.net> wrote in message
news:eIl646eTGHA.424@.TK2MSFTNGP12.phx.gbl...
I am working on a system where we wish toc reat a full text catalog in sql
server 2000. I created a test catalog and started a 'full population' but it
failed. After several attempts I restarted the 'Mircosoft Search' service
and it is failing with the following error:
"The Gatherer property mapping file cannot be opened. Error: 80070003. The
default values are being used. You may have to copy the property mapping
file from the setup CD, or reinstall the application".
I have little knowledge about MS seraching and the relationship with full
text catalogs in sql server 2000. I have been able from google to find the
following MS knowledge base article:
http://support.microsoft.com/?kbid=827449
Is this the best solution for my problem?
The system I am working on is not a clustered database and has the sql
installtion on the 'C:' drive with the log and data files fdor the database
seperated oput onto to seperate physical drives
Cheers
Ollie Riches

Full Text Index

Could Full Index option only be configured during installation? When I
try sp_fulltext_table on a table, I get the message that full text is
not enabled for the system.

--sharif"Sharif Islam" <mislam@.npspam.uiuc.eduwrote in message
news:fe8olf$aav$1@.news.ks.uiuc.edu...

Quote:

Originally Posted by

Could Full Index option only be configured during installation? When I try
sp_fulltext_table on a table, I get the message that full text is not
enabled for the system.
>
>
--sharif

You can install it after if you need to. Just pop in the CD.

Make sure to install any applicable Service Packs also afterwards.

--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html