I/O Error

Dear Experts,
During the execution of a select statement i faced this error message.
"I/O error 23(Data error (cyclic redundancy check).) detected during read at
offset
0x00000190efa000 in file 'd:\sqldb\MSSQL\data\Data2005_Data.MDF'."
Pls. advise solution
Thanks in advance.
Subhash ChandraSounds like a hard disk issue. Are you using a SAN, or otherwise
vendor-supported hardware? Do you have a good backup?
A
"Subhash" <Subhash@.discussions.microsoft.com> wrote in message
news:FF723DE3-1CD2-4912-AC49-1E4FA0D7B6D4@.microsoft.com...
> Dear Experts,
> During the execution of a select statement i faced this error
> message.
> "I/O error 23(Data error (cyclic redundancy check).) detected during read
> at
> offset
> 0x00000190efa000 in file 'd:\sqldb\MSSQL\data\Data2005_Data.MDF'."
> Pls. advise solution
> Thanks in advance.
> Subhash Chandra

I was wondering..

Dear folks,
Does anyone know where on earth are the Sql Server 2005 newsgroups?
I can't see any clue of them around here!
Thanks in advance and regards,http://communities.microsoft.com/ne...p=sqlserver2005
Roji. P. Thomas
Net Asset Management
http://toponewithties.blogspot.com
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:981A5BB8-AC6D-41C7-8575-F374DF1ADFE9@.microsoft.com...
> Dear folks,
> Does anyone know where on earth are the Sql Server 2005 newsgroups?
> I can't see any clue of them around here!
> Thanks in advance and regards,|||thanks
"Roji. P. Thomas" wrote:

> http://communities.microsoft.com/ne...p=sqlserver2005
> --
> Roji. P. Thomas
> Net Asset Management
> http://toponewithties.blogspot.com
>
> "Enric" <Enric@.discussions.microsoft.com> wrote in message
> news:981A5BB8-AC6D-41C7-8575-F374DF1ADFE9@.microsoft.com...
>
>

I want to use multiple select queries in a stored procedure

Dear all
I actually want to query multiple tables from a single stored
procedure. Please let me know the possibility of doing this. If some
have any idea regarding this please contact me at
resume2karthik@.gmail.com.
Of course it is possible, but your statement is so general that I do not
know what you want to do. For example:
1. Can you join several tables to produce a single result set? (Yes.)
2. Can you independently query several tables producing several result sets?
(Yes.)
3. Can you independently query several tables to finally producing a single
result set? (Yes.)
4. Et cetera.
Returning information from a stored procedure:
http://technet.microsoft.com/en-us/library/aa214398(SQL.80).aspx
Comments on processing multiple result sets:
http://technet.microsoft.com/en-us/library/ms187602.aspx
The UNION command: http://technet.microsoft.com/en-us/library/ms180026.aspx
Explain a little bit more and you will probably get a more useful answer.
RLF
<resume2karthik@.gmail.com> wrote in message
news:8cc48990-c843-4f34-b03e-b3b1d290701c@.x69g2000hsx.googlegroups.com...
> Dear all
> I actually want to query multiple tables from a single stored
> procedure. Please let me know the possibility of doing this. If some
> have any idea regarding this please contact me at
> resume2karthik@.gmail.com.
|||You can have multiple SELECT statements in your stored procuedre to return
the data and access each result sets using ADOs NextRecordset method.
- Sha Anand
"resume2karthik@.gmail.com" wrote:

> Dear all
> I actually want to query multiple tables from a single stored
> procedure. Please let me know the possibility of doing this. If some
> have any idea regarding this please contact me at
> resume2karthik@.gmail.com.
>

I want to use multiple select queries in a stored procedure

Dear all
I actually want to query multiple tables from a single stored
procedure. Please let me know the possibility of doing this. If some
have any idea regarding this please contact me at
resume2karthik@.gmail.com.Of course it is possible, but your statement is so general that I do not
know what you want to do. For example:
1. Can you join several tables to produce a single result set? (Yes.)
2. Can you independently query several tables producing several result sets?
(Yes.)
3. Can you independently query several tables to finally producing a single
result set? (Yes.)
4. Et cetera.
Returning information from a stored procedure:
http://technet.microsoft.com/en-us/library/aa214398(SQL.80).aspx
Comments on processing multiple result sets:
http://technet.microsoft.com/en-us/library/ms187602.aspx
The UNION command: http://technet.microsoft.com/en-us/library/ms180026.aspx
Explain a little bit more and you will probably get a more useful answer.
RLF
<resume2karthik@.gmail.com> wrote in message
news:8cc48990-c843-4f34-b03e-b3b1d290701c@.x69g2000hsx.googlegroups.com...
> Dear all
> I actually want to query multiple tables from a single stored
> procedure. Please let me know the possibility of doing this. If some
> have any idea regarding this please contact me at
> resume2karthik@.gmail.com.|||You can have multiple SELECT statements in your stored procuedre to return
the data and access each result sets using ADOs NextRecordset method.
- Sha Anand
"resume2karthik@.gmail.com" wrote:
> Dear all
> I actually want to query multiple tables from a single stored
> procedure. Please let me know the possibility of doing this. If some
> have any idea regarding this please contact me at
> resume2karthik@.gmail.com.
>

I want to use multiple select queries in a stored procedure

Dear all
I actually want to query multiple tables from a single stored
procedure. Please let me know the possibility of doing this. If some
have any idea regarding this please contact me at
resume2karthik@.gmail.com.Of course it is possible, but your statement is so general that I do not
know what you want to do. For example:
1. Can you join several tables to produce a single result set? (Yes.)
2. Can you independently query several tables producing several result sets?
(Yes.)
3. Can you independently query several tables to finally producing a single
result set? (Yes.)
4. Et cetera.
Returning information from a stored procedure:
http://technet.microsoft.com/en-us/library/aa214398(SQL.80).aspx
Comments on processing multiple result sets:
http://technet.microsoft.com/en-us/...y/ms187602.aspx
The UNION command: http://technet.microsoft.com/en-us/...y/ms180026.aspx
Explain a little bit more and you will probably get a more useful answer.
RLF
<resume2karthik@.gmail.com> wrote in message
news:8cc48990-c843-4f34-b03e-b3b1d290701c@.x69g2000hsx.googlegroups.com...
> Dear all
> I actually want to query multiple tables from a single stored
> procedure. Please let me know the possibility of doing this. If some
> have any idea regarding this please contact me at
> resume2karthik@.gmail.com.|||You can have multiple SELECT statements in your stored procuedre to return
the data and access each result sets using ADOs NextRecordset method.
- Sha Anand
"resume2karthik@.gmail.com" wrote:

> Dear all
> I actually want to query multiple tables from a single stored
> procedure. Please let me know the possibility of doing this. If some
> have any idea regarding this please contact me at
> resume2karthik@.gmail.com.
>

I want the user to only see the History Tab and nothing else

Dear Anyone,

Is it possible to configure the security of a report to only allow the user to see the history tab and not the properties, subcription and view tab and in addition, only view the snapshot reports and not the actual report itself?

Thanks,

Joseph

Joseph,

This is not possible with the current security granularity. You can apply "Manage Report History" which gives the user the rights to view history snapshots, but this also gives the ability to manage report history and execution properties.

You could apply "View Reports", but this also gives the ability to view the live report.

A crude simulation of what you want can be achieved with a combination of security and configuration:

1. configure the report to render from a snapshot, using Execution settings

2. select "Store all report execution snapshots in history" under History properties

3. give the user only View Reports permissions

Now, the user will only be able to view the report from either the most current snapshot (which is also the most current history snapshot), or through older history snapshots. The user wil not be able to view the report live, and will not be able to change the execution or history configuration. He will still see the Properties tab, but the only information available will be "General" information.

I want my custom SQL errors to display on the RS Page

Dear Anyone,

We have custom raise error messages embedded in our stored procedures. I've noticed that using Business Intelligence Dev, when these errors are invoked, they actually display on the RS report. But unfortunately, when I tried it on a deployed report, I always get the error below.

Is there a way to display custom SQL errors from my stored proc to the RS page? Where do I enable the remote errors?

Thanks,

Joseph

An error has occurred during report processing.

Cannot create a connection to data source 'AdventureWorks'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors.

Regarding remote errors:

You could set the "EnableRemoteErrors" configuration value to True in the ReportServer.ConfigurationInfo database table. Alternatively, you can use the SetSystemProperties SOAP call:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_ref_soapapi_service_lz_63le.asp

Here is an example for a .rss script that will turn it on:

Public Sub Main()
Dim P As New [Property]()
P.Name = "EnableRemoteErrors"
P.Value = True
Dim Properties(0) As [Property]
Properties(0) = P
Try
rs.SetSystemProperties(Properties)
Console.WriteLine("Remote errors enabled.")
Catch SE As SoapException
Console.WriteLine(SE.Detail.OuterXml)
End Try
End Sub

Then run the .rss script by using the rs.exe command line utility:

rs -i EnableRemoteErrors.rss -s http://Server/ReportServer

Once remote errors are enabled, you could throw a specific exeception with a informative error string in the stored procedure. That message should then be shown as inner message.

-- Robert

I need to rebuild Log file from Master file

Dear sir,
Now i have big problem with SQL i lost Log file now i have only master
file . i used recovery to find Log file but not found.
Please tell me how to rebuild Log file from Master file?
Waiting your suport,
Bunthach Eng student of Cambodia (My mail bunthachx@.yahoo.com, My phone
85512 500 382
*** Sent via Developersdex http://www.examnotes.net ***Bunthach Eng wrote:

> Dear sir,
> Now i have big problem with SQL i lost Log file now i have only master
> file . i used recovery to find Log file but not found.
> Please tell me how to rebuild Log file from Master file?
> Waiting your suport,
With master file you mean data file I presume?
Try he following (procedure by Raino Botha):
shutdown sql
move the current database file or rename it
restart sql server
create a new database of the same name and log file and location as the
old database and log file
get rid of the old database. you may be able to right click delete it
in this situation or used sp_removedb
create a new database of the right size and shape with correct log and
data file locations
stop sql
rename the new databases.mdf or delete it if you don't have enough
space - do not touch the .ldf
move back in the old database .mdf file or rename it back again
restart sql server
it should come up suspect
--
1. From a query window, set the status so that you can update the system
tables by running the following query:
use Master
go
sp_configure "allow", 1
go
reconfigure with override
go
2. Then set the status of the DB that is giving you the problem (XXXXX)
into Emergency Mode by running the following query:
update sysdatabases set status = 32768 where name = '<DBName>'
go
checkpoint
go
shutdown with nowait
go
3. Go into the data directory (MSSQL7\DATA) and rename the log file
associated the DB in question (XXXX.ldf) to some temporary name, such
as XXXX.TMP.
4. Exit the query window.
5. Then start up SQL Server from a DOS command window by issuing:
sqlservr -c -T3608 -T4022.
6. Bring up another query window and verify that the DB is in emergency
mode by issuing:
select Name, Status from Sysdatabases where name = '<DB_Name>'
7. Verify that the status is 32768. If it is, then issue the query:
dbcc traceon(3604)
dbcc rebuild_log ('<DB_Name>','<log_filename>') <-- You will need the
quotation marks REBUILD_LOG should take less than 5 minutes even on a
very large
database. It should complete with the message DBCC execution completed
8. Take the database out of bypass recovery mode by issuing the command
update sysdatabases set status = 0 where name = '<DBName>'
9. Exit the query window and then shutdown (Ctrl-C in the DOS window)
and restart SQL server. Verify the status of the database by running
DBCC NEWALLOC and DBCC CHECKDB on the database."
HTH,
Stijn Verrept.|||Stijn
There is no sp_removedb stored procedure. I think you meant DROP DATABASE
...command
"Stijn Verrept" <TURN_moc.tfosyrtne@.njits_AROUND> wrote in message
news:JMadnf956pkAWzXeRVnyrQ@.scarlet.biz...
> Bunthach Eng wrote:
>
> With master file you mean data file I presume?
> Try he following (procedure by Raino Botha):
> shutdown sql
> move the current database file or rename it
> restart sql server
> create a new database of the same name and log file and location as the
> old database and log file
> get rid of the old database. you may be able to right click delete it
> in this situation or used sp_removedb
> create a new database of the right size and shape with correct log and
> data file locations
> stop sql
> rename the new databases.mdf or delete it if you don't have enough
> space - do not touch the .ldf
> move back in the old database .mdf file or rename it back again
> restart sql server
> it should come up suspect
> --
> 1. From a query window, set the status so that you can update the system
> tables by running the following query:
> use Master
> go
> sp_configure "allow", 1
> go
> reconfigure with override
> go
> 2. Then set the status of the DB that is giving you the problem (XXXXX)
> into Emergency Mode by running the following query:
> update sysdatabases set status = 32768 where name = '<DBName>'
> go
> checkpoint
> go
> shutdown with nowait
> go
> 3. Go into the data directory (MSSQL7\DATA) and rename the log file
> associated the DB in question (XXXX.ldf) to some temporary name, such
> as XXXX.TMP.
> 4. Exit the query window.
> 5. Then start up SQL Server from a DOS command window by issuing:
> sqlservr -c -T3608 -T4022.
> 6. Bring up another query window and verify that the DB is in emergency
> mode by issuing:
> select Name, Status from Sysdatabases where name = '<DB_Name>'
> 7. Verify that the status is 32768. If it is, then issue the query:
> dbcc traceon(3604)
> dbcc rebuild_log ('<DB_Name>','<log_filename>') <-- You will need the
> quotation marks REBUILD_LOG should take less than 5 minutes even on a
> very large
> database. It should complete with the message DBCC execution completed
> 8. Take the database out of bypass recovery mode by issuing the command
> update sysdatabases set status = 0 where name = '<DBName>'
> 9. Exit the query window and then shutdown (Ctrl-C in the DOS window)
> and restart SQL server. Verify the status of the database by running
> DBCC NEWALLOC and DBCC CHECKDB on the database."
> --
> HTH,
> Stijn Verrept.|||Uri Dimant wrote:

> Stijn
> There is no sp_removedb stored procedure. I think you meant DROP
> DATABASE ...command
You are right sp_removedb doesn't exist. Well as I said this procedure
isn't mine.
HTH,
Stijn Verrept.

I need to figure out an property

Dear all,
I would need to know where is the variable for the time inverted for each
DTS in each launching.
In what table is stored.
Regards,Hi
If these are run as a job look at the sysjobhistory table in msdb, otherwise
I think you will need to create your history table.
John
"Enric" wrote:

> Dear all,
> I would need to know where is the variable for the time inverted for each
> DTS in each launching.
> In what table is stored.
> Regards,|||Thanks a lot John, are scheduled DTS. I've got it!
"John Bell" wrote:
> Hi
> If these are run as a job look at the sysjobhistory table in msdb, otherwi
se
> I think you will need to create your history table.
> John
> "Enric" wrote:
>

i need to cancel conflict when replication

Dear Sir,
i need to make merge application.
the problem is ,i need to make the replication every 3 hours,if there are a
conflict it will deletes the conflicting rows for the tables
that have primary keys.
i need each row for the same table at publisher and subscriber will be
replicated to each other,
but what happen is one of them deleted !!!!!
I can not use identity ranges to solve this problem that because of the
business needs of the software which i implement.
Thanks alot
Tamer
From what you describe it sounds like you want the Susbcriber to "win" primary key conflicts.
To do this you would need to click on the articles properties (the three dots to the right of your table name) in the specify articles dialog when creating your merge publication, and then in the resolver section, select the Use this custom resolver secti
on and select "Microsoft SQL Server subscriber always wins conflict resolver.".
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Tamer Nagi" wrote:

> Dear Sir,
> i need to make merge application.
> the problem is ,i need to make the replication every 3 hours,if there are a
> conflict it will deletes the conflicting rows for the tables
> that have primary keys.
> i need each row for the same table at publisher and subscriber will be
> replicated to each other,
> but what happen is one of them deleted !!!!!
> I can not use identity ranges to solve this problem that because of the
> business needs of the software which i implement.
> Thanks alot
> Tamer
>
>
|||Thanks for your reply.
But what i need exactly is,
the rows of publisher inserted at publisher and subscriber AND
the rows of subscriber inserted at publisher and subscriber
without delete any rows if conflict happening because of the existance of
the primary key in the table.
Example:
if i have Table name= Department
and i insert department="support" at the publisher with primary key=1 and
department="marketing" with primary key=1 at the subscriber
i need the two department inserted at the publisher and the subscriber with
department="support" has primary key=1 and department="marketing" has
primary key=2
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:CD5D0265-6440-4695-8BA1-769E87B1BD00@.microsoft.com...
> From what you describe it sounds like you want the Susbcriber to "win"
primary key conflicts.
> To do this you would need to click on the articles properties (the three
dots to the right of your table name) in the specify articles dialog when
creating your merge publication, and then in the resolver section, select
the Use this custom resolver section and select "Microsoft SQL Server
subscriber always wins conflict resolver.".[vbcol=seagreen]
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "Tamer Nagi" wrote:
are a[vbcol=seagreen]
|||Tamer,
If your subscriber insert needs to hold, but the PK column has to be altered
then you'll have to avoid the conflict as this precludes bith inserts
remaining. As you mention in your first post, this is normally done by
partitioning the data, eg using identity ranges. I would use this
methodology, and have another column which has an item counter number for
use in your business application.
hth,
Paul Ibison
|||Tamer,
Probably you need to implement your own custom conflict resolver.
Raj Moloye
|||I think the suggestion of separate PK seed and increment values is the best
way to go. A popular example of this is to start the Publisher with a seed
of 1, an increment of 2. Then start the Subscriber with a seed of 2 and an
increment of 2. This makes the odds on the Publisher, and the evens on teh
subscriber. Then everything replicates both ways just fine. New records
from both sides replicate without any conflicts. Hope this helps.
"Raj Moloye" wrote:

> Tamer,
> Probably you need to implement your own custom conflict resolver.
> Raj Moloye
>
>