problem recreating a report - 2nd dataset doesn't exist?

Hello,
I am just starting out with reporting services (I have a book which I have
not read yet). I have copied the basic part of a report to a new report for
learning purposes. This contains a parameter which I included in the query.
This works so far. But the original report also includes a table of fields
that are based on a separate dataset. I am getting an error now. How do I
add/imlement this secondary dataset? The error message says that this
dataset does not exist. I presume it means the dataset does not exist in the
report because the tables in sql server exist. How do I create this dataset?
Thanks,
Richopen report project by using visual studio
open report document (double click the report file - solution explorer)
go to Data tab (Data / Layout / Preview)
click dataset dropdown and choose <new dataset...>
have fun
"Rich" <Rich@.discussions.microsoft.com> escreveu na mensagem
news:D8EE2D83-6A8B-49AF-B875-DF9191DAD51A@.microsoft.com...
> Hello,
> I am just starting out with reporting services (I have a book which I have
> not read yet). I have copied the basic part of a report to a new report
> for
> learning purposes. This contains a parameter which I included in the
> query.
> This works so far. But the original report also includes a table of
> fields
> that are based on a separate dataset. I am getting an error now. How do
> I
> add/imlement this secondary dataset? The error message says that this
> dataset does not exist. I presume it means the dataset does not exist in
> the
> report because the tables in sql server exist. How do I create this
> dataset?
> Thanks,
> Rich|||Nevermind. I figured it out. Goto Data, New Dataset.
I didn't check the entire list of datasets in the original report.
"Rich" wrote:
> Hello,
> I am just starting out with reporting services (I have a book which I have
> not read yet). I have copied the basic part of a report to a new report for
> learning purposes. This contains a parameter which I included in the query.
> This works so far. But the original report also includes a table of fields
> that are based on a separate dataset. I am getting an error now. How do I
> add/imlement this secondary dataset? The error message says that this
> dataset does not exist. I presume it means the dataset does not exist in the
> report because the tables in sql server exist. How do I create this dataset?
> Thanks,
> Rich|||Thanks. I am sort of having fun. At least I can get my report to run.
Note: I am outputting this report in Excel format. The first set of fields
(about 3 of them) are based on the first dataset - the master data. Then I
have the 2nd dataset which is the detail data (about 6 fields). When I run
the report (outside of VS, like from an Access database app) the first
dataset displays on the first sheet of an Excel workbook, but the 2nd
dataset, the detail data, is displaying on a 2nd Excel sheet. How can I keep
the detail data on the same sheet as the master data? Is there something I
need to do in the Layout view in VS?
Thanks,
Rich
"Ricardo" wrote:
> open report project by using visual studio
> open report document (double click the report file - solution explorer)
> go to Data tab (Data / Layout / Preview)
> click dataset dropdown and choose <new dataset...>
> have fun
> "Rich" <Rich@.discussions.microsoft.com> escreveu na mensagem
> news:D8EE2D83-6A8B-49AF-B875-DF9191DAD51A@.microsoft.com...
> > Hello,
> >
> > I am just starting out with reporting services (I have a book which I have
> > not read yet). I have copied the basic part of a report to a new report
> > for
> > learning purposes. This contains a parameter which I included in the
> > query.
> > This works so far. But the original report also includes a table of
> > fields
> > that are based on a separate dataset. I am getting an error now. How do
> > I
> > add/imlement this secondary dataset? The error message says that this
> > dataset does not exist. I presume it means the dataset does not exist in
> > the
> > report because the tables in sql server exist. How do I create this
> > dataset?
> >
> > Thanks,
> > Rich
>
>

Problem querying SysObjects and SysIndexes

When executing a basic query against (see below) the system object
table in a SQL 2000 database it displays the following error.
SELECT 1 FROM SYSOBJECTS
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'SYSOBJECTS'.
The table does exist and the query is being run as an account with SQL
Admin privileges. This also occurs when trying to query the SysIndexes
table. Other databases on the server are able to query these tables.
What is causing this problem on this one database and how can it be
resolved?Some ideas.
1)Try SELECT 1 FROM sysobjects
2)Try SELECT 1 FROM dbo.sysobjects
--
Jack Vamvas
___________________________________
Need an IT job? http://www.ITjobfeed.com/SQL
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:1190368228.718871.96350@.57g2000hsv.googlegroups.com...
> When executing a basic query against (see below) the system object
> table in a SQL 2000 database it displays the following error.
> SELECT 1 FROM SYSOBJECTS
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'SYSOBJECTS'.
> The table does exist and the query is being run as an account with SQL
> Admin privileges. This also occurs when trying to query the SysIndexes
> table. Other databases on the server are able to query these tables.
> What is causing this problem on this one database and how can it be
> resolved?
>|||> What is causing this problem on this one database and how can it be
> resolved?
Object name case sensitivity is determined by the database collation. I
suspect the following query will return a case-sensitive collation:
SELECT DATABASEPROPERTYEX(DB_NAME(), 'Collation')
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:1190368228.718871.96350@.57g2000hsv.googlegroups.com...
> When executing a basic query against (see below) the system object
> table in a SQL 2000 database it displays the following error.
> SELECT 1 FROM SYSOBJECTS
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'SYSOBJECTS'.
> The table does exist and the query is being run as an account with SQL
> Admin privileges. This also occurs when trying to query the SysIndexes
> table. Other databases on the server are able to query these tables.
> What is causing this problem on this one database and how can it be
> resolved?
>|||Since posting I had resolved it.
I already thought of the suggestions that Jack posted, it was what Dan
has suggested a particular 3rd party database had been setup as case
sensitive.
On 21 Sep, 12:22, "Dan Guzman" <guzma...@.nospam-online.sbcglobal.net>
wrote:
> > What is causing this problem on this one database and how can it be
> > resolved?
> Object name case sensitivity is determined by the database collation. I
> suspect the following query will return a case-sensitive collation:
> SELECT DATABASEPROPERTYEX(DB_NAME(), 'Collation')
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Robin9876" <robin9...@.hotmail.com> wrote in message
> news:1190368228.718871.96350@.57g2000hsv.googlegroups.com...
> > When executing a basic query against (see below) the system object
> > table in a SQL 2000 database it displays the following error.
> > SELECT 1 FROM SYSOBJECTS
> > Server: Msg 208, Level 16, State 1, Line 1
> > Invalid object name 'SYSOBJECTS'.
> > The table does exist and the query is being run as an account with SQL
> > Admin privileges. This also occurs when trying to query the SysIndexes
> > table. Other databases on the server are able to query these tables.
> > What is causing this problem on this one database and how can it be
> > resolved?

Problem Month Granularity

Hello,

I suppose that my problem is something basic but it's the first time i'm confronted with this.

I want to link a measure group to a time dimension on a Month granularity.

My time dimension is a server time dimension, the inventory data comes on a monthly base, but with a normal datetime field (always the last day of the month). Linking this on a date granularity is no problem, but has no sense. When i set the granularity to Month i'm getting this error.

Errors in the OLAP storage engine: The attribute key cannot be found: Table: ASW_Monthly_Stock, Column: ASW_STOCK_DATE, Value: 31/08/2006. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Month of Dimension: Calendar Time from Database: SdwCubes, Cube: c_Sales, Measure Group: ASW Monthly Stock, Partition: ASW Monthly Stock, Record: 1. Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'ASW Monthly Stock' partition of the 'ASW Monthly Stock' measure group for the 'c_Sales' cube from the SdwCubes database.

I've seen that when setting the granularity in the Define Relationship window i'm getting a warning 'If you Select a non-key ....', but when i go into the 'Advanced...' button i can link more attributes.

But what function do i have to put on my ASW_STOCK_DATE to link it to the Month attribute of the time dimension ? The T-Sql function Month only returns the Month-number, and not the year ...

So ... if anyone could get me a bit furter on this ... greatly appreciated.

Please check that releationship between measure group and dimension columns is correct, most likely you still have days as a measure group column. To do this go to the Dimension Usage Tab, click on ... near the time dimension name, you'll get window "define relationship".|||

Hi,

Does your table AS_Monthly_Stock stock, store data for the last day of the month.

It seems like the server time dimension has the "month key" as the first day of the month. This can be the cause of your issue.

The easiet option is to change your fact table to record data on the first day of the month.

CAST(CAST(year(getdate())asvarchar)+'-'+CAST(month(getdate())asvarchar)+'-'+'01'asdatetime)

Punita

Problem Month Granularity

Hello,

I suppose that my problem is something basic but it's the first time i'm confronted with this.

I want to link a measure group to a time dimension on a Month granularity.

My time dimension is a server time dimension, the inventory data comes on a monthly base, but with a normal datetime field (always the last day of the month). Linking this on a date granularity is no problem, but has no sense. When i set the granularity to Month i'm getting this error.

Errors in the OLAP storage engine: The attribute key cannot be found: Table: ASW_Monthly_Stock, Column: ASW_STOCK_DATE, Value: 31/08/2006. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Month of Dimension: Calendar Time from Database: SdwCubes, Cube: c_Sales, Measure Group: ASW Monthly Stock, Partition: ASW Monthly Stock, Record: 1. Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'ASW Monthly Stock' partition of the 'ASW Monthly Stock' measure group for the 'c_Sales' cube from the SdwCubes database.

I've seen that when setting the granularity in the Define Relationship window i'm getting a warning 'If you Select a non-key ....', but when i go into the 'Advanced...' button i can link more attributes.

But what function do i have to put on my ASW_STOCK_DATE to link it to the Month attribute of the time dimension ? The T-Sql function Month only returns the Month-number, and not the year ...

So ... if anyone could get me a bit furter on this ... greatly appreciated.

Please check that releationship between measure group and dimension columns is correct, most likely you still have days as a measure group column. To do this go to the Dimension Usage Tab, click on ... near the time dimension name, you'll get window "define relationship".|||

Hi,

Does your table AS_Monthly_Stock stock, store data for the last day of the month.

It seems like the server time dimension has the "month key" as the first day of the month. This can be the cause of your issue.

The easiet option is to change your fact table to record data on the first day of the month.

CAST(CAST(year(getdate())asvarchar)+'-'+CAST(month(getdate())asvarchar)+'-'+'01'asdatetime)

Punita

Problem Making Sql database Connection in Deployed Site

VWD 2005 Express. Visual Basic. Sql Server 2005. I am trying to establish a connection to a SQL database. The connection (and all other database reads and writes) work fine in debug and in "view in browser" from VWD. I am running the VWD on the same server that hosts the site. When on my server (Windows 2003 Server) under IIS, the connection attempt times out.

Below is the code that is failing (only on the server when deployed):

PrivateSharedSub OpenConn(ByVal cmdAs SqlCommand,ByVal SuccessAsBoolean)

Dim connAsNew SqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings("GoodNews_IntranetConnectionString").ToString)

'The connection string resolves to ("Data Source=HQSERVER\HQSERVER;Initial Catalog=GoodNews_Intranet;Integrated Security=True"

Try

conn.Open()

cmd.Connection = conn

Success =True

Catch exAs Exception

Success =False

EndTry

EndSub

It would be great if you could post the error message that you are getting.

And in a hosted environment, it is advisable to protect your database by providing a username and password.

|||

That may be the ticket. The database does require windows authentication, so how may I make the connection (in vb code) providing a username and password? Perhaps when I am in debug, the sql calls use my windows login, however, when on the server, there is not password being passed?

|||

Please visitwww.connectionstrings.com to know the syntax for creating a connection string for your backend with user name and password.

If you think, this resolves your problem, please mark the post as "Answer". by this way we all know your issue is resolved

|||

Thank you. I found the answer on the page. I put the User Id and Password in the web.config file where the connection is defined. How can I ensure that this will not be readable when the web site is deployed?

|||

It won't be readable to a normal user, but for added security, if its not already in web.confing, then put it there. You can then use encryption to encrypt the connectionstring section (which is much easier than it sounds).

This might help:

http://msdn2.microsoft.com/en-us/library/dx0f3cf2.aspx

|||

WEB.CONFIG file is a secure one. No one can read that file outside of your application. In other words, web.config can only be read by the pages within application.

every body uses the web.config to store connection strings and is safe so far.

read the following article to know more about web.config.

http://www.aspdev.org/articles/web.config/

also, please do not forget to mark my post as answer so that we will know for sure that your issue has been resolved.

PROBLEM INSTALLING SQL SERVER EXPRESS

Hi,

I successfully installed Visual Basic 2005 express edition and but the SQL Server component did not get installed.

12:37:11 AM Sunday, April 09, 2006: [Fail] ConfigSamplesDll_DoTasks:: [Fail] Config_SSE_INST_Install: SQL Express service install (failed). The process did not return a success value. ExitCode: 1282 Command: 'C:\Documents and Settings\Oluwaseyi Awoga\Local Settings\Temp\SQLEXPR32.exe -q /norebootchk /qn reboot=ReallySuppress addlocal=all SCCCHECKLEVEL=IncompatibleComponents:1 instancename=SQLEXPRESS'.

I keep getting this error. Can anybody help me? I have uninstalled and installed ALL versions of the .NET framework etc several times. Thanks

This is also the error signature. Thanks for your help.

Error Signature:
EventType : BEX P1 : setup.exe P2 : 2005.90.1399.0 P3 : 434f6403
P4 : msdtcprx.dll P5 : 2001.12.4414.258 P6 : 41109703 P7 : 0000a2c9
P8 : c0000409 P9 : 00000000

|||

This is the content of the C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

Microsoft SQL Server 2005 Setup beginning at Sun Apr 09 01:46:18 2006
Process ID : 952
c:\e37376beb65a16277a8441b9\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2006/3/9 1:46:17
Complete: LoadResourcesAction at: 2006/3/9 1:46:18, returned true
Running: ParseBootstrapOptionsAction at: 2006/3/9 1:46:18
Loaded DLL:c:\e37376beb65a16277a8441b9\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2006/3/9 1:46:18, returned true
Running: ValidateWinNTAction at: 2006/3/9 1:46:18
Complete: ValidateWinNTAction at: 2006/3/9 1:46:18, returned true
Running: ValidateMinOSAction at: 2006/3/9 1:46:18
Complete: ValidateMinOSAction at: 2006/3/9 1:46:18, returned true
Running: PerformSCCAction at: 2006/3/9 1:46:18
Complete: PerformSCCAction at: 2006/3/9 1:46:18, returned true
Running: ActivateLoggingAction at: 2006/3/9 1:46:18
Complete: ActivateLoggingAction at: 2006/3/9 1:46:18, returned true
Running: DetectPatchedBootstrapAction at: 2006/3/9 1:46:18
Complete: DetectPatchedBootstrapAction at: 2006/3/9 1:46:18, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__952" returned false.
Running: PerformSCCAction2 at: 2006/3/9 1:46:18
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Complete: PerformSCCAction2 at: 2006/3/9 1:46:18, returned true
Running: PerformDotNetCheck at: 2006/3/9 1:46:18
Complete: PerformDotNetCheck at: 2006/3/9 1:46:18, returned true
Running: ComponentUpdateAction at: 2006/3/9 1:46:18
Complete: ComponentUpdateAction at: 2006/3/9 1:46:23, returned true
Running: DetectLocalBootstrapAction at: 2006/3/9 1:46:23
Complete: DetectLocalBootstrapAction at: 2006/3/9 1:46:23, returned true
Running: LaunchLocalBootstrapAction at: 2006/3/9 1:46:23
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 1282
Aborting queue processing as nested installer has completed
Message pump returning: 1282

Thanks!!

|||

I'm going to move this to the SQL Setup forum.

- Mike

|||

I don't believe 1282 is a Setup error code; it's probably a Windows error code. 1282 translates to stack buffer overflow. We did fix one or two such issues a long time back. If the version of Express you're trying to install is pre-RTM then please download the RTM version or the remastered Express SP1 which should be available soon, and try again. If you're already trying with RTM then I suspect we're going to need to see the complete SQL Install logs to debug your problem.

Paul

Problem installing either sql2000 or sql2005 on vista

i have a vista basic running on my lappy,i have beeen trying to install either sql2000 or sql2005 on it for the past one month i keep getting funny errors like installshield engine has stopped working.WHile on the sql2005 the installation will exclude the database mangament studio ,etc..I had disabled the norton antivirus running to no effect.

I really need help here!

Hi,

Have you tried running it as an administrator?

Mayur Tendulkar

Microsoft Student Partner

|||

i am logged on as an administator already.

its really frustrating my web development projects

i need help!!!!!!!!!!!!!!!

|||

Hi,

Although you are logged in as an Administrator, in Windows Vista, due to enhanced security features, you need to run the setup or management studio as an administrator. Just right click the short-cut and say "Run As Administrator"

It may solve the problem.

Mayur Tendulkar

Microsoft Student Partner

|||By doing that, it still cannot resolved the problem.
Any other solution ?

Problem in Visual Basic

When I run Visual Basic Application With Back hand Is SQL SERVER DataBAse I Had Connect database with ODBC
But its very Slow What can i do
As there are many ways of doing the same thing, I would recommend that you
encapsulate your data manipulation language into a stored procedure and
make calls to that SP through your VB application. In programming, I can
assure you that short cuts kill the performance.
You can always embed the manipulation language in your VB code itself, but
to enhance performance, the recommended way (from experience) would be to
do so through Stored Procedures. However, this is not a generic statement
but should be evaluated in the light of your own application's
architecture. Have a look at this great article
http://www.sql-server-performance.co...erformance.asp
Kindly review it and analyse the same with respect to your application and
database design.
Hope this helps.
Sanchan [MSFT]
sanchans@.online.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.