I know that when you select Multi from the parameter report properties, that it automatically makes "Select All" Available. So how would i take off the "All Value". My users dont want to see All, if Select ALL is available.
How do i exclude from "All" from my report parameter/dataset?
Are you returning "All" from a stored procedure or is it one of your multi value parameter value?The 'user options' configuration option is a bitmask specification. You
need to perform a bitwise OR in order to leave the other options intact.
The script below will turn on the specified option on and retain the other
option settings.
DECLARE
@.run_value int,
@.new_run_value int
CREATE TABLE #UserOptions
(
name varchar(40) NOT NULL,
minimun int,
maximmun int,
config_value int,
run_value int
)
INSERT INTO #UserOptions
EXEC sp_configure 'user options'
SELECT @.new_run_value = run_value | 16384
FROM #UserOptions
EXEC sp_configure 'user options', @.new_run_value
RECONFIGURE WITH OVERRIDE
DROP TABLE #UserOptions
GO
--
Hope this helps.
Dan Guzman
SQL Server MVP
"T.S.Negi" <tilak.negi@.mind-infotech.com> wrote in message
news:a1930058.0402152114.6d399d0c@.posting.google.c om...
> To support remote transaction on SQL Server i have configured user
> options to 16384. However if i make changes in other properties of SQL
> Server, user option setting reverts to its original value. I would
> like to know 1. Is it possible to protect this setting so that change
> in other properties do not effect this setting? 2. What are the
> properties of SQL Server that are linked with user option settings
> (i.e. Changes in those properties cause reverting in user options)?
Hi, I am trying to enable remote access on a SQL Server 2005 standard edition instance. I have enabled it in the properties using the Management studio and have enabled it under Sql Server Surface Area Configuration under "Database engine".
But it didn't work. I know for a fact that my connection string is correct (I tested it on the actual machine)
So I checked everything again and I noticed in the Sql Server Surface Area under "Analysis Services" there is another "remote connection" checkbox to be enabled, however it won't let me enable it there because it says the "Sql Browser" is not started. I checked and the Sql Browser is started.
I'm thinking maybe the problem there is that I have an instance of SQL 2000 running and perhaps it is the sql browser for that (I can remotely connect ot my SQL 2000 instance).
I checked under Computer management -> services and their is no SQL Browser for the instance of SQL 2005. Not even a thing to enable. Just the Default instance SQL Browser, which is for my SQL 2000 instance. Am I missing something here?
Also there is no SQL Browser to enable in the management or Surface Area Configuration programs.
I have also tried to connect using the default port number (1433) and the IP (to bypass the need for the SQL Browser). It apparently finds my Server 2000 instance because it doesn't accept my user name and password and connot find the specific database (note: I verified the username and pswd are correct by testing the values on the SQL machine). How do I find what port number a specific instance of SQL Server is running on?
Hi,the fact that you are using the default instance of SQL Server 2000 on your computer and that you can connect to the SQL Server 2k with the default settings (1433) indicates that SQL Server 2l5 is installed on another port than 1433, because ports can′t be shared. So try to see on which port you installed SQL Server 2k and on therefore on which port it is listening. Then specify the port within your connection string with the following syntax:
MachineName\instanceName,Portnumber
HTH; Jens Suessmeyer.
http://www.sqlserver2005.de
|||
I've tried figuring out what port the SQL 2005 is running on by running a port scan, but nothing really jumped out at me other than the 1433, which the SQL 2000 is running on.
What is a good way to find out what port the SQL 2005 is running on?
|||Hi,
you can have a look at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;823938
The port which SQL Server is listening to can be retrieved via looking in the eventlog or using the statement xp_readerrorlog which shows up something like "SQL Server listening on xxx.xxx.xxx.xxx:PortNumber"
HTH, Jens Suessmeyer.
http//www.sqlserver2005.de
