Encryption at the database field level

Hello Everyone

I need a solution for the following problem ASAP

Configuration
SQL 2000 ENT Edition
Client - Server Application Designed in VB

I have one filed in one of my tables in a database E.g Credit Card Number. I need this fields to be Encrypted so that no body can see and mis use that information. One option is to change the application and incorporate the encryption logic into the application. Does SQL 2000 Provides some kind of Encryption at a field level? or can i manage this thing at the database level? I desperatelly want to do it at the database level.Refer to this MSDN link (http://msdn.microsoft.com/library/en-us/dnnetsec/html/SecNetHT19.asp) about using SSL communication.

Also on SQL Server level you can use MULTI-PROTOCOL netlib with ENCRYPTION option for the security, refer to books online for more information.

Encryption and the client

I have a basic understanding of the encryption using T-SQL, but is all of this at the T-SQL level? Like can a client have a certificate, be sent the encrypted value (that was encrypted on SQL Server), and using the same cert that is on the server decrypt the data?

Is there a good article/book that covered encryption in detail that you can suggest? Or is this something that you would build in .NET?

If your concern is to protect data in transit, I would strongly recommend you to use SSL to protect the data between your server and the client.

If your goal is to protect data at rest, but in such a way that the protected data cannot be decrypted by the server (i.e. the decryption key is never stored/used in the server hosting SQL Server) you can use .Net to protect the data directly, but all the key management should be on your client application.

Typically, for normal data I don’t recommend using a model where you use public keys to protect data directly on SQL Server, and use the private key on the client to decrypt it (or vice versa).

The main reasons are that your application will still have to do most of the key management (private/public keys), the performance of asymmetric key encryption is orders of magnitude slower than symmetric key encryption and that in SQL Server the limit for encrypting data using an asymmetric key is 1 block (based on the private key modulus, for the self signed certificates SQL Server generates this means you can only encrypt up to ~117 bytes of plaintext).

After saying that, there may be some cases where this mechanism may actually work better for your particular needs. You can find one sample on how to use the .Net framework to encrypt data and decrypt it on SQL Server using asymmetric keys: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=384472&SiteID=1

I hope this information can help you.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Actually my question was largely academic in nature, as I was trying to get my head straight on a few topics with SQL Server for a client. I had a few preconcieved notions about how things worked with encryption.

Thanks again (you have helped me before :)!

Encryption and Compatibility level 80

Does anyone have any insight as to whether the new data encryption features of SQL Server 2005 work when the database is set to compatibility level 80?I would recommended testing in development to be sure.sql

encrypted email

Hi,
is there anyway to encrypt any emails that are sent out by using send db
mail? is that hanlded at the database level or exchange server level?
Any Idea?
Thanks
EdHi
"Ed" wrote:

> Hi,
> is there anyway to encrypt any emails that are sent out by using send db
> mail? is that hanlded at the database level or exchange server level?
> Any Idea?
> Thanks
> Ed
AFAIK there is no way to encrypt your email when using database mail, you
could encrypt the contents/attachments (separately) and send the encrypted
content/attachment, but you would need a method of decryption at the
recipient.
This is not the same as sending the email over an IPSEC or a similar
connection see
[url]http://www.microsoft.com/technet/prodtechnol/windows2000serv/howto/ispstep.mspx[/u
rl]
John

encrypted email

Hi,
is there anyway to encrypt any emails that are sent out by using send db
mail? is that hanlded at the database level or exchange server level?
Any Idea?
Thanks
EdHi
"Ed" wrote:
> Hi,
> is there anyway to encrypt any emails that are sent out by using send db
> mail? is that hanlded at the database level or exchange server level?
> Any Idea?
> Thanks
> Ed
AFAIK there is no way to encrypt your email when using database mail, you
could encrypt the contents/attachments (separately) and send the encrypted
content/attachment, but you would need a method of decryption at the
recipient.
This is not the same as sending the email over an IPSEC or a similar
connection see
http://www.microsoft.com/technet/prodtechnol/windows2000serv/howto/ispstep.mspx
John

encrypted email

Hi,
is there anyway to encrypt any emails that are sent out by using send db
mail? is that hanlded at the database level or exchange server level?
Any Idea?
Thanks
Ed
Hi
"Ed" wrote:

> Hi,
> is there anyway to encrypt any emails that are sent out by using send db
> mail? is that hanlded at the database level or exchange server level?
> Any Idea?
> Thanks
> Ed
AFAIK there is no way to encrypt your email when using database mail, you
could encrypt the contents/attachments (separately) and send the encrypted
content/attachment, but you would need a method of decryption at the
recipient.
This is not the same as sending the email over an IPSEC or a similar
connection see
http://www.microsoft.com/technet/prodtechnol/windows2000serv/howto/ispstep.mspx
John

Encrypt payroll fields

I need to store payroll information (pay rates) in my data warehouse.
I've search on field level encryption and most the stuff i find is for
passwords, I.E. not reversable. I need to protect the payrate field
from dba's and sa's, but I need to allow the authorized users to see
the contents.
Any ideas? Does 2005 handle this?
I don't have a web app, per se, that access's this information. however
I am using Cognos' Report Net.
thanks in advance
RobThe most common solution is to use some kind of encryption library in
your client application or middle-tier, and encrypt/decrpyt the data as
people enter it or retrieve it. In SQL2005, you could use the .NET
crypto libraries within a .NET stored proc, but you can use them
already in a .NET client application regardless of the database.

So it probably depends on what your development environment and
language are. These links might give you some ideas:

http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=22
http://www.aspfaq.com/show.asp?id=2536

Simon|||SQL2005 actually has encryption built-in using either shared key or
certificates (which it can generate). Alternatively, for SQL2000 look
at xp_crypt from http://www.activecrypt.com/.

Encrption Level

Does anyone know what encryption level (algorithm, API, strength, etc.) is used when SSAS 2005 encrypts data between a client and the server?

Thanks,
Dave Fackler1. For native connections (when you connect directly to AS2005, no http/IIS) SSPI is used for authentication, signatures and encryption and these 2 connection string properties can be used:

Protection Level =
NONE (no authentication, no signatures, no encryption)
CONNECT (authentication, clear text without signatures)
PKT INTEGRITY (authentication, clear text with signatures - for replay and data tempering protection)
PKT PRIVACY (authentication, encryption, signatures included)

SSPI = the name of the SSPI package to be used, for example 'Kerberos' or 'NTLM' (default is 'Negociate')

2. For http connections, you can use https

3. For local cubes connections, the problem won't apply

Adrian Dumitrascu.|||Do you know how can we change the protection level to NONE on a deployed OLAP project?

Encrption Level

Does anyone know what encryption level (algorithm, API, strength, etc.) is used when SSAS 2005 encrypts data between a client and the server?

Thanks,
Dave Fackler1. For native connections (when you connect directly to AS2005, no http/IIS) SSPI is used for authentication, signatures and encryption and these 2 connection string properties can be used:

Protection Level =
NONE (no authentication, no signatures, no encryption)
CONNECT (authentication, clear text without signatures)
PKT INTEGRITY (authentication, clear text with signatures - for replay and data tempering protection)
PKT PRIVACY (authentication, encryption, signatures included)

SSPI = the name of the SSPI package to be used, for example 'Kerberos' or 'NTLM' (default is 'Negociate')

2. For http connections, you can use https

3. For local cubes connections, the problem won't apply

Adrian Dumitrascu.|||Do you know how can we change the protection level to NONE on a deployed OLAP project?

Encrption Level

Does anyone know what encryption level (algorithm, API, strength, etc.) is used when SSAS 2005 encrypts data between a client and the server?

Thanks,
Dave Fackler1. For native connections (when you connect directly to AS2005, no http/IIS) SSPI is used for authentication, signatures and encryption and these 2 connection string properties can be used:

Protection Level =
NONE (no authentication, no signatures, no encryption)
CONNECT (authentication, clear text without signatures)
PKT INTEGRITY (authentication, clear text with signatures - for replay and data tempering protection)
PKT PRIVACY (authentication, encryption, signatures included)

SSPI = the name of the SSPI package to be used, for example 'Kerberos' or 'NTLM' (default is 'Negociate')

2. For http connections, you can use https

3. For local cubes connections, the problem won't apply

Adrian Dumitrascu.|||Do you know how can we change the protection level to NONE on a deployed OLAP project?

Encoding errors

Somewhat complex:
I'm getting the following error in a sp (SQL Server 2000):
"Server: Msg 6603, Level 16, State 1, Procedure sp_xml_preparedocument, Line
8
XML parsing error: Switch from current encoding to specified encoding not
supported."
When a ntext xml string has the encoding set to "utf-8", but not utf-16. So
it would seem
obvious that the document stored in the database is in utf-16...?
However, when the data is written to the database, the XmlDocument class in
..NET (1.1)
is convinced the document is utf-8 (looking in the VS debugger). The call to
the sp in
C# uses:
parameter = command.Parameters.Add("@.Body", SqlDbType.NText);
parameter.Direction = ParameterDirection.Input;
parameter.Value = xd.OuterXml;
where xd is the XmlDocument. I can only conclude that somewhere the xml is
being converted
into a .NET string (and hence utf-16), I would guess at .OuterXml. But I
can't see a way
round this. At some point I need to pass the parameter value!
Any help would be appreciated.
Rgds
Peter Johnston
The problem here is that both UTF-16 and UTF-8 are encodings for UCS-4
Unicode characters but they are quite different beasts at the byte level.
SQL Server's ntext type is for historical reasons supporting UCS-2 Unicode
and for our XML parser thus should only be used to contain UCS-2 or UTF-16
encoded XML (UTF-16 uses two 2-byte code points, the so called surrogate
pairs, to represent the Unicode characters that go beyond UCS-2).
UTF-8 is a variable-length multi-byte encoding (1 to 4 bytes) of UCS-4 and
thus conflicts with the two-byte representation of ntext. The server-side
XML parser does not allow switching to UTF-8 while it parses ntext
characters since it could lead to data corruption.
Unfortunately, SQL Server does not really support a UFT-8 code page for
text/varchar either. I think that the windows-1256 encoding is mostly UTF-8
code point safe though (meaning, it does not change the code points to ?).
If you need to load data in SQL Server 2000 that contains UTF-8 encoded
data, you have the following options:
1. Change the encoding of the document to UTF-16 before passing it to the
server as ntext parameter (both the native and managed client XML libraries
have mechanisms to set the encoding)
2. If you know that you can just drop the encoding indicator, since you are
only loading ASCII anyway, do so. But be careful - even some 127-255 range
characters can get corrupted this way.
3. Load the data with the UTF-8 encoding into a text that has a collation
that implies Windows-1256.
In SQL Server 2005, we have added the ability to load the data into the XML
datatype either as XML or as varbinary() in which cases UTF-8 will work
without problems.
Best regards
Michael
"Peter Johnston" <nospam@.nospam.com> wrote in message
news:usP7DnCwFHA.2076@.TK2MSFTNGP14.phx.gbl...
> Somewhat complex:
> I'm getting the following error in a sp (SQL Server 2000):
> "Server: Msg 6603, Level 16, State 1, Procedure sp_xml_preparedocument,
> Line 8
> XML parsing error: Switch from current encoding to specified encoding not
> supported."
> When a ntext xml string has the encoding set to "utf-8", but not utf-16.
> So it would seem
> obvious that the document stored in the database is in utf-16...?
> However, when the data is written to the database, the XmlDocument class
> in .NET (1.1)
> is convinced the document is utf-8 (looking in the VS debugger). The call
> to the sp in
> C# uses:
> parameter = command.Parameters.Add("@.Body", SqlDbType.NText);
> parameter.Direction = ParameterDirection.Input;
> parameter.Value = xd.OuterXml;
> where xd is the XmlDocument. I can only conclude that somewhere the xml is
> being converted
> into a .NET string (and hence utf-16), I would guess at .OuterXml. But I
> can't see a way
> round this. At some point I need to pass the parameter value!
> Any help would be appreciated.
> Rgds
> Peter Johnston
>

Encoding errors

Somewhat complex:
I'm getting the following error in a sp (SQL Server 2000):
"Server: Msg 6603, Level 16, State 1, Procedure sp_xml_preparedocument, Line
8
XML parsing error: Switch from current encoding to specified encoding not
supported."
When a ntext xml string has the encoding set to "utf-8", but not utf-16. So
it would seem
obvious that the document stored in the database is in utf-16...?
However, when the data is written to the database, the XmlDocument class in
.NET (1.1)
is convinced the document is utf-8 (looking in the VS debugger). The call to
the sp in
C# uses:
parameter = command.Parameters.Add("@.Body", SqlDbType.NText);
parameter.Direction = ParameterDirection.Input;
parameter.Value = xd.OuterXml;
where xd is the XmlDocument. I can only conclude that somewhere the xml is
being converted
into a .NET string (and hence utf-16), I would guess at .OuterXml. But I
can't see a way
round this. At some point I need to pass the parameter value!
Any help would be appreciated.
Rgds
Peter JohnstonThe problem here is that both UTF-16 and UTF-8 are encodings for UCS-4
Unicode characters but they are quite different beasts at the byte level.
SQL Server's ntext type is for historical reasons supporting UCS-2 Unicode
and for our XML parser thus should only be used to contain UCS-2 or UTF-16
encoded XML (UTF-16 uses two 2-byte code points, the so called surrogate
pairs, to represent the Unicode characters that go beyond UCS-2).
UTF-8 is a variable-length multi-byte encoding (1 to 4 bytes) of UCS-4 and
thus conflicts with the two-byte representation of ntext. The server-side
XML parser does not allow switching to UTF-8 while it parses ntext
characters since it could lead to data corruption.
Unfortunately, SQL Server does not really support a UFT-8 code page for
text/varchar either. I think that the windows-1256 encoding is mostly UTF-8
code point safe though (meaning, it does not change the code points to ?).
If you need to load data in SQL Server 2000 that contains UTF-8 encoded
data, you have the following options:
1. Change the encoding of the document to UTF-16 before passing it to the
server as ntext parameter (both the native and managed client XML libraries
have mechanisms to set the encoding)
2. If you know that you can just drop the encoding indicator, since you are
only loading ASCII anyway, do so. But be careful - even some 127-255 range
characters can get corrupted this way.
3. Load the data with the UTF-8 encoding into a text that has a collation
that implies Windows-1256.
In SQL Server 2005, we have added the ability to load the data into the XML
datatype either as XML or as varbinary() in which cases UTF-8 will work
without problems.
Best regards
Michael
"Peter Johnston" <nospam@.nospam.com> wrote in message
news:usP7DnCwFHA.2076@.TK2MSFTNGP14.phx.gbl...
> Somewhat complex:
> I'm getting the following error in a sp (SQL Server 2000):
> "Server: Msg 6603, Level 16, State 1, Procedure sp_xml_preparedocument,
> Line 8
> XML parsing error: Switch from current encoding to specified encoding not
> supported."
> When a ntext xml string has the encoding set to "utf-8", but not utf-16.
> So it would seem
> obvious that the document stored in the database is in utf-16...?
> However, when the data is written to the database, the XmlDocument class
> in .NET (1.1)
> is convinced the document is utf-8 (looking in the VS debugger). The call
> to the sp in
> C# uses:
> parameter = command.Parameters.Add("@.Body", SqlDbType.NText);
> parameter.Direction = ParameterDirection.Input;
> parameter.Value = xd.OuterXml;
> where xd is the XmlDocument. I can only conclude that somewhere the xml is
> being converted
> into a .NET string (and hence utf-16), I would guess at .OuterXml. But I
> can't see a way
> round this. At some point I need to pass the parameter value!
> Any help would be appreciated.
> Rgds
> Peter Johnston
>

Enabling "not for replication" contraint on a mass level

HI,
sql server 2000,uni directional transaction replication with initial
snapshot . Can not be simpler than this.
My database has around 100 tables and ever time i setup replication, i have
to make sure that none of the referential integrity constraints are copied
over to the subscriber because they are not set for "not for replication".
And if i want to set it up , i might have to go to each and every table and
specify this contraint. My questions are
1. is there any way i can have all the referential integrity contraints on
the subscriber and still not have "not for replication" checked?
2. if the answer is NO , then is there any way , any script i could use to
mass update all the PKs\ FKs with "Not For Replication" constraint?
Thanks
Muzammil
AFAIK - there is no way of doing this - but why do you want to enforce DRI
on the subscriber? Normally the subscriber is read only.
Hilary Cotter
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
"sameer" <sameer@.discussions.microsoft.com> wrote in message
news:34ACBAE1-9F82-46CB-B844-B5B68F2B4798@.microsoft.com...
> HI,
> sql server 2000,uni directional transaction replication with initial
> snapshot . Can not be simpler than this.
> My database has around 100 tables and ever time i setup replication, i
have
> to make sure that none of the referential integrity constraints are copied
> over to the subscriber because they are not set for "not for replication".
> And if i want to set it up , i might have to go to each and every table
and
> specify this contraint. My questions are
> 1. is there any way i can have all the referential integrity contraints on
> the subscriber and still not have "not for replication" checked?
> 2. if the answer is NO , then is there any way , any script i could use to
> mass update all the PKs\ FKs with "Not For Replication" constraint?
> Thanks
> Muzammil
|||Hilary, thanks for you response.
Yes even though the subscriber is read only , but the client just can not
accept that the database does not have any referencial integrity contraints.
I still can not beleive that there is no way i could write down a script to
get every table from Sysobjects , find the referential integrity contraints
and append the "not for replication" contraints on them. Please suggest.
Thanks
Muzammil
"Hilary Cotter" wrote:

> AFAIK - there is no way of doing this - but why do you want to enforce DRI
> on the subscriber? Normally the subscriber is read only.
> --
> Hilary Cotter
> 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
> "sameer" <sameer@.discussions.microsoft.com> wrote in message
> news:34ACBAE1-9F82-46CB-B844-B5B68F2B4798@.microsoft.com...
> have
> and
>
>

Enable the CLR at database level only

Hi,

Is there a way to allow specific databases access to the CLR. Currently, my understanding is that when this setting is enabled, it applies to all databases within the instance.

Kind regards,

Jan.

CLR is enabled by instance, you could sepearate the database by instances whereas one would allow, the other one would t allow the CLR.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Empty table check!

Hi,

Is there any way i can check at report level or from a container object if a given table is empty?

Thank you all..

Please see this thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=562956&SiteID=1

If you want to check whether or not a table is empty, use the RowNumber function.

For example, you can set Hidden = Iif(RowNumber("DataSetName") = 0, True, False)

Empty DataSet Problem

I am having problems with a report that has subreports nested 2 deep. If
the query for top level subreport returns an empty data set, a blank page
with the message "An internal error occurred on the report server. See the
error log for more details. (rsInternalError)" is displayed.
If the query in the top level subreport contains no rows, I want to hide it
and stop processing the subreport it contains. I have tried setting the
visibility of the table containing the top level subreport based on
CountRows() and have tried using the NoRows property to display a message
instead of the table. Neither of these works.
It seems like CountRows() does not work on empty data sets. In other
similar situations, I have made sure my data set returned at least one empty
row and tested for the data set containing more than one row but it seems
like there should be a better way.
Can someone please tell me how to hide the table and stop processing the
nested subreport so the error message isn't displayed?Hi Tom,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the
internal error when the top level subreport gets empty dataset. If i
misunderstood your concern, please feel free to point it out.
What's the parameter you pass to the nested subreport?
I don't think hide the top level subreport will resolve the issue because
this error is occured when the report is processing.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Tom,
No Rows property works great. Dont toggle using visiblity. Just write the
text on the No Rows property. When it doesn't find the records it displays
the text in the No Row property.
Amarnath
"Tom Bean" wrote:
> I am having problems with a report that has subreports nested 2 deep. If
> the query for top level subreport returns an empty data set, a blank page
> with the message "An internal error occurred on the report server. See the
> error log for more details. (rsInternalError)" is displayed.
> If the query in the top level subreport contains no rows, I want to hide it
> and stop processing the subreport it contains. I have tried setting the
> visibility of the table containing the top level subreport based on
> CountRows() and have tried using the NoRows property to display a message
> instead of the table. Neither of these works.
> It seems like CountRows() does not work on empty data sets. In other
> similar situations, I have made sure my data set returned at least one empty
> row and tested for the data set containing more than one row but it seems
> like there should be a better way.
> Can someone please tell me how to hide the table and stop processing the
> nested subreport so the error message isn't displayed?
>
>|||Wei Lu,
Since the top level subreport returns an empty data set, I have no idea what
is being passed to the nested subreport. I suspect that nothing (not NULL
but nothing) is being passed for the parameters. I removed the nested
subreport from the table and put in an expression to display the value
("Parameter: " + Fields!Id.Value) that would be used for the nested
subreport's parameter and the error message is displayed.
I need to find a way to stop processing the report when the empty data set
is returned by the query in the top level subreport. The top level
subreport cannot be displayed because there is no data for it and the nested
subreport's query cannot be run because there are no parameters to pass to
it. But, nothing I've tried, including the NoRows property, stops the
subreports from processing.
Do you have any suggestions?
Thanks,
Tom
"Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
news:UF49vu$QGHA.940@.TK2MSFTNGXA03.phx.gbl...
> Hi Tom,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the
> internal error when the top level subreport gets empty dataset. If i
> misunderstood your concern, please feel free to point it out.
> What's the parameter you pass to the nested subreport?
> I don't think hide the top level subreport will resolve the issue because
> this error is occured when the report is processing.
>
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Amarnath,
Ever since we started running Reporting Service 2005, the NoRows property
seems to have stop working. I had used it sucessfully before converting to
2005 but it doesn't display anything now.
Have you heard anything about NoRows being broken in RS 2005?
Tom
"Amarnath" <Amarnath@.discussions.microsoft.com> wrote in message
news:A16C5558-32DD-4CF8-A5C4-2B3F1E2913B9@.microsoft.com...
> Hi Tom,
> No Rows property works great. Dont toggle using visiblity. Just write the
> text on the No Rows property. When it doesn't find the records it displays
> the text in the No Row property.
>
> Amarnath
>
> "Tom Bean" wrote:
>> I am having problems with a report that has subreports nested 2 deep. If
>> the query for top level subreport returns an empty data set, a blank page
>> with the message "An internal error occurred on the report server. See
>> the
>> error log for more details. (rsInternalError)" is displayed.
>> If the query in the top level subreport contains no rows, I want to hide
>> it
>> and stop processing the subreport it contains. I have tried setting the
>> visibility of the table containing the top level subreport based on
>> CountRows() and have tried using the NoRows property to display a message
>> instead of the table. Neither of these works.
>> It seems like CountRows() does not work on empty data sets. In other
>> similar situations, I have made sure my data set returned at least one
>> empty
>> row and tested for the data set containing more than one row but it seems
>> like there should be a better way.
>> Can someone please tell me how to hide the table and stop processing the
>> nested subreport so the error message isn't displayed?
>>|||Hi Tom,
Thanks for the update.
From your description, you memtioned that you can use NoRows to resolved
this issue in Reporting Service 2000, but it does not work in SSRS 2005. If
I misunderstood, please feel free to point it out.
Where's the NoRows property you set? For the subreport or the table which
contain the records?
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Wei Lu,
I have tried setting the NoRows property for both the subreport and the
table but neither works. That's what prompted me to ask if NoRows is broken
in RS2005.
The documentation clearly states "When the dataset for a data region returns
no data, the data region is not rendered. Instead, a text box is rendered
that displays the value of the NoRows property." and just as clearly, it
doesn't work for me.
Tom
"Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
news:aYOB$BoRGHA.5524@.TK2MSFTNGXA03.phx.gbl...
> Hi Tom,
> Thanks for the update.
> From your description, you memtioned that you can use NoRows to resolved
> this issue in Reporting Service 2000, but it does not work in SSRS 2005.
> If
> I misunderstood, please feel free to point it out.
> Where's the NoRows property you set? For the subreport or the table which
> contain the records?
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||I am having a similar problem and I think is connected to the re-rendering of
a page containing a sub-report with an empty dataset.
In my case I have a report consisting of a top part using a different
datasource with a (+) for more details. The other part has a table with data
from another datasource. This table also has a subreport that uses a field
for input.
The report works great when the second part has a valid dataset. When the
dataset is empty everything is OK until I press the (+) sign and the report
is re-drawn. Then I get the same error message as you. I tried some other
versions where data is split between different pages, the error immideately
comes if I go to page 2 which re-draws the screen.
I have seen several similar problems on this forum so I belive that it is an
annoying bug for which I can not find a workaround. If anyone can offer help
I would be very happy.
"Tom Bean" wrote:
> Wei Lu,
> I have tried setting the NoRows property for both the subreport and the
> table but neither works. That's what prompted me to ask if NoRows is broken
> in RS2005.
> The documentation clearly states "When the dataset for a data region returns
> no data, the data region is not rendered. Instead, a text box is rendered
> that displays the value of the NoRows property." and just as clearly, it
> doesn't work for me.
> Tom
> "Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
> news:aYOB$BoRGHA.5524@.TK2MSFTNGXA03.phx.gbl...
> > Hi Tom,
> >
> > Thanks for the update.
> >
> > From your description, you memtioned that you can use NoRows to resolved
> > this issue in Reporting Service 2000, but it does not work in SSRS 2005.
> > If
> > I misunderstood, please feel free to point it out.
> >
> > Where's the NoRows property you set? For the subreport or the table which
> > contain the records?
> >
> > Wei Lu
> > Microsoft Online Partner Support
> >
> > Get Secure! - www.microsoft.com/security
> > =====================================================> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> > =====================================================> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
>
>