Change Lincense Key

We currently have a SQL cluster which was built on pirated license keys.
This was a managerial mistake let me point out.~
Can we change the license key to legal copy without re-installing SQL? I
see that they license key is stored in the registry, but it appears that the
Product ID is generated randomly.
Any help is appreciated.Hi
You may want to try the rebuild registry option in the setup program or see
http://tinyurl.com/ad484
John
"Andrew" wrote:
> We currently have a SQL cluster which was built on pirated license keys.
> This was a managerial mistake let me point out.~
> Can we change the license key to legal copy without re-installing SQL? I
> see that they license key is stored in the registry, but it appears that the
> Product ID is generated randomly.
> Any help is appreciated.
>

Change Lincense Key

We currently have a SQL cluster which was built on pirated license keys.
This was a managerial mistake let me point out.~
Can we change the license key to legal copy without re-installing SQL? I
see that they license key is stored in the registry, but it appears that the
Product ID is generated randomly.
Any help is appreciated.
Hi
You may want to try the rebuild registry option in the setup program or see
http://tinyurl.com/ad484
John
"Andrew" wrote:

> We currently have a SQL cluster which was built on pirated license keys.
> This was a managerial mistake let me point out.~
> Can we change the license key to legal copy without re-installing SQL? I
> see that they license key is stored in the registry, but it appears that the
> Product ID is generated randomly.
> Any help is appreciated.
>

Change Dataset on existing reports

Hi All,

I have a set of reports already built. I want to use the same reports using a different dataset(different server). I have tried to add a new datasource and data set, then set the data tab of the report to reflect the new dataset. All seems fine, but when I deploy the report, it is deployed with the new dataset into the new location, but the data displayed is from the original dataset. Any pointers?

regards

Have you tried getting out of report manager and going back in? Refreshing. Something sounds like it's pointing to the wrong server. The report is doing what you have told it to do. Check your data sources and check your report on the report manager to see where the data source is pointing. It may be pointing somewhere else.|||I have done what you suggested. Still not working. Odd thing is, if I go to the report properties in the RS website and look at the data sources, both data sources are listed. Let me be clear on what I am looking for here, so I dont waste anyones time. I have 2databases I want to access and have 1 RS web server. I want to set up 2 folders on the RS and in each of the folders are the same reports , pointing at different data sources. So in the report designer I created a report and deployed it for datasource#1. Then I added a new datasource (#2) and created a new dataset with the same query from #1, but used #2 as the datasource. This is now selectable from the dropdown on the data tab in the designer. When I run the query from the data tab in the designer, the results are correct. They reflect the data from the selected datasource. But in deployed and preview mode, the report is reporting the data from the original datasource.|||

Did you delete the original dataset from this. if not delete the original data set and keep only the new dataset you added.

Then select the layout tab and select the table properties and change the Datasetname to the new dataset name.

|||Problem is, I am trying to d this and keep both datasets. Any time I have to deploy report updates, I have to push it for both datasources. I would rather not delete and creaqte for each deployment. But, if thats the way it is... thats the way it is.|||

Often the report properties persist from old versions. You may want to delete the report on report server using the manager webpage, and then repost the report. As long as you are using two different named datasources, you should be ok. If the datasources have the same name, make sure the deploy path for the second one is going to a different folder. Remember that the deploy path for the report and datasource are separate properties of the VS2005 project.

Hope that helps.

sql

change data types

Hi,
The company I work is updating our software for
localization/internationalization. Unfortunately, when we built our backend
design, we did not foresee needing to go international. So almost all of
our text data types are not built for internationalization. Basically, the
only fields we really need to change are text and varchar, to ntext and
nvarchar. Are there any issues with running a SQL script as part of a
service pack, in order to change these data types in the tables?
If there are or aren't any problems, are there any articles someone can
point me to. Most articles I have found on localization deal specifically
with creating a new application.
So in summary, I need to know if there are any issues with changing a text
to an ntext and varchar to an nvarchar. Additionally, there may be some
char fields that need to be changed to nchar.
Any help/direction/articles would be very much appreciated. Thank you.
Paul
Well, one issue that pops to mind immediately is that if you have a
VARCHAR(8000) and it has 4001 characters or more, you're going to lose data.
NVARCHAR can only go to 4000, since every character takes two bytes.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Paul" <paul@.gotheta.com> wrote in message
news:ebUJn1sMEHA.2628@.TK2MSFTNGP12.phx.gbl...
> Hi,
> The company I work is updating our software for
> localization/internationalization. Unfortunately, when we built our
backend
> design, we did not foresee needing to go international. So almost all of
> our text data types are not built for internationalization. Basically,
the
> only fields we really need to change are text and varchar, to ntext and
> nvarchar. Are there any issues with running a SQL script as part of a
> service pack, in order to change these data types in the tables?
> If there are or aren't any problems, are there any articles someone can
> point me to. Most articles I have found on localization deal specifically
> with creating a new application.
> So in summary, I need to know if there are any issues with changing a text
> to an ntext and varchar to an nvarchar. Additionally, there may be some
> char fields that need to be changed to nchar.
> Any help/direction/articles would be very much appreciated. Thank you.
> Paul
>

Catching report exceptions

Instead of using the Report Manager that comes with Reporting Services, I
have built a custom ASP.NET report interface that launches reports using URL
access. When there is a problem displaying a report, I get the usual
reporting services error, but I would like to redirect to a custom report
page. How do I do that ?
Thanks, Craig"Craig HB" <CraigHB@.discussions.microsoft.com> wrote in message
news:A040A3CA-2A55-4D2A-8410-75E2B353566D@.microsoft.com...
> Instead of using the Report Manager that comes with Reporting Services, I
> have built a custom ASP.NET report interface that launches reports using
> URL
> access. When there is a problem displaying a report, I get the usual
> reporting services error, but I would like to redirect to a custom report
> page. How do I do that ?
> Thanks, Craig
You can use web service Render method to catch an error, but if you want to
use URL approach, than
grab your's url output by using System.Net.HttpWebRequest ( or WebRequest)
class.
If the output is text based (HTML, CSV) - just convert returned by
WebResponse byte array to - char - string and check it for specific error
messages. If the output has to be binary (PDF, EXCEL, etc.) -just check
ContentType of your System.Net.WebResponse class and if it is "text/html" -
the error has occured ( you can always parse byte array to be sure as I
proposed above).