Showing posts with label current. Show all posts
Showing posts with label current. Show all posts

Tuesday, March 27, 2012

customize template.ini to upgrade from msde to express edition?

I need to create the script to upgrade the current named instance of sql 2000 desktop engine to sql server 2005 express edition. I am having difficulty preparing the template.ini and would appreciate help.

[Options]
INSTANCENAME=MY_INSTANCE
SQLBROWSERACCOUNT=NT AUTHORITY\NETWORK SERVICE
SECURITYMODE=SQL
SAPWD=music
UPGRADE=SQL_Engine
SQLBROWSERAUTOSTART=1
RSCANINSTALLDEFAULT=0
RSCONFIGURATION=FilesOnly
RSSQLLOCAL=0

I get an error that this file is invalid..Any clues? I am trying to upgrade existing instance of msde 2k to sql express 2005 and uses sql authentication

http://www.microsoft.com/sql/editions/express/upgrade.mspx

http://www.microsoft.com/technet/prodtechnol/sql/2005/msde2sqlexpress.mspx

http://msdn2.microsoft.com/en-us/ms143491.aspx

|||

When a parameter includes space characters, you need quote with " or '. For example, the browser account should be specified as SQLBROWSERACCOUNT="NT AUTHORITY\NETWORK SERVICE " or SQLBROWSERACCOUNT='NT AUTHORITY\NETWORK SERVICE'

Note, this account is localized on some localized operating system. You need to use the localized version if required. In addition, MSDE already has its SP4. So please use MSDE SP4 directly.

The following are two command lines that may be useful to you.

1. Install MSDE SP4.

start /wait setup.exe /qb INSTANCENAME=msde4instance SAPWD="<password>" SECURITYMODE=SQL

2. Upgrade to SQL 2005 SP1.

start /wait setup.exe UPGRADE=SQL_Engine INSTANCENAME=msdesp4instance SAPWD=""<password>" SECURITYMODE=SQL

Friday, February 24, 2012

custom code to populate parm default

I am using custom code to retrieve the current year to populate the default
year parameter for a report. The custom code correctly retrieves the year
when tested within the body of the report. However, when referenced as an
expression code.CurYr in the "default" seection of the report parameters, it
causes the preview pane to grey-out the prompt. I can not enter anything in
the prompt and it does not contain a value. When I remove the custom code
from the expression for the "default", the prompt is white and available to
me for entry. Does anyone have any idea why this is happening, or how I can
default the current year into my prompt parameter?
Thank you...On May 1, 8:24 am, ppbedz <ppb...@.discussions.microsoft.com> wrote:
> I am using custom code to retrieve the current year to populate the default
> year parameter for a report. The custom code correctly retrieves the year
> when tested within the body of the report. However, when referenced as an
> expression code.CurYr in the "default" seection of the report parameters, it
> causes the preview pane to grey-out the prompt. I can not enter anything in
> the prompt and it does not contain a value. When I remove the custom code
> from the expression for the "default", the prompt is white and available to
> me for entry. Does anyone have any idea why this is happening, or how I can
> default the current year into my prompt parameter?
> Thank you...
I don't think you need to use custom code. Using a date part function
that SSRS will accept should do the trick. Try =YEAR(getdate()) or
=YEAR(now())|||=year(now is acceptable , HOWEVER, the preview pane still greys-out the year
prompt and does Not let me enter anything. It also does Not display the
results for the =year(now expression
For some reason, the preview pane doesn't work properly when an expression
provides the default value. In the past, I have specified a specific default
value, or used a query to load and had no difficulty.
Thoughts?
"toolman" wrote:
> On May 1, 8:24 am, ppbedz <ppb...@.discussions.microsoft.com> wrote:
> > I am using custom code to retrieve the current year to populate the default
> > year parameter for a report. The custom code correctly retrieves the year
> > when tested within the body of the report. However, when referenced as an
> > expression code.CurYr in the "default" seection of the report parameters, it
> > causes the preview pane to grey-out the prompt. I can not enter anything in
> > the prompt and it does not contain a value. When I remove the custom code
> > from the expression for the "default", the prompt is white and available to
> > me for entry. Does anyone have any idea why this is happening, or how I can
> > default the current year into my prompt parameter?
> >
> > Thank you...
> I don't think you need to use custom code. Using a date part function
> that SSRS will accept should do the trick. Try =YEAR(getdate()) or
> =YEAR(now())
>|||On May 2, 3:24 pm, ppbedz <ppb...@.discussions.microsoft.com> wrote:
> =year(now is acceptable , HOWEVER, the preview pane still greys-out the year
> prompt and does Not let me enter anything. It also does Not display the
> results for the =year(now expression
> For some reason, the preview pane doesn't work properly when an expression
> provides the default value. In the past, I have specified a specific default
> value, or used a query to load and had no difficulty.
> Thoughts?
>
> "toolman" wrote:
> > On May 1, 8:24 am, ppbedz <ppb...@.discussions.microsoft.com> wrote:
> > > I am using custom code to retrieve the current year to populate the default
> > > year parameter for a report. The custom code correctly retrieves the year
> > > when tested within the body of the report. However, when referenced as an
> > > expression code.CurYr in the "default" seection of the report parameters, it
> > > causes the preview pane to grey-out the prompt. I can not enter anything in
> > > the prompt and it does not contain a value. When I remove the custom code
> > > from the expression for the "default", the prompt is white and available to
> > > me for entry. Does anyone have any idea why this is happening, or how I can
> > > default the current year into my prompt parameter?
> > > Thank you...
> > I don't think you need to use custom code. Using a date part function
> > that SSRS will accept should do the trick. Try =YEAR(getdate()) or
> > =YEAR(now())- Hide quoted text -
> - Show quoted text -
Apparently once you establish an expression as your default that's
what you get without options for editing.
The way around it (although it bugs me to have to jump the extra
hoops) is as follows.
Create a new Text type dataset and enter this query SELECT
year(getdate()) AS 'Year'
In the Parameters dialog, set the default to From query and use the
new dataset. This plugs in the year but allows it to be edited.|||Got it... Thanks! :)
"toolman" wrote:
> On May 2, 3:24 pm, ppbedz <ppb...@.discussions.microsoft.com> wrote:
> > =year(now is acceptable , HOWEVER, the preview pane still greys-out the year
> > prompt and does Not let me enter anything. It also does Not display the
> > results for the =year(now expression
> >
> > For some reason, the preview pane doesn't work properly when an expression
> > provides the default value. In the past, I have specified a specific default
> > value, or used a query to load and had no difficulty.
> >
> > Thoughts?
> >
> >
> >
> > "toolman" wrote:
> > > On May 1, 8:24 am, ppbedz <ppb...@.discussions.microsoft.com> wrote:
> > > > I am using custom code to retrieve the current year to populate the default
> > > > year parameter for a report. The custom code correctly retrieves the year
> > > > when tested within the body of the report. However, when referenced as an
> > > > expression code.CurYr in the "default" seection of the report parameters, it
> > > > causes the preview pane to grey-out the prompt. I can not enter anything in
> > > > the prompt and it does not contain a value. When I remove the custom code
> > > > from the expression for the "default", the prompt is white and available to
> > > > me for entry. Does anyone have any idea why this is happening, or how I can
> > > > default the current year into my prompt parameter?
> >
> > > > Thank you...
> >
> > > I don't think you need to use custom code. Using a date part function
> > > that SSRS will accept should do the trick. Try =YEAR(getdate()) or
> > > =YEAR(now())- Hide quoted text -
> >
> > - Show quoted text -
> Apparently once you establish an expression as your default that's
> what you get without options for editing.
> The way around it (although it bugs me to have to jump the extra
> hoops) is as follows.
> Create a new Text type dataset and enter this query SELECT
> year(getdate()) AS 'Year'
> In the Parameters dialog, set the default to From query and use the
> new dataset. This plugs in the year but allows it to be edited.
>