Display date: 二月 2012

2012年2月25日星期六

Disabling the flat file destination at run-time?

I noticed that The flat file destination that I am using, creates a blank file everytime even if there are no records processed by the data flow.

I just wanted to know if there is any way to stop this. I dont want to see a chunk of blank files on the disk. (I create the files with a timestamp in the file name so every run creates a new file.)

So I want to implement a logic to stop the creation of these blank files in case there are no records to write into it.

Any suggestion would be of great help.

Regards

Saurabh

One option is to use an Execute SQL in the control flow before the data flow to check the record count, and use a condition on a precedence constraint to the data flow to prevent it from running at all.

Another option is to use a Row Count component in the data flow to capture the number of rows written to the flat file. Set a File System task to delete the file after the data flow, with a precedence constraint that uses the row count to determine whether the File System task should execute.

|||

well the first option is not suitable for me because I cannot determine the number of records to be written beforehand.

second option looks good. I'll do that but again that will be having to do one extra task. if at all there is any way to stop the file creation then that will be great. (I am playing around with a script component with no luck)

Thanks for your response John!

Please get back if you find out any other way...

|||

jwelch wrote:

One option is to use an Execute SQL in the control flow before the data flow to check the record count, and use a condition on a precedence constraint to the data flow to prevent it from running at all.

Another option is to use a Row Count component in the data flow to capture the number of rows written to the flat file. Set a File System task to delete the file after the data flow, with a precedence constraint that uses the row count to determine whether the File System task should execute.

Or to adapt a theme, push the data into a raw file or recordset (http://blogs.conchango.com/jamiethomson/archive/2006/06/28/SSIS_3A00_-Comparing-performance-of-a-raw-file-against-a-recordset-destination.aspx) and then use a conditional precedence constraint (as suggested by John) to decide whether to push the data into your flat file or not.

Plenty of ways anyway.

-Jamie

|||

Sounds good! though me too didn't like to push the intermediate data to the disk, the performance analysis shown by Jamie is really helpful in making a decision.

Thanks for the response. I shall go with this solution insead of adding more complications to my short and sweet package!

Regards

Saurabh

disabling the export option

Hi,

As we can disable the toolbar by url access like '&rc:toolbar=false', I would like to know whether there is any way to disable the export control.

The reason for this is, I dont want to show the exporting option in my reports and I want to show the print and other options in the toolbar.

No, that's not possible, using the "rc" parameter.

Ayzan

|||Is there any other way to do this , I'm opening the report through HTML hyperlink.|||

No,

the export functionality can only be disabled within the config file, disabling the rendering extensions. But this can only be done per se, not per user, per permission set etc, only per Reporting Server Instance.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Disabling the AUTOCOMMIT option in MSSQLServer

Hello,

Is there anyway.. we can disable AUTOCOMMIT option in MSSQL server
while executing the SQL queries via SQL ANALYZERbegin transaction|||On 8 Jun 2006 08:01:15 -0700, Uncle Sam wrote:

>Hello,
>Is there anyway.. we can disable AUTOCOMMIT option in MSSQL server
>while executing the SQL queries via SQL ANALYZER

Hi Sam,

In Query Analyzer (for SQL Server 2000): Tools / Options / Connection
Properties / Set implicit_transactions to ON. This affects only new
connections.
Also in Query Analyzer: Query / Current coonnection pproperties / Set
implicit_transactions ON to affect the current connection.

In SQL Server Management Studio (for SQL Server 2005): Tools / Options /
Query Execution / SQL Server / ANSI / SET IMPLICIT_TRANSACTIONS ON (for
new connections), and Query / Query Options / Execution / ANSI / SET
IMPLICIT_TRANSACTIONS ON (for the current connection).

--
Hugo Kornelis, SQL Server MVP

Disabling SQLISPackage start/finish events sent to eventlog

I'm running my SSIS packages from a scheduler (WindowsService) that I wrote in .Net. For the logging of the SSIS events I only use te SSIS Log provider for SQL Server. Nevertheless, the package run start and stop events (and execution failures) are still logged in the Windows Event Log. Is there a way to stop SSIS from writing this event-log entries?

Hi,

i have a scheduled package that runs every one minute and my eventviewer/application is full of these start/finish events.

i would like to see the resolution for this issue.

TIA

Disabling SQLISPackage start/finish events sent to eventlog

Hi,

i have a scheduled package that runs every one minute and my eventviewer/application is full of these start/finish events.

i would like to see the resolution for this issue.

TIA

Disabling SQL jobs using command line

Hi,
Is it possble to disable a SQL using command line?
If so, pls show me how or direct me to somewhere where I can find the
information.
Thanks in advance
Simply stop the service, see the Screencast on my website for more
detailed information.
In summary you just use the NET STOP command.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Sorry did not read the "job" in the subject:
UPDATE sysjobs
SET enabled = 0
WHERE jobId = 'SomeId'
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Or
calling sp_update_job via SQLCMD or OSQL.
(No I think I am done. :-) )
|||Sure. try:
exec msdb..sp_update_job @.job_name = 'yourjobname', @.enabled=0
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Thanks everyboday. It worked great!!
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OmCG5gCUHHA.4668@.TK2MSFTNGP04.phx.gbl...
> Sure. try:
> exec msdb..sp_update_job @.job_name = 'yourjobname', @.enabled=0
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>

Disabling SQL jobs using command line

Hi,
Is it possble to disable a SQL using command line?
If so, pls show me how or direct me to somewhere where I can find the
information.
Thanks in advanceSimply stop the service, see the Screencast on my website for more
detailed information.
In summary you just use the NET STOP command.
HTH, Jens K. Suessmeyer.
--
http://www.sqlserver2005.de
--|||Sorry did not read the "job" in the subject:
UPDATE sysjobs
SET enabled = 0
WHERE jobId = 'SomeId'
HTH, Jens K. Suessmeyer.
--
http://www.sqlserver2005.de
--|||Or
calling sp_update_job via SQLCMD or OSQL.
(No I think I am done. :-) )|||Check out sp_update_job.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"AppleDopod" <hk_007@.hotmail.com> wrote in message news:OgWwQxBUHHA.4832@.TK2MSFTNGP04.phx.gbl...
> Hi,
> Is it possble to disable a SQL using command line?
> If so, pls show me how or direct me to somewhere where I can find the information.
> Thanks in advance
>|||Sure. try:
exec msdb..sp_update_job @.job_name = 'yourjobname', @.enabled=0
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Thanks everyboday. It worked great!!
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OmCG5gCUHHA.4668@.TK2MSFTNGP04.phx.gbl...
> Sure. try:
> exec msdb..sp_update_job @.job_name = 'yourjobname', @.enabled=0
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>

Disabling SQL jobs using command line

Hi,
Is it possble to disable a SQL using command line?
If so, pls show me how or direct me to somewhere where I can find the
information.
Thanks in advanceSimply stop the service, see the Screencast on my website for more
detailed information.
In summary you just use the NET STOP command.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--|||Sorry did not read the "job" in the subject:
UPDATE sysjobs
SET enabled = 0
WHERE jobId = 'SomeId'
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--|||Check out sp_update_job.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"AppleDopod" <hk_007@.hotmail.com> wrote in message news:OgWwQxBUHHA.4832@.TK2MSFTNGP04.phx.gb
l...
> Hi,
> Is it possble to disable a SQL using command line?
> If so, pls show me how or direct me to somewhere where I can find the info
rmation.
> Thanks in advance
>|||Or
calling sp_update_job via SQLCMD or OSQL.
(No I think I am done. :-) )|||Sure. try:
exec msdb..sp_update_job @.job_name = 'yourjobname', @.enabled=0
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Thanks everyboday. It worked great!!
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OmCG5gCUHHA.4668@.TK2MSFTNGP04.phx.gbl...
> Sure. try:
> exec msdb..sp_update_job @.job_name = 'yourjobname', @.enabled=0
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>

Disabling SQL 2005 Case Sensitive

In SQL 2005 is there a way of disabling the case sensitive option for
database objects and data criteria at the database or server level?Case sensitivity are determined by the collation. When you install SQL Serve
r, you specify a
collation, which:
Acts as default for a new database.
Is the collation for the system databases.
When you create a new database, you either define a collation or don't. If y
ou don't, you inherit
what you selected when you installed. This collation is the default collatio
n for the database.
When you create a table, you can at the column level specify collation. If y
ou don't, you get the
database default collation.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<robin9876@.hotmail.com> wrote in message news:1161686322.061321.14570@.e3g2000cwe.googlegroup
s.com...
> In SQL 2005 is there a way of disabling the case sensitive option for
> database objects and data criteria at the database or server level?
>|||In 2005 is their a way of resetting the server value after it has been
installed?
Tibor Karaszi wrote:[vbcol=seagreen]
> Case sensitivity are determined by the collation. When you install SQL Ser
ver, you specify a
> collation, which:
> Acts as default for a new database.
> Is the collation for the system databases.
> When you create a new database, you either define a collation or don't. If
you don't, you inherit
> what you selected when you installed. This collation is the default collat
ion for the database.
> When you create a table, you can at the column level specify collation. If
you don't, you get the
> database default collation.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> <robin9876@.hotmail.com> wrote in message news:1161686322.061321.14570@.e3g2
000cwe.googlegroups.com...|||You have to rebuild the system database, which mean that all information in
the system databases are
lost. Use setup.exe for this (details in Books Online). Then you have to att
ach or restore all user
databases, and of course detach or backup those first. The user databases wi
ll have the same
collation as before the rebuild.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<robin9876@.hotmail.com> wrote in message news:1161877957.117735.3190@.f16g2000cwb.googlegroup
s.com...
> In 2005 is their a way of resetting the server value after it has been
> installed?
> Tibor Karaszi wrote:
>

Disabling SQL 2005 Case Sensitive

In SQL 2005 is there a way of disabling the case sensitive option for
database objects and data criteria at the database or server level?Case sensitivity are determined by the collation. When you install SQL Server, you specify a
collation, which:
Acts as default for a new database.
Is the collation for the system databases.
When you create a new database, you either define a collation or don't. If you don't, you inherit
what you selected when you installed. This collation is the default collation for the database.
When you create a table, you can at the column level specify collation. If you don't, you get the
database default collation.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<robin9876@.hotmail.com> wrote in message news:1161686322.061321.14570@.e3g2000cwe.googlegroups.com...
> In SQL 2005 is there a way of disabling the case sensitive option for
> database objects and data criteria at the database or server level?
>|||In 2005 is their a way of resetting the server value after it has been
installed?
Tibor Karaszi wrote:
> Case sensitivity are determined by the collation. When you install SQL Server, you specify a
> collation, which:
> Acts as default for a new database.
> Is the collation for the system databases.
> When you create a new database, you either define a collation or don't. If you don't, you inherit
> what you selected when you installed. This collation is the default collation for the database.
> When you create a table, you can at the column level specify collation. If you don't, you get the
> database default collation.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> <robin9876@.hotmail.com> wrote in message news:1161686322.061321.14570@.e3g2000cwe.googlegroups.com...
> > In SQL 2005 is there a way of disabling the case sensitive option for
> > database objects and data criteria at the database or server level?
> >|||You have to rebuild the system database, which mean that all information in the system databases are
lost. Use setup.exe for this (details in Books Online). Then you have to attach or restore all user
databases, and of course detach or backup those first. The user databases will have the same
collation as before the rebuild.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<robin9876@.hotmail.com> wrote in message news:1161877957.117735.3190@.f16g2000cwb.googlegroups.com...
> In 2005 is their a way of resetting the server value after it has been
> installed?
> Tibor Karaszi wrote:
>> Case sensitivity are determined by the collation. When you install SQL Server, you specify a
>> collation, which:
>> Acts as default for a new database.
>> Is the collation for the system databases.
>> When you create a new database, you either define a collation or don't. If you don't, you inherit
>> what you selected when you installed. This collation is the default collation for the database.
>> When you create a table, you can at the column level specify collation. If you don't, you get the
>> database default collation.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> <robin9876@.hotmail.com> wrote in message
>> news:1161686322.061321.14570@.e3g2000cwe.googlegroups.com...
>> > In SQL 2005 is there a way of disabling the case sensitive option for
>> > database objects and data criteria at the database or server level?
>> >
>

disabling security

It is possible to disable security in sql server ?
A user will need to go through the authentication process to
access the server so not from that end. Database objects are
accessed based on the permissions set for users or groups in
that database so not from that end. You can modify security
settings but you can't disable the security checks at the
different levels.
-Sue
..
On Mon, 7 Feb 2005 14:11:38 -0800,
<anonymous@.discussions.microsoft.com> wrote:

>It is possible to disable security in sql server ?
|||Hi
No. It is a intrinsic function of the database and engine.
What issues do you have?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<anonymous@.discussions.microsoft.com> wrote in message
news:01d301c50d61$feb5c000$a601280a@.phx.gbl...
> It is possible to disable security in sql server ?
|||anonymous@.discussions.microsoft.com wrote:
> It is possible to disable security in sql server ?
In what respect? Do you mean not requiring a user log in? No, you need
to log in. Can you provide more information about what you're trying to
accomplish.
David Gugick
Imceda Software
www.imceda.com

disabling security

It is possible to disable security in sql server ?A user will need to go through the authentication process to
access the server so not from that end. Database objects are
accessed based on the permissions set for users or groups in
that database so not from that end. You can modify security
settings but you can't disable the security checks at the
different levels.
-Sue
.
On Mon, 7 Feb 2005 14:11:38 -0800,
<anonymous@.discussions.microsoft.com> wrote:

>It is possible to disable security in sql server ?|||Hi
No. It is a intrinsic function of the database and engine.
What issues do you have?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<anonymous@.discussions.microsoft.com> wrote in message
news:01d301c50d61$feb5c000$a601280a@.phx.gbl...
> It is possible to disable security in sql server ?|||anonymous@.discussions.microsoft.com wrote:
> It is possible to disable security in sql server ?
In what respect? Do you mean not requiring a user log in? No, you need
to log in. Can you provide more information about what you're trying to
accomplish.
David Gugick
Imceda Software
www.imceda.com

disabling security

It is possible to disable security in sql server ?A user will need to go through the authentication process to
access the server so not from that end. Database objects are
accessed based on the permissions set for users or groups in
that database so not from that end. You can modify security
settings but you can't disable the security checks at the
different levels.
-Sue
.
On Mon, 7 Feb 2005 14:11:38 -0800,
<anonymous@.discussions.microsoft.com> wrote:
>It is possible to disable security in sql server ?|||Hi
No. It is a intrinsic function of the database and engine.
What issues do you have?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<anonymous@.discussions.microsoft.com> wrote in message
news:01d301c50d61$feb5c000$a601280a@.phx.gbl...
> It is possible to disable security in sql server ?|||anonymous@.discussions.microsoft.com wrote:
> It is possible to disable security in sql server ?
In what respect? Do you mean not requiring a user log in? No, you need
to log in. Can you provide more information about what you're trying to
accomplish.
--
David Gugick
Imceda Software
www.imceda.com

Disabling report processing

Hi
I have to disable report processing at certain times for some reports. It's
like when you don't have selected a value in a combo parameter. I have a
function that returns true if you can view the report or false if don't.
Any ideas?
AndrésWhen you configure your parameter, ensure you do not allow null.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"afontan" <andres.fontan@.alcuadrado.com> wrote in message
news:%23Itbbo1eEHA.2848@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have to disable report processing at certain times for some reports.
> It's
> like when you don't have selected a value in a combo parameter. I have a
> function that returns true if you can view the report or false if don't.
> Any ideas?
> Andrés
>

Disabling replication problems

Hello,
When I try to remove/disable replication on a particular
server nothing happens. The message box 'Removing
publishing and distribution components ...' comes up and
just hangs from there on. Does anyone know why this is
happening?
Any help would be greatly appreciated!
Thanks in advance
watch what is going on while you try to disable replication using Profiler.
By chance do you have a remote distributor/publisher?
Do you get any error messages?
Try running sp_who2 while you are disabling replication to see if there is
any locking occurring.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mike S." <anonymous@.discussions.microsoft.com> wrote in message
news:26c3101c46371$95c70940$a601280a@.phx.gbl...
> Hello,
> When I try to remove/disable replication on a particular
> server nothing happens. The message box 'Removing
> publishing and distribution components ...' comes up and
> just hangs from there on. Does anyone know why this is
> happening?
> Any help would be greatly appreciated!
> Thanks in advance
|||Hilary,
Can't wait to see this book hit the shelf. You got one buyer here.
"Hilary Cotter" wrote:

> watch what is going on while you try to disable replication using Profiler.
> By chance do you have a remote distributor/publisher?
> Do you get any error messages?
> Try running sp_who2 while you are disabling replication to see if there is
> any locking occurring.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mike S." <anonymous@.discussions.microsoft.com> wrote in message
> news:26c3101c46371$95c70940$a601280a@.phx.gbl...
>
>

Disabling replication on existing databases

Hi,
we are adding new verisons of databases to out SQL Instance. we want to
disable existing databases replication, with out effecting production db
replication process.
i think if u use GUI, SQL Server will disable all the prublications? i am
not sure this is correct or wrong.
please advise me, the scripts which should execute, perform and go smooth.
good luck for endeavors.
Thanks,
John.
It will drop publications and subscriptions.
If I were you, I would script out the publications and subscriptions, (right
click on your publication and select generate sql script to do this).
upgrade your database, and then reapply the scripts.
There is something bothering me about your post though - it sounds like you
are about to do this in a production environment. I would advise you to do
this in a test environment first to see what will happen.
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
"John" <John@.discussions.microsoft.com> wrote in message
news:29AC881F-3837-4BE8-BB9F-AFA8DF6CAB13@.microsoft.com...
> Hi,
> we are adding new verisons of databases to out SQL Instance. we want to
> disable existing databases replication, with out effecting production db
> replication process.
> i think if u use GUI, SQL Server will disable all the prublications? i am
> not sure this is correct or wrong.
> please advise me, the scripts which should execute, perform and go smooth.
> good luck for endeavors.
> Thanks,
> John.

Disabling Repl error (22538)

Posted - 02/01/2007 : 22:35:02

one week ago, for testing purpose, I set up trans repl, trans repl with updateable, snapshot repl using the same instance.

configuration is like this,

publisher and distributor are on the same server, 2 remote subscribers, one is 2000, the other is 2005.

It works OK, today I am trying to disable the replicaiton, clean up the machine. keep getting the errors:

an exception occurred while executing a T-SQL statement or batch
only replicaiton jobs,or job schedules can be added, modified,dropped or viewed through replicaiton SPs
could not update the distribution database subscription table, the subscription status could not be changed.
changed database context to 'master',(MSSQL SERVER error 22538)

Please help

publisher: 2005 Standard SP2 CTP

Try dropping the subscriptions before trying to disable publishing and distribution. If you still have issues cleaning up, try using sp_removedbreplication at the subscriber and publisher. You can get more information on sp_removedbreplication from http://msdn2.microsoft.com/en-us/library/ms188734.aspx

Hope this helps,

Tom

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Tom, thanks,

Could not be able to drop subscriptions, getting the same error.

Trying to use sp_removedbreplication, it works at subscribers side, while does not work at publisher side, getting the error:

Msg 22538, Level 16, State 1, Procedure sp_MSrepl_check_job_access, Line 155

Only replication jobs or job schedules can be added, modified, dropped or viewed through replication stored procedures.

Disabling Referential integrity database-wide on import

Is there a way to disable referential integrity on all destination tables for an import?

Thanks.

No, you have to disable all the related constraints. You can do this by:

1. In Enterprise Manager, see 'Disabling a Foreign Key Constraint with INSERT and UPDATE Statements' topic in SQL2000 Books Online

2. In Query Analyzer, use 'ALTER TABLE' command as:

ALTER TABLEMytableNOCHECK CONSTRAINTFK_MyFKCnt

Disabling Product Feedback on en masse deployment?

Hello.

After installing SQL 2005 Enterprise (MSDN-version), I was greeted with Product Feedback pop-ups on opening SSMS.

I'm all about product feedback (hence why I'm here), but before I deploy a final/non-MSDN version to lots of users, I was wondering
- if this also occurs with the non-MSDN version?
- if there is a way to pre-disable the feedback options?

I assume you're referring to the Watson and SQM messages, which I think is the final screen of the Setup process. This is present in all versions of the product.

One way to disable the pop-up is to do a command line install, specifying an appropriate value for Errorreporting and SQMReporting. Read through template.ini in the Dev folder of the CD/DVD for specifics.

|||

Ok, will research.

Once SSMS is installed, and opened for the first time, two pop-ups appear...

Microsoft SQL Server Customer Feedback Options
O Yes, I am will to participate anonymously...
O No, I don't wish to participate

and

Customer Experience Improvement Program (appears with Visual Studio icon)
O Yes, I am will to participate anonymously...
O No, I would not like to participate

I am also able to regenerate the Feedback pop-ups when I open SSMS using "Run As" and supplying another user's credentials.

|||

I think this is different. Your suggestion may map to the setup-step that says the following:

Error and Usage Report Settings

[] Automatically send Error Reports for SQL Server 2005 to Microsoft or your corporate error reporting server.... (Watson setting?)

[] Automatically send Feature Usage data for SQL Server 2005 to Microsoft.... (SQM setting?)

[Help] [< Back] [Next >] [Cancel]
__

The feedback balloons/pop-ups appear after setup.

|||Ah, you're right. I don't know how to deal with the pop-up you're referring to. I'll ask a couple people but don't know if I'll get an answer...|||

Thanks for any info if possible. I've built the following Registry adjustment, but has been unsuccessful. (SSMS seems to regenerate values on first-time use?)

Windows Registry Editor Version 5.00

[HKEY_USERS\.DEFAULT\Software\Microsoft\Microsoft SQL Server]
[HKEY_USERS\.DEFAULT\Software\Microsoft\Microsoft SQL Server\90]
"CustomerFeedback"=dword:00000000
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server]
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90]
"CustomerFeedback"=dword:00000000
[HKEY_USERS\S-1-5-18\Software\Microsoft\Microsoft SQL Server]
[HKEY_USERS\S-1-5-18\Software\Microsoft\Microsoft SQL Server\90]
"CustomerFeedback"=dword:00000000
[HKEY_USERS\.DEFAULT\Software\Microsoft\VSCommon]
[HKEY_USERS\.DEFAULT\Software\Microsoft\VSCommon\8.0]
[HKEY_USERS\.DEFAULT\Software\Microsoft\VSCommon\8.0\SQM]
@.="0"
[HKEY_CURRENT_USER\Software\Microsoft\VSCommon]
[HKEY_CURRENT_USER\Software\Microsoft\VSCommon\8.0]
[HKEY_CURRENT_USER\Software\Microsoft\VSCommon\8.0\SQM]
@.="0"
[HKEY_USERS\S-1-5-18\Software\Microsoft\VSCommon]
[HKEY_USERS\S-1-5-18\Software\Microsoft\VSCommon\8.0]
[HKEY_USERS\S-1-5-18\Software\Microsoft\VSCommon\8.0\SQM]
@.="0"

I also take your response as verifying this behavior is the same on the final, non-MSDN release?

|||

Rather than speculate further, I'm just moving this thread to the Tools forum, where Management Studio experts can help you out.

Paul

Disabling print and export options

Hi,

Obviusly RS wasn't created for this, but i have to ask.

It's posible disable print and export buttons for specific reports?
For example, reports in a specific directory.

Thanks.

Hi Dark_V

It is possible to hide the Toolbar. You can use the following as your url

The following example hides the HTML Viewer toolbar by setting therc:Toolbar parameter value tofalse:

http://servername/reportserver?/ReportName&rs:Command=Render&rs:Format=HTML4.0&rc:Toolbar=false

|||

l0n3i200n wrote:
Hi Dark_V
It is possible to hide the Toolbar. You can use the following as your url
The following example hides the HTML Viewer toolbar by setting therc:Toolbar parameter value tofalse:
http://servername/reportserver?/ReportName&rs:Command=Render&rs:Format=HTML4.0&rc:Toolbar=false

Although, this is the best option I can think of, I just want to pointout that the user can remove the toolbar=false part to still access thetoolbar. I don't think there's any capability to keep the user fromprinting because they can still just print the page from the browser'smenu.

Disabling print and export options

Hi,

Obviusly RS wasn't created for this, but i have to ask.

It's posible disable print and export buttons for specific reports?
For example, reports in a specific directory.

Thanks.

This is not possible using the default viewer. You can hide or disable them entirely but having this logic would require you building your own viewer.

|||

Thanks,

I can't find any component or viewer code with this features.

Someone find something with this functions?

Thanks

Disabling primary key

Hi
i have a table with primary key defined on col1 and col2. now i want to
have col3 also included in primary key. when i alter the table it gives
me error for duplicate rows. there is an option for 'with nocheck' but
it only works with check or foreign key constraint. is there any option
in sql server like in oracle 'no validate' which doesnt validate the
existing data and force the data validation from new records.
thanx
Farid

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!"Ghulam Farid" <gfaryd@.yahoo.com> wrote in message
news:40b49d58$0$209$75868355@.news.frii.net...
>
> Hi
> i have a table with primary key defined on col1 and col2. now i want to
> have col3 also included in primary key. when i alter the table it gives
> me error for duplicate rows. there is an option for 'with nocheck' but
> it only works with check or foreign key constraint. is there any option
> in sql server like in oracle 'no validate' which doesnt validate the
> existing data and force the data validation from new records.
> thanx
> Farid
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

No - CHECK/NOCHECK is for foreign keys and check constraints only. I'm not
entirely sure I understand your post - are you saying that you want to allow
duplicate values in a primary key? If so, then it's not possible, and
shouldn't be. Perhaps if you can post some more details (the table DDL and
sample data), someone may be able to suggest an alternative approach.

Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message
news:40b4d73d_1@.news.bluewin.ch...
> "Ghulam Farid" <gfaryd@.yahoo.com> wrote in message
> news:40b49d58$0$209$75868355@.news.frii.net...
> > Hi
> > i have a table with primary key defined on col1 and col2. now i want to
> > have col3 also included in primary key. when i alter the table it gives
> > me error for duplicate rows. there is an option for 'with nocheck' but
> > it only works with check or foreign key constraint. is there any option
> > in sql server like in oracle 'no validate' which doesnt validate the
> > existing data and force the data validation from new records.
> > thanx
> > Farid
> > *** Sent via Developersdex http://www.developersdex.com ***
> > Don't just participate in USENET...get rewarded for it!
> No - CHECK/NOCHECK is for foreign keys and check constraints only. I'm not
> entirely sure I understand your post - are you saying that you want to
allow
> duplicate values in a primary key? If so, then it's not possible, and
> shouldn't be. Perhaps if you can post some more details (the table DDL and
> sample data), someone may be able to suggest an alternative approach.

I think he wants: SET IDENTITY_INSERT.

> Simon|||>> I have a table with primary key defined on col1 and col2. Now I
want to
have col3 also included in primary key. When I alter the table it
gives me error for duplicate rows. <<

That does not make sense to me. Given this

CREATE TABLE Foobar
(col1 INTEGER NOT NULL,
col2 INTEGER NOT NULL,
col3 INTEGER NOT NULL,
PRIMARY KEY (col1, col2),
..);

Then a superkey is still unique:

CREATE TABLE Foobar
(col1 INTEGER NOT NULL,
col2 INTEGER NOT NULL,
col3 INTEGER NOT NULL,
PRIMARY KEY (col1, col2, col3),
..);|||i think u people didn't understand the problem.
i have created table
create table test(col1 int, col2 int, col3 int,col4...)
Primary key(col1,col2)
as there is primary key on col1 and col2 no duolicate data can exist in
them now the scenario changed i have to change the primary key on the
table. now when i alter the table
alter table test primary key (col1, col3, col4) it gives me error
duplicate rows exist.
but in my scenario i want the existing duplication to remain in the
table. and the primary key enforcement starts from new data.
in oracle there is an option of 'no validate' which doesnt check the
existing data in the table but enforce the uniqueness of data from new
records. i want to know is there any option available in sql server
which doesnt check the existing data but enforces the uniqueness of
records from new records.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||Ghulam Farid <gfaryd@.yahoo.com> wrote in message news:<40b57e55$0$207$75868355@.news.frii.net>...
> i think u people didn't understand the problem.
> i have created table
> create table test(col1 int, col2 int, col3 int,col4...)
> Primary key(col1,col2)
> as there is primary key on col1 and col2 no duolicate data can exist in
> them now the scenario changed i have to change the primary key on the
> table. now when i alter the table
> alter table test primary key (col1, col3, col4) it gives me error
> duplicate rows exist.
> but in my scenario i want the existing duplication to remain in the
> table. and the primary key enforcement starts from new data.
> in oracle there is an option of 'no validate' which doesnt check the
> existing data in the table but enforce the uniqueness of data from new
> records. i want to know is there any option available in sql server
> which doesnt check the existing data but enforces the uniqueness of
> records from new records.
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

It sounds like you want to place a primary key on columns which
contain duplicates, but you want to ignore those duplicates and only
enforce the primary key for new values? If so, then it's not possible
- all values in a primary key must always be unique, otherwise it
couldn't be a primary key.

Simon

create table dbo.Test (
col1 int not null,
col2 int not null,
col3 int not null,
col4 int not null,
constraint PK_Test primary key (col1, col2)
)
go

insert into dbo.Test
select 1,1,1,1
union all
select 1,2,1,1
union all
select 3,1,1,1
go

alter table dbo.Test
drop constraint PK_Test

-- This will always fail because of duplicate data
alter table dbo.Test
add constraint PK_Test primary key (col1, col3, col4)
go

drop table dbo.Test
go

Disabling or Getting Rid of Foreign Keys So I Can Drop My Table

Kinda new to SQL, using SQL Server 2005.

I have some foreign keys in a couple of tables. I need to drop these
tables, but can't since I'll get the error:

Msg 3726,

Level 16, State 1, Line 1
Could not drop object 'Client' because it is referenced by a FOREIGN
KEY constraint.

I'm not sure how to disable or get rid of these foreign keys so that I
can drop my tables. I tried:

ALTER TABLE Client NOCHECK CONSTRAINT ALL

Alter Table Client Drop Column Foreign Key Boss_ID;

I went into the Object Explorer and deleted the FK lines from each
table, but still the same error.

What am I doing wrong?

Thanks for your help.apax999@.gmail.com (apax999@.gmail.com) writes:

Quote:

Originally Posted by

Kinda new to SQL, using SQL Server 2005.
>
I have some foreign keys in a couple of tables. I need to drop these
tables, but can't since I'll get the error:
>
Msg 3726,
>
Level 16, State 1, Line 1
Could not drop object 'Client' because it is referenced by a FOREIGN
KEY constraint.
>
I'm not sure how to disable or get rid of these foreign keys so that I
can drop my tables. I tried:
>
ALTER TABLE Client NOCHECK CONSTRAINT ALL
>
Alter Table Client Drop Column Foreign Key Boss_ID;
>
I went into the Object Explorer and deleted the FK lines from each
table, but still the same error.

You need to drop the foreign keys from the tables that references
Client, not the FKs of Client itself. Say there is an Orders table
with a column ClientID. Then you need to drop that FK constraint.
Then again, this would mean that the client ids in Orders would
be hanging in thin air. Of course, if you create the table, and
repopulate, it may be OK. But don't forget to reapply the foreign
keys you dropped.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Disabling One Input Parameter...?

Hi All,
I am creating a report which calls for four input parameters A, B, C, and D.
How can I disable D if A, B, and C are selected or disable C if A, B, and D
are selected?
Thx, ChuckThis is not supported. The only way to achieve this right now is to
implement your own front end application which handles the parameter UI and
then e.g. uses SOAP or URL-access to pass the "validated" parameters to the
report server.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chuck" <Chuck@.discussions.microsoft.com> wrote in message
news:32F07069-7C11-4608-9E86-68796ED25A99@.microsoft.com...
> Hi All,
> I am creating a report which calls for four input parameters A, B, C, and
> D.
> How can I disable D if A, B, and C are selected or disable C if A, B, and
> D
> are selected?
> Thx, Chuck|||Set a table up in your database called "NILL" with a column called "NILL"
as well. Use the from query section in the report parameters and create a
query which points to this table. Set your Non-queried Default value to
NILL.
Create a dataset for each report parameter. Some duplication, but is quick
and it works. Have done it for database table and columns names where one
or more can be selected and the column info is passed back as a results
alias and is returned independently of the other report parameters.
Eg. DBTableNames
Select Name, Id
From sysobjects where xtype ='U'And ID <> 197555541
Order by Name
DBTablesColNames relys on a tablename to be selected before the report will
allow the selection of a column
Select Name
From syscolumns
Where id = (Select Id
From sysobjects
Where xtype = 'U' AND Name = @.DBName)
** @.DBName = Parameters!TableParameter.Value **
I had to implement custom code in order for this to be of benefit.
Eg. Dataset CustomSQL
= Code.GetSQL(Parameters!TableParameter.Value, Parameters!
ColumnParameter.Value, Parameters!EndDate.Value, Parameters!Interval.Value,
Parameters!NoOfIntervals.Value)
As you can see from the dataset CustomSQL this is one of my so called
"Adhoc Reports" which allows the user to choose a database table and one of
its columns with a given date, an iterval (ie. Daily, Monthly etc), and the
No. of intevals. I have three tables on the report page that each call this
dataset passing in their own report parameters.
Note you have to manually set the name and database feild under "Fields" to
Results to get any data back

Disabling NetBIOS from private/heartbeat NICs after SQL Server installation

In document "Installation order for SQL Server 2000 Enterprise Edition
on Microsoft Cluster Server"
(http://support.microsoft.com/kb/q243218/), as one of the
pre-installation checklist tasks it states "You have disabled NetBIOS
for all private network cards before you start the SQL Server Setup
program."
Here is the thing, our NT Admin. configured the cluster service and
installed SQL Server with the NetBIOS enabled. We know we can change
this setting after the fact but we don't know if there are any
repercussions to doing this? Does anybody have any insight into making
this post-facto installation change?
It shouldn't hurt anything on the heartbeat cable.
dw
Hope it helps
dw
_______________________________
Don Wilwol
donwilwol(DELETE)@.yahoo.com
http://spaces.msn.com/members/wilwol/
"Sean" <spowell71@.hotmail.com> wrote in message
news:1125431374.514801.234000@.g44g2000cwa.googlegr oups.com...
> In document "Installation order for SQL Server 2000 Enterprise Edition
> on Microsoft Cluster Server"
> (http://support.microsoft.com/kb/q243218/), as one of the
> pre-installation checklist tasks it states "You have disabled NetBIOS
> for all private network cards before you start the SQL Server Setup
> program."
> Here is the thing, our NT Admin. configured the cluster service and
> installed SQL Server with the NetBIOS enabled. We know we can change
> this setting after the fact but we don't know if there are any
> repercussions to doing this? Does anybody have any insight into making
> this post-facto installation change?
>
|||For the Private, this is a best practice, it won't hurt a thing!
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
http://msmvps.com/clustering/archive.../20/58233.aspx NYC Clustering
class
"Sean" <spowell71@.hotmail.com> wrote in message
news:1125431374.514801.234000@.g44g2000cwa.googlegr oups.com...
> In document "Installation order for SQL Server 2000 Enterprise Edition
> on Microsoft Cluster Server"
> (http://support.microsoft.com/kb/q243218/), as one of the
> pre-installation checklist tasks it states "You have disabled NetBIOS
> for all private network cards before you start the SQL Server Setup
> program."
> Here is the thing, our NT Admin. configured the cluster service and
> installed SQL Server with the NetBIOS enabled. We know we can change
> this setting after the fact but we don't know if there are any
> repercussions to doing this? Does anybody have any insight into making
> this post-facto installation change?
>
|||Thanks, it worked out great for us. There is a big stability difference
NetBIOS disabled.

Disabling Named Pipes

In the process of doing some routine monitoring/clean-up we've
discovered that several (many?) users are apparently set to access our
SQL Server 2000 database instances via the Named Pipes protocol. In
readings and recommendations we've decided that our WAN would be best
served if we use the less "chatty" TCP/IP.

As such we've also decided to try to enforce this decision to use
TCP/IP exclusively using the domain login script used by all of our
end-users.

Question: does anyone know what registry entries are created/used to
indicate that TCP/IP is enabled and is the default protocol for SQL
Server 2000? Our environment is: XP Pro SP2 and SQL Server 2000
(typically SP3).

TIA
Glenn - newbie DBA(glenn.owens@.gmail.com) writes:
> In the process of doing some routine monitoring/clean-up we've
> discovered that several (many?) users are apparently set to access our
> SQL Server 2000 database instances via the Named Pipes protocol. In
> readings and recommendations we've decided that our WAN would be best
> served if we use the less "chatty" TCP/IP.
> As such we've also decided to try to enforce this decision to use
> TCP/IP exclusively using the domain login script used by all of our
> end-users.
> Question: does anyone know what registry entries are created/used to
> indicate that TCP/IP is enabled and is the default protocol for SQL
> Server 2000? Our environment is: XP Pro SP2 and SQL Server 2000
> (typically SP3).

The brutal variant would be to open the Server Network Utility on
the server box, and disable Named Pipes (server restart needed, as I
recall.)

On the clients it could be a good thing to use the Client Network
Utility to disable Named Pipes, or put it lower in priority than
TCP/IP.

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland, I appreciate the input but we're not looking at wiping out the
use of named pipes all-together (there may be background processes and
legacy applications which use/require the protocol). We're hoping only
to disable Named Pipes for End-Users who login via the default domain.
So, the question still stands...

Erland Sommarskog wrote:
> (glenn.owens@.gmail.com) writes:
> > In the process of doing some routine monitoring/clean-up we've
> > discovered that several (many?) users are apparently set to access
our
> > SQL Server 2000 database instances via the Named Pipes protocol. In
> > readings and recommendations we've decided that our WAN would be
best
> > served if we use the less "chatty" TCP/IP.
> > As such we've also decided to try to enforce this decision to use
> > TCP/IP exclusively using the domain login script used by all of our
> > end-users.
> > Question: does anyone know what registry entries are created/used
to
> > indicate that TCP/IP is enabled and is the default protocol for SQL
> > Server 2000? Our environment is: XP Pro SP2 and SQL Server 2000
> > (typically SP3).
> The brutal variant would be to open the Server Network Utility on
> the server box, and disable Named Pipes (server restart needed, as I
> recall.)
> On the clients it could be a good thing to use the Client Network
> Utility to disable Named Pipes, or put it lower in priority than
> TCP/IP.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||(gowens@.nixonpeabody.com) writes:
> Erland, I appreciate the input but we're not looking at wiping out the
> use of named pipes all-together (there may be background processes and
> legacy applications which use/require the protocol). We're hoping only
> to disable Named Pipes for End-Users who login via the default domain.
> So, the question still stands...
> Question: does anyone know what registry entries are created/used to
> indicate that TCP/IP is enabled and is the default protocol for SQL
> Server 2000? Our environment is: XP Pro SP2 and SQL Server 2000
> (typically SP3).

I'm still not sure what you are asking for. Your question make it
seem like you want to do this on the server level, but this appears
to be impossible, since you want to keep Named Pipes for some clients.

Thus, your only option is to change this at the clients. The supported
way to do this, is to use the Client Network Utility.

If you want to hack the registry yourself, it appeats that the relevant
values and keys are under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\SuperSocketNetLib
The value Protocol Order appears to be the priority order, and should
thus have "tcp" in the beginning. Under the subkey Tcp, there should
be a REG_DWORD value DefaulPort with the value of 0x00000599 (1433.)

I recommend you to play around from the Client Network Utility a little
more, before you start any remote registry hacking or whatever you are
planning to do.

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland, what I'm suggesting is that we do NOT do this at the server
level but rather on a per user basis using our standard login script.

We have several hundred end-users in geographically different
locations. Virtually none of the users have access to, or have
knowledge of, the SQL Client Utility. So, the idea is that when they
logon to their PCs a scriptlet will be run which will disable Named
Pipes and/or insure that TCP/IP is the default protocol.

I was hoping that someone could suggest/provide such a script or
specify the WIN XP registry key/values that define the protocol, etc.

I hope that this clears thing up.

Thanks

Erland Sommarskog wrote:
> (gowens@.nixonpeabody.com) writes:
> > Erland, I appreciate the input but we're not looking at wiping out
the
> > use of named pipes all-together (there may be background processes
and
> > legacy applications which use/require the protocol). We're hoping
only
> > to disable Named Pipes for End-Users who login via the default
domain.
> > So, the question still stands...
> > Question: does anyone know what registry entries are created/used
to
> > indicate that TCP/IP is enabled and is the default protocol for SQL
> > Server 2000? Our environment is: XP Pro SP2 and SQL Server 2000
> > (typically SP3).
> I'm still not sure what you are asking for. Your question make it
> seem like you want to do this on the server level, but this appears
> to be impossible, since you want to keep Named Pipes for some
clients.
> Thus, your only option is to change this at the clients. The
supported
> way to do this, is to use the Client Network Utility.
> If you want to hack the registry yourself, it appeats that the
relevant
> values and keys are under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\SuperSocketNetLib
> The value Protocol Order appears to be the priority order, and should
> thus have "tcp" in the beginning. Under the subkey Tcp, there should
> be a REG_DWORD value DefaulPort with the value of 0x00000599 (1433.)
> I recommend you to play around from the Client Network Utility a
little
> more, before you start any remote registry hacking or whatever you
are
> planning to do.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||(gowens@.nixonpeabody.com) writes:
> I was hoping that someone could suggest/provide such a script or
> specify the WIN XP registry key/values that define the protocol, etc.

My post contained some hints in this direction, and my hope was that
you could work from this suggestion. If you want something ready of
the shelf, I'm afraid that I don't have any thing in store.

A quick search lead me to:
http://msdn.microsoft.com/library/d...dbnetlib_22.asp

There you find some more information about the registrty entries.

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

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

Disabling merge distribution change my table definitions at publisher

I have merge replication between sql 2005 SP1, and when I disable distribution from my publisher, my tables with identity columns change the property "Not for replication" to "NO", does somebody knows if this is a known problem ?

Other information : the compatibilty level for database is 2000.

Do you see a problem with that?

Typically when replication is involved, Not For Replication is needed because when the identity value is tried to insert on the other node, this constraint needs to be skipped. Now with no replication on the machine, it would not matter if this property is ON or OFF.

Disabling Links in Excel, PDF

I am displaying some links using Jump To URL in my Report. I want to Disable
those links when I export the report to Excel or PDF
Does anyone have any clue as how wwe can disable those links when report
gets exported to Excel, PDF.
--
Thanks!
AshishI also need to know how to disable this.
"Ashish" wrote:
> I am displaying some links using Jump To URL in my Report. I want to Disable
> those links when I export the report to Excel or PDF
> Does anyone have any clue as how wwe can disable those links when report
> gets exported to Excel, PDF.
> --
> Thanks!
> Ashish

Disabling JavaScript for report shown in ASP.Net ReportViewer

Hey guys,
I could not figure out a way how to disable rendering using JavaScript when
displaying a report in ReportViewer (ASP.Net). I need to render for browser
with JavaScript disabled. Is there a way to pass those URL parameters to the
report or so? I didn't see where.
Thanks, ChristophYou can do it by using any rendering extentions, but HTML4.0,
but you'd loose all interactive features of the report and report's
pagination.
You'll have to build your own pagination.
"Christoph Wienands" <christoph.wienands@.siemens.remove.com> wrote in
message news:OYPKzrLEGHA.1312@.TK2MSFTNGP09.phx.gbl...
> Hey guys,
> I could not figure out a way how to disable rendering using JavaScript
> when displaying a report in ReportViewer (ASP.Net). I need to render for
> browser with JavaScript disabled. Is there a way to pass those URL
> parameters to the report or so? I didn't see where.
> Thanks, Christoph
>|||Hey Oleg,
> You can do it by using any rendering extentions, but HTML4.0,
> but you'd loose all interactive features of the report and report's
> pagination.
> You'll have to build your own pagination.
Thanks for your help. As far as I know, if I use URL access with something
like this
http://localhost/reportserver?%2fReports%2fMyReport&ReportingPeriod=20054&rs:Command=Render&rs:Format=HTML4.0&rc:Parameters=False&rc:JavaScript=False&rc:Toolbar=True
I get a report with:
1) Toolbar and paging support
2) No parameters showing
3) No JavaScript, it's all plain HTML <-- and that's the feature I need
The ReportViewer control has a couple properties like ShowToolbar or
ShowParameterPrompts where I can control #1 and 2. However, there is no
property for #3.
Anybody any idea?
Thanks, Christoph|||The toolbar is controlled by Javascript, once you set ..&rc:Toolbar=True..
it disables it and no javascript present.
You need to write your own code to simulate paging and a toolbar using the
web service approach.
Not too difficult to do.
"Christoph Wienands" <christoph.wienands@.siemens.remove.com> wrote in
message news:%23b1RozTEGHA.828@.TK2MSFTNGP10.phx.gbl...
> Hey Oleg,
>> You can do it by using any rendering extentions, but HTML4.0,
>> but you'd loose all interactive features of the report and report's
>> pagination.
>> You'll have to build your own pagination.
> Thanks for your help. As far as I know, if I use URL access with something
> like this
> http://localhost/reportserver?%2fReports%2fMyReport&ReportingPeriod=20054&rs:Command=Render&rs:Format=HTML4.0&rc:Parameters=False&rc:JavaScript=False&rc:Toolbar=True
> I get a report with:
> 1) Toolbar and paging support
> 2) No parameters showing
> 3) No JavaScript, it's all plain HTML <-- and that's the feature I need
> The ReportViewer control has a couple properties like ShowToolbar or
> ShowParameterPrompts where I can control #1 and 2. However, there is no
> property for #3.
> Anybody any idea?
> Thanks, Christoph
>|||"Oleg Yevteyev" <myfirstname001atgmaildotcom> wrote in message
news:eFo1cCVEGHA.1424@.TK2MSFTNGP12.phx.gbl...
> The toolbar is controlled by Javascript, once you set ..&rc:Toolbar=True..
> it disables it and no javascript present.
> You need to write your own code to simulate paging and a toolbar using the
> web service approach.
> Not too difficult to do.
Hey Oleg,
now I understand. Thanks for the hint. I didn't realize that JavaScript was
coupled with the toolbar. Since most of our reports are single pages reports
anyway I probably won't even have to do the paging.
Christoph

Disabling Integration with MOSS

I have been able to integrate RS and MOSS without any issues but do not know
how to remove or disable this integration.
I am working on a roll-back plan. Can anyone assist with the process involved?On Dec 18, 9:30 pm, Ravinder <Ravin...@.discussions.microsoft.com>
wrote:
> I have been able to integrate RS and MOSS without any issues but do not know
> how to remove or disable this integration.
> I am working on a roll-back plan. Can anyone assist with the process involved?
This article might be helpful.
http://technet.microsoft.com/en-us/library/ms159697.aspx
Regards,
Enrique Martinez
Sr. Software Consultant

disabling identity with bulk insert

hi,
can identity be disabled with the bulk insert operation.
if so then how is it to be done?
thnks
anu
use WITH KEEPIDENTITY as an option if usign BULK INSERT, -E is using bcp.
--
Mary Bray [SQL Server MVP]
Please only reply to newsgroups
"Anuradha" <Anuradha@.discussions.microsoft.com> wrote in message
news:237F7136-AEE5-440F-8495-BFEB475F477F@.microsoft.com...
> hi,
> can identity be disabled with the bulk insert operation.
> if so then how is it to be done?
> thnks
> anu

disabling identity with bulk insert

hi,
can identity be disabled with the bulk insert operation.
if so then how is it to be done?
thnks
anuuse WITH KEEPIDENTITY as an option if usign BULK INSERT, -E is using bcp.
--
--
Mary Bray [SQL Server MVP]
Please only reply to newsgroups
"Anuradha" <Anuradha@.discussions.microsoft.com> wrote in message
news:237F7136-AEE5-440F-8495-BFEB475F477F@.microsoft.com...
> hi,
> can identity be disabled with the bulk insert operation.
> if so then how is it to be done?
> thnks
> anu

disabling identity with bulk insert

hi,
can identity be disabled with the bulk insert operation.
if so then how is it to be done?
thnks
anuuse WITH KEEPIDENTITY as an option if usign BULK INSERT, -E is using bcp.
--
Mary Bray [SQL Server MVP]
Please only reply to newsgroups
"Anuradha" <Anuradha@.discussions.microsoft.com> wrote in message
news:237F7136-AEE5-440F-8495-BFEB475F477F@.microsoft.com...
> hi,
> can identity be disabled with the bulk insert operation.
> if so then how is it to be done?
> thnks
> anu

Disabling guest account doesn't work as expected (please help!)

Hi all, I want to disable access of the SQL guest account except
master and tempdb. I tried it for one database now, but before I used
this script in query analyzer to check whether the guest account had
access whatsoever:
select has_dbaccess('DatabaseName') as Access,* from sysusers
and it gave me a 1 for the row corresponding to guest:
>1< 2 0 guest 0x00 0x00 2000-08-06 01:27:55.187[...]
now I tried to disable it for the database via:
USE <DatabaseName
GO
EXECUTE sp_revokedbaccess guest
and I got an appropriate message that the account was disabled.
When I queried the sysusers table again as I did in the first
statement, I still get a 1 for has_dbaccess('DatabaseName'), how is
this possible? In addition to this problem I tried to disable it again
for the same database, but now I get "User 'guest' does not exist in
the current database." which is actually that what I expected after
disabling the account, but why does it still show up in sysusers with
access to exactly the database that I disabled its access to!'!?!
Any help greatly appreciated, thank you
TimGuest always exists in sysusers, it's just only enabled when
you add the user. If it's not enabled in the database, the
status is 0 in sysusers.
-Sue
On 6 Apr 2004 09:07:17 -0700, google@.supertimmy.com (Tim
Gorgs) wrote:

>Hi all, I want to disable access of the SQL guest account except
>master and tempdb. I tried it for one database now, but before I used
>this script in query analyzer to check whether the guest account had
>access whatsoever:
>select has_dbaccess('DatabaseName') as Access,* from sysusers
>and it gave me a 1 for the row corresponding to guest:
>now I tried to disable it for the database via:
>USE <DatabaseName
>GO
>EXECUTE sp_revokedbaccess guest
>and I got an appropriate message that the account was disabled.
>When I queried the sysusers table again as I did in the first
>statement, I still get a 1 for has_dbaccess('DatabaseName'), how is
>this possible? In addition to this problem I tried to disable it again
>for the same database, but now I get "User 'guest' does not exist in
>the current database." which is actually that what I expected after
>disabling the account, but why does it still show up in sysusers with
>access to exactly the database that I disabled its access to!'!?!
>Any help greatly appreciated, thank you
>Tim|||> select has_dbaccess('DatabaseName') as Access,* from sysusers
Note that there is no correlation in this query between HAS_DBACCESS and the
sysusers table so HAS_DBACCESS will have the same value for each row
returned. If your login has access to the specified database, it will
return 1 for all rows.
The guest account will always be in the sysusers table but can
enabled/disabled using sp_grantdbaccess/sp_revokedbaccess (or
sp_adduser/sp_dropuser). The guest account is disabled by default in user
databases.
Hope this helps.
Dan Guzman
SQL Server MVP
"Tim Gorgs" <google@.supertimmy.com> wrote in message
news:afa954a3.0404060807.509acc2a@.posting.google.com...
> Hi all, I want to disable access of the SQL guest account except
> master and tempdb. I tried it for one database now, but before I used
> this script in query analyzer to check whether the guest account had
> access whatsoever:
> select has_dbaccess('DatabaseName') as Access,* from sysusers
> and it gave me a 1 for the row corresponding to guest:
> now I tried to disable it for the database via:
> USE <DatabaseName
> GO
> EXECUTE sp_revokedbaccess guest
> and I got an appropriate message that the account was disabled.
> When I queried the sysusers table again as I did in the first
> statement, I still get a 1 for has_dbaccess('DatabaseName'), how is
> this possible? In addition to this problem I tried to disable it again
> for the same database, but now I get "User 'guest' does not exist in
> the current database." which is actually that what I expected after
> disabling the account, but why does it still show up in sysusers with
> access to exactly the database that I disabled its access to!'!?!
> Any help greatly appreciated, thank you
> Tim|||> Guest always exists in sysusers, it's just only enabled when
> you add the user. If it's not enabled in the database, the
> status is 0 in sysusers.
> -Sue
>
Thank you very much, I thought it must be something easy like that,
but somehow the status column in sysusers isn't documented in the
online help ("only for internal purposes") and I couldn't figure out
how to check if the guest user was enabled or not.
Have a nice day
Tim

Disabling guest account doesn't work as expected (please help!)

Hi all, I want to disable access of the SQL guest account except
master and tempdb. I tried it for one database now, but before I used
this script in query analyzer to check whether the guest account had
access whatsoever:
select has_dbaccess('DatabaseName') as Access,* from sysusers
and it gave me a 1 for the row corresponding to guest:
>1<20guest0x000x002000-08-06 01:27:55.187[...]
now I tried to disable it for the database via:
USE <DatabaseName
GO
EXECUTE sp_revokedbaccess guest
and I got an appropriate message that the account was disabled.
When I queried the sysusers table again as I did in the first
statement, I still get a 1 for has_dbaccess('DatabaseName'), how is
this possible? In addition to this problem I tried to disable it again
for the same database, but now I get "User 'guest' does not exist in
the current database." which is actually that what I expected after
disabling the account, but why does it still show up in sysusers with
access to exactly the database that I disabled its access to!?!?!
Any help greatly appreciated, thank you
Tim
> select has_dbaccess('DatabaseName') as Access,* from sysusers
Note that there is no correlation in this query between HAS_DBACCESS and the
sysusers table so HAS_DBACCESS will have the same value for each row
returned. If your login has access to the specified database, it will
return 1 for all rows.
The guest account will always be in the sysusers table but can
enabled/disabled using sp_grantdbaccess/sp_revokedbaccess (or
sp_adduser/sp_dropuser). The guest account is disabled by default in user
databases.
Hope this helps.
Dan Guzman
SQL Server MVP
"Tim Gorgs" <google@.supertimmy.com> wrote in message
news:afa954a3.0404060807.509acc2a@.posting.google.c om...
> Hi all, I want to disable access of the SQL guest account except
> master and tempdb. I tried it for one database now, but before I used
> this script in query analyzer to check whether the guest account had
> access whatsoever:
> select has_dbaccess('DatabaseName') as Access,* from sysusers
> and it gave me a 1 for the row corresponding to guest:
> now I tried to disable it for the database via:
> USE <DatabaseName
> GO
> EXECUTE sp_revokedbaccess guest
> and I got an appropriate message that the account was disabled.
> When I queried the sysusers table again as I did in the first
> statement, I still get a 1 for has_dbaccess('DatabaseName'), how is
> this possible? In addition to this problem I tried to disable it again
> for the same database, but now I get "User 'guest' does not exist in
> the current database." which is actually that what I expected after
> disabling the account, but why does it still show up in sysusers with
> access to exactly the database that I disabled its access to!?!?!
> Any help greatly appreciated, thank you
> Tim
|||> Guest always exists in sysusers, it's just only enabled when
> you add the user. If it's not enabled in the database, the
> status is 0 in sysusers.
> -Sue
>
Thank you very much, I thought it must be something easy like that,
but somehow the status column in sysusers isn't documented in the
online help ("only for internal purposes") and I couldn't figure out
how to check if the guest user was enabled or not.
Have a nice day
Tim

Disabling Foreign Key Constraint in Trigger

Hey,
Can anybody tell me how to disable a Foreign Key contraint from executing
while a Trigger is executing on DELETE event?
Best regards,
BillDRI are checked berofe the AFTER TRIGGERS, so if it is a problem the trigger
will not be fired.
AMB
"AST" wrote:

> Hey,
> Can anybody tell me how to disable a Foreign Key contraint from executing
> while a Trigger is executing on DELETE event?
> Best regards,
> Bill
>
>|||Hey AMB,
The table [HistoryDetails] has a FK on the column HistoryID that is being
used to enforce integrity with the table[History].
I am not sure if you are stating you can't disable the FK or if I have to
modify the context of the Trigger?
Best regards,
Bill
The Trigger is defined as:
/****** Object: Trigger dbo.TRIGGER_CascDeleteOnHistoryDetails Script
Date: 5/24/2002 12:14:53 AM ******/
CREATE TRIGGER [TRIGGER_CascDeleteOnHistoryDetails] ON dbo.History
FOR DELETE
AS
DELETE HistoryDetails FROM deleted, HistoryDetails WHERE deleted.HistoryID =
HistoryDetails.HistoryID
"Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> wrote in message
news:4662B0B5-25C5-4217-84F0-B75E5ECCF604@.microsoft.com...
> DRI are checked berofe the AFTER TRIGGERS, so if it is a problem the
trigger
> will not be fired.
>
> AMB
>
> "AST" wrote:
>
executing|||That will make quite a mess:
1) Disabling a Foreign Key constraint is Data Definition Language, and can
only be executed by the table owner and members of the sy

min fixed server
roles and the db_owner and db_ddladmin database roles, and is not
transferable. So you have to give your users a large number of unnecessary
permissions.
2) Disabling a foreign key works for all connections, not just the current
one. So while you disable it in your trigger, someone else might need it.
What exactly are you trying to achieve? This is definitely not the right
way.
Jacco Schalkwijk
SQL Server MVP
"AST" <no_reply@.please.com> wrote in message
news:O50z0N6EFHA.3672@.TK2MSFTNGP14.phx.gbl...
> Hey,
> Can anybody tell me how to disable a Foreign Key contraint from executing
> while a Trigger is executing on DELETE event?
> Best regards,
> Bill
>|||Hey Jacco,
What I am trying to achieve is the following:
I have 2 tables [History], [HistoryDetails] where the Primary Table
[History] mantains detailed data in the [HistoryDetails] table. The key
relationship is History.HistoryID=> HistoryDetails.HistoryID.
I have place a constraint on the [HistoryDetails] table such that a record
cannot be added unless the HistoryID is existing in the [History] table.
I had also created a trigger to delete all relational records in the
[HistoryDetails] table when the Primary Key record in the [History] table
was deleted.
This is where I run into problems because the execution of the trigger fails
due to the FK Constraint.
Any suggestions would be very welcome?
Best regards,
Bill
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid> wrote
in message news:uEUZEs6EFHA.2700@.TK2MSFTNGP14.phx.gbl...
> That will make quite a mess:
> 1) Disabling a Foreign Key constraint is Data Definition Language, and can
> only be executed by the table owner and members of the sy

min fixed
server
> roles and the db_owner and db_ddladmin database roles, and is not
> transferable. So you have to give your users a large number of unnecessary
> permissions.
> 2) Disabling a foreign key works for all connections, not just the current
> one. So while you disable it in your trigger, someone else might need it.
> What exactly are you trying to achieve? This is definitely not the right
> way.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "AST" <no_reply@.please.com> wrote in message
> news:O50z0N6EFHA.3672@.TK2MSFTNGP14.phx.gbl...
executing
>|||Drop the trigger and use the ON DELETE CASCADE option on the foreign
key constraint.
David Portas
SQL Server MVP
--|||Hey David,
I don't think this is supported in SQL 7 and I have to support both SQL7 and
SQL2000
I tried running the SQL to add this constraint in SQL7 and it fails and
doesn't seem to recognize anthing to do with cascaded deletes?
Best regards,
Bill
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1108507933.414888.306670@.l41g2000cwc.googlegroups.com...
> Drop the trigger and use the ON DELETE CASCADE option on the foreign
> key constraint.
> --
> David Portas
> SQL Server MVP
> --
>|||AST
Well, you have to drop a FK constraint and to allow deletion within a
trigger.
"AST" <no_reply@.please.com> wrote in message
news:emTg1W8EFHA.624@.TK2MSFTNGP09.phx.gbl...
> Hey David,
> I don't think this is supported in SQL 7 and I have to support both SQL7
and
> SQL2000
> I tried running the SQL to add this constraint in SQL7 and it fails and
> doesn't seem to recognize anthing to do with cascaded deletes?
> Best regards,
> Bill
> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
> news:1108507933.414888.306670@.l41g2000cwc.googlegroups.com...
>

Disabling firewall only way to connect, was working

Well, I discovered my once-working web app is failing to connect to SQL Server.
I had the windows Firewall running and working with a non-standard port and
responding to subnet only.
Windows update is configure to auto install. At some point in late December
the machine was rebooted. Coincidentally, after that, the only way to make
the connection work was to completely disable the windows firewall. Not an
option.
Windows 2003 - With latest critical updates from MS
SQL Server 2005 SP1
SQL and IIS are on separate machines.
TCP is the only enabled protocol for SQL
VS.Net 2005, using System.Data.SqlClient
Connection string is: Data Source=nnn.nnn.nnn.nnn,9919;Initial
Catalog=dbname;User Id=yourname;Password=yourpassword
I have tried moving SQL back to PORT 1433, and added sqlsvrer.exe as an
acceptable application, but it did not work.
MS SQL Server Management Studio does not connect with firewall enabled.
I was able to connect our production web application to our development
database. I was not able to connect our development server's version to the
production database. Both production and development have the same firewall
settings and MS updates. So, I am guessing there is something very wrong with
our production SQL?
Not sure if this is related, but I have noticed a 10 or so second lag
between Remote Desktop access initiation and an answer. On our
web servers the answer is near instant. Once in, it works fine. We are on
a very large network.
Any ideas? Am I missing a port?
Nevermind. Fixed.
Removed and recreated firewall setting for SQL. Also, the default gateway
was not the same between machines. These had not been modified in over 6
months.
Seems to work now.
"Devin" wrote:

> Well, I discovered my once-working web app is failing to connect to SQL Server.
> I had the windows Firewall running and working with a non-standard port and
> responding to subnet only.
> Windows update is configure to auto install. At some point in late December
> the machine was rebooted. Coincidentally, after that, the only way to make
> the connection work was to completely disable the windows firewall. Not an
> option.
> Windows 2003 - With latest critical updates from MS
> SQL Server 2005 SP1
> SQL and IIS are on separate machines.
> TCP is the only enabled protocol for SQL
> VS.Net 2005, using System.Data.SqlClient
> Connection string is: Data Source=nnn.nnn.nnn.nnn,9919;Initial
> Catalog=dbname;User Id=yourname;Password=yourpassword
> I have tried moving SQL back to PORT 1433, and added sqlsvrer.exe as an
> acceptable application, but it did not work.
> MS SQL Server Management Studio does not connect with firewall enabled.
> I was able to connect our production web application to our development
> database. I was not able to connect our development server's version to the
> production database. Both production and development have the same firewall
> settings and MS updates. So, I am guessing there is something very wrong with
> our production SQL?
> Not sure if this is related, but I have noticed a 10 or so second lag
> between Remote Desktop access initiation and an answer. On our
> web servers the answer is near instant. Once in, it works fine. We are on
> a very large network.
> Any ideas? Am I missing a port?
>

Disabling firewall only way to connect, was working

Well, I discovered my once-working web app is failing to connect to SQL Serv
er.
I had the windows Firewall running and working with a non-standard port and
responding to subnet only.
Windows update is configure to auto install. At some point in late December
the machine was rebooted. Coincidentally, after that, the only way to make
the connection work was to completely disable the windows firewall. Not an
option.
Windows 2003 - With latest critical updates from MS
SQL Server 2005 SP1
SQL and IIS are on separate machines.
TCP is the only enabled protocol for SQL
VS.Net 2005, using System.Data.SqlClient
Connection string is: Data Source=nnn.nnn.nnn.nnn,9919;Initial
Catalog=dbname;User Id=yourname;Password=yourpassword
I have tried moving SQL back to PORT 1433, and added sqlsvrer.exe as an
acceptable application, but it did not work.
MS SQL Server Management Studio does not connect with firewall enabled.
I was able to connect our production web application to our development
database. I was not able to connect our development server's version to the
production database. Both production and development have the same firewall
settings and MS updates. So, I am guessing there is something very wrong wit
h
our production SQL?
Not sure if this is related, but I have noticed a 10 or so second lag
between Remote Desktop access initiation and an answer. On our
web servers the answer is near instant. Once in, it works fine. We are on
a very large network.
Any ideas? Am I missing a port?Nevermind. Fixed.
Removed and recreated firewall setting for SQL. Also, the default gateway
was not the same between machines. These had not been modified in over 6
months.
Seems to work now.
"Devin" wrote:

> Well, I discovered my once-working web app is failing to connect to SQL Se
rver.
> I had the windows Firewall running and working with a non-standard port an
d
> responding to subnet only.
> Windows update is configure to auto install. At some point in late Decembe
r
> the machine was rebooted. Coincidentally, after that, the only way to make
> the connection work was to completely disable the windows firewall. Not a
n
> option.
> Windows 2003 - With latest critical updates from MS
> SQL Server 2005 SP1
> SQL and IIS are on separate machines.
> TCP is the only enabled protocol for SQL
> VS.Net 2005, using System.Data.SqlClient
> Connection string is: Data Source=nnn.nnn.nnn.nnn,9919;Initial
> Catalog=dbname;User Id=yourname;Password=yourpassword
> I have tried moving SQL back to PORT 1433, and added sqlsvrer.exe as an
> acceptable application, but it did not work.
> MS SQL Server Management Studio does not connect with firewall enabled.
> I was able to connect our production web application to our development
> database. I was not able to connect our development server's version to t
he
> production database. Both production and development have the same firewa
ll
> settings and MS updates. So, I am guessing there is something very wrong w
ith
> our production SQL?
> Not sure if this is related, but I have noticed a 10 or so second lag
> between Remote Desktop access initiation and an answer. On our
> web servers the answer is near instant. Once in, it works fine. We are o
n
> a very large network.
> Any ideas? Am I missing a port?
>

Disabling extended stored procedures for security

Our security team wants us to disable access to (or drop) all of the built-in extended stored procedures in MSDE 2000 as they feel it is a vulnerability. Where can I find out which extended procs are safe to disable or how we can disable them during install time? Or, is the security team being too cautious and we should just tell them to leave these intact?

There are some that are extremely useful (perhaps even necessary) for many routine maintenance tasks.

Perhaps your security department just needs to know that you have access to the stored procedures 'locked' down to only administrative users.

|||

The onyl procedure which is questionable to let it enabled it the xp_cmdshell procedure as it can execute a command shell on the server. But... if noone (or only adminstrators) are granted access to this procedure there should be no security impact for you at all. make just sure that noone create a extended stored procedure which is not shipped by MS.

Code Snippet

SELECT

xproc.name AS [Name],

SCHEMA_NAME(xproc.schema_id)AS [Schema],

CAST(

xproc.is_ms_shipped

ASbit)AS [IsSystemObject],

xproc.create_date AS [CreateDate]

FROM

sys.all_objectsAS xproc

WHERE

(xproc.type='X')and(CAST(

xproc.is_ms_shipped

ASbit)=0)

ORDERBY

[Schema] ASC,[Name] ASC

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks Jens. The security dept wants us to drop xp_cmdshell, not just remove the rights. Our MSDE 2000 database stores app settings and is not involved in heavy transactions or replication, etc. So would dropping this cause any harm? I read in the Microsoft KB article that it could affect some other stored procedures that depend on it, but those SPs appear to support enterprise-level features.

|||

I agree with Jens. I would not remove xp_cmdshell since I find it very useful for automating maintenance tasks.

However, set the permissions so that only the sysadmin role can execute xp_cmdshell. (Unless, of course, the worst imaginable sin has been commited and the application is running under the 'sa' account.)

No one, no group, no other role, except the very small list of SQL Server administrators 'should' be in the sysadmin role -AND the sa account 'should' NOT be used at all, and it should be tightly locked down with a strong password.

Since the SQL Server administrators have access to the server, there is nothing that they could do using xp_cmdshell that they couldn't do at an OS level command prompt.

Completely removing xp_cmdshell is folly. Tightly limiting access through appropriate permissions is a 'best practice'.

But if you MUST remove it, there 'may' be little impact. Only time will tell. And you can always put it back if necessary.

Disabling extended stored procedures for security

There are some that are extremely useful (perhaps even necessary) for many routine maintenance tasks.

Perhaps your security department just needs to know that you have access to the stored procedures 'locked' down to only administrative users.

|||

Code Snippet

SELECT

xproc.name AS [Name],

SCHEMA_NAME(xproc.schema_id) AS [Schema],

CAST(

xproc.is_ms_shipped

AS bit) AS [IsSystemObject],

xproc.create_date AS [CreateDate]

FROM

sys.all_objects AS xproc

WHERE

(xproc.type='X')and(CAST(

xproc.is_ms_shipped

AS bit)=0)

ORDER BY

[Schema] ASC,[Name] ASC

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

I agree with Jens. I would not remove xp_cmdshell since I find it very useful for automating maintenance tasks.

Since the SQL Server administrators have access to the server, there is nothing that they could do using xp_cmdshell that they couldn't do at an OS level command prompt.

Completely removing xp_cmdshell is folly. Tightly limiting access through appropriate permissions is a 'best practice'.

But if you MUST remove it, there 'may' be little impact. Only time will tell. And you can always put it back if necessary.

Disabling Export to Excel Sheets In MS SQL Reports 2005

Hello All,

Can i disable export to Excel sheet in ms sql server 2005 reporting services.

This is due to security reasons as the client doesnt want the reports to be send via mail.

Can someone provide the solution on how to disable export to excel

Thanks

Pritam Shetty

Look at the article here:

http://msdn2.microsoft.com/en-us/library/ms156281.aspx

This will only disable the option in the Report Manager, URL access will be still allowed.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

I'm a little concerned about something...

This is due to security reasons as the client doesnt want the reports to be send via mail.

Disabling export doesn't prevent the reports from being sent email. Someone can still select the text on the page and dump it into an e-mail message from the HTML version, or Save the page As and attach the result to an email.

>L<

|||

Hello Lisa,

Indirectly i will be disabling all the options.

As of the copy paste thing the clients are ok with it.

But They have just asked to disble the export feature.

So i m just going with it as of now

Thanks & Regards

Pritam Shetty

Disabling 'Export to excel' option when record count >5000 in a re

Hi,
I have a report that has two drill downs that drill to about 5000 records
and due to this I am having time out problems while exporting to excel. For
now, we have worked around the timeout problem but what I would like to know
is whether or not there is a way to disable the excel option in the export
drop down list - only when the SQL report generates like more than 5000 rows.
The reason to disable being, the RS/RM is consuming CPU like crazy and its
repurcussions are unbearable.Hi,
The only thing you can do is to disable Excel export server wide. This you
can do in the RSReportServer.config and add Visible="false" to the element of
the Excel export.
Unfortunately it isn't possible to set it per report or even dynamic.
Jan Pieter Posthuma
"Jammer" wrote:
> Hi,
> I have a report that has two drill downs that drill to about 5000 records
> and due to this I am having time out problems while exporting to excel. For
> now, we have worked around the timeout problem but what I would like to know
> is whether or not there is a way to disable the excel option in the export
> drop down list - only when the SQL report generates like more than 5000 rows.
> The reason to disable being, the RS/RM is consuming CPU like crazy and its
> repurcussions are unbearable.|||"Jan Pieter Posthuma" <JanPieterPosthuma@.discussions.microsoft.com> wrote in
message news:B18CDAAB-35F2-4CA6-AC13-EC30640558EA@.microsoft.com...
> Hi,
> The only thing you can do is to disable Excel export server wide. This you
> can do in the RSReportServer.config and add Visible="false" to the element
> of
> the Excel export.
> Unfortunately it isn't possible to set it per report or even dynamic.
>
If you take a short peek into the generated script when you activate the
toolbar, you can create your own 'export' button with or without excel
export very easily (rs:format=EXCEL)
I modified the ReportViewer sample to display a small popup toolbar with:
export the Excel, PDF and Print on it (takes up way less space then the
standard toolbar)
Alfred|||Hey Alfred,
Can you tell me how you achieved creating your own export to excel bar:
Thanks
Balaji
"Smeenk, A.D." wrote:
> "Jan Pieter Posthuma" <JanPieterPosthuma@.discussions.microsoft.com> wrote in
> message news:B18CDAAB-35F2-4CA6-AC13-EC30640558EA@.microsoft.com...
> > Hi,
> >
> > The only thing you can do is to disable Excel export server wide. This you
> > can do in the RSReportServer.config and add Visible="false" to the element
> > of
> > the Excel export.
> >
> > Unfortunately it isn't possible to set it per report or even dynamic.
> >
> If you take a short peek into the generated script when you activate the
> toolbar, you can create your own 'export' button with or without excel
> export very easily (rs:format=EXCEL)
> I modified the ReportViewer sample to display a small popup toolbar with:
> export the Excel, PDF and Print on it (takes up way less space then the
> standard toolbar)
> Alfred
>
>|||"Balaji" <Balaji@.discussions.microsoft.com> wrote in message
news:29713B57-0C78-4AB9-B7BE-8E5234D59809@.microsoft.com...
> Hey Alfred,
> Can you tell me how you achieved creating your own export to excel bar:
>
Like I said, I modifed the ReportViewer sample, its (by default) installed
here:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\Samples\Applications\ReportViewer
I modified the properties and added 'small' to the ToolBar options, and when
selected I generate different code. I add an extra table around the iframe
and use a div to display a popup menu like when you hover over an image in
IE. The 'onclick' of the images activates a new window with the requested
export of the report (actually a re-render of the report I think, I didn't
add the session ID)
Alfred|||Instead of disabling export to Excel you might want to add a link at the top
of the page that says Export Data. Use jump to URL and specify CSV and ASCII
(the CSV export does Unicode and Excel doesn't handle unicode CSV). By
rendering in ASCII CSV Excel comes up automatically and this is very very
fast. I had an Excel export that took 5 minutes and brought the server to
its knees go to 10 seconds.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Smeenk, A.D." <alfreds@.dbs-at-nospam-at-nl> wrote in message
news:uX66yHuVFHA.2196@.TK2MSFTNGP09.phx.gbl...
> "Balaji" <Balaji@.discussions.microsoft.com> wrote in message
> news:29713B57-0C78-4AB9-B7BE-8E5234D59809@.microsoft.com...
>> Hey Alfred,
>> Can you tell me how you achieved creating your own export to excel bar:
> Like I said, I modifed the ReportViewer sample, its (by default) installed
> here:
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\Samples\Applications\ReportViewer
> I modified the properties and added 'small' to the ToolBar options, and
> when selected I generate different code. I add an extra table around the
> iframe and use a div to display a popup menu like when you hover over an
> image in IE. The 'onclick' of the images activates a new window with the
> requested export of the report (actually a re-render of the report I
> think, I didn't add the session ID)
> Alfred
>|||"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23HdntxuVFHA.2664@.TK2MSFTNGP15.phx.gbl...
> Instead of disabling export to Excel you might want to add a link at the
> top of the page that says Export Data. Use jump to URL and specify CSV and
> ASCII (the CSV export does Unicode and Excel doesn't handle unicode CSV).
> By rendering in ASCII CSV Excel comes up automatically and this is very
> very fast. I had an Excel export that took 5 minutes and brought the
> server to its knees go to 10 seconds.
>
That 'export to CSV' should 'officially' be on the right-click menu when you
view a table layout report part, now for some reason that does not function
on all machines... any idea's?
Yes same report, all machines Windows XP SP2, IE 6.
With one person the option re-appeared after a reset of the local intranet
security to default...
Alfred|||No idea about that. Note that the export to CSV you are talking about
exports as Unicode and Excel will bring it all together in a single column.
Bruce L-C
"Smeenk, A.D." <alfreds@.dbs-at-nospam-at-nl> wrote in message
news:OFAlFu4VFHA.1452@.TK2MSFTNGP14.phx.gbl...
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%23HdntxuVFHA.2664@.TK2MSFTNGP15.phx.gbl...
>> Instead of disabling export to Excel you might want to add a link at the
>> top of the page that says Export Data. Use jump to URL and specify CSV
>> and ASCII (the CSV export does Unicode and Excel doesn't handle unicode
>> CSV). By rendering in ASCII CSV Excel comes up automatically and this is
>> very very fast. I had an Excel export that took 5 minutes and brought the
>> server to its knees go to 10 seconds.
> That 'export to CSV' should 'officially' be on the right-click menu when
> you view a table layout report part, now for some reason that does not
> function on all machines... any idea's?
> Yes same report, all machines Windows XP SP2, IE 6.
> With one person the option re-appeared after a reset of the local intranet
> security to default...
> Alfred
>|||Why don't you increase the timeout?
Farahmand
"Jammer" wrote:
> Hi,
> I have a report that has two drill downs that drill to about 5000 records
> and due to this I am having time out problems while exporting to excel. For
> now, we have worked around the timeout problem but what I would like to know
> is whether or not there is a way to disable the excel option in the export
> drop down list - only when the SQL report generates like more than 5000 rows.
> The reason to disable being, the RS/RM is consuming CPU like crazy and its
> repurcussions are unbearable.|||Why don't you increase the timeout?
Farahmand
"Jammer" wrote:
> Hi,
> I have a report that has two drill downs that drill to about 5000 records
> and due to this I am having time out problems while exporting to excel. For
> now, we have worked around the timeout problem but what I would like to know
> is whether or not there is a way to disable the excel option in the export
> drop down list - only when the SQL report generates like more than 5000 rows.
> The reason to disable being, the RS/RM is consuming CPU like crazy and its
> repurcussions are unbearable.

订阅：博文 (Atom)

2012年2月25日星期六

Blog Archive

About Me