Estimating Log File Size

Dear All,
Yesterday I was given a sp to calculate the size of tables
and the overall size of data files.
Is there something similar for log files, i.e. an
algorithm to calculate the size now and say 2 years time
of a log file ?
Thanks
JimJimbo
Look at sp_helpfile as well as sysfiles system table
It is hard to estimate what is your log file will be in the next two years.
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:33ff01c47ec6$197af750$a501280a@.phx.gbl...
> Dear All,
> Yesterday I was given a sp to calculate the size of tables
> and the overall size of data files.
> Is there something similar for log files, i.e. an
> algorithm to calculate the size now and say 2 years time
> of a log file ?
> Thanks
> Jim|||Probably the best way to estimate future sizes is to capture growth over
time and predict from that...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:33ff01c47ec6$197af750$a501280a@.phx.gbl...
> Dear All,
> Yesterday I was given a sp to calculate the size of tables
> and the overall size of data files.
> Is there something similar for log files, i.e. an
> algorithm to calculate the size now and say 2 years time
> of a log file ?
> Thanks
> Jim|||Hi,
You could also use the below command to get current log size and usage
dbcc sqlperf(logspace)
Estimating the log size for next 2 years will be hard.. That depends up on
the amount of batch operation and frequency in which
you perform the transaction log backup. Normally it is not required to
project Log size because the log file will be cleared once
you perform the transaction log backup.
Thanks
Hari
MCDBA
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eFgFomsfEHA.3932@.TK2MSFTNGP09.phx.gbl...
> Jimbo
> Look at sp_helpfile as well as sysfiles system table
> It is hard to estimate what is your log file will be in the next two
years.
>
> "Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
> news:33ff01c47ec6$197af750$a501280a@.phx.gbl...
> > Dear All,
> >
> > Yesterday I was given a sp to calculate the size of tables
> > and the overall size of data files.
> >
> > Is there something similar for log files, i.e. an
> > algorithm to calculate the size now and say 2 years time
> > of a log file ?
> >
> > Thanks
> > Jim
>

Estimated Execution Plan-Diff betw Seek Predicate and Predicate?

Hi experts,
I am looking at an estimated execution plan for a query that joins between 2
significantly big tables. One of the Clustered Index Seek uses has both
Predicate and Seek Predicate. What are the differences between Seek Predicate
and Predicate?
In detail, this is what I have done:
...
INNER JOIN BonusPromotion BP ON
...
AND BP.status = 'A'--Active
AND BP.validStartDate >= @.tlBeginDate AND BP.endDate <= @.tlEndDate
...
The index used is the primary key along fields.
endDate,
validStartDate,
storeID,
emEAN,
bpID
Seek predicate is along field endDate, while Predicate is along field
validStartDate. My impression of Seek predicate is very fast search
performance. So why can't the Seek predicate include BOTH endDate and
validStartDate? Therefore back to my 1st question: What are the differences
between Seek Predicate and Predicate?
Hi
What are the differences between Seek Predicate
> and Predicate?
http://blogs.msdn.com/craigfr/archive/2006/07/07/652668.aspx
..
"HardKhor" <HardKhor@.discussions.microsoft.com> wrote in message
news:4AC93D3A-69C0-4BD2-9CBD-2EEB86714040@.microsoft.com...
> Hi experts,
> I am looking at an estimated execution plan for a query that joins between
> 2
> significantly big tables. One of the Clustered Index Seek uses has both
> Predicate and Seek Predicate. What are the differences between Seek
> Predicate
> and Predicate?
> In detail, this is what I have done:
> ...
> INNER JOIN BonusPromotion BP ON
> ...
> AND BP.status = 'A' --Active
> AND BP.validStartDate >= @.tlBeginDate AND BP.endDate <= @.tlEndDate
> ...
> The index used is the primary key along fields.
> endDate,
> validStartDate,
> storeID,
> emEAN,
> bpID
> Seek predicate is along field endDate, while Predicate is along field
> validStartDate. My impression of Seek predicate is very fast search
> performance. So why can't the Seek predicate include BOTH endDate and
> validStartDate? Therefore back to my 1st question: What are the
> differences
> between Seek Predicate and Predicate?
|||HardKhor,
BP.endDate will be the only seek predicate, because you are not
searching for an exact match for that column, but for a range of values.
This means the other predicates will be evaluated by scanning the index
pages in this range of endDate.
Theoretically, it could still seek the next index column (in your case
validStartDate), but SQL Server does not support this. And even if it
did, the multiple (looped) seeks would only be useful if the preceding
column (in your case endDate) has a very low selectivity, and the index
is very shallow. Otherwise the cost of the multiple seeks would exceed
the cost of scanning the index pages.
HTH,
Gert-Jan
HardKhor wrote:
> Hi experts,
> I am looking at an estimated execution plan for a query that joins between 2
> significantly big tables. One of the Clustered Index Seek uses has both
> Predicate and Seek Predicate. What are the differences between Seek Predicate
> and Predicate?
> In detail, this is what I have done:
> ...
> INNER JOIN BonusPromotion BP ON
> ...
> AND BP.status = 'A' --Active
> AND BP.validStartDate >= @.tlBeginDate AND BP.endDate <= @.tlEndDate
> ...
> The index used is the primary key along fields.
> endDate,
> validStartDate,
> storeID,
> emEAN,
> bpID
> Seek predicate is along field endDate, while Predicate is along field
> validStartDate. My impression of Seek predicate is very fast search
> performance. So why can't the Seek predicate include BOTH endDate and
> validStartDate? Therefore back to my 1st question: What are the differences
> between Seek Predicate and Predicate?
sql

Estimated Execution Plan-Diff betw Seek Predicate and Predicate?

Hi experts,
I am looking at an estimated execution plan for a query that joins between 2
significantly big tables. One of the Clustered Index Seek uses has both
Predicate and Seek Predicate. What are the differences between Seek Predicate
and Predicate?
In detail, this is what I have done:
...
INNER JOIN BonusPromotion BP ON
...
AND BP.status = 'A' --Active
AND BP.validStartDate >= @.tlBeginDate AND BP.endDate <= @.tlEndDate
...
The index used is the primary key along fields.
endDate,
validStartDate,
storeID,
emEAN,
bpID
Seek predicate is along field endDate, while Predicate is along field
validStartDate. My impression of Seek predicate is very fast search
performance. So why can't the Seek predicate include BOTH endDate and
validStartDate? Therefore back to my 1st question: What are the differences
between Seek Predicate and Predicate?Hi
What are the differences between Seek Predicate
> and Predicate?
http://blogs.msdn.com/craigfr/archive/2006/07/07/652668.aspx
.
"HardKhor" <HardKhor@.discussions.microsoft.com> wrote in message
news:4AC93D3A-69C0-4BD2-9CBD-2EEB86714040@.microsoft.com...
> Hi experts,
> I am looking at an estimated execution plan for a query that joins between
> 2
> significantly big tables. One of the Clustered Index Seek uses has both
> Predicate and Seek Predicate. What are the differences between Seek
> Predicate
> and Predicate?
> In detail, this is what I have done:
> ...
> INNER JOIN BonusPromotion BP ON
> ...
> AND BP.status = 'A' --Active
> AND BP.validStartDate >= @.tlBeginDate AND BP.endDate <= @.tlEndDate
> ...
> The index used is the primary key along fields.
> endDate,
> validStartDate,
> storeID,
> emEAN,
> bpID
> Seek predicate is along field endDate, while Predicate is along field
> validStartDate. My impression of Seek predicate is very fast search
> performance. So why can't the Seek predicate include BOTH endDate and
> validStartDate? Therefore back to my 1st question: What are the
> differences
> between Seek Predicate and Predicate?|||HardKhor,
BP.endDate will be the only seek predicate, because you are not
searching for an exact match for that column, but for a range of values.
This means the other predicates will be evaluated by scanning the index
pages in this range of endDate.
Theoretically, it could still seek the next index column (in your case
validStartDate), but SQL Server does not support this. And even if it
did, the multiple (looped) seeks would only be useful if the preceding
column (in your case endDate) has a very low selectivity, and the index
is very shallow. Otherwise the cost of the multiple seeks would exceed
the cost of scanning the index pages.
HTH,
Gert-Jan
HardKhor wrote:
> Hi experts,
> I am looking at an estimated execution plan for a query that joins between 2
> significantly big tables. One of the Clustered Index Seek uses has both
> Predicate and Seek Predicate. What are the differences between Seek Predicate
> and Predicate?
> In detail, this is what I have done:
> ...
> INNER JOIN BonusPromotion BP ON
> ...
> AND BP.status = 'A' --Active
> AND BP.validStartDate >= @.tlBeginDate AND BP.endDate <= @.tlEndDate
> ...
> The index used is the primary key along fields.
> endDate,
> validStartDate,
> storeID,
> emEAN,
> bpID
> Seek predicate is along field endDate, while Predicate is along field
> validStartDate. My impression of Seek predicate is very fast search
> performance. So why can't the Seek predicate include BOTH endDate and
> validStartDate? Therefore back to my 1st question: What are the differences
> between Seek Predicate and Predicate?

Estimated Execution Plan-Diff betw Seek Predicate and Predicate?

Hi experts,
I am looking at an estimated execution plan for a query that joins between 2
significantly big tables. One of the Clustered Index Seek uses has both
Predicate and Seek Predicate. What are the differences between Seek Predicat
e
and Predicate?
In detail, this is what I have done:
...
INNER JOIN BonusPromotion BP ON
...
AND BP.status = 'A' --Active
AND BP.validStartDate >= @.tlBeginDate AND BP.endDate <= @.tlEndDate
...
The index used is the primary key along fields.
endDate,
validStartDate,
storeID,
emEAN,
bpID
Seek predicate is along field endDate, while Predicate is along field
validStartDate. My impression of Seek predicate is very fast search
performance. So why can't the Seek predicate include BOTH endDate and
validStartDate? Therefore back to my 1st question: What are the differences
between Seek Predicate and Predicate?Hi
What are the differences between Seek Predicate
> and Predicate?
http://blogs.msdn.com/craigfr/archi.../07/652668.aspx
.
"HardKhor" <HardKhor@.discussions.microsoft.com> wrote in message
news:4AC93D3A-69C0-4BD2-9CBD-2EEB86714040@.microsoft.com...
> Hi experts,
> I am looking at an estimated execution plan for a query that joins between
> 2
> significantly big tables. One of the Clustered Index Seek uses has both
> Predicate and Seek Predicate. What are the differences between Seek
> Predicate
> and Predicate?
> In detail, this is what I have done:
> ...
> INNER JOIN BonusPromotion BP ON
> ...
> AND BP.status = 'A' --Active
> AND BP.validStartDate >= @.tlBeginDate AND BP.endDate <= @.tlEndDate
> ...
> The index used is the primary key along fields.
> endDate,
> validStartDate,
> storeID,
> emEAN,
> bpID
> Seek predicate is along field endDate, while Predicate is along field
> validStartDate. My impression of Seek predicate is very fast search
> performance. So why can't the Seek predicate include BOTH endDate and
> validStartDate? Therefore back to my 1st question: What are the
> differences
> between Seek Predicate and Predicate?|||HardKhor,
BP.endDate will be the only seek predicate, because you are not
searching for an exact match for that column, but for a range of values.
This means the other predicates will be evaluated by scanning the index
pages in this range of endDate.
Theoretically, it could still seek the next index column (in your case
validStartDate), but SQL Server does not support this. And even if it
did, the multiple (looped) seeks would only be useful if the preceding
column (in your case endDate) has a very low selectivity, and the index
is very shallow. Otherwise the cost of the multiple seeks would exceed
the cost of scanning the index pages.
HTH,
Gert-Jan
HardKhor wrote:
> Hi experts,
> I am looking at an estimated execution plan for a query that joins between
2
> significantly big tables. One of the Clustered Index Seek uses has both
> Predicate and Seek Predicate. What are the differences between Seek Predic
ate
> and Predicate?
> In detail, this is what I have done:
> ...
> INNER JOIN BonusPromotion BP ON
> ...
> AND BP.status = 'A' --Active
> AND BP.validStartDate >= @.tlBeginDate AND BP.endDate <= @.tlEndDate
> ...
> The index used is the primary key along fields.
> endDate,
> validStartDate,
> storeID,
> emEAN,
> bpID
> Seek predicate is along field endDate, while Predicate is along field
> validStartDate. My impression of Seek predicate is very fast search
> performance. So why can't the Seek predicate include BOTH endDate and
> validStartDate? Therefore back to my 1st question: What are the difference
s
> between Seek Predicate and Predicate?

estimate of transaction log size for reindexing

Hello,
Is there anyway to estimate the transaction log files needed to reindex all
tables in a database?
I mean any formula that can be used?
regards,
meLook at how big your indexes are now. this is different depending on the
version of sql server you are on. tlog will vary depending on this size and
the type of defrag operation done.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:FF5149C0-A8B3-4B34-BFE3-D18A7E2ED15E@.microsoft.com...
> Hello,
> Is there anyway to estimate the transaction log files needed to reindex
> all
> tables in a database?
> I mean any formula that can be used?
> regards,
> me|||Hi
You have to identify what tables are defragmented and run rebuild index only
on them. Please tell us what SQL Server you are using?
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:FF5149C0-A8B3-4B34-BFE3-D18A7E2ED15E@.microsoft.com...
> Hello,
> Is there anyway to estimate the transaction log files needed to reindex
> all
> tables in a database?
> I mean any formula that can be used?
> regards,
> mesql

Estimate necessary hardware

I would like to ask some help for estimating necessary hardware for a database, I can tell you about usage profile the following:

- 2 tables, approximately 100.000 records, the tables joined in 1:1 relation, one record is approximately 500 bytes long
- typical scenario:
- select what returns 1 or zero record
- if it returned 1 record an update performed on this record
- the event logged in a third table (one insert)
- this typical scenario needs to run 100-300 times in every second

Can you tell me any advice on sizing of hardware for this? We can rely on a well designed database structure (proper indexes, etc...)

Thanx in advance

It is really a smallish database.

These are just minimal suggestions, and without more detail, they are just as good as visiting a seer.

A dual proc, dual core box, 64 bit

4GB memory -8GB would be better

64 Bit Win2003 Server

64 bit SQL Server

A SAN/NAS (or drive array) with the following LUNs/Drives: (I would go for 15K, 144GB or larger, drives.

Drive/LUN for TempDB

Drive/LUN for Log file

Drive/LUN for Database

(Separate local drive for OS and virtual memory file.)

By combining 64bit software with the fastest possible hardware you can afford, you will have planned ahead for scaling out.

Estimate DB Size: how to calculate clustered and non-clustered ind

I am doing an estimation on db size based on this link:
http://msdn.microsoft.com/library/en...asp?frame=true
How can I check which tables have clustered index and non-clustered index
fastly?
Thank you!
In addition, noting the sentence "Total Table Size = Data Space Used +
Nonclustered Index + Clustered Index + ...n"
What are the other "...n" factors and how significant (can measure to %?)
are these factors affecting the result?
Many thanks!
|||Get the script I posted at the following link.
http://www.sqlservercentral.com/colu...xdetection.asp
"Jackie Chow" wrote:

> I am doing an estimation on db size based on this link:
> http://msdn.microsoft.com/library/en...asp?frame=true
> How can I check which tables have clustered index and non-clustered index
> fastly?
> Thank you!
|||Check for fragmentation using DBCC SHOWCONTIG.
I will send you a document explaining the use and the Excel Document.
Regards
Andre
"Jackie Chow" wrote:

> I am doing an estimation on db size based on this link:
> http://msdn.microsoft.com/library/en...asp?frame=true
> How can I check which tables have clustered index and non-clustered index
> fastly?
> Thank you!

Errors Upsizing an access 2002 Database to SQL server 2005

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

MrKim wrote:

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

Regrading the 4 tables that fail; Are you sure you don't have other errors? 'Table was skipped, or export failed' Is not clear enough

The other message is just a warning telling you that at some point a certain column in the dataflow is not used anymore; the intention is to suggest to remove it if it is no necessary....only you can answer that question.

|||

No, that is is. When you use the Access upsizing wizard that is all the info it gives on the report. More useful maybe is the error messages given when trying to import the data through SQL server. I did finally import the data. There were bad dates which had to be fixed first.

I did it by turning of the SQL atuonumber/Prim Key, then writing a progam to import one record at a time, and noting the ID on the ones that fail - they all had bad dates.

Errors Upsizing an access 2002 Database to SQL server 2005

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

MrKim wrote:

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

Regrading the 4 tables that fail; Are you sure you don't have other errors? 'Table was skipped, or export failed' Is not clear enough

The other message is just a warning telling you that at some point a certain column in the dataflow is not used anymore; the intention is to suggest to remove it if it is no necessary....only you can answer that question.

|||

No, that is is. When you use the Access upsizing wizard that is all the info it gives on the report. More useful maybe is the error messages given when trying to import the data through SQL server. I did finally import the data. There were bad dates which had to be fixed first.

I did it by turning of the SQL atuonumber/Prim Key, then writing a progam to import one record at a time, and noting the ID on the ones that fail - they all had bad dates.

sql

Errors in the OLAP storage engine:

Errors in the OLAP storage engine: I am new to Analysis Services. I created a cube using Analysis Services 2005 with 3 fact tables and five dimensions. All the dimensions processed successfully apart from one dimension table which gave the following error. The attribute key cannot be found: Table:
dbo_Severity, Column:
SeverityCode, Value: 6

When i try to deploy the cube, I also fail. Is it because of this dimension table in which the attribute key can not be found.

<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Object>
<DatabaseID>AnalysisServices</DatabaseID>
<CubeID>MSCPROJECTDSV</CubeID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Processing Dimension 'Allergy' failed.
Start time: 6/14/2006 6:04:32 PM; End time: 6/14/2006 6:05:00 PM; Duration: 0:00:28
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/14/2006 6:04:32 PM; End time: 6/14/2006 6:04:32 PM; Duration: 0:00:00
Processing Dimension Attribute 'Allergy Name' completed successfully. 7 rows have been read.
Start time: 6/14/2006 6:04:32 PM; End time: 6/14/2006 6:04:41 PM; Duration: 0:00:09
SQL queries 1
SELECT
DISTINCT
[dbo_Allergy].[AllergyName] AS [dbo_AllergyAllergyName0_0]
FROM [dbo].[Allergy] AS [dbo_Allergy]
Processing Dimension Attribute 'Severity Name' completed successfully. 6 rows have been read.
Start time: 6/14/2006 6:04:32 PM; End time: 6/14/2006 6:04:41 PM; Duration: 0:00:09
SQL queries 1
SELECT
DISTINCT
[dbo_Severity].[SeverityName] AS [dbo_SeveritySeverityName0_0]
FROM [dbo].[Severity] AS [dbo_Severity]
Processing Dimension Attribute 'Severity' completed successfully. 6 rows have been read.
Start time: 6/14/2006 6:04:41 PM; End time: 6/14/2006 6:04:51 PM; Duration: 0:00:10
SQL queries 1
SELECT
DISTINCT
[dbo_Severity].[SeverityCode] AS [dbo_SeveritySeverityCode0_0],[dbo_Severity].[SeverityName] AS [dbo_SeveritySeverityName0_1]
FROM [dbo].[Severity] AS [dbo_Severity]
Processing Dimension Attribute 'Allergy' failed. 1 rows have been read.
Start time: 6/14/2006 6:04:51 PM; End time: 6/14/2006 6:05:00 PM; Duration: 0:00:09
SQL queries 1
SELECT
DISTINCT
[dbo_Allergy].[AllergyCode] AS [dbo_AllergyAllergyCode0_0],[dbo_Allergy].[AllergyName] AS [dbo_AllergyAllergyName0_1],[dbo_Allergy].[SeverityCode] AS [dbo_AllergySeverityCode0_2]
FROM [dbo].[Allergy] AS [dbo_Allergy]
Error Messages 2
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Severity, Column: SeverityCode, Value: 6. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Record: 7.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Severity, Column: SeverityCode, Value: 6. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Record: 7. 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 the 'Allergy' attribute of the 'Allergy' dimension from the 'AnalysisServices' database was being processed.
Errors and Warnings from Response
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 the 'Allergy' attribute of the 'Allergy' dimension from the 'AnalysisServices' database was being processed.
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: The attribute key cannot be found: Table: dbo_Severity, Column: SeverityCode, Value: 6.
Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Record: 7.

Please help me out.

Regards,

Ronaldlee

Looks like the problem is in the relational database.

Looks like you have a record in the Allergy table with a value in the SeverirtyCode column that does not exist in the Severity table.

Try first sending a SQL query AS sends for the Severity attribute

Then send a SQL query for the Allergy attribute and see which value appears in the SeverityCode column and does not appear in the Severity table.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanx a Lot.

You are the man.

Ronald

|||

I have made all the necassary changes,

I have three fact tables in Cube, two of them process successfully, but one doesnot execute successfully.

<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Object>
<DatabaseID>AnalysisServices</DatabaseID>
<CubeID>MSCPROJECTDVS</CubeID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Processing Cube 'MSCPROJECTDVS' failed.
Start time: 6/15/2006 12:31:24 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:01
Processing Measure Group 'Medication Allergy' completed successfully.
Start time: 6/15/2006 12:31:24 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:01
Processing Partition 'Medication Allergy' completed successfully.
Start time: 6/15/2006 12:31:25 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:00
SQL queries 1
SELECT [dbo_MedicationAllergy].[dbo_MedicationAllergy0_0] AS [dbo_MedicationAllergy0_0],[dbo_MedicationAllergy].[dbo_MedicationAllergyMedicineCode0_1] AS [dbo_MedicationAllergyMedicineCode0_1]
FROM
(

SELECT 1 AS [dbo_MedicationAllergy0_0],[MedicineCode] AS [dbo_MedicationAllergyMedicineCode0_1]
FROM [dbo].[MedicationAllergy]
)
AS [dbo_MedicationAllergy]
Processing Measure Group 'Prescription' failed.
Start time: 6/15/2006 12:31:24 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:01
Processing Partition 'Prescription' failed.
Start time: 6/15/2006 12:31:25 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:00
SQL queries 1
SELECT [dbo_Prescription].[Quantity] AS [dbo_PrescriptionQuantity0_0],[dbo_Prescription].[Price] AS [dbo_PrescriptionPrice0_1],[dbo_Prescription].[MedicineCode] AS [dbo_PrescriptionMedicineCode0_2],[dbo_Prescription].[PatientId] AS [dbo_PrescriptionPatientId0_3],[dbo_Prescription].[Date] AS [dbo_PrescriptionDate0_4]
FROM [dbo].[Prescription] AS [dbo_Prescription]
Error Messages 2
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Prescription, Column: PatientId, Value: 10001; Table: dbo_Prescription, Column: Date, Value: 2/9/2000. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: PatientId - Date of Dimension: Return Visit from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Prescription, Partition: Prescription, Record: 1.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Prescription, Column: PatientId, Value: 10001; Table: dbo_Prescription, Column: Date, Value: 2/9/2000. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: PatientId - Date of Dimension: Return Visit from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Prescription, Partition: Prescription, 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 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Processing Measure Group 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:31:24 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:01
Processing Partition 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:31:25 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:00
SQL queries 1
SELECT [dbo_PatientDiagnosis].[dbo_PatientDiagnosis0_0] AS [dbo_PatientDiagnosis0_0],[dbo_PatientDiagnosis].[dbo_PatientDiagnosisDiagnosisCode0_1] AS [dbo_PatientDiagnosisDiagnosisCode0_1],[dbo_PatientDiagnosis].[dbo_PatientDiagnosisPatientId0_2] AS [dbo_PatientDiagnosisPatientId0_2],[dbo_Diagnosis_3].[MedicineCode] AS [dbo_DiagnosisMedicineCode2_0]
FROM
(

SELECT 1 AS [dbo_PatientDiagnosis0_0],[DiagnosisCode] AS [dbo_PatientDiagnosisDiagnosisCode0_1],[PatientId] AS [dbo_PatientDiagnosisPatientId0_2]
FROM [dbo].[PatientDiagnosis]
)
AS [dbo_PatientDiagnosis],[dbo].[Diagnosis] AS [dbo_Diagnosis_3]
WHERE
(

(
[dbo_PatientDiagnosis].[dbo_PatientDiagnosisDiagnosisCode0_1] = [dbo_Diagnosis_3].[DiagnosisCode]
)
)
Errors and Warnings from Response
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 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
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: The attribute key cannot be found: Table: dbo_Prescription, Column: PatientId, Value: 10001; Table: dbo_Prescription, Column: Date, Value: 2/9/2000.
Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: PatientId - Date of Dimension: Return Visit from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Prescription, Partition: Prescription, Record: 1.

Is there any connected to my attributes in the relational data base tables

|||

I have solved the problem though i am still getting some error.

Now it is the MedicationAllergy Fact Table giving me errors.

<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Object>
<DatabaseID>AnalysisServices</DatabaseID>
<CubeID>MSCPROJECTDVS</CubeID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Processing Cube 'MSCPROJECTDVS' failed.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
Processing Measure Group 'Prescription' completed successfully.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
Processing Partition 'Prescription' completed successfully.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
Processing Measure Group 'Medication Allergy' failed.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
Processing Partition 'Medication Allergy' failed. 1 rows have been read.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
SQL queries 1
SELECT [dbo_MedicationAllergy].[dbo_MedicationAllergy0_0] AS [dbo_MedicationAllergy0_0],[dbo_MedicationAllergy].[dbo_MedicationAllergyMedicineCode0_1] AS [dbo_MedicationAllergyMedicineCode0_1]
FROM
(

SELECT 1 AS [dbo_MedicationAllergy0_0],[MedicineCode] AS [dbo_MedicationAllergyMedicineCode0_1]
FROM [dbo].[MedicationAllergy]
)
AS [dbo_MedicationAllergy]
Error Messages 2
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_MedicationAllergy, Column: MedicineCode, Value: 7. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Medication Allergy, Partition: Medication Allergy, Record: 6.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_MedicationAllergy, Column: MedicineCode, Value: 7. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Medication Allergy, Partition: Medication Allergy, Record: 6. 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 'Medication Allergy' partition of the 'Medication Allergy' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Processing Measure Group 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
Processing Partition 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
Errors and Warnings from Response
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 'Medication Allergy' partition of the 'Medication Allergy' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
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 high-level relational engine. The database operation was cancelled because of an earlier failure.
Errors in the OLAP storage engine: An error occurred while processing the 'Patient Diagnosis' partition of the 'Patient Diagnosis' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Errors in the OLAP storage engine: An error occurred while processing the 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_MedicationAllergy, Column: MedicineCode, Value: 7.
Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Medication Allergy, Partition: Medication Allergy, Record: 6.

Ronald

|||

In your fact table you have keys that dont appear in the dimension table.

I think in the dbo_MedicationAllergy fact table, MedicineCode column in has more keys than the Allergy dimension.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Errors in scripting from Enterprise Manager

Has anybody ever had problems with strange characters appearing in the names
of tables or constraints when scripting a database? I'm on SQL Serv2000 +
sp3a and I've never known this happen before.
Philyou might want to try the free scripter (also does data) from Innovartis.
http://www.innovartis.co.uk/Evaluation.aspx
"Philip Turtle" wrote:

> Has anybody ever had problems with strange characters appearing in the nam
es
> of tables or constraints when scripting a database? I'm on SQL Serv2000 +
> sp3a and I've never known this happen before.
> Phil
>
>

Errors in scripting from Enterprise Manager

Has anybody ever had problems with strange characters appearing in the names
of tables or constraints when scripting a database? I'm on SQL Serv2000 +
sp3a and I've never known this happen before.
Phil
you might want to try the free scripter (also does data) from Innovartis.
http://www.innovartis.co.uk/Evaluation.aspx
"Philip Turtle" wrote:

> Has anybody ever had problems with strange characters appearing in the names
> of tables or constraints when scripting a database? I'm on SQL Serv2000 +
> sp3a and I've never known this happen before.
> Phil
>
>

Errors in scripting from Enterprise Manager

Has anybody ever had problems with strange characters appearing in the names
of tables or constraints when scripting a database? I'm on SQL Serv2000 +
sp3a and I've never known this happen before.
Philyou might want to try the free scripter (also does data) from Innovartis.
http://www.innovartis.co.uk/Evaluation.aspx
"Philip Turtle" wrote:
> Has anybody ever had problems with strange characters appearing in the names
> of tables or constraints when scripting a database? I'm on SQL Serv2000 +
> sp3a and I've never known this happen before.
> Phil
>
>

Errors in High-level Relational Engine and OLAP storage Engine

Hi all,,

Could someone help me out and explain to me why my two fact tables process successfully but the process still fails when i try to process the cube.

This is the detailed error message.

Ronald

<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Object>
<DatabaseID>FirstCube</DatabaseID>
<CubeID>MSCPROJECT</CubeID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Processing Cube 'MSCPROJECT' completed successfully.
Start time: 6/20/2006 1:52:34 PM; End time: 6/20/2006 1:52:35 PM; Duration: 0:00:01
Processing Measure Group 'Patient Diagnosis' completed successfully.
Start time: 6/20/2006 1:52:35 PM; End time: 6/20/2006 1:52:35 PM; Duration: 0:00:00
Processing Partition 'Patient Diagnosis' completed successfully.
Start time: 6/20/2006 1:52:35 PM; End time: 6/20/2006 1:52:35 PM; Duration: 0:00:00
Processing Measure Group 'Prescription' completed successfully.
Start time: 6/20/2006 1:52:35 PM; End time: 6/20/2006 1:52:35 PM; Duration: 0:00:00
Processing Partition 'Prescription' completed successfully.
Start time: 6/20/2006 1:52:35 PM; End time: 6/20/2006 1:52:35 PM; Duration: 0:00:00
Errors and Warnings from Response
Errors in the high-level relational engine. The data source view does not contain a definition for the 'dbo_Prescription' table or view. The Source property may not have been set.
Errors in the OLAP storage engine: An error occurred while processing the 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECT' cube from the FirstCube database.
Errors in the high-level relational engine. The database operation was cancelled because of an earlier failure.
Errors in the OLAP storage engine: An error occurred while processing the 'Patient Diagnosis' partition of the 'Patient Diagnosis' measure group for the 'MSCPROJECT' cube from the FirstCube database.

Check your DSV - data source view.
Looks like your DSV is missing 'dbo_Prescription' table.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

It looks like as if I have dbo_Prescription table in my data source View.

I will check it out tomorrow morning and i will get back to you.

Thank you for your time.

Ronald

|||

Hi Edward, In my data source view i have the dbo.Prescription table not dbo_Prescription.

Do these namings really matter.

Ronald

|||

The naming is really important. Without you specifying names correctly Analysis Server has no idea how to construct a valid SQL query.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Edward,

In My data source view, I have the dbo.Prescription table. You know dbo.Prescription and dbo.PatientDiagnosis are my fact tables. I have failed to understand this since i have these two tables in my data source view.

Please help out.

Is this connected with SQL SERVER 2005 service pack1.

Ronald

Below is the same error i get when i process the cube.

<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Object>
<DatabaseID>Analysis Services Project1</DatabaseID>
<CubeID>MSCPROJECT</CubeID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Processing Dimension 'Initial Visit' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
Processing Dimension Attribute 'Physician Id' completed successfully. 8 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_InitialVisit].[PhysicianId] AS [dbo_InitialVisitPhysicianId0_0]
FROM [dbo].[InitialVisit] AS [dbo_InitialVisit]
Processing Dimension Attribute 'Nurse ID' completed successfully. 7 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_InitialVisit].[NurseID] AS [dbo_InitialVisitNurseID0_0]
FROM [dbo].[InitialVisit] AS [dbo_InitialVisit]
Processing Dimension Attribute 'Initial Visit' completed successfully. 51 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_InitialVisit].[PatientId] AS [dbo_InitialVisitPatientId0_0],[dbo_InitialVisit].[Date] AS [dbo_InitialVisitDate0_1],[dbo_InitialVisit].[PhysicianId] AS [dbo_InitialVisitPhysicianId0_2],[dbo_InitialVisit].[NurseID] AS [dbo_InitialVisitNurseID0_3]
FROM [dbo].[InitialVisit] AS [dbo_InitialVisit]
Processing Dimension 'Project' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
Processing Dimension Attribute 'Project Name' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Project].[ProjectName] AS [dbo_ProjectProjectName0_0]
FROM [dbo].[Project] AS [dbo_Project]
Processing Dimension Attribute 'Project' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Project].[ProjectId] AS [dbo_ProjectProjectId0_0],[dbo_Project].[ProjectName] AS [dbo_ProjectProjectName0_1]
FROM [dbo].[Project] AS [dbo_Project]
Processing Dimension 'Medicine Type' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
Processing Dimension Attribute 'Name' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_MedicineType].[Name] AS [dbo_MedicineTypeName0_0]
FROM [dbo].[MedicineType] AS [dbo_MedicineType]
Processing Dimension Attribute 'Medicine Type' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_MedicineType].[MedicineTypeCode] AS [dbo_MedicineTypeMedicineTypeCode0_0],[dbo_MedicineType].[Name] AS [dbo_MedicineTypeName0_1]
FROM [dbo].[MedicineType] AS [dbo_MedicineType]
Processing Dimension 'Patient' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
Processing Dimension Attribute 'DateOfBirth' completed successfully. 49 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Patient].[DateOfBirth] AS [dbo_PatientDateOfBirth0_0]
FROM [dbo].[Patient] AS [dbo_Patient]
Processing Dimension Attribute 'Gender' completed successfully. 3 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Patient].[Gender] AS [dbo_PatientGender0_0]
FROM [dbo].[Patient] AS [dbo_Patient]
Processing Dimension Attribute 'PatientId' completed successfully. 50 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Patient].[PatientId] AS [dbo_PatientPatientId0_0],[dbo_Patient].[DateOfBirth] AS [dbo_PatientDateOfBirth0_1],[dbo_Patient].[Gender] AS [dbo_PatientGender0_2]
FROM [dbo].[Patient] AS [dbo_Patient]
Processing Hierarchy 'PatientId - DateOfBirth - Gender' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension 'Diagnosis' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension Attribute 'Diagnosis Name' completed successfully. 5 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Diagnosis].[Diagnosis name] AS [dbo_DiagnosisDiagnosis_x0020_name0_0]
FROM [dbo].[Diagnosis] AS [dbo_Diagnosis]
Processing Dimension Attribute 'Description' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Diagnosis].[Description] AS [dbo_DiagnosisDescription0_0]
FROM [dbo].[Diagnosis] AS [dbo_Diagnosis]
Processing Dimension Attribute 'Diagnosis' completed successfully. 5 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Diagnosis].[DiagnosisCode] AS [dbo_DiagnosisDiagnosisCode0_0],[dbo_Diagnosis].[Diagnosis name] AS [dbo_DiagnosisDiagnosis_x0020_name0_1],[dbo_Diagnosis].[Description] AS [dbo_DiagnosisDescription0_2]
FROM [dbo].[Diagnosis] AS [dbo_Diagnosis]
Processing Dimension 'Medical Provider' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension Attribute 'Name' completed successfully. 15 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[Name] AS [dbo_MedicalProviderName0_0]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension Attribute 'Gender' completed successfully. 3 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[Gender] AS [dbo_MedicalProviderGender0_0]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension Attribute 'Indicator Nurseor Physician' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[IndicatorNurseorPhysician] AS [dbo_MedicalProviderIndicatorNurseorPhysician0_0]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension Attribute 'Physician Id' completed successfully. 9 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[PhysicianId] AS [dbo_MedicalProviderPhysicianId0_0]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension Attribute 'Nurse Id' completed successfully. 9 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[NurseId] AS [dbo_MedicalProviderNurseId0_0]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension Attribute 'Medical Provider' completed successfully. 15 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[MedicalProviderId] AS [dbo_MedicalProviderMedicalProviderId0_0],[dbo_MedicalProvider].[Name] AS [dbo_MedicalProviderName0_1],[dbo_MedicalProvider].[Gender] AS [dbo_MedicalProviderGender0_2],[dbo_MedicalProvider].[IndicatorNurseorPhysician] AS [dbo_MedicalProviderIndicatorNurseorPhysician0_3],[dbo_MedicalProvider].[PhysicianId] AS [dbo_MedicalProviderPhysicianId0_4],[dbo_MedicalProvider].[NurseId] AS [dbo_MedicalProviderNurseId0_5]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension 'Allergy' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension Attribute 'Allergy Name' completed successfully. 6 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Allergy].[AllergyName] AS [dbo_AllergyAllergyName0_0]
FROM [dbo].[Allergy] AS [dbo_Allergy]
Processing Dimension Attribute 'Allergy' completed successfully. 6 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Allergy].[AllergyCode] AS [dbo_AllergyAllergyCode0_0],[dbo_Allergy].[AllergyName] AS [dbo_AllergyAllergyName0_1]
FROM [dbo].[Allergy] AS [dbo_Allergy]
Processing Dimension 'Medicine' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension Attribute 'Name' completed successfully. 19 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Medicine].[Name] AS [dbo_MedicineName0_0]
FROM [dbo].[Medicine] AS [dbo_Medicine]
Processing Dimension Attribute 'Medicine' completed successfully. 20 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Medicine].[MedicineCode] AS [dbo_MedicineMedicineCode0_0],[dbo_Medicine].[Name] AS [dbo_MedicineName0_1]
FROM [dbo].[Medicine] AS [dbo_Medicine]
Processing Dimension 'Services' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
Processing Dimension Attribute 'Service Title' completed successfully. 36 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Services].[Service_Title] AS [dbo_ServicesService_Title0_0]
FROM [dbo].[Services] AS [dbo_Services]
Processing Dimension Attribute 'Service Order' completed successfully. 18 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Services].[Service_Order] AS [dbo_ServicesService_Order0_0]
FROM [dbo].[Services] AS [dbo_Services]
Processing Dimension Attribute 'Services' completed successfully. 36 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Services].[ServiceId] AS [dbo_ServicesServiceId0_0],[dbo_Services].[Service_Title] AS [dbo_ServicesService_Title0_1],[dbo_Services].[Service_Order] AS [dbo_ServicesService_Order0_2]
FROM [dbo].[Services] AS [dbo_Services]
Processing Dimension 'Return Visit' completed successfully.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:23 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
Processing Dimension Attribute 'Physician Id' completed successfully. 8 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_ReturnVisit].[PhysicianId] AS [dbo_ReturnVisitPhysicianId0_0]
FROM [dbo].[ReturnVisit] AS [dbo_ReturnVisit]
Processing Dimension Attribute 'Nurse Id' completed successfully. 9 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_ReturnVisit].[NurseId] AS [dbo_ReturnVisitNurseId0_0]
FROM [dbo].[ReturnVisit] AS [dbo_ReturnVisit]
Processing Dimension Attribute 'Time Start' completed successfully. 11 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_ReturnVisit].[TimeStart] AS [dbo_ReturnVisitTimeStart0_0]
FROM [dbo].[ReturnVisit] AS [dbo_ReturnVisit]
Processing Dimension Attribute 'Time End' completed successfully. 22 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_ReturnVisit].[TimeEnd] AS [dbo_ReturnVisitTimeEnd0_0]
FROM [dbo].[ReturnVisit] AS [dbo_ReturnVisit]
Processing Dimension Attribute 'Return Visit' completed successfully. 50 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_ReturnVisit].[PatientId] AS [dbo_ReturnVisitPatientId0_0],[dbo_ReturnVisit].[Date] AS [dbo_ReturnVisitDate0_1],[dbo_ReturnVisit].[PhysicianId] AS [dbo_ReturnVisitPhysicianId0_2],[dbo_ReturnVisit].[NurseId] AS [dbo_ReturnVisitNurseId0_3],[dbo_ReturnVisit].[TimeStart] AS [dbo_ReturnVisitTimeStart0_4],[dbo_ReturnVisit].[TimeEnd] AS [dbo_ReturnVisitTimeEnd0_5]
FROM [dbo].[ReturnVisit] AS [dbo_ReturnVisit]
Processing Dimension 'Severity' completed successfully.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:23 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
Processing Dimension Attribute 'Severity Name' completed successfully. 6 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:23 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Severity].[SeverityName] AS [dbo_SeveritySeverityName0_0]
FROM [dbo].[Severity] AS [dbo_Severity]
Processing Dimension Attribute 'Severity' completed successfully. 6 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:23 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Severity].[SeverityCode] AS [dbo_SeveritySeverityCode0_0],[dbo_Severity].[SeverityName] AS [dbo_SeveritySeverityName0_1]
FROM [dbo].[Severity] AS [dbo_Severity]
Processing Cube 'MSCPROJECT' completed successfully.
Start time: 6/21/2006 11:59:23 AM; End time: 6/21/2006 11:59:24 AM; Duration: 0:00:01
Processing Measure Group 'Patient Diagnosis' completed successfully.
Start time: 6/21/2006 11:59:23 AM; End time: 6/21/2006 11:59:24 AM; Duration: 0:00:01
Processing Partition 'Patient Diagnosis' completed successfully.
Start time: 6/21/2006 11:59:23 AM; End time: 6/21/2006 11:59:24 AM; Duration: 0:00:01
Processing Measure Group 'Prescription' completed successfully.
Start time: 6/21/2006 11:59:23 AM; End time: 6/21/2006 11:59:24 AM; Duration: 0:00:01
Processing Partition 'Prescription' completed successfully.
Start time: 6/21/2006 11:59:23 AM; End time: 6/21/2006 11:59:24 AM; Duration: 0:00:01
Errors and Warnings from Response
Errors in the high-level relational engine. The data source view does not contain a definition for the 'dbo_Prescription' table or view. The Source property may not have been set.
Errors in the OLAP storage engine: An error occurred while processing the 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECT' cube from the Analysis Services Project1 database.
Errors in the high-level relational engine. The database operation was cancelled because of an earlier failure.
Errors in the OLAP storage engine: An error occurred while processing the 'Patient Diagnosis' partition of the 'Patient Diagnosis' measure group for the 'MSCPROJECT' cube from the Analysis Services Project1 database.

Error: unable to retrieve column information from the data source

Hi,

I am trying to set up a data flow task. The source is "SQL Command" which is
a stored procedure. The proc has a few temp tables that it outputs the final
resultset from. When I hit preview in the ole db source editor, I see the
right output. When I select the "Columns" tab on the right, the "Available
External Column List" is empty. Why don't the column names appear? What is
the work around to get the column mappings to work b/w source and
destination in this scenario.

In DTS previously, you could "fool" the package by first compiling the
stored procedure with hardcoded column names and dummy values, creating and
saving the package and finally changing the procedure back to the actual
output. As long as the columns remained the same, all would work.
Thats not working for me in SSIS.

Thanks in advance.
Asim.

Anyone?

|||I am having the same problem. I assume it is because the stored procedure I am using is long running (1min 20s) The designer looks like it starts to run the sproc to get the metadata, but then gives up after 15 or 30 seconds. Any solutions?|||

Hi,

If your final select statement is for a temporary table, u will get this problem. Use table variable or actual table instead of temp table.

|||

Yes, I figured out a solution. Basically create a hard coded resultset (select stmt) at the top of the procedure with the same columns as the actual resultset.

That did it for me.

Asim.

|||

Ok, that solution does not work. By adding the header, the package compiles and runs, but the row from the header is inserted in the destination, not from the (actual) second resultset. So I am back to square one.

Can anyone please help.

Asim.

|||This solved my problem. However, it was not enough to change the last select from a temp table to table variable. I had to change all occurences of temp tables to table variables. I also found that it sped up my query by a factor of 16x from 1min 20s to 5s.|||My workaround is to create output columns that are being returned by the query manually.

Error: Timeout Expired

I have an Update stored procedure that is used to update four tables at the same time. The issue is that it works perfect when i run the application in local server,but when i upload the application on to the server that is located in U.S, it gives an error "System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."

I think the sqlCommand is timing out and the value is not returned. Is there a workaround to this issue? What could be the reason for this?

Any ideas.. Please help..

Do any of the tables you are tying to update have indexes on them? If not, adding indexes might help.

Ryan

|||How long will it takes to complete update on the local? Try to set the SqlCommand.CommandTimeout (default to 30 secs) to a larger value, as well as the SqlConnection.ConnectionTimeout.|||I haven't given any indexes.. But usually indexes are helpful when you perform a search on the data , rt? Will it help if while i update a table.. Im not sure.. could you give me more info on this? pls..|||I tried specifying the CommandTimeout to a larger value (4 minutes) and it still times out.. Is there a diff approach?|||

Developer_.NET:

I haven't given any indexes.. But usually indexes are helpful when you perform a search on the data , rt? Will it help if while i update a table.. Im not sure.. could you give me more info on this? pls..

Seehttp://www.odetocode.com/Articles/70.aspx.

Ryan

Error: SQL server failed to communicate with Full-Text Service

Hello,

I've enabled full-text indexing on one of my tables, and the following query used to work:

SELECT *
FROM TempAttachment
WHERE CONTAINS(attachment, 'text')

However, now I get the following error:

Msg 9955, Level 16, State 1, Line 1SQL server failed to communicate with Full-Text Service (msftesql). The system administrator must make sure that same service account is used for both services and the service account has the permission to auto start the full-text service.

I've checked the configuration and verified that both accounts are the same. I've restarted the services, and tried rebooting, and still no luck. I did a search on this error, and found this page from MSDN, which doesn't help me much: http://msdn2.microsoft.com/en-us/library/aa337365.aspx.

Has anybody come across this before? Any help would be greatly appreciated!

Just want to be sure, which 2 services' account did you update?

|||

Thanks for your reply.

I didn't update any settings. I went to SQL Server Configuration Manager and selected "SQL Server 2005 Services" on the left menu. On the right side, I right-clicked and viewed properties of "SQL Server FullText Search" and "SQL Server". They both have the same log-on account (Local System).

This morning, I tried to back up my database and got a clue about this issue when the back up failed. It says "The backup of full-text catalog is not permitted because it is not online. Check errorlog file for the reason that full-text catalog became offline and bring it online..." I searched the error logs for my table name and didn't find anything (other than the backup failing because of it). Any ideas? Thanks.

|||

Okay, I found the problem!

Somehow, I didn't have permissions to the directory where the full-text data was being stored. (I'm unclear on how this happened - maybe someone else can reply if they have an idea?)

First, run the following query to find the path to your full-text catalog:

SELECT * FROM sysfulltextcatalogs

Then check the permissions for the directory or directories identified.