Database in Recovering/suspect mode

Hi,
We have database of around 500 GB. Y'day nite we got a error msg saying
unable to write error to errorlog file.We were not able to login to the
sqlserver this morning.
So we restarted our server. It went to recover mode & started recovering
the database. It was fine till 96% then
we got a error msg
"Could not redo log record (635160:1109455:186),
for transaction ID (0:733497362), on page (4:840931), database 'VADI_NFDW'
(8). Page: LSN = (635147:63129:440), type = 2. Log: OpCode = 3, context 3,
PrevPageLSN: (635160:1100226:202)."
and one more msg as
"Error while redoing logged operation in database 'VADI_NFDW'. Error at log
record ID (635160:1109455:186)"
How could we solve this problem...It's our production db...
Thanks
Muthu
You need to contact PSS to help you with this.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"muthu" <muthu@.discussions.microsoft.com> wrote in message
news:DFB0D7F3-5236-48B9-8A4B-87BB0C1F8D24@.microsoft.com...
> Hi,
> We have database of around 500 GB. Y'day nite we got a error msg saying
> unable to write error to errorlog file.We were not able to login to the
> sqlserver this morning.
> So we restarted our server. It went to recover mode & started recovering
> the database. It was fine till 96% then
> we got a error msg
> "Could not redo log record (635160:1109455:186),
> for transaction ID (0:733497362), on page (4:840931), database 'VADI_NFDW'
> (8). Page: LSN = (635147:63129:440), type = 2. Log: OpCode = 3, context 3,
> PrevPageLSN: (635160:1100226:202)."
> and one more msg as
> "Error while redoing logged operation in database 'VADI_NFDW'. Error at
log
> record ID (635160:1109455:186)"
> How could we solve this problem...It's our production db...
> Thanks
> Muthu
>

Database in Recovering/suspect mode

Hi,
We have database of around 500 GB. Y'day nite we got a error msg saying
unable to write error to errorlog file.We were not able to login to the
sqlserver this morning.
So we restarted our server. It went to recover mode & started recovering
the database. It was fine till 96% then
we got a error msg
"Could not redo log record (635160:1109455:186),
for transaction ID (0:733497362), on page (4:840931), database 'VADI_NFDW'
(8). Page: LSN = (635147:63129:440), type = 2. Log: OpCode = 3, context 3,
PrevPageLSN: (635160:1100226:202)."
and one more msg as
"Error while redoing logged operation in database 'VADI_NFDW'. Error at log
record ID (635160:1109455:186)"
How could we solve this problem...It's our production db...
Thanks
MuthuYou need to contact PSS to help you with this.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"muthu" <muthu@.discussions.microsoft.com> wrote in message
news:DFB0D7F3-5236-48B9-8A4B-87BB0C1F8D24@.microsoft.com...
> Hi,
> We have database of around 500 GB. Y'day nite we got a error msg saying
> unable to write error to errorlog file.We were not able to login to the
> sqlserver this morning.
> So we restarted our server. It went to recover mode & started recovering
> the database. It was fine till 96% then
> we got a error msg
> "Could not redo log record (635160:1109455:186),
> for transaction ID (0:733497362), on page (4:840931), database 'VADI_NFDW'
> (8). Page: LSN = (635147:63129:440), type = 2. Log: OpCode = 3, context 3,
> PrevPageLSN: (635160:1100226:202)."
> and one more msg as
> "Error while redoing logged operation in database 'VADI_NFDW'. Error at
log
> record ID (635160:1109455:186)"
> How could we solve this problem...It's our production db...
> Thanks
> Muthu
>

Database in Recovering/suspect mode

Hi,
We have database of around 500 GB. Y'day nite we got a error msg saying
unable to write error to errorlog file.We were not able to login to the
sqlserver this morning.
So we restarted our server. It went to recover mode & started recovering
the database. It was fine till 96% then
we got a error msg
"Could not redo log record (635160:1109455:186),
for transaction ID (0:733497362), on page (4:840931), database 'VADI_NFDW'
(8). Page: LSN = (635147:63129:440), type = 2. Log: OpCode = 3, context 3,
PrevPageLSN: (635160:1100226:202)."
and one more msg as
"Error while redoing logged operation in database 'VADI_NFDW'. Error at log
record ID (635160:1109455:186)"
How could we solve this problem...It's our production db...
Thanks
MuthuYou need to contact PSS to help you with this.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"muthu" <muthu@.discussions.microsoft.com> wrote in message
news:DFB0D7F3-5236-48B9-8A4B-87BB0C1F8D24@.microsoft.com...
> Hi,
> We have database of around 500 GB. Y'day nite we got a error msg saying
> unable to write error to errorlog file.We were not able to login to the
> sqlserver this morning.
> So we restarted our server. It went to recover mode & started recovering
> the database. It was fine till 96% then
> we got a error msg
> "Could not redo log record (635160:1109455:186),
> for transaction ID (0:733497362), on page (4:840931), database 'VADI_NFDW'
> (8). Page: LSN = (635147:63129:440), type = 2. Log: OpCode = 3, context 3,
> PrevPageLSN: (635160:1100226:202)."
> and one more msg as
> "Error while redoing logged operation in database 'VADI_NFDW'. Error at
log
> record ID (635160:1109455:186)"
> How could we solve this problem...It's our production db...
> Thanks
> Muthu
>

database encryption

Hello!
i am aware of the ability to encrypt something or issue a certificate for a
column, etc.
does the sql server itself write to disk in clear text?
if so, is there a feature to prevent that?
can a db not be mountable to another sql server without a password?
thank you very much for your help!
-Bahman"Bahman" <Bahman@.discussions.microsoft.com> wrote in message
news:4C85593A-F3A3-467B-AD51-32A87A99143C@.microsoft.com...
> Hello!
> i am aware of the ability to encrypt something or issue a certificate for
> a
> column, etc.
> does the sql server itself write to disk in clear text?
SQL Server stores data in binary format. Their might be some plain text
that can be seen if someone were to dissect your MDF files.

> if so, is there a feature to prevent that?
There are third party software encryption tools that encrypt the actual MDF
files, or even entire hard drives.|||"Bahman" <Bahman@.discussions.microsoft.com> wrote in message
news:4C85593A-F3A3-467B-AD51-32A87A99143C@.microsoft.com...
> Hello!
> i am aware of the ability to encrypt something or issue a certificate for
> a
> column, etc.
> does the sql server itself write to disk in clear text?
SQL Server stores data in binary format. Their might be some plain text
that can be seen if someone were to dissect your MDF files.

> if so, is there a feature to prevent that?
There are third party software encryption tools that encrypt the actual MDF
files, or even entire hard drives.|||In SQL Server 2005 the private key associated with a certificate is always
stored encrypted. See the famous Encryption Hierarchy chart at
http://msdn2.microsoft.com/en-US/library/ms189586.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Bahman" <Bahman@.discussions.microsoft.com> wrote in message
news:4C85593A-F3A3-467B-AD51-32A87A99143C@.microsoft.com...
> Hello!
> i am aware of the ability to encrypt something or issue a certificate for
> a
> column, etc.
> does the sql server itself write to disk in clear text?
> if so, is there a feature to prevent that?
> can a db not be mountable to another sql server without a password?
> thank you very much for your help!
> -Bahman
>|||In SQL Server 2005 the private key associated with a certificate is always
stored encrypted. See the famous Encryption Hierarchy chart at
http://msdn2.microsoft.com/en-US/library/ms189586.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Bahman" <Bahman@.discussions.microsoft.com> wrote in message
news:4C85593A-F3A3-467B-AD51-32A87A99143C@.microsoft.com...
> Hello!
> i am aware of the ability to encrypt something or issue a certificate for
> a
> column, etc.
> does the sql server itself write to disk in clear text?
> if so, is there a feature to prevent that?
> can a db not be mountable to another sql server without a password?
> thank you very much for your help!
> -Bahman
>|||Can someone recommend a good highly scalable and easy to use 3rd party tool
to encrypt the contents of a disk. Keep in mind that I run a SQL Cluster. So
the disk is not local. It resides on the SAN.
TIA!
"Mike C#" <xxx@.yyy.com> wrote in message news:Na1lg.294$B95.11@.fe10.lga...
> "Bahman" <Bahman@.discussions.microsoft.com> wrote in message
> news:4C85593A-F3A3-467B-AD51-32A87A99143C@.microsoft.com...
> SQL Server stores data in binary format. Their might be some plain text
> that can be seen if someone were to dissect your MDF files.
>
> There are third party software encryption tools that encrypt the actual
> MDF files, or even entire hard drives.
>|||Can someone recommend a good highly scalable and easy to use 3rd party tool
to encrypt the contents of a disk. Keep in mind that I run a SQL Cluster. So
the disk is not local. It resides on the SAN.
TIA!
"Mike C#" <xxx@.yyy.com> wrote in message news:Na1lg.294$B95.11@.fe10.lga...
> "Bahman" <Bahman@.discussions.microsoft.com> wrote in message
> news:4C85593A-F3A3-467B-AD51-32A87A99143C@.microsoft.com...
> SQL Server stores data in binary format. Their might be some plain text
> that can be seen if someone were to dissect your MDF files.
>
> There are third party software encryption tools that encrypt the actual
> MDF files, or even entire hard drives.
>|||You can use encrypt data and file using SQL Server 2005.
In SQL Serer 2005 support many Encryption methods.
And can use EFS, NTFS .
"Bahman"?? ??? ??:

> Hello!
> i am aware of the ability to encrypt something or issue a certificate for
a
> column, etc.
> does the sql server itself write to disk in clear text?
> if so, is there a feature to prevent that?
> can a db not be mountable to another sql server without a password?
> thank you very much for your help!
> -Bahman
>|||You can use encrypt data and file using SQL Server 2005.
In SQL Serer 2005 support many Encryption methods.
And can use EFS, NTFS .
"Bahman"?? ??? ??:

> Hello!
> i am aware of the ability to encrypt something or issue a certificate for
a
> column, etc.
> does the sql server itself write to disk in clear text?
> if so, is there a feature to prevent that?
> can a db not be mountable to another sql server without a password?
> thank you very much for your help!
> -Bahman
>

Database design question....

I am building an application which is part directory (yellow page style). As I began to build the database and write up the design I found my self challenged with the following:

In part of the db I have a table for companies, categories and subcategories. The problem is that some of the companies fall into more than 1 category and I am not sure how to effeciently design this.

Can anyone share some thoughts or suggestions?::The problem is that some of the companies fall into more than 1 category and I am not
::sure how to effeciently design this.

What you need to make is a m:n relation and is a standard pattern for handling this standard problem in db design.

First, you should have three tables, but NOT two for category and subcategory.

You should have one table for Category (and a subcategory IS a category, build a tree using a relation pointing back to the table), one for the entires (companies), one for coupling one entry with one caategory - a mid table that allows you to assign an entry to x categories.

This table would basically contain one field (fk-relation) to the category, one to the entry.

Get a beginner book for SQL and relational databases that explains M:N relations in depth.|||doesn't look that hard, basic relational db design:

Category
* CatID (PK)
* CatName
* ...

Company
* CompID (PK)
* CompName
* ...

Company_Category
* CompID (PK ; FK to Company.CompID)
* CatID (PK ; FK Category.CatID)

By the way, implement subcategories as a category with a parent. Category table becomes:

Category
* CatID
* CatName
* CatParentCatID (maybe NULL for top level category)|||look up tables. Just store the primary keys in the look up tables.