database failure to restore from NT backup

Hello,
Have you seen this from Microsoft ?
http://support.microsoft.com/default.aspx?scid=kb;en-
us;268481
J

>--Original Message--
>One of our customers had a problem with SQL Server 7. We
have instigated a work around, but they want to know what
the root cause was.
>Problem description
>It seems that they had disk problems, then wanted to
restore the database from a backup. They were not doing
backups to disk, just to shutting down the services &
doing a cold NT backup to tape.
>Error Details
>The server lost a disc (one of five from RAID5 array).
After it was fixed, the data was restored from a backup
tape and the following appeared in the SQL Server activity
log. The database was in suspect mode.
>2004-04-29 19:36:45.31 spid9 Starting up
database 'dataname'.
>2004-04-29 19:36:45.31 spid9 Opening file
d:\SQL\data\dataname_Data.MDF.
>2004-04-29 19:36:45.31 spid9 Opening file
e:\SQL\data\dataname2_Data.NDF.
>2004-04-29 19:36:45.31 spid9 The header for
file 'e:\SQL\data\dataname2_Data.NDF' is not a valid
database file header. The PageAudit property is incorrect.
>2004-04-29 19:36:45.32 spid9 Device activation error.
The physical file name 'e:\SQL\data\dataname2_Data.NDF'
may be incorrect.
>2004-04-29 19:36:45.32 spid9 Opening file
d:\SQL\data\dataname_Log.LDF.
>2004-04-29 19:36:45.32 spid9 Opening file
e:\SQL\data\dataname2_Log.LDF.
>System Details
>SQL Server 7
>NT 4
>Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model
0
>4 * PIII 700 Mhz
>2 GB RAM
>40/80GB SCSI DLT Internal Tape Drive
>9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
>32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet
Pro100+)
>Regards
>David
>.
>Julie
Thanks for the link, but the customer says that the Bull RAID controller is
a Milex, not Adaptec,|||Ok, but does it use the Abaptec drivers such as graphics
tend to use the same ones ?
J

>--Original Message--
>Julie
>Thanks for the link, but the customer says that the Bull
RAID controller is a Milex, not Adaptec,
>.
>

database failure to restore from NT backup

Hello,
Have you seen this from Microsoft ?
http://support.microsoft.com/default.aspx?scid=kb;en-
us;268481
J

>--Original Message--
>One of our customers had a problem with SQL Server 7. We
have instigated a work around, but they want to know what
the root cause was.
>Problem description
>It seems that they had disk problems, then wanted to
restore the database from a backup. They were not doing
backups to disk, just to shutting down the services &
doing a cold NT backup to tape.
>Error Details
>The server lost a disc (one of five from RAID5 array).
After it was fixed, the data was restored from a backup
tape and the following appeared in the SQL Server activity
log. The database was in suspect mode.
>2004-04-29 19:36:45.31 spid9 Starting up
database 'dataname'.
>2004-04-29 19:36:45.31 spid9 Opening file
d:\SQL\data\dataname_Data.MDF.
>2004-04-29 19:36:45.31 spid9 Opening file
e:\SQL\data\dataname2_Data.NDF.
>2004-04-29 19:36:45.31 spid9 The header for
file 'e:\SQL\data\dataname2_Data.NDF' is not a valid
database file header. The PageAudit property is incorrect.
>2004-04-29 19:36:45.32 spid9 Device activation error.
The physical file name 'e:\SQL\data\dataname2_Data.NDF'
may be incorrect.
>2004-04-29 19:36:45.32 spid9 Opening file
d:\SQL\data\dataname_Log.LDF.
>2004-04-29 19:36:45.32 spid9 Opening file
e:\SQL\data\dataname2_Log.LDF.
>System Details
>SQL Server 7
>NT 4
>Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model
0
>4 * PIII 700 Mhz
>2 GB RAM
>40/80GB SCSI DLT Internal Tape Drive
>9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
>32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet
Pro100+)
>Regards
>David
>.
>
Julie
Thanks for the link, but the customer says that the Bull RAID controller is a Milex, not Adaptec,
|||Ok, but does it use the Abaptec drivers such as graphics
tend to use the same ones ?
J

>--Original Message--
>Julie
>Thanks for the link, but the customer says that the Bull
RAID controller is a Milex, not Adaptec,
>.
>

Database Engine default Isolation Level

Is there a way to change the Database Engine Default Isolation level?
The default is: Read committed (Database Engine default level)
I would like to move it to: Read uncommitted (the lowest level where
transactions are isolated only enough to ensure that physically corrupt data
is not read)
I would like to be able to change it on a database level...or a server
level.
ThanksThat sounds like a very bad idea to me. Why would you want to do that?
And with Read Uncommitted you can definitely get "logically" corrupt
data, you can get incomplete data, you can get an error (when pages are
moved during the dirty query access). I think you are seriously
underestimating the possible side effects of dirty reads. If you are not
using a read-only database, then I would not recommend it.
If you are on SQL Server 2005, BOL mentions this:
In SQL Server 2005, you can also minimize locking contention while
protecting transactions
from dirty reads of uncommitted data modifications using either:
* The READ COMMITTED isolation level with the READ_COMMITTED_SNAPSHOT
database option set to ON.
* The SNAPSHOT isolation level.
Maybe you should take a look at that.
--
Gert-Jan
SQL Server MVP
Sintel Silverblade wrote:
> Is there a way to change the Database Engine Default Isolation level?
> The default is: Read committed (Database Engine default level)
> I would like to move it to: Read uncommitted (the lowest level where
> transactions are isolated only enough to ensure that physically corrupt data
> is not read)
> I would like to be able to change it on a database level...or a server
> level.
> Thanks

Database Defaults

I have a strange (well I think its strange) where I have create a field
(CreateDate) with a default of (getdate()); however, on the server where this
table is built, it is not populating the CreateDate, and as a result I am
getting errors, has anyone ever seen an issue like this were the field
defaults aren't getting populated?Does the column allow nulls?
Is the insert statement inserting a blank string in that column, or
something else that shouldn't be inserted?
Are you receiving any errors?
can we see the insert script?
Simon Worth
Scott wrote:
> I have a strange (well I think its strange) where I have create a field
> (CreateDate) with a default of (getdate()); however, on the server where this
> table is built, it is not populating the CreateDate, and as a result I am
> getting errors, has anyone ever seen an issue like this were the field
> defaults aren't getting populated?|||"Simon Worth" wrote:
The field does NOT allow nuls, and I tested with a very simple script:
Insert into Codes
(Code,Description)
values ('0001','Test Code')
the error message that I received was that the field will not accept nulls
the actual verbage was "Cannot insert the value NULL into column
'CreateDate',table test_app.dbo.codes, column does not allow NULLs. Update
Fails."
I use this all the time, and I am sure alot of others as well, this is the
first time I have ever run into anything like this
> Does the column allow nulls?
> Is the insert statement inserting a blank string in that column, or
> something else that shouldn't be inserted?
> Are you receiving any errors?
> can we see the insert script?
> Simon Worth|||Are you certain that the default constraint is still on the column? Try
verifying existence with sp_help 'Codes'.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:B5F635A5-6379-41C9-A849-BC10B57865A7@.microsoft.com...
>
> "Simon Worth" wrote:
> The field does NOT allow nuls, and I tested with a very simple script:
> Insert into Codes
> (Code,Description)
> values ('0001','Test Code')
> the error message that I received was that the field will not accept nulls
> the actual verbage was "Cannot insert the value NULL into column
> 'CreateDate',table test_app.dbo.codes, column does not allow NULLs.
> Update
> Fails."
> I use this all the time, and I am sure alot of others as well, this is the
> first time I have ever run into anything like this
>
>> Does the column allow nulls?
>> Is the insert statement inserting a blank string in that column, or
>> something else that shouldn't be inserted?
>> Are you receiving any errors?
>> can we see the insert script?
>> Simon Worth
>

Database Defaults

I have a strange (well I think its strange) where I have create a field
(CreateDate) with a default of (getdate()); however, on the server where this
table is built, it is not populating the CreateDate, and as a result I am
getting errors, has anyone ever seen an issue like this were the field
defaults aren't getting populated?
Does the column allow nulls?
Is the insert statement inserting a blank string in that column, or
something else that shouldn't be inserted?
Are you receiving any errors?
can we see the insert script?
Simon Worth
Scott wrote:
> I have a strange (well I think its strange) where I have create a field
> (CreateDate) with a default of (getdate()); however, on the server where this
> table is built, it is not populating the CreateDate, and as a result I am
> getting errors, has anyone ever seen an issue like this were the field
> defaults aren't getting populated?
|||"Simon Worth" wrote:
The field does NOT allow nuls, and I tested with a very simple script:
Insert into Codes
(Code,Description)
values ('0001','Test Code')
the error message that I received was that the field will not accept nulls
the actual verbage was "Cannot insert the value NULL into column
'CreateDate',table test_app.dbo.codes, column does not allow NULLs. Update
Fails."
I use this all the time, and I am sure alot of others as well, this is the
first time I have ever run into anything like this

> Does the column allow nulls?
> Is the insert statement inserting a blank string in that column, or
> something else that shouldn't be inserted?
> Are you receiving any errors?
> can we see the insert script?
> Simon Worth
|||Are you certain that the default constraint is still on the column? Try
verifying existence with sp_help 'Codes'.
Hope this helps.
Dan Guzman
SQL Server MVP
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:B5F635A5-6379-41C9-A849-BC10B57865A7@.microsoft.com...
>
> "Simon Worth" wrote:
> The field does NOT allow nuls, and I tested with a very simple script:
> Insert into Codes
> (Code,Description)
> values ('0001','Test Code')
> the error message that I received was that the field will not accept nulls
> the actual verbage was "Cannot insert the value NULL into column
> 'CreateDate',table test_app.dbo.codes, column does not allow NULLs.
> Update
> Fails."
> I use this all the time, and I am sure alot of others as well, this is the
> first time I have ever run into anything like this
>
>

Database Defaults

I have a strange (well I think its strange) where I have create a field
(CreateDate) with a default of (getdate()); however, on the server where thi
s
table is built, it is not populating the CreateDate, and as a result I am
getting errors, has anyone ever seen an issue like this were the field
defaults aren't getting populated?Does the column allow nulls?
Is the insert statement inserting a blank string in that column, or
something else that shouldn't be inserted?
Are you receiving any errors?
can we see the insert script?
Simon Worth
Scott wrote:
> I have a strange (well I think its strange) where I have create a field
> (CreateDate) with a default of (getdate()); however, on the server where t
his
> table is built, it is not populating the CreateDate, and as a result I am
> getting errors, has anyone ever seen an issue like this were the field
> defaults aren't getting populated?|||"Simon Worth" wrote:
The field does NOT allow nuls, and I tested with a very simple script:
Insert into Codes
(Code,Description)
values ('0001','Test Code')
the error message that I received was that the field will not accept nulls
the actual verbage was "Cannot insert the value NULL into column
'CreateDate',table test_app.dbo.codes, column does not allow NULLs. Update
Fails."
I use this all the time, and I am sure alot of others as well, this is the
first time I have ever run into anything like this

> Does the column allow nulls?
> Is the insert statement inserting a blank string in that column, or
> something else that shouldn't be inserted?
> Are you receiving any errors?
> can we see the insert script?
> Simon Worth|||Are you certain that the default constraint is still on the column? Try
verifying existence with sp_help 'Codes'.
Hope this helps.
Dan Guzman
SQL Server MVP
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:B5F635A5-6379-41C9-A849-BC10B57865A7@.microsoft.com...
>
> "Simon Worth" wrote:
> The field does NOT allow nuls, and I tested with a very simple script:
> Insert into Codes
> (Code,Description)
> values ('0001','Test Code')
> the error message that I received was that the field will not accept nulls
> the actual verbage was "Cannot insert the value NULL into column
> 'CreateDate',table test_app.dbo.codes, column does not allow NULLs.
> Update
> Fails."
> I use this all the time, and I am sure alot of others as well, this is the
> first time I have ever run into anything like this
>
>
>

database creation in XP

I am an SQL beginer, and have installed SQL 2000 in Windows XP SP2. Only the client components of SQL were installed by default in XP. SQL query analyser doesnot detect any servers (I already have IIS installed). In such a scenario how do I create a Database and gain access to it ?Do you know SQL server name?|||

Quote:

Originally Posted by iburyak

Do you know SQL server name?

No. The SQL Query analyser doesnot show any available servers. Also I am not connected to any networked PC. I wish to connect to the local/virtual server in IIS in C drive. I have an ASP.Net application in my wwwroot forlder for which I need to create a database to store and access data. Please note that while installing SQL server in XP I was prompted with the following message: "Microsoft SQL Server 2000 Enterprise Edition server component is not suported on this operating system. Only client components will be available for installation". Also due to this reason the MSSQL server service has not been installed.|||IIS server is a web server and not SQL server.
As far as I understand you didn't install SQL server at all and this is why you can't connect to it.

The only option you have is to use Access database instead. Go to Microsoft Office and you will be able to find it.|||

Quote:

Originally Posted by iburyak

IIS server is a web server and not SQL server.
As far as I understand you didn't install SQL server at all and this is why you can't connect to it.

The only option you have is to use Access database instead. Go to Microsoft Office and you will be able to find it.

Yes you were right. Although SQL was installed the server components were not installed. I have added the server components and now its working fine.
Thanks a lot.