Changing the FROM in the email on a subscription

I need to change the email address that appears as the FROM email on reports
that are being delivered via RS2000. I have change the REPLY email and that
is working correctly but I can't seem to find where the FROM email is stored.
Thanks...It is configurable in the rsreportserver.config file on the report
server machine; edit that file and look for the <FROM> tag under the
<RSEmailDPConfiguration> section
Matt A
Steve wrote:
> I need to change the email address that appears as the FROM email on reports
> that are being delivered via RS2000. I have change the REPLY email and that
> is working correctly but I can't seem to find where the FROM email is stored.
> Thanks...|||That did it! Thanks Matt!!!
"Matt" wrote:
> It is configurable in the rsreportserver.config file on the report
> server machine; edit that file and look for the <FROM> tag under the
> <RSEmailDPConfiguration> section
> Matt A
>
> Steve wrote:
> > I need to change the email address that appears as the FROM email on reports
> > that are being delivered via RS2000. I have change the REPLY email and that
> > is working correctly but I can't seem to find where the FROM email is stored.
> > Thanks...
>|||what if I want to have a diffrent from address for each send?
same as you bind the To and the CC? can it be done?
"Steve" wrote:
> That did it! Thanks Matt!!!
> "Matt" wrote:
> > It is configurable in the rsreportserver.config file on the report
> > server machine; edit that file and look for the <FROM> tag under the
> > <RSEmailDPConfiguration> section
> >
> > Matt A
> >
> >
> > Steve wrote:
> > > I need to change the email address that appears as the FROM email on reports
> > > that are being delivered via RS2000. I have change the REPLY email and that
> > > is working correctly but I can't seem to find where the FROM email is stored.
> > > Thanks...
> >
> >

Changing Licensing Model on production server

Hello All,
I have a pre-existing SQL server that appears to have been installed with
the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I need
to change the licensing model on the server to reflect the proper licensing
configuration that is in place.
Is there a way that this can ben done absent of having to reinstall SQL?
Thanks!
Licensing should'nt affect QSL Operation; if you change from CAL to
Processor, just verify that the number of concurrent connections (Server
properties - Connections) arises to 0; eventually reset manually that value.
Passing from Processor to CAL you should set the same value to the right
value.
Remember however that the respect of your licensing option is something the
YOU and Microsoft agreed, and is'nt controlled by some software feature.
To be completely advised about licensing terms i suggest a call to your
Microsoft representative.
Gilberto Zampatti
"DBADave" wrote:

> Hello All,
> I have a pre-existing SQL server that appears to have been installed with
> the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I need
> to change the licensing model on the server to reflect the proper licensing
> configuration that is in place.
> Is there a way that this can ben done absent of having to reinstall SQL?
> Thanks!
|||Thanks Gilberto,
Specifically I need to know how I can change the licensing model from CAL to
Processor within Control Panel, as by default there is no option to switch
between the 2 modes. I understand that outside of reinstalling SQL, there
may be a registry change that is required and am interested to understand
what registry change (or alternate method other then reinstalling) can be
employed.
Thanks,
Dave
"Gilberto Zampatti" wrote:
[vbcol=seagreen]
> Licensing should'nt affect QSL Operation; if you change from CAL to
> Processor, just verify that the number of concurrent connections (Server
> properties - Connections) arises to 0; eventually reset manually that value.
> Passing from Processor to CAL you should set the same value to the right
> value.
> Remember however that the respect of your licensing option is something the
> YOU and Microsoft agreed, and is'nt controlled by some software feature.
> To be completely advised about licensing terms i suggest a call to your
> Microsoft representative.
> Gilberto Zampatti
> "DBADave" wrote:

Changing Licensing Model on production server

Hello All,
I have a pre-existing SQL server that appears to have been installed with
the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I need
to change the licensing model on the server to reflect the proper licensing
configuration that is in place.
Is there a way that this can ben done absent of having to reinstall SQL?
Thanks!Licensing should'nt affect QSL Operation; if you change from CAL to
Processor, just verify that the number of concurrent connections (Server
properties - Connections) arises to 0; eventually reset manually that value.
Passing from Processor to CAL you should set the same value to the right
value.
Remember however that the respect of your licensing option is something the
YOU and Microsoft agreed, and is'nt controlled by some software feature.
To be completely advised about licensing terms i suggest a call to your
Microsoft representative.
Gilberto Zampatti
"DBADave" wrote:
> Hello All,
> I have a pre-existing SQL server that appears to have been installed with
> the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I need
> to change the licensing model on the server to reflect the proper licensing
> configuration that is in place.
> Is there a way that this can ben done absent of having to reinstall SQL?
> Thanks!|||Thanks Gilberto,
Specifically I need to know how I can change the licensing model from CAL to
Processor within Control Panel, as by default there is no option to switch
between the 2 modes. I understand that outside of reinstalling SQL, there
may be a registry change that is required and am interested to understand
what registry change (or alternate method other then reinstalling) can be
employed.
Thanks,
Dave
"Gilberto Zampatti" wrote:
> Licensing should'nt affect QSL Operation; if you change from CAL to
> Processor, just verify that the number of concurrent connections (Server
> properties - Connections) arises to 0; eventually reset manually that value.
> Passing from Processor to CAL you should set the same value to the right
> value.
> Remember however that the respect of your licensing option is something the
> YOU and Microsoft agreed, and is'nt controlled by some software feature.
> To be completely advised about licensing terms i suggest a call to your
> Microsoft representative.
> Gilberto Zampatti
> "DBADave" wrote:
> > Hello All,
> >
> > I have a pre-existing SQL server that appears to have been installed with
> > the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I need
> > to change the licensing model on the server to reflect the proper licensing
> > configuration that is in place.
> >
> > Is there a way that this can ben done absent of having to reinstall SQL?
> >
> > Thanks!

Changing Licensing Model on production server

Hello All,
I have a pre-existing SQL server that appears to have been installed with
the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I nee
d
to change the licensing model on the server to reflect the proper licensing
configuration that is in place.
Is there a way that this can ben done absent of having to reinstall SQL?
Thanks!Licensing should'nt affect QSL Operation; if you change from CAL to
Processor, just verify that the number of concurrent connections (Server
properties - Connections) arises to 0; eventually reset manually that value.
Passing from Processor to CAL you should set the same value to the right
value.
Remember however that the respect of your licensing option is something the
YOU and Microsoft agreed, and is'nt controlled by some software feature.
To be completely advised about licensing terms i suggest a call to your
Microsoft representative.
Gilberto Zampatti
"DBADave" wrote:

> Hello All,
> I have a pre-existing SQL server that appears to have been installed with
> the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I n
eed
> to change the licensing model on the server to reflect the proper licensin
g
> configuration that is in place.
> Is there a way that this can ben done absent of having to reinstall SQL?
> Thanks!|||Thanks Gilberto,
Specifically I need to know how I can change the licensing model from CAL to
Processor within Control Panel, as by default there is no option to switch
between the 2 modes. I understand that outside of reinstalling SQL, there
may be a registry change that is required and am interested to understand
what registry change (or alternate method other then reinstalling) can be
employed.
Thanks,
Dave
"Gilberto Zampatti" wrote:
[vbcol=seagreen]
> Licensing should'nt affect QSL Operation; if you change from CAL to
> Processor, just verify that the number of concurrent connections (Server
> properties - Connections) arises to 0; eventually reset manually that valu
e.
> Passing from Processor to CAL you should set the same value to the right
> value.
> Remember however that the respect of your licensing option is something th
e
> YOU and Microsoft agreed, and is'nt controlled by some software feature.
> To be completely advised about licensing terms i suggest a call to your
> Microsoft representative.
> Gilberto Zampatti
> "DBADave" wrote:
>

Changing IP of SQL virtual server

Check out KB 244980. There appears to be an error near the bottom where it
talks about changing the subnet mask. After step 10, it says "To make sure
that the SQL server IP address is changed, follow these steps:
a. Check the registry on both nodes for the key that is mentioned in step
11."
I cannot find step 11 anywhere on the page, nor can I find any reference to
a registry key.
Does anyone know this key I should check?
Thanks,
RB
I'd guess the registry key it's referring to is
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\/<instancename>/\Cluster
but that's just a guess (that's where the IP address & network name for
the cluster group resources for the virtual server are stored in the
registry).
*mike hodgson*
http://sqlnerd.blogspot.com
RB wrote:

>Check out KB 244980. There appears to be an error near the bottom where it
>talks about changing the subnet mask. After step 10, it says "To make sure
>that the SQL server IP address is changed, follow these steps:
> a. Check the registry on both nodes for the key that is mentioned in step
>11."
>I cannot find step 11 anywhere on the page, nor can I find any reference to
>a registry key.
>Does anyone know this key I should check?
>Thanks,
>

Changing data type

Hi all,

I have to extend the length of a field, which appears in hundred of tables in a database, and maybe involved in constraints/index/primary key. It is difficult for me to drop all the constraints/index/primary key before altering each table one by one....Is there any easier way to drop all constraints and keys (instead of dropping them one by one)? Or any better (faster) way to extend the length of this field?

Thanks for any help here!OK, here's one method:

Script out your entire database. Then use search and replace to modify all instances of the field length (character, I assume?). Then use this script to create a new, corrected database, and use DTS to transfer data from the old database.

I hope you are aware, though, that you may likely render much of your SQL code (procedures, functions, triggers...) obsolete if they reference your field and attempt to assign it or concatenate it to variables that are of insufficient length. You may have quite a debugging job ahead of you. A 3rd party package such as ERWIN might be of assistance.

blindman|||Just generate ALTER TABLE statements:

SELECT 'ALTER TABLE ' + T.Name + ' ALTER COLUMN ' + C.Name + ' nVarChar(<YourNewFieldLength>);'
FROM SysColumns C INNER JOIN
SysObjects T ON T.id = C.id
WHERE T.XType = 'U' AND T.Name <> 'dtproperties' AND
C.Name = < YourColumnName >

You can consider to open a cursor, and to execute your statement dynamically. Alternatively, you can also generate a script.

I didn't check it for constraints, but indices are automatically updated by this statement.