Hi,
Is it possible to display values from different fields in the same textbox.I
have a field that returns system generated IDs and a field that returns ID
values that have been manually input by the user.
I want values from these fields to display on the same textbox as they act
Product Id for Products that shown on the invoice report.
Does anyone know how I can achieve this?
Regards,
--
Noels
"The Best thing in life is life"You can do this either with the textbox or the query. Let's say you have a
field called sys_id and manual_id.
With a query:
select convert(varchar(15), sys_id) + ' ' + manual_id as product_id from
sometable where ...
That would be my preferred way of handling this.
The other way is to set the textbox to an expression and in the expression
concatenate the two fields.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Noels" <noels@.gmail.com> wrote in message
news:7528B73A-5EF9-4449-A85E-2F816282A148@.microsoft.com...
> Hi,
> Is it possible to display values from different fields in the same
> textbox.I
> have a field that returns system generated IDs and a field that returns ID
> values that have been manually input by the user.
> I want values from these fields to display on the same textbox as they act
> Product Id for Products that shown on the invoice report.
> Does anyone know how I can achieve this?
> Regards,
> --
> Noels
> "The Best thing in life is life"|||Thank you so much,why didnt I think of that!
Noels
"The Best thing in life is life"
"Bruce L-C [MVP]" wrote:
> You can do this either with the textbox or the query. Let's say you have a
> field called sys_id and manual_id.
> With a query:
> select convert(varchar(15), sys_id) + ' ' + manual_id as product_id from
> sometable where ...
> That would be my preferred way of handling this.
> The other way is to set the textbox to an expression and in the expression
> concatenate the two fields.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Noels" <noels@.gmail.com> wrote in message
> news:7528B73A-5EF9-4449-A85E-2F816282A148@.microsoft.com...
> > Hi,
> >
> > Is it possible to display values from different fields in the same
> > textbox.I
> > have a field that returns system generated IDs and a field that returns ID
> > values that have been manually input by the user.
> >
> > I want values from these fields to display on the same textbox as they act
> > Product Id for Products that shown on the invoice report.
> >
> > Does anyone know how I can achieve this?
> >
> > Regards,
> > --
> > Noels
> > "The Best thing in life is life"
>
>
Showing posts with label values. Show all posts
Showing posts with label values. Show all posts
Tuesday, March 27, 2012
Dimenstion on measure
There is count measure in the cube. I need to create a dimension that should list the range of values based on that count values:
Exp:
0-99
100-199
200-399
...
...
..
and so on.
User wants to pick the any range level in the dimension and cube should show corresponding cell values of count measure which would fall into range of the dimension level value.
For example:
if user picks up level 100-199 then cube would filter cell values of measure that has a value between 100 and 199 within 12 month range. So, it would be year to date value of the measure. My problem is how go about creating Dimension that based on measure in the cube and dimension should have level with range of measure values.
Any hint would be appreciated greatly.
Thank You.you need your Range lookup table
Range_lkp
---
Range_ID (PK)
Range_Desc
containing values
1 0-99
2 100-199
3 200-399
in your Fact table data would look like:
... Measure ..... RangeID (FK)
----------
... 104.56 ..... 1
... 95.47 ..... 3
... 345.77 ..... 3
the point is you have to populate your RangeID's to your Fact table during ETL
1) populate table with RangeID = NULL
2) update table set RangeID = ... use procedure (I don't think you'll handle it by one update statement)|||Well, it would be best solution. But, in my case wont work.
Measure in fact table will be aggregated over 12 month period in the Cube.
So, in your example Range Id = 1 of 104.56
Might be in the cube something like that:
313.68
Sum(
104.56
104.56
104. 56
)
So, 313.68 is no longer Range id 1
Point here is over period of time. Not fact value of that measure and that most of the cases will be aggregations of those facts (104.56).|||OK I know what you mean...
Maybe you could create another few snapshot tables. Weekly snapshot, Monthly snapshot, Quarter snapshot, Yearly snapshot. Set up Range ID's in those tables and use them for reporting. Another option could be solve this somehow on reports level. It's hard to say how, it depends on your business intelligence tool. BTW what tool do you use? Or how you report your data?|||We use MS Analysis.
Doing something like that in report is easy. But, users want it on the cube. I believe it should be done dynamically with MDX. I thought maybe somebody else already done it then I dont have to invent the wheel.
Thanks for response anyway.
Exp:
0-99
100-199
200-399
...
...
..
and so on.
User wants to pick the any range level in the dimension and cube should show corresponding cell values of count measure which would fall into range of the dimension level value.
For example:
if user picks up level 100-199 then cube would filter cell values of measure that has a value between 100 and 199 within 12 month range. So, it would be year to date value of the measure. My problem is how go about creating Dimension that based on measure in the cube and dimension should have level with range of measure values.
Any hint would be appreciated greatly.
Thank You.you need your Range lookup table
Range_lkp
---
Range_ID (PK)
Range_Desc
containing values
1 0-99
2 100-199
3 200-399
in your Fact table data would look like:
... Measure ..... RangeID (FK)
----------
... 104.56 ..... 1
... 95.47 ..... 3
... 345.77 ..... 3
the point is you have to populate your RangeID's to your Fact table during ETL
1) populate table with RangeID = NULL
2) update table set RangeID = ... use procedure (I don't think you'll handle it by one update statement)|||Well, it would be best solution. But, in my case wont work.
Measure in fact table will be aggregated over 12 month period in the Cube.
So, in your example Range Id = 1 of 104.56
Might be in the cube something like that:
313.68
Sum(
104.56
104.56
104. 56
)
So, 313.68 is no longer Range id 1
Point here is over period of time. Not fact value of that measure and that most of the cases will be aggregations of those facts (104.56).|||OK I know what you mean...
Maybe you could create another few snapshot tables. Weekly snapshot, Monthly snapshot, Quarter snapshot, Yearly snapshot. Set up Range ID's in those tables and use them for reporting. Another option could be solve this somehow on reports level. It's hard to say how, it depends on your business intelligence tool. BTW what tool do you use? Or how you report your data?|||We use MS Analysis.
Doing something like that in report is easy. But, users want it on the cube. I believe it should be done dynamically with MDX. I thought maybe somebody else already done it then I dont have to invent the wheel.
Thanks for response anyway.
Dimension values without data in a fact table
I have an ODS system and a Data warehouse system
I have a Sales fact table in the ODS system and I have these fields:
SALES
ID_CUSTOMER (PK),
ID_MODEL (PK),
ID_TIME (PK),
SALES,
QUANT_ART,
COST
Then in some records in the fields ID_Time or ID_Model or ID_Customer I
don’t have values (NULL) because in the transactional systems these record
don’t have values (NULL).
The users want to generate aggregate reports with the Sales table...
The question is:
I have to put a “dummy” value in the dimensions Customer, Model and Time
(for example “0”) and put this value in the fact table if the dimensions
fields have NULL values?
Or I have to leave the NULL values?
What is the best choice? Why?
Personally -- and this really does boil down to personal preference -- I
believe that one of the key things that should happen during an ETL is
elimination of all "questionable" data. That includes unknown data -- can
you really report on something that's unknown? At the least, generate
well-known tokens to replace the NULLs with. If possible, get rid of those
rows on the way in (of course, that really depends on context) -- perhaps
they can appear in the aggregate data, but not in the line-level data?
There are various ways of dealing with the problem, but personally I am very
firm when designing data warehouses and ensure that, one way or another,
there will be absolutely no NULLs in the database.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
"CLAUDIO" <CLAUDIO@.discussions.microsoft.com> wrote in message
news:937E414E-AB9A-4E4D-8A58-D8251139550E@.microsoft.com...
> I have an ODS system and a Data warehouse system
> I have a Sales fact table in the ODS system and I have these fields:
> SALES
> ID_CUSTOMER (PK),
> ID_MODEL (PK),
> ID_TIME (PK),
> SALES,
> QUANT_ART,
> COST
>
> Then in some records in the fields ID_Time or ID_Model or ID_Customer I
> don't have values (NULL) because in the transactional systems these record
> don't have values (NULL).
> The users want to generate aggregate reports with the Sales table...
> The question is:
> I have to put a "dummy" value in the dimensions Customer, Model and Time
> (for example "0") and put this value in the fact table if the dimensions
> fields have NULL values?
> Or I have to leave the NULL values?
> What is the best choice? Why?
>
sql
I have a Sales fact table in the ODS system and I have these fields:
SALES
ID_CUSTOMER (PK),
ID_MODEL (PK),
ID_TIME (PK),
SALES,
QUANT_ART,
COST
Then in some records in the fields ID_Time or ID_Model or ID_Customer I
don’t have values (NULL) because in the transactional systems these record
don’t have values (NULL).
The users want to generate aggregate reports with the Sales table...
The question is:
I have to put a “dummy” value in the dimensions Customer, Model and Time
(for example “0”) and put this value in the fact table if the dimensions
fields have NULL values?
Or I have to leave the NULL values?
What is the best choice? Why?
Personally -- and this really does boil down to personal preference -- I
believe that one of the key things that should happen during an ETL is
elimination of all "questionable" data. That includes unknown data -- can
you really report on something that's unknown? At the least, generate
well-known tokens to replace the NULLs with. If possible, get rid of those
rows on the way in (of course, that really depends on context) -- perhaps
they can appear in the aggregate data, but not in the line-level data?
There are various ways of dealing with the problem, but personally I am very
firm when designing data warehouses and ensure that, one way or another,
there will be absolutely no NULLs in the database.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
"CLAUDIO" <CLAUDIO@.discussions.microsoft.com> wrote in message
news:937E414E-AB9A-4E4D-8A58-D8251139550E@.microsoft.com...
> I have an ODS system and a Data warehouse system
> I have a Sales fact table in the ODS system and I have these fields:
> SALES
> ID_CUSTOMER (PK),
> ID_MODEL (PK),
> ID_TIME (PK),
> SALES,
> QUANT_ART,
> COST
>
> Then in some records in the fields ID_Time or ID_Model or ID_Customer I
> don't have values (NULL) because in the transactional systems these record
> don't have values (NULL).
> The users want to generate aggregate reports with the Sales table...
> The question is:
> I have to put a "dummy" value in the dimensions Customer, Model and Time
> (for example "0") and put this value in the fact table if the dimensions
> fields have NULL values?
> Or I have to leave the NULL values?
> What is the best choice? Why?
>
sql
Sunday, March 25, 2012
Dimension values without data in a fact table
I have an ODS system and a Data warehouse system
I have a Sales fact table in the ODS system and I have these fields:
SALES
ID_CUSTOMER (PK),
ID_MODEL (PK),
ID_TIME (PK),
SALES,
QUANT_ART,
COST
Then in some records in the fields ID_Time or ID_Model or ID_Customer I
don’t have values (NULL) because in the transactional systems these record
don’t have values (NULL).
The users want to generate aggregate reports with the Sales table...
The question is:
I have to put a “dummy” value in the dimensions Customer, Model and Time
(for example “0”) and put this value in the fact table if the dimensions
fields have NULL values'
Or I have to leave the NULL values?
What is the best choice? Why?Personally -- and this really does boil down to personal preference -- I
believe that one of the key things that should happen during an ETL is
elimination of all "questionable" data. That includes unknown data -- can
you really report on something that's unknown? At the least, generate
well-known tokens to replace the NULLs with. If possible, get rid of those
rows on the way in (of course, that really depends on context) -- perhaps
they can appear in the aggregate data, but not in the line-level data?
There are various ways of dealing with the problem, but personally I am very
firm when designing data warehouses and ensure that, one way or another,
there will be absolutely no NULLs in the database.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"CLAUDIO" <CLAUDIO@.discussions.microsoft.com> wrote in message
news:937E414E-AB9A-4E4D-8A58-D8251139550E@.microsoft.com...
> I have an ODS system and a Data warehouse system
> I have a Sales fact table in the ODS system and I have these fields:
> SALES
> ID_CUSTOMER (PK),
> ID_MODEL (PK),
> ID_TIME (PK),
> SALES,
> QUANT_ART,
> COST
>
> Then in some records in the fields ID_Time or ID_Model or ID_Customer I
> don't have values (NULL) because in the transactional systems these record
> don't have values (NULL).
> The users want to generate aggregate reports with the Sales table...
> The question is:
> I have to put a "dummy" value in the dimensions Customer, Model and Time
> (for example "0") and put this value in the fact table if the dimensions
> fields have NULL values'
> Or I have to leave the NULL values?
> What is the best choice? Why?
>
I have a Sales fact table in the ODS system and I have these fields:
SALES
ID_CUSTOMER (PK),
ID_MODEL (PK),
ID_TIME (PK),
SALES,
QUANT_ART,
COST
Then in some records in the fields ID_Time or ID_Model or ID_Customer I
don’t have values (NULL) because in the transactional systems these record
don’t have values (NULL).
The users want to generate aggregate reports with the Sales table...
The question is:
I have to put a “dummy” value in the dimensions Customer, Model and Time
(for example “0”) and put this value in the fact table if the dimensions
fields have NULL values'
Or I have to leave the NULL values?
What is the best choice? Why?Personally -- and this really does boil down to personal preference -- I
believe that one of the key things that should happen during an ETL is
elimination of all "questionable" data. That includes unknown data -- can
you really report on something that's unknown? At the least, generate
well-known tokens to replace the NULLs with. If possible, get rid of those
rows on the way in (of course, that really depends on context) -- perhaps
they can appear in the aggregate data, but not in the line-level data?
There are various ways of dealing with the problem, but personally I am very
firm when designing data warehouses and ensure that, one way or another,
there will be absolutely no NULLs in the database.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"CLAUDIO" <CLAUDIO@.discussions.microsoft.com> wrote in message
news:937E414E-AB9A-4E4D-8A58-D8251139550E@.microsoft.com...
> I have an ODS system and a Data warehouse system
> I have a Sales fact table in the ODS system and I have these fields:
> SALES
> ID_CUSTOMER (PK),
> ID_MODEL (PK),
> ID_TIME (PK),
> SALES,
> QUANT_ART,
> COST
>
> Then in some records in the fields ID_Time or ID_Model or ID_Customer I
> don't have values (NULL) because in the transactional systems these record
> don't have values (NULL).
> The users want to generate aggregate reports with the Sales table...
> The question is:
> I have to put a "dummy" value in the dimensions Customer, Model and Time
> (for example "0") and put this value in the fact table if the dimensions
> fields have NULL values'
> Or I have to leave the NULL values?
> What is the best choice? Why?
>
Dimension not slicing data - all the same values
When I try to add a referenced dimension, which I done many times already, the values do not slice / are the same value for each dimension entry. Suggestions?Figured it out... I had a many-to-many relationship. Just implemented what was mentioned here: http://technet.microsoft.com/en-us/library/ms345139.aspx
cheers.
Thursday, March 22, 2012
Difficulty installing and upgrading to MSDE SP3a
I have installed MSDE 2000A using the ini file method of supplying
settings. I supplied values for the following settings:
[Options]
ALLOWXDBCHAINING=3D0
BLANKSAPWD=3D1
COLLATION=3DLatin1_General_CI_AS
DATADIR=3DC:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Data\
DISABLENETWORKPROTOCOLS=3D1
INSTANCENAME=3D"HipMSDE" SAPWD=3D"XXXX" SECURITYMODE=3DSQL
TARGETDIR=3DC:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Binn\
Since I was unable to perform this install using the command line:
"Setup.exe /settings Setup.ini"
because it kept telling me the path was not valid, I double clicked on
Setup.exe and it took all the settings in Setup.ini anyway.
In attempting to upgrade to SP3a I attempted to supply the following
settings in an ini file.
[Options]
ALLOWXDBCHAINING=3D0
BLANKSAPWD=3D1
COLLATION=3DLatin1_General_CI_AS
DATADIR=3DC:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Data\
DISABLENETWORKPROTOCOLS=3D1
INSTANCENAME=3D"HipMSDE" SAPWD=3D"XXXX" SECURITYMODE=3DSQL
TARGETDIR=3DC:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Binn\
UPGRADE=3D1 UPGRADEUSER=3D"XXXXUpgr" UPGRADEPWD=3D"XXXXUpgr"
Using the same command line but this time for the SP3a setup file, an
installation does not occur. Trying the same double click too does not
work. Instead I get is the following instructions:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D
Windows =AE Installer. V 3.00.3790.2180
msiexec /Option <Required Parameter> [Optional Parameter]
Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated
value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=3DPropertyValue]
Consult the Windows =AE Installer SDK for additional documentation on
the
command line syntax.
Copyright =A9 Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the
Independent JPEG Group.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D
These windows installer instructions and the wealth of SP3a
documentation only leads me to more confusion. I've spent two days
trying to meticulously decypher and make sense of it. I'm lost! Can
someone please help sort this out for me?
BTW I have successfully updated to SP3a for both of my SQL Server 2000
database installations. It's this MSDE that I am having difficulty
undersatnding
hi,
dbuchanan wrote:
> I have installed MSDE 2000A using the ini file method of supplying
> settings. I supplied values for the following settings:
> [Options]
> ALLOWXDBCHAINING=0
> BLANKSAPWD=1
> COLLATION=Latin1_General_CI_AS
> DATADIR=C:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Data\
> DISABLENETWORKPROTOCOLS=1
> INSTANCENAME="HipMSDE" SAPWD="XXXX" SECURITYMODE=SQL
> TARGETDIR=C:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Binn\
> Since I was unable to perform this install using the command line:
> "Setup.exe /settings Setup.ini"
> because it kept telling me the path was not valid, I double clicked on
> Setup.exe and it took all the settings in Setup.ini anyway.
> In attempting to upgrade to SP3a I attempted to supply the following
> settings in an ini file.
> [Options]
> ALLOWXDBCHAINING=0
> BLANKSAPWD=1
> COLLATION=Latin1_General_CI_AS
> DATADIR=C:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Data\
> DISABLENETWORKPROTOCOLS=1
> INSTANCENAME="HipMSDE" SAPWD="XXXX" SECURITYMODE=SQL
> TARGETDIR=C:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Binn\
> UPGRADE=1 UPGRADEUSER="XXXXUpgr" UPGRADEPWD="XXXXUpgr"
> Using the same command line but this time for the SP3a setup file, an
> installation does not occur. Trying the same double click too does not
> work. Instead I get is the following instructions:
>...
MSDE 2000A is already updated at sp3a level and you do not need to upgrade
it..
if you are experimenting troubles with the ini file, you can directly
provide those parameters to the setup.exe bootstrap installer in the form
c:\..\>setup.exe ALLOWXDBCHAINING=0 COLLATION="Latin1_General_CI_AS"
DATADIR="C:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Data\"
DISABLENETWORKPROTOCOLS=1 INSTANCENAME="HipMSDE" SAPWD="XXXX"
SECURITYMODE=SQL TARGETDIR="C:\Program Files\Microsoft SQL
Server\MSSQL$HipMSDE\Binn\"
all on the same line
you provide BLANKSAPWD=1 and SAPWD="XXXX" parameters, and those should be
mutual exclusive, so please try removing BLANKSAPWD=1
> UPGRADE=1 UPGRADEUSER="XXXXUpgr" UPGRADEPWD="XXXXUpgr"
are not required as you do not have to upgrade...
please always add the
/L*v "c:\MsdeLog.txt"
parameter too in order to verbose log all the installation process, that
will result in an about 2mb txt log file you can inspect, in case of
problems, for
RETURN VALUE 3
entries, that indicate problems and, about 10/20 lines before or after each
entry a more descriptive (often cryptic) explanation of the problem is
reported
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
settings. I supplied values for the following settings:
[Options]
ALLOWXDBCHAINING=3D0
BLANKSAPWD=3D1
COLLATION=3DLatin1_General_CI_AS
DATADIR=3DC:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Data\
DISABLENETWORKPROTOCOLS=3D1
INSTANCENAME=3D"HipMSDE" SAPWD=3D"XXXX" SECURITYMODE=3DSQL
TARGETDIR=3DC:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Binn\
Since I was unable to perform this install using the command line:
"Setup.exe /settings Setup.ini"
because it kept telling me the path was not valid, I double clicked on
Setup.exe and it took all the settings in Setup.ini anyway.
In attempting to upgrade to SP3a I attempted to supply the following
settings in an ini file.
[Options]
ALLOWXDBCHAINING=3D0
BLANKSAPWD=3D1
COLLATION=3DLatin1_General_CI_AS
DATADIR=3DC:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Data\
DISABLENETWORKPROTOCOLS=3D1
INSTANCENAME=3D"HipMSDE" SAPWD=3D"XXXX" SECURITYMODE=3DSQL
TARGETDIR=3DC:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Binn\
UPGRADE=3D1 UPGRADEUSER=3D"XXXXUpgr" UPGRADEPWD=3D"XXXXUpgr"
Using the same command line but this time for the SP3a setup file, an
installation does not occur. Trying the same double click too does not
work. Instead I get is the following instructions:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D
Windows =AE Installer. V 3.00.3790.2180
msiexec /Option <Required Parameter> [Optional Parameter]
Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated
value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=3DPropertyValue]
Consult the Windows =AE Installer SDK for additional documentation on
the
command line syntax.
Copyright =A9 Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the
Independent JPEG Group.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D
These windows installer instructions and the wealth of SP3a
documentation only leads me to more confusion. I've spent two days
trying to meticulously decypher and make sense of it. I'm lost! Can
someone please help sort this out for me?
BTW I have successfully updated to SP3a for both of my SQL Server 2000
database installations. It's this MSDE that I am having difficulty
undersatnding
hi,
dbuchanan wrote:
> I have installed MSDE 2000A using the ini file method of supplying
> settings. I supplied values for the following settings:
> [Options]
> ALLOWXDBCHAINING=0
> BLANKSAPWD=1
> COLLATION=Latin1_General_CI_AS
> DATADIR=C:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Data\
> DISABLENETWORKPROTOCOLS=1
> INSTANCENAME="HipMSDE" SAPWD="XXXX" SECURITYMODE=SQL
> TARGETDIR=C:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Binn\
> Since I was unable to perform this install using the command line:
> "Setup.exe /settings Setup.ini"
> because it kept telling me the path was not valid, I double clicked on
> Setup.exe and it took all the settings in Setup.ini anyway.
> In attempting to upgrade to SP3a I attempted to supply the following
> settings in an ini file.
> [Options]
> ALLOWXDBCHAINING=0
> BLANKSAPWD=1
> COLLATION=Latin1_General_CI_AS
> DATADIR=C:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Data\
> DISABLENETWORKPROTOCOLS=1
> INSTANCENAME="HipMSDE" SAPWD="XXXX" SECURITYMODE=SQL
> TARGETDIR=C:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Binn\
> UPGRADE=1 UPGRADEUSER="XXXXUpgr" UPGRADEPWD="XXXXUpgr"
> Using the same command line but this time for the SP3a setup file, an
> installation does not occur. Trying the same double click too does not
> work. Instead I get is the following instructions:
>...
MSDE 2000A is already updated at sp3a level and you do not need to upgrade
it..
if you are experimenting troubles with the ini file, you can directly
provide those parameters to the setup.exe bootstrap installer in the form
c:\..\>setup.exe ALLOWXDBCHAINING=0 COLLATION="Latin1_General_CI_AS"
DATADIR="C:\Program Files\Microsoft SQL Server\MSSQL$HipMSDE\Data\"
DISABLENETWORKPROTOCOLS=1 INSTANCENAME="HipMSDE" SAPWD="XXXX"
SECURITYMODE=SQL TARGETDIR="C:\Program Files\Microsoft SQL
Server\MSSQL$HipMSDE\Binn\"
all on the same line
you provide BLANKSAPWD=1 and SAPWD="XXXX" parameters, and those should be
mutual exclusive, so please try removing BLANKSAPWD=1
> UPGRADE=1 UPGRADEUSER="XXXXUpgr" UPGRADEPWD="XXXXUpgr"
are not required as you do not have to upgrade...
please always add the
/L*v "c:\MsdeLog.txt"
parameter too in order to verbose log all the installation process, that
will result in an about 2mb txt log file you can inspect, in case of
problems, for
RETURN VALUE 3
entries, that indicate problems and, about 10/20 lines before or after each
entry a more descriptive (often cryptic) explanation of the problem is
reported
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
difficulty in getting result.
hi all
i am working on sql reporting 2005.
i have 3 reports say A, B ,C
i want to display sum of values in column of A & sum of values in column of B in report C
How can i do this?
plz help me.
report c would have to have the same data as in reports A and B. Then you can sum them.
i am working on sql reporting 2005.
i have 3 reports say A, B ,C
i want to display sum of values in column of A & sum of values in column of B in report C
How can i do this?
plz help me.
report c would have to have the same data as in reports A and B. Then you can sum them.
Wednesday, March 21, 2012
Difficult question
Hello,
I have a table with stock values, they are grouped by a stock id. now I want
to get the trend of each stock. I only need this for one value per w
for
one month.
for example:
stockid price
1 20
2 10
3 5
1 21
2 9
3 5
1 24
2 8
3 4
1 28
2 5
3 5
now I wan tot group them like:
stockid price1 price2 price3 price4
1 20 21 24 28
2 10 9 8 5
3 5 5 4 5
This way I can tell what the trend of the prices are, going up or down.
Or is there an other way of doing this?
Any help is appreciated,
-MarkYour design is wrong; we need a date or something by which to arange
the prices. Get a book on basic RDBMS and read Dr. Codd's 12 rules.
Look at the rule about using scalar values in columns of tables to
model all relationships.
SELECT ticker_sym,
CASE WHEN quote_date = '2005-11-22'
THEN price END AS price_1,
CASE WHEN quote_date = '2005-11-23'
THEN price END AS price_2,
CASE WHEN quote_date = '2005-11-24'
THEN price END AS price_3
FROM StockHistory
GROUP BY ticker_sym;|||Thanks,
Well actually there is a date column and other columns as well, I just used
these because I thought they where the importante ones, my mistake.
Table Def:
ID (PK)
StockID (FK)
Date (datetime)
ClosePrice (money)
This gives me the following result:
StockID, P1, P2, P3, P4
1, 20, NULL, NULL, NULL
1, NULL, 21, NULL, NULL
1, NULL, NULL, 24, NULL
1, NULL, NULL, NULL, 28
What I would like is
StockID, P1, P2, P3, P4
1, 20, 21, 24, 28
-Mark
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1132859937.260224.130920@.f14g2000cwb.googlegroups.com...
> Your design is wrong; we need a date or something by which to arange
> the prices. Get a book on basic RDBMS and read Dr. Codd's 12 rules.
> Look at the rule about using scalar values in columns of tables to
> model all relationships.
> SELECT ticker_sym,
> CASE WHEN quote_date = '2005-11-22'
> THEN price END AS price_1,
> CASE WHEN quote_date = '2005-11-23'
> THEN price END AS price_2,
> CASE WHEN quote_date = '2005-11-24'
> THEN price END AS price_3
> FROM StockHistory
> GROUP BY ticker_sym;
>|||SELECT ticker_sym,
SUM( CASE WHEN quote_date = '2005-11-22'
THEN price END) AS price_1,
SUM( CASE WHEN quote_date = '2005-11-23'
THEN price END) AS price_2,
SUM( CASE WHEN quote_date = '2005-11-24'
THEN price END) AS price_3
FROM StockHistory
GROUP BY ticker_sym;|||Thanks Celko,
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1132861841.665270.278530@.g14g2000cwa.googlegroups.com...
> SELECT ticker_sym,
> SUM( CASE WHEN quote_date = '2005-11-22'
> THEN price END) AS price_1,
> SUM( CASE WHEN quote_date = '2005-11-23'
> THEN price END) AS price_2,
> SUM( CASE WHEN quote_date = '2005-11-24'
> THEN price END) AS price_3
> FROM StockHistory
> GROUP BY ticker_sym;
>
I have a table with stock values, they are grouped by a stock id. now I want
to get the trend of each stock. I only need this for one value per w
forone month.
for example:
stockid price
1 20
2 10
3 5
1 21
2 9
3 5
1 24
2 8
3 4
1 28
2 5
3 5
now I wan tot group them like:
stockid price1 price2 price3 price4
1 20 21 24 28
2 10 9 8 5
3 5 5 4 5
This way I can tell what the trend of the prices are, going up or down.
Or is there an other way of doing this?
Any help is appreciated,
-MarkYour design is wrong; we need a date or something by which to arange
the prices. Get a book on basic RDBMS and read Dr. Codd's 12 rules.
Look at the rule about using scalar values in columns of tables to
model all relationships.
SELECT ticker_sym,
CASE WHEN quote_date = '2005-11-22'
THEN price END AS price_1,
CASE WHEN quote_date = '2005-11-23'
THEN price END AS price_2,
CASE WHEN quote_date = '2005-11-24'
THEN price END AS price_3
FROM StockHistory
GROUP BY ticker_sym;|||Thanks,
Well actually there is a date column and other columns as well, I just used
these because I thought they where the importante ones, my mistake.
Table Def:
ID (PK)
StockID (FK)
Date (datetime)
ClosePrice (money)
This gives me the following result:
StockID, P1, P2, P3, P4
1, 20, NULL, NULL, NULL
1, NULL, 21, NULL, NULL
1, NULL, NULL, 24, NULL
1, NULL, NULL, NULL, 28
What I would like is
StockID, P1, P2, P3, P4
1, 20, 21, 24, 28
-Mark
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1132859937.260224.130920@.f14g2000cwb.googlegroups.com...
> Your design is wrong; we need a date or something by which to arange
> the prices. Get a book on basic RDBMS and read Dr. Codd's 12 rules.
> Look at the rule about using scalar values in columns of tables to
> model all relationships.
> SELECT ticker_sym,
> CASE WHEN quote_date = '2005-11-22'
> THEN price END AS price_1,
> CASE WHEN quote_date = '2005-11-23'
> THEN price END AS price_2,
> CASE WHEN quote_date = '2005-11-24'
> THEN price END AS price_3
> FROM StockHistory
> GROUP BY ticker_sym;
>|||SELECT ticker_sym,
SUM( CASE WHEN quote_date = '2005-11-22'
THEN price END) AS price_1,
SUM( CASE WHEN quote_date = '2005-11-23'
THEN price END) AS price_2,
SUM( CASE WHEN quote_date = '2005-11-24'
THEN price END) AS price_3
FROM StockHistory
GROUP BY ticker_sym;|||Thanks Celko,
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1132861841.665270.278530@.g14g2000cwa.googlegroups.com...
> SELECT ticker_sym,
> SUM( CASE WHEN quote_date = '2005-11-22'
> THEN price END) AS price_1,
> SUM( CASE WHEN quote_date = '2005-11-23'
> THEN price END) AS price_2,
> SUM( CASE WHEN quote_date = '2005-11-24'
> THEN price END) AS price_3
> FROM StockHistory
> GROUP BY ticker_sym;
>
Friday, March 9, 2012
different values between Relational and MOLAP in a sum measure... BUG?
Hello,
I'm working in a Windows 2003 Server, SQL Server 2000 and Analysis Services 2000.
I have created two models in Analysis Services (MOLAP):
- MODEL 1 gets info directly from the relational FACT table: "FCT_SALES"
- MODEL 2 gets info from a view with: "SELECT * FROM FCT_SALES"
FCT_SALES has a measure (sum and double - the column in the relational table is float).
This measure has 10 rows in the FCT_SALES.
Problem:
When we agregate the measure rows in Query Analyzer, MODEL 1 and MODEL 2 return 20. --> IT'S OK!
When I use Analysis Services (and ProClarity), MODEL 1 returns 20. --> IT'S OK!
When I use Analysis Services (and ProClarity), MODEL 2 returns 17. -->WRONG!!
WHY?
When I make Drill Through (Drill to Detail) in Analysis Services (or ProClarity) to see the rows that compose the value, and export them to Excel, I get the 20. --> IT'S OK!
So, WHY does Analysis Services (and ProClarity) give me 17 ?!?
If the SUM(rows) give me 20, WHY does Analysis Services give me 17 ?!?
Thanks.
Hi guys,
Yesterday nigth, I found the problem: something that shouldn't happen in the source info, happened! Murphy's Law
)))
Analysis Services wasn't causing the info inconsistent.
Thanks anyway.
I'm working in a Windows 2003 Server, SQL Server 2000 and Analysis Services 2000.
I have created two models in Analysis Services (MOLAP):
- MODEL 1 gets info directly from the relational FACT table: "FCT_SALES"
- MODEL 2 gets info from a view with: "SELECT * FROM FCT_SALES"
FCT_SALES has a measure (sum and double - the column in the relational table is float).
This measure has 10 rows in the FCT_SALES.
Problem:
When we agregate the measure rows in Query Analyzer, MODEL 1 and MODEL 2 return 20. --> IT'S OK!
When I use Analysis Services (and ProClarity), MODEL 1 returns 20. --> IT'S OK!
When I use Analysis Services (and ProClarity), MODEL 2 returns 17. -->WRONG!!
WHY?
When I make Drill Through (Drill to Detail) in Analysis Services (or ProClarity) to see the rows that compose the value, and export them to Excel, I get the 20. --> IT'S OK!
So, WHY does Analysis Services (and ProClarity) give me 17 ?!?
If the SUM(rows) give me 20, WHY does Analysis Services give me 17 ?!?
Thanks.
Hi guys,
Yesterday nigth, I found the problem: something that shouldn't happen in the source info, happened! Murphy's Law
)))Analysis Services wasn't causing the info inconsistent.
Thanks anyway.
different values between Relational and MOLAP in a sum measure... BUG?
Hello,
I'm working in a Windows 2003 Server, SQL Server 2000 and Analysis Services
2000.
I have created two models in Analysis Services (MOLAP):
- MODEL 1 gets info directly from the relational FACT table: "FCT_SALES"
- MODEL 2 gets info from a view with: "SELECT * FROM FCT_SALES"
FCT_SALES has a measure (sum and double - the column in the relational table
is float).
This measure has 10 rows in the FCT_SALES.
Problem:
When we agregate the measure rows in Query Analyzer, MODEL 1 and MODEL 2 ret
urn 20. --> IT'S OK!
When I use Analysis Services (and ProClarity), MODEL 1 returns 20. --> IT'S
OK!
When I use Analysis Services (and ProClarity), MODEL 2 returns 17. -->WRONG!
!
WHY?
When I make Drill Through (Drill to Detail) in Analysis Services (or ProClar
ity) to see the rows that compose the value, and export them to Excel, I get
the 20. --> IT'S OK!
So, WHY does Analysis Services (and ProClarity) give me 17 ?!?
If the SUM(rows) give me 20, WHY does Analysis Services give me 17 ?!?
Thanks.Hi guys,
Yesterday nigth, I found the problem: something that shouldn't happen in the
source info, happened! Murphy's Law)))
Analysis Services wasn't causing the info inconsistent.
Thanks anyway.
I'm working in a Windows 2003 Server, SQL Server 2000 and Analysis Services
2000.
I have created two models in Analysis Services (MOLAP):
- MODEL 1 gets info directly from the relational FACT table: "FCT_SALES"
- MODEL 2 gets info from a view with: "SELECT * FROM FCT_SALES"
FCT_SALES has a measure (sum and double - the column in the relational table
is float).
This measure has 10 rows in the FCT_SALES.
Problem:
When we agregate the measure rows in Query Analyzer, MODEL 1 and MODEL 2 ret
urn 20. --> IT'S OK!
When I use Analysis Services (and ProClarity), MODEL 1 returns 20. --> IT'S
OK!
When I use Analysis Services (and ProClarity), MODEL 2 returns 17. -->WRONG!
!
WHY?
When I make Drill Through (Drill to Detail) in Analysis Services (or ProClar
ity) to see the rows that compose the value, and export them to Excel, I get
the 20. --> IT'S OK!
So, WHY does Analysis Services (and ProClarity) give me 17 ?!?
If the SUM(rows) give me 20, WHY does Analysis Services give me 17 ?!?
Thanks.Hi guys,
Yesterday nigth, I found the problem: something that shouldn't happen in the
source info, happened! Murphy's Law
)))Analysis Services wasn't causing the info inconsistent.
Thanks anyway.
Wednesday, March 7, 2012
Different sums from table
Could someone explain to me, how I can get sum from row which I have values in 2 colums and I want the realtime sum to third column. Fourth colum is for item.
Also can someone tell me how to sum these third colums where the item is same so I have real time values for the item sum.
Thanks!
AD
Hi,
regardless that this makes no sense at all, this could be an example (as far as I understood your problem):
Select OrderId, Sum(Unitprice) + Sum (Quantity) AS ThirdColumn
from [Order Details]
Group by OrderId
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Sunday, February 19, 2012
Different Colors for Values
Hi NG,
i want different colors for the values in my drilldown-tables
i.e.
if value < 0 the values should be red
if value > 0 the values should be black
any suggests?
frankHI
Go to Properties > Color > Expression
And type: =iif(value < 0, â'redâ', â'blackâ')
:-)
"Frank Matthiesen" wrote:
> Hi NG,
> i want different colors for the values in my drilldown-tables
> i.e.
> if value < 0 the values should be red
> if value > 0 the values should be black
> any suggests?
>
> frank
>
>|||Soan wrote:
> Go to Properties > Color > Expression
> And type: =iif(value < 0, "red", "black")
oh man...so easy!
top...thx a lot
frank|||Folks,
I can't get line color changes to appear in a line chart. Did SP1 provide
color control for the Line chart as well?
Thanks,
Chris
"Frank Matthiesen" wrote:
> Soan wrote:
> > Go to Properties > Color > Expression
> > And type: =iif(value < 0, "red", "black")
> oh man...so easy!
> top...thx a lot
> frank
>
>|||For line charts, the line border color property is what you are looking for.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Borgers" <ChrisBorgers@.discussions.microsoft.com> wrote in message
news:D655C59C-1B8F-4BC3-A9D3-6FD3CA409F79@.microsoft.com...
> Folks,
> I can't get line color changes to appear in a line chart. Did SP1 provide
> color control for the Line chart as well?
> Thanks,
> Chris
> "Frank Matthiesen" wrote:
> > Soan wrote:
> > > Go to Properties > Color > Expression
> > > And type: =iif(value < 0, "red", "black")
> >
> > oh man...so easy!
> > top...thx a lot
> >
> > frank
> >
> >
> >
i want different colors for the values in my drilldown-tables
i.e.
if value < 0 the values should be red
if value > 0 the values should be black
any suggests?
frankHI
Go to Properties > Color > Expression
And type: =iif(value < 0, â'redâ', â'blackâ')
:-)
"Frank Matthiesen" wrote:
> Hi NG,
> i want different colors for the values in my drilldown-tables
> i.e.
> if value < 0 the values should be red
> if value > 0 the values should be black
> any suggests?
>
> frank
>
>|||Soan wrote:
> Go to Properties > Color > Expression
> And type: =iif(value < 0, "red", "black")
oh man...so easy!
top...thx a lot
frank|||Folks,
I can't get line color changes to appear in a line chart. Did SP1 provide
color control for the Line chart as well?
Thanks,
Chris
"Frank Matthiesen" wrote:
> Soan wrote:
> > Go to Properties > Color > Expression
> > And type: =iif(value < 0, "red", "black")
> oh man...so easy!
> top...thx a lot
> frank
>
>|||For line charts, the line border color property is what you are looking for.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Borgers" <ChrisBorgers@.discussions.microsoft.com> wrote in message
news:D655C59C-1B8F-4BC3-A9D3-6FD3CA409F79@.microsoft.com...
> Folks,
> I can't get line color changes to appear in a line chart. Did SP1 provide
> color control for the Line chart as well?
> Thanks,
> Chris
> "Frank Matthiesen" wrote:
> > Soan wrote:
> > > Go to Properties > Color > Expression
> > > And type: =iif(value < 0, "red", "black")
> >
> > oh man...so easy!
> > top...thx a lot
> >
> > frank
> >
> >
> >
Subscribe to:
Posts (Atom)