I/O error

Hello,
I am getting following while creating a non-clustered
index on a table having 20 million records. Can anyone
suggest a solution for this...
Server: Msg 823, Level 24, State 11, Line 1
I/O error 33(error not found) detected during write at
offset 0x000002c8450000 in
file 'F:\SQL2K_Data\PROD_Data.MDF'.
Connection Broken
Regards,
ManojManoj,
This error came from the Operating system and not SQL Server. It
indicates a problem with your underlying hardware, most probably your
disk subsystem. Can you reproduce it on another server?
Run sqlhdtst available from http://support.microsoft.com/?id=178444 to
reproduce the error on your hardware.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Manoj Raheja wrote:
> Hello,
> I am getting following while creating a non-clustered
> index on a table having 20 million records. Can anyone
> suggest a solution for this...
> Server: Msg 823, Level 24, State 11, Line 1
> I/O error 33(error not found) detected during write at
> offset 0x000002c8450000 in
> file 'F:\SQL2K_Data\PROD_Data.MDF'.
> Connection Broken
> Regards,
> Manoj
>|||Manoj
It seems to be serious problem.
I suggest to restore database from the last BACKUP or if you don't have then
from query Analyser, master database, execute
dbcc checkdb(<databas_name> )
"Manoj Raheja" <manoj_raheja@.hotmail.com> wrote in message
news:1bfe301c451ed$eaba6680$a101280a@.phx
.gbl...
> Hello,
> I am getting following while creating a non-clustered
> index on a table having 20 million records. Can anyone
> suggest a solution for this...
> Server: Msg 823, Level 24, State 11, Line 1
> I/O error 33(error not found) detected during write at
> offset 0x000002c8450000 in
> file 'F:\SQL2K_Data\PROD_Data.MDF'.
> Connection Broken
> Regards,
> Manoj
>

I/O error

Hello,
I am getting following while creating a non-clustered
index on a table having 20 million records. Can anyone
suggest a solution for this...
Server: Msg 823, Level 24, State 11, Line 1
I/O error 33(error not found) detected during write at
offset 0x000002c8450000 in
file 'F:\SQL2K_Data\PROD_Data.MDF'.
Connection Broken
Regards,
Manoj
Manoj,
This error came from the Operating system and not SQL Server. It
indicates a problem with your underlying hardware, most probably your
disk subsystem. Can you reproduce it on another server?
Run sqlhdtst available from http://support.microsoft.com/?id=178444 to
reproduce the error on your hardware.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Manoj Raheja wrote:
> Hello,
> I am getting following while creating a non-clustered
> index on a table having 20 million records. Can anyone
> suggest a solution for this...
> Server: Msg 823, Level 24, State 11, Line 1
> I/O error 33(error not found) detected during write at
> offset 0x000002c8450000 in
> file 'F:\SQL2K_Data\PROD_Data.MDF'.
> Connection Broken
> Regards,
> Manoj
>
|||Manoj
It seems to be serious problem.
I suggest to restore database from the last BACKUP or if you don't have then
from query Analyser, master database, execute
dbcc checkdb(<databas_name>)
"Manoj Raheja" <manoj_raheja@.hotmail.com> wrote in message
news:1bfe301c451ed$eaba6680$a101280a@.phx.gbl...
> Hello,
> I am getting following while creating a non-clustered
> index on a table having 20 million records. Can anyone
> suggest a solution for this...
> Server: Msg 823, Level 24, State 11, Line 1
> I/O error 33(error not found) detected during write at
> offset 0x000002c8450000 in
> file 'F:\SQL2K_Data\PROD_Data.MDF'.
> Connection Broken
> Regards,
> Manoj
>
sql

I/O error

Hello,
I am getting following while creating a non-clustered
index on a table having 20 million records. Can anyone
suggest a solution for this...
Server: Msg 823, Level 24, State 11, Line 1
I/O error 33(error not found) detected during write at
offset 0x000002c8450000 in
file 'F:\SQL2K_Data\PROD_Data.MDF'.
Connection Broken
Regards,
ManojManoj,
This error came from the Operating system and not SQL Server. It
indicates a problem with your underlying hardware, most probably your
disk subsystem. Can you reproduce it on another server?
Run sqlhdtst available from http://support.microsoft.com/?id=178444 to
reproduce the error on your hardware.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Manoj Raheja wrote:
> Hello,
> I am getting following while creating a non-clustered
> index on a table having 20 million records. Can anyone
> suggest a solution for this...
> Server: Msg 823, Level 24, State 11, Line 1
> I/O error 33(error not found) detected during write at
> offset 0x000002c8450000 in
> file 'F:\SQL2K_Data\PROD_Data.MDF'.
> Connection Broken
> Regards,
> Manoj
>|||Manoj
It seems to be serious problem.
I suggest to restore database from the last BACKUP or if you don't have then
from query Analyser, master database, execute
dbcc checkdb(<databas_name>)
"Manoj Raheja" <manoj_raheja@.hotmail.com> wrote in message
news:1bfe301c451ed$eaba6680$a101280a@.phx.gbl...
> Hello,
> I am getting following while creating a non-clustered
> index on a table having 20 million records. Can anyone
> suggest a solution for this...
> Server: Msg 823, Level 24, State 11, Line 1
> I/O error 33(error not found) detected during write at
> offset 0x000002c8450000 in
> file 'F:\SQL2K_Data\PROD_Data.MDF'.
> Connection Broken
> Regards,
> Manoj
>

I wish to Avoid ...

Hi All,
I am working on Web Application which deals with history data for
reports and keeping track of changes.
Current Solution :
1) For each Entity I am having a column TID (Tracking ID) which
keep on increasing for an instance of Entity. (so history and present
data in the same table) . It makes querying the data difficult.
2) I am also using month year table for Managing data i.e
<TableNameMMYYYY> for a given month and year
Purposed Soluion :
1) Using a seperate table so that history and present data is
placed seperately .
2) Store All data in one table <TableName>
Please guide me on advantages and divantages you pin point in the
two approaches.
With warm regards
JatinderCheck out Partitioned Views in the BOL (or google it).
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"jsfromynr" <jatinder.singh@.clovertechnologies.com> wrote in message
news:1121943363.320745.186330@.o13g2000cwo.googlegroups.com...
Hi All,
I am working on Web Application which deals with history data for
reports and keeping track of changes.
Current Solution :
1) For each Entity I am having a column TID (Tracking ID) which
keep on increasing for an instance of Entity. (so history and present
data in the same table) . It makes querying the data difficult.
2) I am also using month year table for Managing data i.e
<TableNameMMYYYY> for a given month and year
Purposed Soluion :
1) Using a seperate table so that history and present data is
placed seperately .
2) Store All data in one table <TableName>
Please guide me on advantages and divantages you pin point in the
two approaches.
With warm regards
Jatinder|||Thanks for your Time,
I wish to make the solution Portable and Easy to Manage.
With warm regards
Jatinder|||There's really no such thing as portable. Easy to manage is a relative
term, too. Sometimes, you have to go the extra mile for performance.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"jsfromynr" <jatinder.singh@.clovertechnologies.com> wrote in message
news:1121951901.658739.22330@.g47g2000cwa.googlegroups.com...
Thanks for your Time,
I wish to make the solution Portable and Easy to Manage.
With warm regards
Jatinder

I wish to Avoid ...

Hi All,
I am working on Web Application which deals with history data for
reports and keeping track of changes.
Current Solution :

1) For each Entity I am having a column TID (Tracking ID) which
keep on increasing for an instance of Entity. (so history and present
data in the same table) . It makes querying the data difficult.
2) I am also using month year table for Managing data i.e
<TableNameMMYYYY> for a given month and year

Purposed Soluion :

1) Using a seperate table so that history and present data is
placed seperately .

2) Store All data in one table <TableName
Please guide me on advantages and disadvantages you pin point in the
two approaches.

With warm regards
JatinderI'm not sure I understand your description - you say that you have
history and present data in the same table, but then you say you have
separate month/year tables. You should probably give some more
information about what your tables look like (ie a simplified CREATE
TABLE script), what data you have in each one, how many rows you have
per month etc. It's also a good idea to mention which version of MSSQL
you have.

Simon|||jsfromynr (jatinder.singh@.clovertechnologies.com) writes:
> Current Solution :
> 1) For each Entity I am having a column TID (Tracking ID) which
> keep on increasing for an instance of Entity. (so history and present
> data in the same table) . It makes querying the data difficult.
> 2) I am also using month year table for Managing data i.e
><TableNameMMYYYY> for a given month and year
> Purposed Soluion :
> 1) Using a seperate table so that history and present data is
> placed seperately .
> 2) Store All data in one table <TableName>
> Please guide me on advantages and disadvantages you pin point in the
> two approaches.

It's a little unclear what you mean, but anyway having a table for each
month is not a good idea. Well, if you need to distribute the data it
could be, but in such case you should unite the data in a partitioned
view, and all your queries should use that view.

As for having a current data in a separate table, and adding this
data to a history table at the end of a day in a maintenance job can
sometimes be useful. As a matter of fact, this is routine in our
system.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks Erland,
Sorry If my description was not able to make the point / approach
clear. I am using a single table for a given month to hold that month's
changes/transactions
and for Enity there is no month year table

Erland I wish to ask you ;can I mail you my queries (I know posting
here on newsgroup will fetch me many answers) because most of the time
You,David Protas ,Anith and Celko are the ones who are active on these
newsgroups and provide elaborate and good answers . Everytime your
answer give something new to learn and you people bring bitter reality
to the poster especially Celko but that's what required . You all guys
doing great job.
Please keep reading my silly questions / answers
With warm regards
Jatinder

Erland Sommarskog wrote:
> jsfromynr (jatinder.singh@.clovertechnologies.com) writes:
> > Current Solution :
> > 1) For each Entity I am having a column TID (Tracking ID) which
> > keep on increasing for an instance of Entity. (so history and present
> > data in the same table) . It makes querying the data difficult.
> > 2) I am also using month year table for Managing data i.e
> ><TableNameMMYYYY> for a given month and year
> > Purposed Soluion :
> > 1) Using a seperate table so that history and present data is
> > placed seperately .
> > 2) Store All data in one table <TableName>
> > Please guide me on advantages and disadvantages you pin point in the
> > two approaches.
> It's a little unclear what you mean, but anyway having a table for each
> month is not a good idea. Well, if you need to distribute the data it
> could be, but in such case you should unite the data in a partitioned
> view, and all your queries should use that view.
> As for having a current data in a separate table, and adding this
> data to a history table at the end of a day in a maintenance job can
> sometimes be useful. As a matter of fact, this is routine in our
> system.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||jsfromynr wrote:
[snip]
> Erland I wish to ask you ;can I mail you my queries (I know posting
> here on newsgroup will fetch me many answers) because most of the time
> You,David Protas ,Anith and Celko are the ones who are active on these
> newsgroups and provide elaborate and good answers .

I'm hoping that Erland encourages you to continue posting your
questions here on the newsgroups - My first half-hour/hour of the
morning, I spend reading the newsgroups. There's lots of interesting
problems, questions and answers.

Occasionally, I try to help people using some of the knowledge I've
picked up along the way, but a lot of the time I just sit back and try
to absorb the knowledge that these people are kind enough to share - it
makes for a great learning experience. I would say that the schemas I
have worked on in the last few months are literally miles ahead of the
garbage I was producing two years ago :-)

Keep up the good work everybody, and keep the dicussions on usenet.

Just my two-penneth

Damien.|||jsfromynr (jatinder.singh@.clovertechnologies.com) writes:
> Sorry If my description was not able to make the point / approach
> clear. I am using a single table for a given month to hold that month's
> changes/transactions

As I said, that is a design that leads to problem, unless you unite
the tables in a partitioned view.

> Erland I wish to ask you ;can I mail you my queries

I prefer if you keep it to the newsgroups. Then other people can assist.
And, as Damien testified, other people can also benefit from the
exchange.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.aspsql

I think I found the solution

I recently (yesterday) installed a fresh copy of Windows XP with Service Pack 2 applied.

I proceeded with Visual Studio 2005 Express Editions installation straight away.

But I cannot install Microsoft SQL Server 2005 Express Edition x86.

I choose to install Microsoft SQL Server 2005 Express Edition x86 component along with every component of visual studio but it simply would not install.

In the end, after the installation of each complete is complete, I simply get an error message saying that Microsoft SQL Server 2005 Express Edition x86 failed to install.

What is the problem?

First take a look at the following file: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\summary.txt. This should point you to which component failed and the specific log file for the component. When you open the component log file search for "Value 3" (this is a Windows Installer code for the error section). Take a look at +/- 10 lines for the error.

If the summary.txt file doesn't provide any clues, take a look at: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\*_core(local).txt - open the most recent one if there are multiple. Go to the end of the file and you should find some clues as to why the installation failed.

|||

I looked. There were three errors and all of them said that installation cannot be done to a compressed drive

--

Error : SQL Server Setup cannot install files to the compressed or encrypted folder: C:\Program Files\Microsoft SQL Server\. To continue, make sure that your installation directories are not compressed or encrypted, or specify a different directory, and then run SQL Server Setup again.

--

I'll remove drive compression and try again.

Thanks for help!

|||

I am having the same problem - cannot install SQL Server Express, I looked in the file you mentioned to the other fellow and it says:

D43QNW81 : SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.

but I HAVE removed all components except a thing called Enterprise Library June 2005, and thaat one will not un-install without dot net framework 1.1

is that it? do I have to go ALL the way back?

any help will be much appreciated, I installed the whole works in a Virutal machine and now I am trying to install it on my base machine (because the Virtual one is too slow)

|||

David,

You can take a look at the latest *_core(local).log file to see which old component it's detecting. The log files can be found here: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files

If you email me directly at dtjones@.microsoft.com I can send you a clean up script. The script isn't supported but we've had good luck with it.

Cheers,
Dan

I need more

Hi,

Thanks for your answer,

It is a good solution but i need something like a free software from microsoft can do that , or a free script that do this simply because i am not familiar with .Net Programming

Express Advanced comes with most things in the for pay version and it is free you can download it in the link below.

http://msdn.microsoft.com/vstudio/express/sql/download/

|||

You know my sql server is SQL server 2000 express, Does this software work for me?

|||

There is no 2000 Express just MSDE(Microsoft data engine), SQL Server 2005 Express Advanced comes with most of the features of the other SQL Server editions and it is still free, MSDE does not come with Enterprise Manager, this one comes with Management Studio the new Enterprsie Manager. So download and install it as a named instance. Hope this helps.

i need Column names !

Hi, i need a query to have the columns names !!
If you have another solution, let me know !!
superj !!!Originally posted by superj
Hi, i need a query to have the columns names !!
If you have another solution, let me know !!

superj !!! I kind of like Bob, Carol, Ted, and Alice myself. What column names do you like?

-PatP|||I like them blue. Databases I like yellow.|||Originally posted by rdjabarov
I like them blue. Databases I like yellow. So, if you put those columns into a database, does the whole thing turn green?

-PatP|||Hey, that would be cool!|||SELECT COLUMN_NAME
> FROM INFORMATION_SCHEMA.COLUMNS
> WHERE TABLE_NAME = 'authors'
> ORDER BY ORDINAL_POSITION|||select colid, name from syscolumns where object_name(id) = 'authors' order by 1|||Originally posted by rdjabarov
I like them blue. Databases I like yellow.

Don't you read Dilbert?

Muave is the fastest db color|||whatever you do, dont get red
cops look for that color.

i myself , am currently configuring a Puce database with various pastel colored tables and some chince doilys.

yes i work for martha stewart living|||Why not :
EXEC sp_columns @.table_name = 'customers'|||okay i'll bite

exec SP_Help tablename

will give you everything about the table including all column names.|||But that gives whole lot of information where Originator requires only column information for a table.

I feel using INFORMATION SCHEMA VIEWS or SP_COLUMNS will suffice.
Originally posted by Ruprect
okay i'll bite

exec SP_Help tablename

will give you everything about the table including all column names.|||i was just jumpin' in
info_schema are just fine

or

how about

sp_columns

Returns column information for the specified tables or views that can be queried in the current environment.