Professional edition vs. SQL Server

Hi
i am using the professional edition (since i'm running it on a windows 2000 pro machine), but i wanted to know what performance gains there are between the pro. edition vs. the real sql server that would be run on a windows 2000 advanced server machine
currently i'm trying to write/query an enormous amount of data. the bottleneck is now the database, but before i go through the trouble of rebuilding a maching with 2000 server, i wanted to know what the "gains" were and if it would even be worth the time to do this
Thanks
mikeOOPS... i meant PERSONAL and not professional edition.|||Personal Edition has the same performance delimiter as MSDE, i.e. 25
concurrent users is really pushing it. It has no limit on the database size
though, but you need a full SQL Server license to actually be allowed to use
Personal Edition on a separate machine. You can't use personal Edition
separately. I.e. what you are doing probably violates the licensing
agreement.
--
Jacco Schalkwijk
SQL Server MVP
"mike" <anonymous@.discussions.microsoft.com> wrote in message
news:23137F31-435A-4FF0-9AAB-9ACC5190E48B@.microsoft.com...
> OOPS... i meant PERSONAL and not professional edition.

Product level is insufficient error

Configuration: Windows XP Pro with SQL 2005 Workgroup Sp2

Hi, we have a package that runs fine in BI Studio but fails with the following error when executing it using DTExec.

Code: 0xC00470FE
Source: Data Flow Task DTS.Pipeline
Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Derived Column" (10660).

The package imports a CSV into a table mapping some columns. The MSDN article at http://msdn2.microsoft.com/en-us/library/ms143761.aspx describes features supported by different versions.

The article says OLE DB source/destination adapters are supported in WG edition but a couple of lines later seems to imply that all source/destination adapters are not supported in WG.

Could you clarify whether stuff like import of a csv into a table with some column mappings should work in WG edition? Also if we have a legacy SQL 2K package doing the same thing, will that work in WG edition? Thx.

Features/Integration Services Enhancements EE (32-bit) DE (32-bit) EE (64-bit) DE (64-bit) SE (32-bit) WG (32-bit) SSE (32-bit) SSEA (32-bit) SE (64-bit)

SQL Server Import and Export Wizard and supporting connections, source and destination adapters, and tasks

Yes

Yes

Yes

No

Yes

Execute SQL Task

Yes

Yes

Yes

No

Yes

OLE DB Source and Destination Adapters

Yes

Yes

Yes

No

Yes

SSIS command prompt tools

Yes

Yes

Yes

No

Yes

SSIS Package Designer

Yes

Yes

Yes

No

Yes

Legacy support for DTS packages

Yes

Yes

Yes

Yes

Yes

SSIS Service

Yes

Yes

No

No

Yes

All other source and destination adapters, tasks, and transformations, except for those listed below

Yes

Yes

No

No

Yes

You might want to be sure that you have actually installed the full SSIS client.|||

As Phil wrote, most likely you've only Workstation components installed and need to install full SSIS.

See Books Online and my blog for details:

http://msdn2.microsoft.com/en-US/library/aa337371.aspx

http://blogs.msdn.com/michen/archive/2006/11/11/ssis-product-level-is-insufficient.aspx

ProClarity and Windows Vista

I have recently moved over to Windows Vista Business Edition and have issues
with the installation of ProClarity 6.1 (also with v6.3).
Having installed ProClarity, I find that it fails to launch. All I get is a
Windows message stating that it has stopped working.
Has anyone else had this issue and found a resolution?
Hello.
Did you mean ProClarity Desktop? There is hotfix for this :
http://www.microsoft.com/downloads/details.aspx?FamilyID=7a65e401-b298-46c6-a370-ce9d65d4fb21&DisplayLang=en
And checks. As I know, hotfix for ProClarity Analytics released as well.
+--
Kenial.GhostOnNetwork.
Darren wrote:
> I have recently moved over to Windows Vista Business Edition and have issues
> with the installation of ProClarity 6.1 (also with v6.3).
> Having installed ProClarity, I find that it fails to launch. All I get is a
> Windows message stating that it has stopped working.
> Has anyone else had this issue and found a resolution?
sql

ProClarity and Windows Vista

I have recently moved over to Windows Vista Business Edition and have issues
with the installation of ProClarity 6.1 (also with v6.3).
Having installed ProClarity, I find that it fails to launch. All I get is a
Windows message stating that it has stopped working.
Has anyone else had this issue and found a resolution?Hello.
Did you mean ProClarity Desktop? There is hotfix for this :
http://www.microsoft.com/downloads/...&DisplayLang=en
And checks. As I know, hotfix for ProClarity Analytics released as well.
+--
Kenial.GhostOnNetwork.
Darren wrote:
> I have recently moved over to Windows Vista Business Edition and have issu
es
> with the installation of ProClarity 6.1 (also with v6.3).
> Having installed ProClarity, I find that it fails to launch. All I get is
a
> Windows message stating that it has stopped working.
> Has anyone else had this issue and found a resolution?

Processor Utilization

Hi
I am running SQL Server 2000 on a 2 processor system (Windows 2003
Standard). I regularily run large queries. When I run the queries the CPU
utilization is consitantly around 11%.
It appears as if something is limiting SQL Server to 11% CPU per
process/query. I have verified that its not I/O bound.
The Processor properties are set as follows:
- All 2 processors are checked in Processor Control
- "Maximum worker threads" is set to 255
- "Boost SQL Server priority on Windows" is not checked
- "Use Windows NT fibres" is checked
- "Use all available processors" is checked
Why is the CPU not fully utilized? What does "Boost SQL Server priority on
Windows" do?
Any assistance would be greatly appreciated
Thanks
Hi
You may want to check the boost priority option and not use fibres (as
fibres can cause other problems). You could also try using the MAXDOP hint to
only use one processor.
Monitor context switches to see if there is an excessive number before
considering using fibres. Ken Hendersons book The Gurus Guide to SQL Server
Architecture and Internals ISBN 0201700476 has a good section on this.
John
"Macisu" wrote:

> Hi
> I am running SQL Server 2000 on a 2 processor system (Windows 2003
> Standard). I regularily run large queries. When I run the queries the CPU
> utilization is consitantly around 11%.
> It appears as if something is limiting SQL Server to 11% CPU per
> process/query. I have verified that its not I/O bound.
> The Processor properties are set as follows:
> - All 2 processors are checked in Processor Control
> - "Maximum worker threads" is set to 255
> - "Boost SQL Server priority on Windows" is not checked
> - "Use Windows NT fibres" is checked
> - "Use all available processors" is checked
> Why is the CPU not fully utilized? What does "Boost SQL Server priority on
> Windows" do?
> Any assistance would be greatly appreciated
> Thanks

Processor Utilization

Hi
I am running SQL Server 2000 on a 2 processor system (Windows 2003
Standard). I regularily run large queries. When I run the queries the CPU
utilization is consitantly around 11%.
It appears as if something is limiting SQL Server to 11% CPU per
process/query. I have verified that its not I/O bound.
The Processor properties are set as follows:
- All 2 processors are checked in Processor Control
- "Maximum worker threads" is set to 255
- "Boost SQL Server priority on Windows" is not checked
- "Use Windows NT fibres" is checked
- "Use all available processors" is checked
Why is the CPU not fully utilized? What does "Boost SQL Server priority on
Windows" do?
Any assistance would be greatly appreciated
ThanksHi
You may want to check the boost priority option and not use fibres (as
fibres can cause other problems). You could also try using the MAXDOP hint to
only use one processor.
Monitor context switches to see if there is an excessive number before
considering using fibres. Ken Hendersons book The Gurus Guide to SQL Server
Architecture and Internals ISBN 0201700476 has a good section on this.
John
"Macisu" wrote:
> Hi
> I am running SQL Server 2000 on a 2 processor system (Windows 2003
> Standard). I regularily run large queries. When I run the queries the CPU
> utilization is consitantly around 11%.
> It appears as if something is limiting SQL Server to 11% CPU per
> process/query. I have verified that its not I/O bound.
> The Processor properties are set as follows:
> - All 2 processors are checked in Processor Control
> - "Maximum worker threads" is set to 255
> - "Boost SQL Server priority on Windows" is not checked
> - "Use Windows NT fibres" is checked
> - "Use all available processors" is checked
> Why is the CPU not fully utilized? What does "Boost SQL Server priority on
> Windows" do?
> Any assistance would be greatly appreciated
> Thanks

Processor Utilization

Hi
I am running SQL Server 2000 on a 2 processor system (Windows 2003
Standard). I regularily run large queries. When I run the queries the CPU
utilization is consitantly around 11%.
It appears as if something is limiting SQL Server to 11% CPU per
process/query. I have verified that its not I/O bound.
The Processor properties are set as follows:
- All 2 processors are checked in Processor Control
- "Maximum worker threads" is set to 255
- "Boost SQL Server priority on Windows" is not checked
- "Use Windows NT fibres" is checked
- "Use all available processors" is checked
Why is the CPU not fully utilized? What does "Boost SQL Server priority on
Windows" do?
Any assistance would be greatly appreciated
ThanksHi
You may want to check the boost priority option and not use fibres (as
fibres can cause other problems). You could also try using the MAXDOP hint t
o
only use one processor.
Monitor context switches to see if there is an excessive number before
considering using fibres. Ken Hendersons book The Gurus Guide to SQL Server
Architecture and Internals ISBN 0201700476 has a good section on this.
John
"Macisu" wrote:

> Hi
> I am running SQL Server 2000 on a 2 processor system (Windows 2003
> Standard). I regularily run large queries. When I run the queries the CPU
> utilization is consitantly around 11%.
> It appears as if something is limiting SQL Server to 11% CPU per
> process/query. I have verified that its not I/O bound.
> The Processor properties are set as follows:
> - All 2 processors are checked in Processor Control
> - "Maximum worker threads" is set to 255
> - "Boost SQL Server priority on Windows" is not checked
> - "Use Windows NT fibres" is checked
> - "Use all available processors" is checked
> Why is the CPU not fully utilized? What does "Boost SQL Server priority on
> Windows" do?
> Any assistance would be greatly appreciated
> Thanks

Processor Upgrade on a sql cluster

In our environment we have a cluster active standby with a shared storage
iscsi
The two machines are Windows 2000 Advanced Server with Intel Xeon
Single-Core 3.4Ghz with SQL Server 2000
Enterprise Edition.
Now we want to sustitute these two with another two machines with
Dual Intel Xeon Dual-Core 3.6Ghz
We want to clone the actual machines in the new environment cause we want a
current machine for disaster recovery and cause we want also to test the
disaster recovery plan...
1) the two new dual core processors are view from operating system as a four
processor is this configuration supported with the environment Windows 2000
Advanced Server and SQL 2000 Server Enterprise Edition ?
2)when we have transferred the disk and the configuration and the boot is ok
and sql services are started what tuning and best practice we have to apply
for the new environment for tuning performance with new dual vs single cpu
node
Hi Davide,
1) Yes, you can manage 4 processors with these licenses.
2) We need more information about your environment to answer this. Generally
speaking, you should take care of CPU affinity and IO affinity, and take a
look at your files and filegroups configurations, especially on tempdb
database
Regards
Antonio Soto
Solid Quality Leaning
http://www.solidqualitylearning.com
DISCLAIMER:
Anything written in this message represents solely the point of view of the
sender. This message does not imply endorsement from Solid Quality Learning,
and it does not represent the point of view of Solid Quality Learning or any
other person, company or institution mentioned in this message
"Dr Davide BOmbarda" <DrDavideBOmbarda@.discussions.microsoft.com> escribi
en el mensaje news:CC20F619-9ED5-4CBB-BA62-B23AF4B2C75B@.microsoft.com...
> In our environment we have a cluster active standby with a shared storage
> iscsi
> The two machines are Windows 2000 Advanced Server with Intel Xeon
> Single-Core 3.4Ghz with SQL Server 2000
> Enterprise Edition.
> Now we want to sustitute these two with another two machines with
> Dual Intel Xeon Dual-Core 3.6Ghz
> We want to clone the actual machines in the new environment cause we want
> a
> current machine for disaster recovery and cause we want also to test the
> disaster recovery plan...
> 1) the two new dual core processors are view from operating system as a
> four
> processor is this configuration supported with the environment Windows
> 2000
> Advanced Server and SQL 2000 Server Enterprise Edition ?
> 2)when we have transferred the disk and the configuration and the boot is
> ok
> and sql services are started what tuning and best practice we have to
> apply
> for the new environment for tuning performance with new dual vs single cpu
> node
>
>
|||I/O affinity only comes into play with the Datacenter Edition when working
with specific SAN configurations. Even then, you need to be pushing the I/O
channel pretty hard to even see any effect.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Antonio Soto" <antoniosotorodriguez@.gmail.com> wrote in message
news:umQqsqpKGHA.3896@.TK2MSFTNGP15.phx.gbl...
> Hi Davide,
> 1) Yes, you can manage 4 processors with these licenses.
> 2) We need more information about your environment to answer this.
> Generally speaking, you should take care of CPU affinity and IO affinity,
> and take a look at your files and filegroups configurations, especially on
> tempdb database
> Regards
> Antonio Soto
> Solid Quality Leaning
> http://www.solidqualitylearning.com
> DISCLAIMER:
> Anything written in this message represents solely the point of view of
> the sender. This message does not imply endorsement from Solid Quality
> Learning, and it does not represent the point of view of Solid Quality
> Learning or any other person, company or institution mentioned in this
> message
>
>
> "Dr Davide BOmbarda" <DrDavideBOmbarda@.discussions.microsoft.com> escribi
> en el mensaje news:CC20F619-9ED5-4CBB-BA62-B23AF4B2C75B@.microsoft.com...
>

processor maxed out block other process...

Hi,
I'm using a 4 Xeon Hyperthreaded server with Windows 2003 ent. and SQL
Server 2000 ent. (8.0.818)
Whenever a user launch a specific function, let's say a sp, he uses 100% of
one of the 8 CPUs during 30-40 minutes and the workload jump from one
processor to another (every time the sp makes a new query).
I read in here that most of the query, especially the simple ones or the
bulk ones run on only one processor, so I think the behaviour of the sp
described above is normal.
My problem is when a second user comes in and run another application,
running on another database, and run a big process (again a sp doing various
things during 30 minutes or so) I don't see 2 processors running at 100% but
only one, and the process time of the two sp running simultanneously is
almost doubled...
Maybe I have a performancebottleneck somewhere, but I don't see where, I
have some pretty good SCSI Disk, 6GB of Ram almost never used more than 30%.
Except upgrading my processors speed is there a way to have better
performance? Like forcing more parrallelism on some process or queries. I
read something about query plan complexity defining the level of parallelism
of a query, is there a way to tune this level?
Thanks in advance.
Best regard,
Christophe.
There is a setting that adjusts the threshhold for parallism. sp_configure will show you the setting.
Of course indexing well is almost always the best path to follow.
|||"Ken Dutton" <fj60landcruiser@.yahoo.com> a crit dans le message de
news:505E0AD6-A9E0-4BE4-9214-1B3BC7BEE3B8@.microsoft.com...
> There is a setting that adjusts the threshhold for parallism.
sp_configure will show you the setting.
Thanks for your answer,
The threshold is currently at 3. I read in the BOL it's in millisecond, so I
don't think I can make it lower...
But that helped me see I didn't activate the AWE parameter on this server...
I was wondering why I never used more than 2GB!!

> Of course indexing well is almost always the best path to follow.
Yay!
That's what I'm telling my sql devs and db designers every morning, but that
doesn't seem to motivate them... I think a wooden club with long nails will
do the trick, but I'll try to coerce them into indexing their tables and
views one last time...
I'll do some trace and index tuning before, I'm not a monster... yet.
Anyway, thanks again.
Christophe

processor maxed out block other process...

Hi,
I'm using a 4 Xeon Hyperthreaded server with Windows 2003 ent. and SQL
Server 2000 ent. (8.0.818)
Whenever a user launch a specific function, let's say a sp, he uses 100% of
one of the 8 CPUs during 30-40 minutes and the workload jump from one
processor to another (every time the sp makes a new query).
I read in here that most of the query, especially the simple ones or the
bulk ones run on only one processor, so I think the behaviour of the sp
described above is normal.
My problem is when a second user comes in and run another application,
running on another database, and run a big process (again a sp doing various
things during 30 minutes or so) I don't see 2 processors running at 100% but
only one, and the process time of the two sp running simultanneously is
almost doubled...
Maybe I have a performancebottleneck somewhere, but I don't see where, I
have some pretty good SCSI Disk, 6GB of Ram almost never used more than 30%.
Except upgrading my processors speed is there a way to have better
performance? Like forcing more parrallelism on some process or queries. I
read something about query plan complexity defining the level of parallelism
of a query, is there a way to tune this level?
Thanks in advance.
Best regard,
Christophe.There is a setting that adjusts the threshhold for parallism. sp_configure will show you the setting
Of course indexing well is almost always the best path to follow.|||"Ken Dutton" <fj60landcruiser@.yahoo.com> a écrit dans le message de
news:505E0AD6-A9E0-4BE4-9214-1B3BC7BEE3B8@.microsoft.com...
> There is a setting that adjusts the threshhold for parallism.
sp_configure will show you the setting.
Thanks for your answer,
The threshold is currently at 3. I read in the BOL it's in millisecond, so I
don't think I can make it lower...
But that helped me see I didn't activate the AWE parameter on this server...
I was wondering why I never used more than 2GB!!
> Of course indexing well is almost always the best path to follow.
Yay!
That's what I'm telling my sql devs and db designers every morning, but that
doesn't seem to motivate them... I think a wooden club with long nails will
do the trick, but I'll try to coerce them into indexing their tables and
views one last time... :)
I'll do some trace and index tuning before, I'm not a monster... yet.
Anyway, thanks again.
Christophe

processor maxed out block other process...

Hi,
I'm using a 4 Xeon Hyperthreaded server with Windows 2003 ent. and SQL
Server 2000 ent. (8.0.818)
Whenever a user launch a specific function, let's say a sp, he uses 100% of
one of the 8 CPUs during 30-40 minutes and the workload jump from one
processor to another (every time the sp makes a new query).
I read in here that most of the query, especially the simple ones or the
bulk ones run on only one processor, so I think the behaviour of the sp
described above is normal.
My problem is when a second user comes in and run another application,
running on another database, and run a big process (again a sp doing various
things during 30 minutes or so) I don't see 2 processors running at 100% but
only one, and the process time of the two sp running simultanneously is
almost doubled...
Maybe I have a performancebottleneck somewhere, but I don't see where, I
have some pretty good SCSI Disk, 6GB of Ram almost never used more than 30%.
Except upgrading my processors speed is there a way to have better
performance? Like forcing more parrallelism on some process or queries. I
read something about query plan complexity defining the level of parallelism
of a query, is there a way to tune this level?
Thanks in advance.
Best regard,
Christophe.There is a setting that adjusts the threshhold for parallism. sp_configure
will show you the setting.
Of course indexing well is almost always the best path to follow.|||"Ken Dutton" <fj60landcruiser@.yahoo.com> a crit dans le message de
news:505E0AD6-A9E0-4BE4-9214-1B3BC7BEE3B8@.microsoft.com...
> There is a setting that adjusts the threshhold for parallism.
sp_configure will show you the setting.
Thanks for your answer,
The threshold is currently at 3. I read in the BOL it's in millisecond, so I
don't think I can make it lower...
But that helped me see I didn't activate the AWE parameter on this server...
I was wondering why I never used more than 2GB!!

> Of course indexing well is almost always the best path to follow.
Yay!
That's what I'm telling my sql devs and db designers every morning, but that
doesn't seem to motivate them... I think a wooden club with long nails will
do the trick, but I'll try to coerce them into indexing their tables and
views one last time...
I'll do some trace and index tuning before, I'm not a monster... yet.
Anyway, thanks again.
Christophesql

Processor Busy

When my Windows 2000 server is idle the whole processor is used by SQL Server 2000 and all switches and hubs on the network show collisions continuously. When some load comes on server it becomes normal. Can anybody suggest solution.Howdy,

Try removing all network protocols except TCPIP and see what happens.

Also, make sure the OS knows what its local default gateway is ( open command prompt & type ipconfig /all ) , otherwise it may trying broadcasts to find other servers on the network and so give you lots of network traffic.

Cheers,

SG.

Processing User Activity Table

Hello,

I have an application that will be logging to a SQL Server 2000
database user user activity from several Windows 2003 terminal
servers. This information will be retrieved by monitoring the
Security logs of these servers (this part I know how to accomplish
already).

A table in the database, tblLogEntries, will contain the following
fields:
- ID = autoincrementing int
- LogTime = Date/Time the user activity was recorded in the security
log
- Username = User's login ID that the activity was recorded with
- Type = int, referencing a lookup table with the values of Logon,
Logoff, and possible other future items
- Server = The name of the server the activity was recorded on.

The only question I have is, can you offer a way to process the total
user login time during a given range using T-SQL.

For Example...

Given the table data:
ID LogTime Username Type Server
1 10-10-2003 8:30:00 Tom Logon SERVER-A
2 10-10-2003 8:45:00 Sarah Logon SERVER-A
3 10-10-2003 16:45:00 Tom Logoff SERVER-A
4 10-10-2003 17:00:00 Sarah Logoff SERVER-A
5 10-11-2003 8:30:00 Tom Logon SERVER-A
6 10-11-2003 8:45:00 Sarah Logon SERVER-A
7 10-11-2003 16:30:00 Sarah Logoff SERVER-A
8 10-11-2003 17:15:00 Tom Logoff SERVER-A

How would you receive the output:
User Logon Total Time for SERVER-A
Tom 17.0 hrs
Sarah 16.0 hrs

I know I can handle this type of processing on my ASP.NET front-end,
but I'm curious as to how easily it can be done by the database,
itself.

Thanks in advance for your assistance.Do:

SELECT UserName,
SUM( DATEDIFF( hour, Login, COALESCE( Logoff, Login ) ) )
FROM ( SELECT t1.Username, t1.LogTime,
( SELECT MIN( t2.LogTime )
FROM tbl t2
WHERE t2.Server = t1.Server
AND t2.UserName = t1.Username
AND t2.Type = 'LogOff'
AND t2.LogTime > t1.LogTime )
FROM tbl t1
WHERE t1.Type = 'Logon'
AND t1.Server = 'SERVER-A' ) D ( UserName, Login, Logoff )
GROUP BY UserName ;

--
- Anith
( Please reply to newsgroups only )|||Thanks for the reply.. the query looks good, but I'm having a little
trouble following it, and, as a result, cannot get it to work.

Would you mind explaining it a bit or point me to a reference for this
type of processing?

I'm not sure what that "D" operator is for, and I'll read up on the
COALESCE in BOL.

------------
http://members.tripod.com/kcourville0/

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||D is an alias used for a derived table used in the query; when you use a
subquery construct directly in the FROM clause of an SQL statement with an
alias, in t-SQL, it is called a derived table. Pl. refer to SQL Server Books
Online for syntax and more details on this construct.

The logic is simple:

1. Retrieve the list of users with their login times and the subsequent
logout time (this is achieved using a subquery with MIN function). You can
run the derived table by itself to further understand how it is evaluated.

2. With the data in the derived table, the outer query, get the time
difference between the login time and the logout times and then find the
total using the SUM function.

--
- Anith
( Please reply to newsgroups only )|||Cool... I'll have to learn more of derived tables.

Thanks again for your response.

------------
http://members.tripod.com/kcourville0/

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Processing error

Hi all,

This came up and I have never see it before, I have tried logging in as sa and by using Windows Authentication and both give the same error. The error below occurred while using sa and the password. I get the same thing when I use WA (I am sysadmin).

Anyone have any ideas about what could be causing this?

Thanks,

Roy

<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>Pipeline Cube</DatabaseID>

<DimensionID>Tbl Pipeline Date</DimensionID>

</Object>

<Type>ProcessFull</Type>

<WriteBackTableCreation>UseExisting</WriteBackTableCreation>

</Process>

</Parallel>

</Batch>

Processing Dimension 'Tbl Pipeline Date' completed successfully.

Start time: 2/24/2006 9:01:52 AM; End time: 2/24/2006 9:01:57 AM; Duration: 0:00:05

Processing Dimension Attribute '(All)' completed successfully.

Start time: 2/24/2006 9:01:53 AM; End time: 2/24/2006 9:01:53 AM; Duration: 0:00:00

Processing Dimension Attribute 'DYear' completed successfully.

Start time: 2/24/2006 9:01:53 AM; End time: 2/24/2006 9:01:57 AM; Duration: 0:00:04

Processing Dimension Attribute 'Quarter' completed successfully.

Start time: 2/24/2006 9:01:53 AM; End time: 2/24/2006 9:01:57 AM; Duration: 0:00:04

Processing Dimension Attribute 'MonthNumber' completed successfully.

Start time: 2/24/2006 9:01:53 AM; End time: 2/24/2006 9:01:57 AM; Duration: 0:00:04

Processing Dimension Attribute 'ActualDate' completed successfully.

Start time: 2/24/2006 9:01:53 AM; End time: 2/24/2006 9:01:57 AM; Duration: 0:00:04

Processing Dimension Attribute 'WeekNumber' completed successfully.

Start time: 2/24/2006 9:01:53 AM; End time: 2/24/2006 9:01:57 AM; Duration: 0:00:04

Processing Dimension Attribute 'DayOfWeek' completed successfully.

Start time: 2/24/2006 9:01:53 AM; End time: 2/24/2006 9:01:57 AM; Duration: 0:00:04

Processing Dimension Attribute 'DayOfMonth' completed successfully.

Start time: 2/24/2006 9:01:53 AM; End time: 2/24/2006 9:01:57 AM; Duration: 0:00:04

Processing Dimension Attribute 'MonthName' completed successfully.

Start time: 2/24/2006 9:01:53 AM; End time: 2/24/2006 9:01:57 AM; Duration: 0:00:04

Errors and Warnings from Response

The following system error occurred: Logon failure: unknown user name or bad password. .

Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works', Name of 'Adventure Works'.

Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Tbl Pipeline Date', Name of 'Tbl Pipeline Date' was being processed.

Errors in the OLAP storage engine: An error occurred while the 'Quarter' attribute of the 'Tbl Pipeline Date' dimension from the 'Pipeline Cube' database was being processed.

Have you configured your data source to use the service account credentials? Analysis Services only supports that setting.

_-_-_ Dave

|||

Dave,

You are correct. I had forgotten all about using the service account credentials.

Thanks,

Roy

Processing cubes in Analysis Services 2000

I'm working with Analysis Services 2000 (SP4) on a 64 bit Windows Server 2003 where I have installed the framework 2.0.
I need to write an application to process Analysis Services 2000 cubes but I can't use DSO because there isn't a 64 bit version available of this library.
Can I use AMO (Analysis Management Objects) for administering Analysis Services 2000? Is there another solution?
Thanks in advance
Daniele

Unfortunatlely you cannot.
Your only option is to find a 32-bit workstation and run your DSO application from there. This is a restriction of AS2K. Sorry.

_-_-_ Dave

Processing cubes in Analysis Services 2000

I'm working with Analysis Services 2000 (SP4) on a 64 bit Windows Server 2003 where I have installed the framework 2.0.
I need to write an application to process Analysis Services 2000 cubes but I can't use DSO because there isn't a 64 bit version available of this library.
Can I use AMO (Analysis Management Objects) for administering Analysis Services 2000? Is there another solution?
Thanks in advance
DanieleUnfortunately you cannot use AMO against Analysis Services 2000.
You can use DSO to remotely process Analysis Services object from another 32bit machine.
By the way you can use separate Redistributable component to install DSO
http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en
Look for
"Microsoft SQL Server 2005 Backward Compatibility Components "

Edward Melomed (MSFT)

---

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

ProcessId remains in memory?

Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
Server 2003 and notice that applications that have been running during the
day, have more and more ProcessID's for the same application. The
applications sometimes is closed by the user, sometimes crash, but usually
they will (after a refresh of EM) not show. I see the Host name in the list
of items in Process Info, and now see that each machine has multiple entries
for the same application. It seems that the process Info remains fixed in
server memory.
Anyone know why this should have just started to happed. As far as I can
tell, only the clients would have any updates (MS Updates and fixes) the
client application has not changed apart from cosmetically. The connection
is through ADODB MDAC 2.8
Thanks for the time. Hope this is clear.The only times I have seen behavior like what I think you are
describing it was always a problem with the application. Rather than
using the connection it already had open, it kept opening a new
connection with each command. It was easy to see when monitoring
using Performance Monitor, watching the number of connections
climbing.
Which is not to say that your problem is the same, but it sure sounds
familiar.
Roy Harvey
Beacon Falls, CT
On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
<hughessatmdnationwide.co.uk> wrote:
>Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
>Server 2003 and notice that applications that have been running during the
>day, have more and more ProcessID's for the same application. The
>applications sometimes is closed by the user, sometimes crash, but usually
>they will (after a refresh of EM) not show. I see the Host name in the list
>of items in Process Info, and now see that each machine has multiple entries
>for the same application. It seems that the process Info remains fixed in
>server memory.
>Anyone know why this should have just started to happed. As far as I can
>tell, only the clients would have any updates (MS Updates and fixes) the
>client application has not changed apart from cosmetically. The connection
>is through ADODB MDAC 2.8
>Thanks for the time. Hope this is clear.|||Thanks, I believe that you are right, one of our developers did m ake a
change to the application, and did not free a query after use. This I think
has kept the connections open. I thought that SQL Server would release
unused connections after a period of inactivity but I guess that is not the
case. Oh well back to the drawing board
thanks for the input.
regards
steve
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:6jpp02dg831g66klbjtrt1isq4c2jquldk@.4ax.com...
> The only times I have seen behavior like what I think you are
> describing it was always a problem with the application. Rather than
> using the connection it already had open, it kept opening a new
> connection with each command. It was easy to see when monitoring
> using Performance Monitor, watching the number of connections
> climbing.
> Which is not to say that your problem is the same, but it sure sounds
> familiar.
> Roy Harvey
> Beacon Falls, CT
>
> On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
> <hughessatmdnationwide.co.uk> wrote:
>>Can anyone help here. I monitor SQL Server EM (2000) SP4 running on
>>Windows
>>Server 2003 and notice that applications that have been running during the
>>day, have more and more ProcessID's for the same application. The
>>applications sometimes is closed by the user, sometimes crash, but usually
>>they will (after a refresh of EM) not show. I see the Host name in the
>>list
>>of items in Process Info, and now see that each machine has multiple
>>entries
>>for the same application. It seems that the process Info remains fixed in
>>server memory.
>>Anyone know why this should have just started to happed. As far as I can
>>tell, only the clients would have any updates (MS Updates and fixes) the
>>client application has not changed apart from cosmetically. The connection
>>is through ADODB MDAC 2.8
>>Thanks for the time. Hope this is clear.

Processes locking themselves after SP4

Hi All,
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking at
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
Dave Wall
Are you using the very latest SP4 for SQL2K? Does your system use RAM
above 4GB and is AWE-enabled?
This may not be the issue I know but better to check rather than
assume. I know the first SP4 release problems didn't necessarily
manifest in the way your system is but you can never be sure ...
ALI
|||We're using the patch on SP4 to allow us to run AWE with RAM of 5GB
(restricted from 8GB)
Dave
Dave Wall
"zashah@.gmail.com" wrote:

> Are you using the very latest SP4 for SQL2K? Does your system use RAM
> above 4GB and is AWE-enabled?
> This may not be the issue I know but better to check rather than
> assume. I know the first SP4 release problems didn't necessarily
> manifest in the way your system is but you can never be sure ...
> ALI
>
|||Processes appearing to lock themselves is a change in reporting in SP4, not an actual issue. Basically the process reports itself as a blocking process when it goes to grab disk allocation (as I understand it). The Wait Type should display as PAGELATCH IO if I recall correctly.
Took me by surprise too but it isn't an actual blocked process.
As far as performance goes, I haven't seen any performance hits on databases up to 400 GB in size.

Quote:

Originally posted by Dave Wall
Hi All,
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking at
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
Dave Wall

|||Hi
Have a look at this explanation by Santeri Voutilainen from MSFT
http://groups-beta.google.com/group/...513ab281?hl=en
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:B746F00D-1908-4D9B-9934-F35F24304D54@.microsoft.com...
> Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
> 200 SP4. Users are complaining that the system is running slowly, looking
> at
> the processes, the active processes appear to be blocking themselves. The
> configuration of SQL is identical to before and the hardware is the same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall
|||Thanks Kyle,
and thanks to everyone else for your input. Turns out that while our
networking team assured me that the server had been set up to use PAE it
wasn't entriely true. Once it was set and the server rebooted, SQL started to
use the additional memory, IO dropped to nothing (as it can now hold around
1/3 of the DB in memory) and the blocking spids disappeared.
Thanks again for everyones input!
Dave
Dave Wall
"Kyle Quinby" wrote:

> Processes appearing to lock themselves is a change in reporting in SP4,
> not an actual issue. Basically the process reports itself as a blocking
> process when it goes to grab disk allocation (as I understand it). The
> Wait Type should display as PAGELATCH IO if I recall correctly.
> Took me by surprise too but it isn't an actual blocked process.
> As far as performance goes, I haven't seen any performance hits on
> databases up to 400 GB in size.
> Dave Wall wrote:
>
> --
> Kyle Quinby
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message1756427.html
>

Processes locking themselves after SP4

Hi All,
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking at
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
--
Dave WallAre you using the very latest SP4 for SQL2K? Does your system use RAM
above 4GB and is AWE-enabled?
This may not be the issue I know but better to check rather than
assume. I know the first SP4 release problems didn't necessarily
manifest in the way your system is but you can never be sure ...
ALI|||We're using the patch on SP4 to allow us to run AWE with RAM of 5GB
(restricted from 8GB)
Dave
--
Dave Wall
"zashah@.gmail.com" wrote:
> Are you using the very latest SP4 for SQL2K? Does your system use RAM
> above 4GB and is AWE-enabled?
> This may not be the issue I know but better to check rather than
> assume. I know the first SP4 release problems didn't necessarily
> manifest in the way your system is but you can never be sure ...
> ALI
>|||Hi
Have a look at this explanation by Santeri Voutilainen from MSFT
http://groups-beta.google.com/group/microsoft.public.sqlserver.server/msg/b86e343e513ab281?hl=en
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:B746F00D-1908-4D9B-9934-F35F24304D54@.microsoft.com...
> Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
> 200 SP4. Users are complaining that the system is running slowly, looking
> at
> the processes, the active processes appear to be blocking themselves. The
> configuration of SQL is identical to before and the hardware is the same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall|||Processes appearing to lock themselves is a change in reporting in SP4,
not an actual issue. Basically the process reports itself as a blocking
process when it goes to grab disk allocation (as I understand it). The
Wait Type should display as PAGELATCH IO if I recall correctly.
Took me by surprise too but it isn't an actual blocked process.
As far as performance goes, I haven't seen any performance hits on
databases up to 400 GB in size.
Dave Wall wrote:
> *Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL
> Server
> 200 SP4. Users are complaining that the system is running slowly,
> looking at
> the processes, the active processes appear to be blocking themselves.
> The
> configuration of SQL is identical to before and the hardware is the
> same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall *
Kyle Quinby
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1756427.html|||Thanks Kyle,
and thanks to everyone else for your input. Turns out that while our
networking team assured me that the server had been set up to use PAE it
wasn't entriely true. Once it was set and the server rebooted, SQL started to
use the additional memory, IO dropped to nothing (as it can now hold around
1/3 of the DB in memory) and the blocking spids disappeared.
Thanks again for everyones input!
Dave
--
Dave Wall
"Kyle Quinby" wrote:
> Processes appearing to lock themselves is a change in reporting in SP4,
> not an actual issue. Basically the process reports itself as a blocking
> process when it goes to grab disk allocation (as I understand it). The
> Wait Type should display as PAGELATCH IO if I recall correctly.
> Took me by surprise too but it isn't an actual blocked process.
> As far as performance goes, I haven't seen any performance hits on
> databases up to 400 GB in size.
> Dave Wall wrote:
> > *Hi All,
> >
> > We've recently rebuilt our failover cluster to Windows 2003 and SQL
> > Server
> > 200 SP4. Users are complaining that the system is running slowly,
> > looking at
> > the processes, the active processes appear to be blocking themselves.
> > The
> > configuration of SQL is identical to before and the hardware is the
> > same,
> > just the OS and the SP version of SQL has changed.
> >
> > Any ideas what might be causing the blocking? I've checked for lock
> > escalation (using profiler) and we're not experiencing it!
> >
> > --
> > Dave Wall *
>
> --
> Kyle Quinby
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message1756427.html
>

Processes locking themselves after SP4

Hi All,
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking a
t
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
Dave WallAre you using the very latest SP4 for SQL2K? Does your system use RAM
above 4GB and is AWE-enabled?
This may not be the issue I know but better to check rather than
assume. I know the first SP4 release problems didn't necessarily
manifest in the way your system is but you can never be sure ...
ALI|||We're using the patch on SP4 to allow us to run AWE with RAM of 5GB
(restricted from 8GB)
Dave
Dave Wall
"zashah@.gmail.com" wrote:

> Are you using the very latest SP4 for SQL2K? Does your system use RAM
> above 4GB and is AWE-enabled?
> This may not be the issue I know but better to check rather than
> assume. I know the first SP4 release problems didn't necessarily
> manifest in the way your system is but you can never be sure ...
> ALI
>|||Hi
Have a look at this explanation by Santeri Voutilainen from MSFT
http://groups-beta.google.com/group...
513ab281?hl=en
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:B746F00D-1908-4D9B-9934-F35F24304D54@.microsoft.com...
> Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
> 200 SP4. Users are complaining that the system is running slowly, looking
> at
> the processes, the active processes appear to be blocking themselves. The
> configuration of SQL is identical to before and the hardware is the same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall|||Processes appearing to lock themselves is a change in reporting in SP4,
not an actual issue. Basically the process reports itself as a blocking
process when it goes to grab disk allocation (as I understand it). The
Wait Type should display as PAGELATCH IO if I recall correctly.
Took me by surprise too but it isn't an actual blocked process.
As far as performance goes, I haven't seen any performance hits on
databases up to 400 GB in size.
Dave Wall wrote:
> *Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL
> Server
> 200 SP4. Users are complaining that the system is running slowly,
> looking at
> the processes, the active processes appear to be blocking themselves.
> The
> configuration of SQL is identical to before and the hardware is the
> same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall *
Kyle Quinby
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1756427.html|||Thanks Kyle,
and thanks to everyone else for your input. Turns out that while our
networking team assured me that the server had been set up to use PAE it
wasn't entriely true. Once it was set and the server rebooted, SQL started t
o
use the additional memory, IO dropped to nothing (as it can now hold around
1/3 of the DB in memory) and the blocking spids disappeared.
Thanks again for everyones input!
Dave
--
Dave Wall
"Kyle Quinby" wrote:

> Processes appearing to lock themselves is a change in reporting in SP4,
> not an actual issue. Basically the process reports itself as a blocking
> process when it goes to grab disk allocation (as I understand it). The
> Wait Type should display as PAGELATCH IO if I recall correctly.
> Took me by surprise too but it isn't an actual blocked process.
> As far as performance goes, I haven't seen any performance hits on
> databases up to 400 GB in size.
> Dave Wall wrote:
>
> --
> Kyle Quinby
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message1756427.html
>