Proclarity Installation using SQL Server 2005

Hi,

I'm attempting to install Proclarity 6 on a Win2003 Virtual PC, using SQL Server 2005 as my DB platform.

The installation continually fails with the error: "The SQL Serve Selected is not in Mixed Mode...". This occurs even if i specify the 'sa' account during the installation.

My SQL Sever is definitely set to Mixed Mode authentication!

Has anyone come accross this before and is there a fix?

Thanks in advance,

Leigh.

just run this statement and see whether its returning 0 or not

select SERVERPROPERTY('IsIntegratedSecurityOnly')

Madhu

|||

Hi Madhu,

I ran that statement and got 0 back from the server suggesting that i am indeed running in "Mixed Mode".

Cheers,

Leigh

|||

Well, i'm not sure why, but i've applied SQL 2005 SP2 and created a new user which i specified to run the ProClarity installation and hey-presto, suddenly everything works!

Cheers,
Leigh

Processor question

Hello Everyone,
When a certain platform let it be standard or enterprise, the processor
limitation on Standard is currently 4. Does that mean 4 physical processors
or if you had 2 physical processors with hyper threading which in Windows
would give you 4? I a bit confused about that.
Thank you
Alex Anderson
Alex Anderson wrote:
> Hello Everyone,
> When a certain platform let it be standard or enterprise, the
> processor limitation on Standard is currently 4. Does that mean 4
> physical processors or if you had 2 physical processors with hyper
> threading which in Windows would give you 4? I a bit confused about
> that.
> Thank you
> Alex Anderson
Physical. In fact, it's my understanding that dual-core processors are
going to be treated as a single processor according to the Microsoft
Licensing. SO you need to license the physical CPUs in the box (for CPU
licensing). As always, check with Microsoft Licensing for any licensing
issues and questions.
David Gugick - SQL Server MVP
Quest Software
|||David is correct. Multi-core and hyperthreaded processors count as a single
processor for licensing and edition processor limits. This makes MS
licensing highly competitive and much simpler than "the other guys".
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:ebZRcptIGHA.1760@.TK2MSFTNGP10.phx.gbl...
> Alex Anderson wrote:
> Physical. In fact, it's my understanding that dual-core processors are
> going to be treated as a single processor according to the Microsoft
> Licensing. SO you need to license the physical CPUs in the box (for CPU
> licensing). As always, check with Microsoft Licensing for any licensing
> issues and questions.
> --
> David Gugick - SQL Server MVP
> Quest Software
>
|||Thank you both for the information. You know Microsoft, you never know when
the wool will be pulled over our eyes.
Thank you
Alex Anderson
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:eJ1sIGuIGHA.1288@.TK2MSFTNGP09.phx.gbl...
> David is correct. Multi-core and hyperthreaded processors count as a
> single processor for licensing and edition processor limits. This makes
> MS licensing highly competitive and much simpler than "the other guys".
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:ebZRcptIGHA.1760@.TK2MSFTNGP10.phx.gbl...
>
|||Microsoft is often confusing, but most of the time they avoid active
stupidity. Remember, MS is a very large organization and sometimes it takes
a while for feedback to trickle through. This time, they appear to have
gotten it right.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex Anderson" <AAnderson@.Murrieta.org> wrote in message
news:O0Cuq31IGHA.2708@.tk2msftngp13.phx.gbl...
> Thank you both for the information. You know Microsoft, you never know
> when the wool will be pulled over our eyes.
> Thank you
> Alex Anderson
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:eJ1sIGuIGHA.1288@.TK2MSFTNGP09.phx.gbl...
>

Processor question

Hello Everyone,
When a certain platform let it be standard or enterprise, the processor
limitation on Standard is currently 4. Does that mean 4 physical processors
or if you had 2 physical processors with hyper threading which in Windows
would give you 4? I a bit confused about that.
Thank you
Alex AndersonAlex Anderson wrote:
> Hello Everyone,
> When a certain platform let it be standard or enterprise, the
> processor limitation on Standard is currently 4. Does that mean 4
> physical processors or if you had 2 physical processors with hyper
> threading which in Windows would give you 4? I a bit confused about
> that.
> Thank you
> Alex Anderson
Physical. In fact, it's my understanding that dual-core processors are
going to be treated as a single processor according to the Microsoft
Licensing. SO you need to license the physical CPUs in the box (for CPU
licensing). As always, check with Microsoft Licensing for any licensing
issues and questions.
--
David Gugick - SQL Server MVP
Quest Software|||David is correct. Multi-core and hyperthreaded processors count as a single
processor for licensing and edition processor limits. This makes MS
licensing highly competitive and much simpler than "the other guys".
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:ebZRcptIGHA.1760@.TK2MSFTNGP10.phx.gbl...
> Alex Anderson wrote:
>> Hello Everyone,
>> When a certain platform let it be standard or enterprise, the
>> processor limitation on Standard is currently 4. Does that mean 4
>> physical processors or if you had 2 physical processors with hyper
>> threading which in Windows would give you 4? I a bit confused about
>> that.
>> Thank you
>> Alex Anderson
> Physical. In fact, it's my understanding that dual-core processors are
> going to be treated as a single processor according to the Microsoft
> Licensing. SO you need to license the physical CPUs in the box (for CPU
> licensing). As always, check with Microsoft Licensing for any licensing
> issues and questions.
> --
> David Gugick - SQL Server MVP
> Quest Software
>|||Thank you both for the information. You know Microsoft, you never know when
the wool will be pulled over our eyes.
Thank you
Alex Anderson
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:eJ1sIGuIGHA.1288@.TK2MSFTNGP09.phx.gbl...
> David is correct. Multi-core and hyperthreaded processors count as a
> single processor for licensing and edition processor limits. This makes
> MS licensing highly competitive and much simpler than "the other guys".
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:ebZRcptIGHA.1760@.TK2MSFTNGP10.phx.gbl...
>> Alex Anderson wrote:
>> Hello Everyone,
>> When a certain platform let it be standard or enterprise, the
>> processor limitation on Standard is currently 4. Does that mean 4
>> physical processors or if you had 2 physical processors with hyper
>> threading which in Windows would give you 4? I a bit confused about
>> that.
>> Thank you
>> Alex Anderson
>> Physical. In fact, it's my understanding that dual-core processors are
>> going to be treated as a single processor according to the Microsoft
>> Licensing. SO you need to license the physical CPUs in the box (for CPU
>> licensing). As always, check with Microsoft Licensing for any licensing
>> issues and questions.
>> --
>> David Gugick - SQL Server MVP
>> Quest Software
>|||Microsoft is often confusing, but most of the time they avoid active
stupidity. Remember, MS is a very large organization and sometimes it takes
a while for feedback to trickle through. This time, they appear to have
gotten it right.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex Anderson" <AAnderson@.Murrieta.org> wrote in message
news:O0Cuq31IGHA.2708@.tk2msftngp13.phx.gbl...
> Thank you both for the information. You know Microsoft, you never know
> when the wool will be pulled over our eyes.
> Thank you
> Alex Anderson
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:eJ1sIGuIGHA.1288@.TK2MSFTNGP09.phx.gbl...
>> David is correct. Multi-core and hyperthreaded processors count as a
>> single processor for licensing and edition processor limits. This makes
>> MS licensing highly competitive and much simpler than "the other guys".
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
>> news:ebZRcptIGHA.1760@.TK2MSFTNGP10.phx.gbl...
>> Alex Anderson wrote:
>> Hello Everyone,
>> When a certain platform let it be standard or enterprise, the
>> processor limitation on Standard is currently 4. Does that mean 4
>> physical processors or if you had 2 physical processors with hyper
>> threading which in Windows would give you 4? I a bit confused about
>> that.
>> Thank you
>> Alex Anderson
>> Physical. In fact, it's my understanding that dual-core processors are
>> going to be treated as a single processor according to the Microsoft
>> Licensing. SO you need to license the physical CPUs in the box (for CPU
>> licensing). As always, check with Microsoft Licensing for any licensing
>> issues and questions.
>> --
>> David Gugick - SQL Server MVP
>> Quest Software
>>
>

Processor question

Hello Everyone,
When a certain platform let it be standard or enterprise, the processor
limitation on Standard is currently 4. Does that mean 4 physical processors
or if you had 2 physical processors with hyper threading which in Windows
would give you 4? I a bit confused about that.
Thank you
Alex AndersonAlex Anderson wrote:
> Hello Everyone,
> When a certain platform let it be standard or enterprise, the
> processor limitation on Standard is currently 4. Does that mean 4
> physical processors or if you had 2 physical processors with hyper
> threading which in Windows would give you 4? I a bit confused about
> that.
> Thank you
> Alex Anderson
Physical. In fact, it's my understanding that dual-core processors are
going to be treated as a single processor according to the Microsoft
Licensing. SO you need to license the physical CPUs in the box (for CPU
licensing). As always, check with Microsoft Licensing for any licensing
issues and questions.
David Gugick - SQL Server MVP
Quest Software|||David is correct. Multi-core and hyperthreaded processors count as a single
processor for licensing and edition processor limits. This makes MS
licensing highly competitive and much simpler than "the other guys".
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:ebZRcptIGHA.1760@.TK2MSFTNGP10.phx.gbl...
> Alex Anderson wrote:
> Physical. In fact, it's my understanding that dual-core processors are
> going to be treated as a single processor according to the Microsoft
> Licensing. SO you need to license the physical CPUs in the box (for CPU
> licensing). As always, check with Microsoft Licensing for any licensing
> issues and questions.
> --
> David Gugick - SQL Server MVP
> Quest Software
>|||Thank you both for the information. You know Microsoft, you never know when
the wool will be pulled over our eyes.
Thank you
Alex Anderson
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:eJ1sIGuIGHA.1288@.TK2MSFTNGP09.phx.gbl...
> David is correct. Multi-core and hyperthreaded processors count as a
> single processor for licensing and edition processor limits. This makes
> MS licensing highly competitive and much simpler than "the other guys".
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:ebZRcptIGHA.1760@.TK2MSFTNGP10.phx.gbl...
>|||Microsoft is often confusing, but most of the time they avoid active
stupidity. Remember, MS is a very large organization and sometimes it takes
a while for feedback to trickle through. This time, they appear to have
gotten it right.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex Anderson" <AAnderson@.Murrieta.org> wrote in message
news:O0Cuq31IGHA.2708@.tk2msftngp13.phx.gbl...
> Thank you both for the information. You know Microsoft, you never know
> when the wool will be pulled over our eyes.
> Thank you
> Alex Anderson
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:eJ1sIGuIGHA.1288@.TK2MSFTNGP09.phx.gbl...
>

'Processor Affinity from server properties

Hi everyone,

Primary platform is 2005 under 64-bit.

I'm trying to figure out what does 'Processor Affinity' and 'I/O Affinity' means when you're viewing server properties. We've got eight processors.

Thanks for your comments,

Processor Affinity is the list of processors that worker threads are allowed to execute on. The number is a bit mask with one bit aligning to each processor on the system. A value of 0 allows use of all processors.

I/O affinity mask is the list of processors that are allowed to process IO operations, and uses the same bitmask scheme.

In most cases there is no need to change either setting. If you do decide to make changes to either setting ensure that the same processor is not specified in both masks.

|||thankssql

'Processor Affinity from server properties

Hi everyone,

Primary platform is 2005 under 64-bit.

I'm trying to figure out what does 'Processor Affinity' and 'I/O Affinity' means when you're viewing server properties. We've got eight processors.

Thanks for your comments,

Processor Affinity is the list of processors that worker threads are allowed to execute on. The number is a bit mask with one bit aligning to each processor on the system. A value of 0 allows use of all processors.

I/O affinity mask is the list of processors that are allowed to process IO operations, and uses the same bitmask scheme.

In most cases there is no need to change either setting. If you do decide to make changes to either setting ensure that the same processor is not specified in both masks.

|||thanks

Processing a cube on SQL server 2005 from a dts package on SQL server 2000

We just started migrating some cubes to the 2005 platform. Still there are some DTS packages running on the 2000 platform that needs some recoding to fit the 2005 enviroment. Therefore we have some solutions where we have DTS packages running on SQL Server 2000 and their "related" cubes running on the 2005 platform.

My question is therefore: Is there an easy way to initiate a processing of a cube on the 2005 platform from a Sql server 2000 DTS package ?

Hmm seems that there are no easy way|||

Hello cgpl,

I think this may be of help to you: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265208&SiteID=1

-Jamie

Processing a cube on SQL server 2005 from a dts package on SQL server 2000

We just started migrating some cubes to the 2005 platform. Still there are some DTS packages running on the 2000 platform that needs some recoding to fit the 2005 enviroment. Therefore we have some solutions where we have DTS packages running on SQL Server 2000 and their "related" cubes running on the 2005 platform.

My question is therefore: Is there an easy way to initiate a processing of a cube on the 2005 platform from a Sql server 2000 DTS package ?

Hmm seems that there are no easy way|||

Hello cgpl,

I think this may be of help to you: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265208&SiteID=1

-Jamie

Processing a cube on SQL server 2005 from a dts package on SQL server 2000

We just started migrating some cubes to the 2005 platform. Still there are some DTS packages running on the 2000 platform that needs some recoding to fit the 2005 enviroment. Therefore we have some solutions where we have DTS packages running on SQL Server 2000 and their "related" cubes running on the 2005 platform.

My question is therefore: Is there an easy way to initiate a processing of a cube on the 2005 platform from a Sql server 2000 DTS package ?

Hmm seems that there are no easy way|||

Hello cgpl,

I think this may be of help to you: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265208&SiteID=1

-Jamie