I have a SQL 2000 (SP3) running on a Windows NT 4.0 (SP6) box used in our test environment. The SQL Server was configured to run under the local system account before I got here. In an effort to standardize things, I tried changing the SQL Service account to run under a designated domain user account purpose built for the job. We use this particular account for all of our new-build servers (which are W2K). This domain account is configured to be a "Power User" on the NT 4.0 Server in question.
Soon after changing things over to run under the new account, all the developers complained that they could no longer connect to the server. I could through QA and EM, but none of the developers could.
The developers are using WebLogic and JDBC drivers for the most part. I wasn't aware that the SQL Server service account affected client connectivity. Was I wrong or is there something else at work here?
Thanks,
hmscottDamn...I'm dealing with something similar right now...
The SSSA run things on behalf of the server...
My guess is that they all connect using sa blank (or whatever, connection pooling id and are still connectiong using sql server auth) and now that it's trusted, their connections are wrong...
How do they connect?
Like when you register a server in EM?
I don't think the service account has anything to do with it...
MOO|||Hi Brett,
They're connecting via various user accounts that are application-specific. Unfortunately, I am only beginning to make progress on convincing management to swing to all trusted connections. The developers insist that WebLogic doesn't support the concept of running under a service account.
Anyway, one guy was using sa, others were using different application accounts. I was able to connect successfully using a trusted connection (but then, I'm a Domain Admin, too, so there's no telling for sure.
It's far from an ideal setup; I'm just trying to correct things bit by bit.
Regards,
Hugh|||Hi Brett,
The developers insist that WebLogic doesn't support the concept of running under a service account.
That may be true...we use websphere and we set a connection pooling account that authenticates through sql server...but it's 1 id and many connections
Anyway, one guy was using sa
Hugh
There's always one...
Still no one is using the SSSA to connect...right?|||No, no one is using that account. I'm sure because the pasword is quite complex and other than being documented in a restricted folder for the DBAs, it's not known.
Thanks for your time...
Regards,
hmscott
Showing posts with label box. Show all posts
Showing posts with label box. Show all posts
Thursday, March 29, 2012
Changing the SQL Server Name
I have SQL 2000 std installed on a win2000 box with latest svc packs and box
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thks
Did SQL Server start with an error along the lines of "has beeen tampered
with?"
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
In order to fix the jobs you will have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>
|||Some info here: http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and box
> was originally designated with a development name which SQL also inherited.
> Now the server box name has been changed but the server still indicates the
> old box name.
> What are the implications if I leave as is and how difficult is it to change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan and
> had to be re-defined.
> thks
>
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thks
Did SQL Server start with an error along the lines of "has beeen tampered
with?"
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
In order to fix the jobs you will have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>
|||Some info here: http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and box
> was originally designated with a development name which SQL also inherited.
> Now the server box name has been changed but the server still indicates the
> old box name.
> What are the implications if I leave as is and how difficult is it to change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan and
> had to be re-defined.
> thks
>
Changing the SQL Server Name
I have SQL 2000 std installed on a win2000 box with latest svc packs and box
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thksDid SQL Server start with an error along the lines of "has beeen tampered
with?"
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
In order to fix the jobs you will have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>|||Some info here: http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and bo
x
> was originally designated with a development name which SQL also inherited
.
> Now the server box name has been changed but the server still indicates th
e
> old box name.
> What are the implications if I leave as is and how difficult is it to chan
ge
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan an
d
> had to be re-defined.
> thks
>
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thksDid SQL Server start with an error along the lines of "has beeen tampered
with?"
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
In order to fix the jobs you will have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>|||Some info here: http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and bo
x
> was originally designated with a development name which SQL also inherited
.
> Now the server box name has been changed but the server still indicates th
e
> old box name.
> What are the implications if I leave as is and how difficult is it to chan
ge
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan an
d
> had to be re-defined.
> thks
>
Changing the SQL Server Name
I have SQL 2000 std installed on a win2000 box with latest svc packs and box
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thksDid SQL Server start with an error along the lines of "has beeen tampered
with?"
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
In order to fix the jobs you will have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>|||Some info here: http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and box
> was originally designated with a development name which SQL also inherited.
> Now the server box name has been changed but the server still indicates the
> old box name.
> What are the implications if I leave as is and how difficult is it to change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan and
> had to be re-defined.
> thks
>
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thksDid SQL Server start with an error along the lines of "has beeen tampered
with?"
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
In order to fix the jobs you will have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>|||Some info here: http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and box
> was originally designated with a development name which SQL also inherited.
> Now the server box name has been changed but the server still indicates the
> old box name.
> What are the implications if I leave as is and how difficult is it to change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan and
> had to be re-defined.
> thks
>
Monday, March 19, 2012
Changing SQL authentication method
Have a central SQL box (SQL server 2000 SP3a) which serves
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
Changing SQL authentication method
Have a central SQL box (SQL server 2000 SP3a) which serves
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi chaps
Thanks for the advice - thought as much, I'll give it a
whirl.
Gary|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi chaps
Thanks for the advice - thought as much, I'll give it a
whirl.
Gary|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
Changing SQL authentication method
Have a central SQL box (SQL server 2000 SP3a) which serves
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanks
On Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks
|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks
|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanks
On Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks
|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks
|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
Wednesday, March 7, 2012
Changing Parameter Dropdown Size
I have parameters that are too long to fit into the dropdown box which then
requires horizontal scrolling. How can i change the width of the dropdown
controls?
TIA
DeanOn Jun 25, 9:35 am, "Dean" <deanl...@.hotmail.com.nospam> wrote:
> I have parameters that are too long to fit into the dropdown box which then
> requires horizontal scrolling. How can i change the width of the dropdown
> controls?
> TIA
> Dean
Currently, there is no way to control the width of the drop-down
boxes. Possibly, the next version of SSRS (V2008) will have this
functionality, since this topic has come up a few times in this group.
Sorry that I can not be of greater assistance.
Regards,
Enrique Martinez
Sr. Software Consultant
requires horizontal scrolling. How can i change the width of the dropdown
controls?
TIA
DeanOn Jun 25, 9:35 am, "Dean" <deanl...@.hotmail.com.nospam> wrote:
> I have parameters that are too long to fit into the dropdown box which then
> requires horizontal scrolling. How can i change the width of the dropdown
> controls?
> TIA
> Dean
Currently, there is no way to control the width of the drop-down
boxes. Possibly, the next version of SSRS (V2008) will have this
functionality, since this topic has come up a few times in this group.
Sorry that I can not be of greater assistance.
Regards,
Enrique Martinez
Sr. Software Consultant
Saturday, February 25, 2012
Changing Name of Host Server Box and MSDE
Please help!
I have changed the name of my Win2KAS Server box and cannot find out how to
get the MSDE MSSQLServer Service to start back up.
MSDE was installed as part of Crystal Enterprise, so I do not have ANY
source CD's to use. I cannot find a "setup.exe" file to re-run either.
Any help would be appreciated.
Thanks in advance...
Hi
What does the NT Event log say? It is a login failure, a Crystal failure etc?
Regards
Mike
"jmr" wrote:
> Please help!
> I have changed the name of my Win2KAS Server box and cannot find out how to
> get the MSDE MSSQLServer Service to start back up.
> MSDE was installed as part of Crystal Enterprise, so I do not have ANY
> source CD's to use. I cannot find a "setup.exe" file to re-run either.
> Any help would be appreciated.
> Thanks in advance...
I have changed the name of my Win2KAS Server box and cannot find out how to
get the MSDE MSSQLServer Service to start back up.
MSDE was installed as part of Crystal Enterprise, so I do not have ANY
source CD's to use. I cannot find a "setup.exe" file to re-run either.
Any help would be appreciated.
Thanks in advance...
Hi
What does the NT Event log say? It is a login failure, a Crystal failure etc?
Regards
Mike
"jmr" wrote:
> Please help!
> I have changed the name of my Win2KAS Server box and cannot find out how to
> get the MSDE MSSQLServer Service to start back up.
> MSDE was installed as part of Crystal Enterprise, so I do not have ANY
> source CD's to use. I cannot find a "setup.exe" file to re-run either.
> Any help would be appreciated.
> Thanks in advance...
Sunday, February 19, 2012
Changing IP
I am using merge replication with SQL ver 7, on a NT4 box. I need to
move one of seven subscribing servers to a new location which means
changing the IP address. I want to do the move without taking down
replication if possible. My plan is to move the box and change to new
IP address. Then update the WINS entry for the new address, and have
replication resume.
Should this work? Let me know if anyone can think of potential
problems.
thanks in advance, Jim
It should work. Replication is sensitive to subscriber name changes, not ip
address changes. Just make sure that you did not hard code an ip address in
the alias you may have created for this server in client network utility.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jim" <ndpace@.att.net> wrote in message
news:c834d859.0409291039.4499a3df@.posting.google.c om...
> I am using merge replication with SQL ver 7, on a NT4 box. I need to
> move one of seven subscribing servers to a new location which means
> changing the IP address. I want to do the move without taking down
> replication if possible. My plan is to move the box and change to new
> IP address. Then update the WINS entry for the new address, and have
> replication resume.
> Should this work? Let me know if anyone can think of potential
> problems.
> thanks in advance, Jim
|||Guys!
I have the similar problem, but the server name will be changed also.
I believe it should be enough to call a kind of system SP, which will
replace old box names to the new ones. Could you point me to the right
direction?
Best regards,
Serge.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uEUCatlpEHA.1816@.TK2MSFTNGP09.phx.gbl...
> It should work. Replication is sensitive to subscriber name changes, not
ip
> address changes. Just make sure that you did not hard code an ip address
in
> the alias you may have created for this server in client network utility.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jim" <ndpace@.att.net> wrote in message
> news:c834d859.0409291039.4499a3df@.posting.google.c om...
>
|||Serge,
Use Master
go
Sp_DropServer 'OldName'
GO
Use Master
go
Sp_Addserver 'NewName', 'local'
GO
Stop and Start SQL Services
This will rename your server, but you'll need to set up
the publications from fresh afterwards.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
move one of seven subscribing servers to a new location which means
changing the IP address. I want to do the move without taking down
replication if possible. My plan is to move the box and change to new
IP address. Then update the WINS entry for the new address, and have
replication resume.
Should this work? Let me know if anyone can think of potential
problems.
thanks in advance, Jim
It should work. Replication is sensitive to subscriber name changes, not ip
address changes. Just make sure that you did not hard code an ip address in
the alias you may have created for this server in client network utility.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jim" <ndpace@.att.net> wrote in message
news:c834d859.0409291039.4499a3df@.posting.google.c om...
> I am using merge replication with SQL ver 7, on a NT4 box. I need to
> move one of seven subscribing servers to a new location which means
> changing the IP address. I want to do the move without taking down
> replication if possible. My plan is to move the box and change to new
> IP address. Then update the WINS entry for the new address, and have
> replication resume.
> Should this work? Let me know if anyone can think of potential
> problems.
> thanks in advance, Jim
|||Guys!
I have the similar problem, but the server name will be changed also.
I believe it should be enough to call a kind of system SP, which will
replace old box names to the new ones. Could you point me to the right
direction?
Best regards,
Serge.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uEUCatlpEHA.1816@.TK2MSFTNGP09.phx.gbl...
> It should work. Replication is sensitive to subscriber name changes, not
ip
> address changes. Just make sure that you did not hard code an ip address
in
> the alias you may have created for this server in client network utility.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jim" <ndpace@.att.net> wrote in message
> news:c834d859.0409291039.4499a3df@.posting.google.c om...
>
|||Serge,
Use Master
go
Sp_DropServer 'OldName'
GO
Use Master
go
Sp_Addserver 'NewName', 'local'
GO
Stop and Start SQL Services
This will rename your server, but you'll need to set up
the publications from fresh afterwards.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Tuesday, February 14, 2012
Changing DB Owner
Inadvertantly I moved several DB's from one SQL box to another however when
I reattached the DB's onte Target server I was logged in as the incorrect
user so the DB Owner shows up as my personal login and not the
Domain\SQLAdmin user which we are supposed to perform maintanence under
(oops). I suspect things worked because my login ID is domain admin. I did
find the command sp_changedbowner however I think it only works with SQL
users and not Windows Domain users. If this is correct could some one
please send/post the exact syntax to change the DB owner from Domain\mylogin
to Domain\SQLAdmin? Thanks!sp_changedbowner ought to work with both Windows and SQL logins. The
specified login must not already be a user in the database. Examples below.
--standard login
USE MyDatabase
EXEC sp_changedbowner 'SQLAdmin'
--Windows login
USE MyDatabase
EXEC sp_changedbowner 'Domain\SQLAdmin'
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike B." <Autobahn97@.hotmail.com> wrote in message
news:e$ytVNFhEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Inadvertantly I moved several DB's from one SQL box to another however
when
> I reattached the DB's onte Target server I was logged in as the incorrect
> user so the DB Owner shows up as my personal login and not the
> Domain\SQLAdmin user which we are supposed to perform maintanence under
> (oops). I suspect things worked because my login ID is domain admin. I
did
> find the command sp_changedbowner however I think it only works with SQL
> users and not Windows Domain users. If this is correct could some one
> please send/post the exact syntax to change the DB owner from
Domain\mylogin
> to Domain\SQLAdmin? Thanks!
>
I reattached the DB's onte Target server I was logged in as the incorrect
user so the DB Owner shows up as my personal login and not the
Domain\SQLAdmin user which we are supposed to perform maintanence under
(oops). I suspect things worked because my login ID is domain admin. I did
find the command sp_changedbowner however I think it only works with SQL
users and not Windows Domain users. If this is correct could some one
please send/post the exact syntax to change the DB owner from Domain\mylogin
to Domain\SQLAdmin? Thanks!sp_changedbowner ought to work with both Windows and SQL logins. The
specified login must not already be a user in the database. Examples below.
--standard login
USE MyDatabase
EXEC sp_changedbowner 'SQLAdmin'
--Windows login
USE MyDatabase
EXEC sp_changedbowner 'Domain\SQLAdmin'
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike B." <Autobahn97@.hotmail.com> wrote in message
news:e$ytVNFhEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Inadvertantly I moved several DB's from one SQL box to another however
when
> I reattached the DB's onte Target server I was logged in as the incorrect
> user so the DB Owner shows up as my personal login and not the
> Domain\SQLAdmin user which we are supposed to perform maintanence under
> (oops). I suspect things worked because my login ID is domain admin. I
did
> find the command sp_changedbowner however I think it only works with SQL
> users and not Windows Domain users. If this is correct could some one
> please send/post the exact syntax to change the DB owner from
Domain\mylogin
> to Domain\SQLAdmin? Thanks!
>
Changing DB Owner
Inadvertantly I moved several DB's from one SQL box to another however when
I reattached the DB's onte Target server I was logged in as the incorrect
user so the DB Owner shows up as my personal login and not the
Domain\SQLAdmin user which we are supposed to perform maintanence under
(oops). I suspect things worked because my login ID is domain admin. I did
find the command sp_changedbowner however I think it only works with SQL
users and not Windows Domain users. If this is correct could some one
please send/post the exact syntax to change the DB owner from Domain\mylogin
to Domain\SQLAdmin? Thanks!
sp_changedbowner ought to work with both Windows and SQL logins. The
specified login must not already be a user in the database. Examples below.
--standard login
USE MyDatabase
EXEC sp_changedbowner 'SQLAdmin'
--Windows login
USE MyDatabase
EXEC sp_changedbowner 'Domain\SQLAdmin'
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike B." <Autobahn97@.hotmail.com> wrote in message
news:e$ytVNFhEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Inadvertantly I moved several DB's from one SQL box to another however
when
> I reattached the DB's onte Target server I was logged in as the incorrect
> user so the DB Owner shows up as my personal login and not the
> Domain\SQLAdmin user which we are supposed to perform maintanence under
> (oops). I suspect things worked because my login ID is domain admin. I
did
> find the command sp_changedbowner however I think it only works with SQL
> users and not Windows Domain users. If this is correct could some one
> please send/post the exact syntax to change the DB owner from
Domain\mylogin
> to Domain\SQLAdmin? Thanks!
>
I reattached the DB's onte Target server I was logged in as the incorrect
user so the DB Owner shows up as my personal login and not the
Domain\SQLAdmin user which we are supposed to perform maintanence under
(oops). I suspect things worked because my login ID is domain admin. I did
find the command sp_changedbowner however I think it only works with SQL
users and not Windows Domain users. If this is correct could some one
please send/post the exact syntax to change the DB owner from Domain\mylogin
to Domain\SQLAdmin? Thanks!
sp_changedbowner ought to work with both Windows and SQL logins. The
specified login must not already be a user in the database. Examples below.
--standard login
USE MyDatabase
EXEC sp_changedbowner 'SQLAdmin'
--Windows login
USE MyDatabase
EXEC sp_changedbowner 'Domain\SQLAdmin'
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike B." <Autobahn97@.hotmail.com> wrote in message
news:e$ytVNFhEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Inadvertantly I moved several DB's from one SQL box to another however
when
> I reattached the DB's onte Target server I was logged in as the incorrect
> user so the DB Owner shows up as my personal login and not the
> Domain\SQLAdmin user which we are supposed to perform maintanence under
> (oops). I suspect things worked because my login ID is domain admin. I
did
> find the command sp_changedbowner however I think it only works with SQL
> users and not Windows Domain users. If this is correct could some one
> please send/post the exact syntax to change the DB owner from
Domain\mylogin
> to Domain\SQLAdmin? Thanks!
>
Sunday, February 12, 2012
Changing DB Owner
Inadvertantly I moved several DB's from one SQL box to another however when
I reattached the DB's onte Target server I was logged in as the incorrect
user so the DB Owner shows up as my personal login and not the
Domain\SQLAdmin user which we are supposed to perform maintanence under
(oops). I suspect things worked because my login ID is domain admin. I did
find the command sp_changedbowner however I think it only works with SQL
users and not Windows Domain users. If this is correct could some one
please send/post the exact syntax to change the DB owner from Domain\mylogin
to Domain\SQLAdmin? Thanks!sp_changedbowner ought to work with both Windows and SQL logins. The
specified login must not already be a user in the database. Examples below.
--standard login
USE MyDatabase
EXEC sp_changedbowner 'SQLAdmin'
--Windows login
USE MyDatabase
EXEC sp_changedbowner 'Domain\SQLAdmin'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike B." <Autobahn97@.hotmail.com> wrote in message
news:e$ytVNFhEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Inadvertantly I moved several DB's from one SQL box to another however
when
> I reattached the DB's onte Target server I was logged in as the incorrect
> user so the DB Owner shows up as my personal login and not the
> Domain\SQLAdmin user which we are supposed to perform maintanence under
> (oops). I suspect things worked because my login ID is domain admin. I
did
> find the command sp_changedbowner however I think it only works with SQL
> users and not Windows Domain users. If this is correct could some one
> please send/post the exact syntax to change the DB owner from
Domain\mylogin
> to Domain\SQLAdmin? Thanks!
>
I reattached the DB's onte Target server I was logged in as the incorrect
user so the DB Owner shows up as my personal login and not the
Domain\SQLAdmin user which we are supposed to perform maintanence under
(oops). I suspect things worked because my login ID is domain admin. I did
find the command sp_changedbowner however I think it only works with SQL
users and not Windows Domain users. If this is correct could some one
please send/post the exact syntax to change the DB owner from Domain\mylogin
to Domain\SQLAdmin? Thanks!sp_changedbowner ought to work with both Windows and SQL logins. The
specified login must not already be a user in the database. Examples below.
--standard login
USE MyDatabase
EXEC sp_changedbowner 'SQLAdmin'
--Windows login
USE MyDatabase
EXEC sp_changedbowner 'Domain\SQLAdmin'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike B." <Autobahn97@.hotmail.com> wrote in message
news:e$ytVNFhEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Inadvertantly I moved several DB's from one SQL box to another however
when
> I reattached the DB's onte Target server I was logged in as the incorrect
> user so the DB Owner shows up as my personal login and not the
> Domain\SQLAdmin user which we are supposed to perform maintanence under
> (oops). I suspect things worked because my login ID is domain admin. I
did
> find the command sp_changedbowner however I think it only works with SQL
> users and not Windows Domain users. If this is correct could some one
> please send/post the exact syntax to change the DB owner from
Domain\mylogin
> to Domain\SQLAdmin? Thanks!
>
Friday, February 10, 2012
Changing control/Property box values
Help!
I'm trying to figure out how to change the values on the properties control
box dynamically. Things such as Hidden, size, font. With the RS format of
<name>!<fieldname>.Value, how are such things called?
Example code (which doesn't work because of compile problems:
=iif(Fields!TableName.Value = Parameters!tblName.Value,
ReportItems!Hidden.Value = "False", ReportItems!Hidden.Value = "True")
The goal is to hide a list box/field. What do I use in place of
ReportItems!Hidden.Value to make this work?
Thanks,
CatadminHi,
I have the same problem as you. I'm trying with custom code, you can see a
description:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RShowto/htm/hrs_designer_v1_1nfp.asp
But only can access the "value", somethig like this:
Function NullData (txt As textbox) As Boolean
If (txt.value = "") Or _
(txt.value) Is Nothing Then
Return False
End If
Return True
End Function
I'm working to change the width property value. If I'm sucess I will post
here.
Maybe you can do something more with this. I hope it can be helpfull.
"Catadmin" wrote:
> Help!
> I'm trying to figure out how to change the values on the properties control
> box dynamically. Things such as Hidden, size, font. With the RS format of
> <name>!<fieldname>.Value, how are such things called?
> Example code (which doesn't work because of compile problems:
> =iif(Fields!TableName.Value = Parameters!tblName.Value,
> ReportItems!Hidden.Value = "False", ReportItems!Hidden.Value = "True")
> The goal is to hide a list box/field. What do I use in place of
> ReportItems!Hidden.Value to make this work?
> Thanks,
> Catadmin
I'm trying to figure out how to change the values on the properties control
box dynamically. Things such as Hidden, size, font. With the RS format of
<name>!<fieldname>.Value, how are such things called?
Example code (which doesn't work because of compile problems:
=iif(Fields!TableName.Value = Parameters!tblName.Value,
ReportItems!Hidden.Value = "False", ReportItems!Hidden.Value = "True")
The goal is to hide a list box/field. What do I use in place of
ReportItems!Hidden.Value to make this work?
Thanks,
CatadminHi,
I have the same problem as you. I'm trying with custom code, you can see a
description:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RShowto/htm/hrs_designer_v1_1nfp.asp
But only can access the "value", somethig like this:
Function NullData (txt As textbox) As Boolean
If (txt.value = "") Or _
(txt.value) Is Nothing Then
Return False
End If
Return True
End Function
I'm working to change the width property value. If I'm sucess I will post
here.
Maybe you can do something more with this. I hope it can be helpfull.
"Catadmin" wrote:
> Help!
> I'm trying to figure out how to change the values on the properties control
> box dynamically. Things such as Hidden, size, font. With the RS format of
> <name>!<fieldname>.Value, how are such things called?
> Example code (which doesn't work because of compile problems:
> =iif(Fields!TableName.Value = Parameters!tblName.Value,
> ReportItems!Hidden.Value = "False", ReportItems!Hidden.Value = "True")
> The goal is to hide a list box/field. What do I use in place of
> ReportItems!Hidden.Value to make this work?
> Thanks,
> Catadmin
Subscribe to:
Posts (Atom)