Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts

Wednesday, March 28, 2012

It's possibel run SSIS in SQL Server 2005 Express Edition

Hy,

I wont now if it's possible to run SSIS in my server client that have instaled SQL Server 2005 Express Edition?

Regards,

Filipe Silva

Hello,

SSIS comes only with Microsoft SQL Server, it's not part odf the Express Edition

Regards,
Ovidiu Burlacu

|||

No. SQL Server Express does not include SSIS.

-Jamie

Friday, March 23, 2012

Issues with Un-Installng and Re-Installing SQL Server 2005

Are there any issues with un-installing and re-installing sql server 2005
dev edition? I think it installed SSRS. I know that un-installing and
re-installing sql server 2000 is pretty painless as I've done it many times
with no problems, however, un-installing and re-installing SSRS 2000 is a
MAJOR pain as it leaves many splinters behind that are difficult to deal
with prioer to re-installing SSRS.
My main concern is that I thought I specified the Data files to reside on
the D drive, however, sql server 2005 installed the data files in:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
Would it be be painless and trouble free to move the databases to
D:\MSSQL05\Data, and then from SQL Server Management
Studio/Properties/Database Settings/Database Default locations, set it to:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
Thanks.
moondaddy@.nospam.nospamBasially I don't see any issues, besides for the fact that you need to make
sure you have a copy of the database master key.
See Books online on how to export it.If you want to move you would be able
to do a database attach / detach.
I didn't really test it myself on RTM but on September CTP I had quite some
issues with it
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
"moondaddy" <moondaddy@.nospam.nospam> wrote in message
news:Oq9jG006FHA.2384@.TK2MSFTNGP12.phx.gbl...
> Are there any issues with un-installing and re-installing sql server 2005
> dev edition? I think it installed SSRS. I know that un-installing and
> re-installing sql server 2000 is pretty painless as I've done it many
> times with no problems, however, un-installing and re-installing SSRS 2000
> is a MAJOR pain as it leaves many splinters behind that are difficult to
> deal with prioer to re-installing SSRS.
> My main concern is that I thought I specified the Data files to reside on
> the D drive, however, sql server 2005 installed the data files in:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
> Would it be be painless and trouble free to move the databases to
> D:\MSSQL05\Data, and then from SQL Server Management
> Studio/Properties/Database Settings/Database Default locations, set it to:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
> Thanks.
> --
> moondaddy@.nospam.nospam
>sql

Issues with Un-Installng and Re-Installing SQL Server 2005

Are there any issues with un-installing and re-installing sql server 2005
dev edition? I think it installed SSRS. I know that un-installing and
re-installing sql server 2000 is pretty painless as I've done it many times
with no problems, however, un-installing and re-installing SSRS 2000 is a
MAJOR pain as it leaves many splinters behind that are difficult to deal
with prioer to re-installing SSRS.
My main concern is that I thought I specified the Data files to reside on
the D drive, however, sql server 2005 installed the data files in:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
Would it be be painless and trouble free to move the databases to
D:\MSSQL05\Data, and then from SQL Server Management
Studio/Properties/Database Settings/Database Default locations, set it to:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
Thanks.
moondaddy@.nospam.nospam
Basially I don't see any issues, besides for the fact that you need to make
sure you have a copy of the database master key.
See Books online on how to export it.If you want to move you would be able
to do a database attach / detach.
I didn't really test it myself on RTM but on September CTP I had quite some
issues with it
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
"moondaddy" <moondaddy@.nospam.nospam> wrote in message
news:Oq9jG006FHA.2384@.TK2MSFTNGP12.phx.gbl...
> Are there any issues with un-installing and re-installing sql server 2005
> dev edition? I think it installed SSRS. I know that un-installing and
> re-installing sql server 2000 is pretty painless as I've done it many
> times with no problems, however, un-installing and re-installing SSRS 2000
> is a MAJOR pain as it leaves many splinters behind that are difficult to
> deal with prioer to re-installing SSRS.
> My main concern is that I thought I specified the Data files to reside on
> the D drive, however, sql server 2005 installed the data files in:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
> Would it be be painless and trouble free to move the databases to
> D:\MSSQL05\Data, and then from SQL Server Management
> Studio/Properties/Database Settings/Database Default locations, set it to:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
> Thanks.
> --
> moondaddy@.nospam.nospam
>

Issues with Un-Installng and Re-Installing SQL Server 2005

Are there any issues with un-installing and re-installing sql server 2005
dev edition? I think it installed SSRS. I know that un-installing and
re-installing sql server 2000 is pretty painless as I've done it many times
with no problems, however, un-installing and re-installing SSRS 2000 is a
MAJOR pain as it leaves many splinters behind that are difficult to deal
with prioer to re-installing SSRS.
My main concern is that I thought I specified the Data files to reside on
the D drive, however, sql server 2005 installed the data files in:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
Would it be be painless and trouble free to move the databases to
D:\MSSQL05\Data, and then from SQL Server Management
Studio/Properties/Database Settings/Database Default locations, set it to:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
Thanks.
--
moondaddy@.nospam.nospamBasially I don't see any issues, besides for the fact that you need to make
sure you have a copy of the database master key.
See Books online on how to export it.If you want to move you would be able
to do a database attach / detach.
I didn't really test it myself on RTM but on September CTP I had quite some
issues with it
--
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
"moondaddy" <moondaddy@.nospam.nospam> wrote in message
news:Oq9jG006FHA.2384@.TK2MSFTNGP12.phx.gbl...
> Are there any issues with un-installing and re-installing sql server 2005
> dev edition? I think it installed SSRS. I know that un-installing and
> re-installing sql server 2000 is pretty painless as I've done it many
> times with no problems, however, un-installing and re-installing SSRS 2000
> is a MAJOR pain as it leaves many splinters behind that are difficult to
> deal with prioer to re-installing SSRS.
> My main concern is that I thought I specified the Data files to reside on
> the D drive, however, sql server 2005 installed the data files in:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
> Would it be be painless and trouble free to move the databases to
> D:\MSSQL05\Data, and then from SQL Server Management
> Studio/Properties/Database Settings/Database Default locations, set it to:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
> Thanks.
> --
> moondaddy@.nospam.nospam
>

Wednesday, March 21, 2012

Issues with Microsoft SQL Serever 2005 Express Edition and other versions of SQL Express

I have uninstalled the SQL Server Express Edition that I have installed from the CDs that were given to me during a Chicago Conference when READY TO LAUNCH Visual Studio 2005, SQL SERVER 2005, and Biz Talk 2005.

Then I went to microsoft website: http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx and downloaded and installed the so called Microsoft SQL Server 2005 Express Edition and I got the messages Error that you read below. Then I Uninstalled Microsoft SQL Server 2005 Express Edition and went again to msdn website and downloaded Microsoft SQL Server 2005 Express Edition Advanced Services SP1 and installed it. I got again the same message as below.

MESSAGE:

1. First comes a window with the title: “setup.exe – Unable to Locate Component
And it displays a message:

This application has failed to start because MSTDCPRX.dll was not found.

Re-installing the application may fix this problem.

2. After I click the OK button of this window it comes another window with the title: “Microsoft SQL Server 2005 Server Setup”

And it displays a message: Failed to load SqlSpars.dll

Does anybody can tell what is going on with the 3 times I tried to installed different SQL Server 2005 Express Edition and I get the same message?

Thanks for your help and support when you have time to respond.

Sincerely,

TonyC

MORE INFORMATION ON THE:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

1. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.txt

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 87

Aborting queue processing as nested installer has completed

Message pump returning: 87

2. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).txt Running: InvokeSqlSetupDllAction at: 2007/1/20 1:22:8

Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.

Unable to load setup helper module : 87

Message displayed to user

Failed to load SqlSpars.dll

Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0001.cab" Error Code : 2

Running: UploadDrWatsonLogAction at: 2007/1/20 1:22:17

Message pump returning: 87

3. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Datastore.xml

<

<S,<Scope Type="SetupStateScope" Id="">

<Property Id="machineName">B3-XP</Property>

<Property Id="logDirectory">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\</Property>

<Property Id="logSummaryFilename">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt</Property>

<Property Id="logSequenceNumber">1</Property>

<Property Id="primaryLogFiles">{ ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Support.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).log"] }</Property>

<Property Id="watsonFailedAction">InvokeSqlSetupDllAction</Property>

<Property Id="watsonFailedActionErrorCode">87</Property>

<Property Id="watsonFailedFunction">sqls::InvokeSqlSetupDllAction::perform</Property>

<Property Id="watsonFailedFunctionErrorCode">87</Property>

<Property Id="watsonSourceFileAndLineNo">setup\sqlsetupactions.cpp@.1709</Property>

<Property Id="watsonModuleAndVersion">setup.exe@.2005.90.3042.0</Property>

<Property Id="watsonMsi">None</Property>

<Property Id="watsonMsiAndVersion">None</Property>

<Property Id="watsonSourceFile">setup\sqlsetupactions.cpp</Property>

</<Scope>

This application has failed to start because MSTDCPRX.dll was not found.

It seems that DTS is corrupted on your computer. Would you reinstall DTC (Distributed Transaction Coordinator) and try setup.exe again?

|||

Can you be more specific because I am not familiar with what you just said.
1. Can you tell me where to find the DTC or where I can download it so I can reinstal or instal?
Does anybody else also has a different suggestion.
Thanks again

|||

I need more help with the SQL Server Express or more other responses, please.
Is anymore people out there who can tell me what to do?
I am still waiting to here from anybody, I check this forum almost twice a day and I see no answers.
I really would appreciate any of your advice if you look through my LOG files?
If you need me to look for some more code in the Log files like the one named something like log_support.txt which is a very long file I will do that as long as you tell me for what specific line or value or string to look.

Please help and thanks for your time if you try to help me.

Sincerely,
TonyCorrona

|||

Hello there,

PLEASE DELETE THIS THREAD.

Thanks and Regards,
TonyC

|||

Thanks to everybody's time reading my thread and trying to help me maybe.
Anyways, I have fixed the problem on my own without having to reinstall Microsoft Distributed Transaction Coordinator and do all the steps that Microsoft People say in their document they provide in msdn.microsoft site.

My problem above I have fixed using some logics of my head and fixed in less then 10 seconds and then tried to install SQL Server Express and it did install it without problem and generated successfull message without any errors and is working fine so far.

Now you can Delete this thread the Microsoft Admin People.
P.S. I like this TechNet forum site but the only lack of this site is that it does not allow us users to delete our own threads.
Maybe I might be misaken but I don't see anywhere a delete button besides the three or sometimes four buttons which
are: Mark as Answer, Reply, Quote and Edit.

Sincerely,
T C

|||

Tony, can you please supply your solution so that it may help others in the future? Congrats on getting it solved. :)

Sam

|||

I am replying to this only on behalf of the users which are struggling with SQL 2005.
If it would be to helping the Programmers or Administrator of MSFT, I would never reply to this blog because they got the job and should try to help people because they get paid for it.
I don't get paid for this to help Microsoft Employee to resolve thier issues.
Myself I am unemployed since last year when I got laid off from a company. Today nobody is helping me with anything, nor to get a job or any interview just because I have only 2 years of work experience.

Anyways let get to the job helping you kindly users.

Since MSFT personnnel could not help me I thought would try to resolve the issue on my own without thier help.


After instaling SQL SERVER 2005, I was missing the MSTDCPRX.dll in the computer that I was installed the SQL 2005 and one thing that I remeber I have done was this.

So I went in another computer that I had Windows XP and searched for the DLL file MSTDCPRX.dll and copy the file and then pasted to the computer that I was missing the file. For those people who do not know where to paste the file, it should be in the directory C:\WINDOWS\system32.

After I copied this file and pasted I did not have any problems anymore with SQL Spars.DLL or any other issues instaling the SQL SERVER 2005.

Hope this will help to all of you who is having problems with SQL SERVER 2005.

Wish you a good day.

Sincerely,

T

Issues with Microsoft SQL Serever 2005 Express Edition and other versions of SQL Express

I have uninstalled the SQL Server Express Edition that I have installed from the CDs that were given to me during a Chicago Conference when READY TO LAUNCH Visual Studio 2005, SQL SERVER 2005, and Biz Talk 2005.

Then I went to microsoft website: http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx and downloaded and installed the so called Microsoft SQL Server 2005 Express Edition and I got the messages Error that you read below. Then I Uninstalled Microsoft SQL Server 2005 Express Edition and went again to msdn website and downloaded Microsoft SQL Server 2005 Express Edition Advanced Services SP1 and installed it. I got again the same message as below.

MESSAGE:

1. First comes a window with the title: “setup.exe – Unable to Locate Component
And it displays a message:

This application has failed to start because MSTDCPRX.dll was not found.

Re-installing the application may fix this problem.

2. After I click the OK button of this window it comes another window with the title: “Microsoft SQL Server 2005 Server Setup”

And it displays a message: Failed to load SqlSpars.dll

Does anybody can tell what is going on with the 3 times I tried to installed different SQL Server 2005 Express Edition and I get the same message?

Thanks for your help and support when you have time to respond.

Sincerely,

TonyC

MORE INFORMATION ON THE:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

1. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.txt

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 87

Aborting queue processing as nested installer has completed

Message pump returning: 87

2. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).txt Running: InvokeSqlSetupDllAction at: 2007/1/20 1:22:8

Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.

Unable to load setup helper module : 87

Message displayed to user

Failed to load SqlSpars.dll

Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0001.cab" Error Code : 2

Running: UploadDrWatsonLogAction at: 2007/1/20 1:22:17

Message pump returning: 87

3. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Datastore.xml

<

<S,<Scope Type="SetupStateScope" Id="">

<Property Id="machineName">B3-XP</Property>

<Property Id="logDirectory">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\</Property>

<Property Id="logSummaryFilename">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt</Property>

<Property Id="logSequenceNumber">1</Property>

<Property Id="primaryLogFiles">{ ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Support.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).log"] }</Property>

<Property Id="watsonFailedAction">InvokeSqlSetupDllAction</Property>

<Property Id="watsonFailedActionErrorCode">87</Property>

<Property Id="watsonFailedFunction">sqls::InvokeSqlSetupDllAction::perform</Property>

<Property Id="watsonFailedFunctionErrorCode">87</Property>

<Property Id="watsonSourceFileAndLineNo">setup\sqlsetupactions.cpp@.1709</Property>

<Property Id="watsonModuleAndVersion">setup.exe@.2005.90.3042.0</Property>

<Property Id="watsonMsi">None</Property>

<Property Id="watsonMsiAndVersion">None</Property>

<Property Id="watsonSourceFile">setup\sqlsetupactions.cpp</Property>

</<Scope>

This application has failed to start because MSTDCPRX.dll was not found.

It seems that DTS is corrupted on your computer. Would you reinstall DTC (Distributed Transaction Coordinator) and try setup.exe again?

|||

Can you be more specific because I am not familiar with what you just said.
1. Can you tell me where to find the DTC or where I can download it so I can reinstal or instal?
Does anybody else also has a different suggestion.
Thanks again

|||

I need more help with the SQL Server Express or more other responses, please.
Is anymore people out there who can tell me what to do?
I am still waiting to here from anybody, I check this forum almost twice a day and I see no answers.
I really would appreciate any of your advice if you look through my LOG files?
If you need me to look for some more code in the Log files like the one named something like log_support.txt which is a very long file I will do that as long as you tell me for what specific line or value or string to look.

Please help and thanks for your time if you try to help me.

Sincerely,
TonyCorrona

|||

Hello there,

PLEASE DELETE THIS THREAD.

Thanks and Regards,
TonyC

|||

Thanks to everybody's time reading my thread and trying to help me maybe.
Anyways, I have fixed the problem on my own without having to reinstall Microsoft Distributed Transaction Coordinator and do all the steps that Microsoft People say in their document they provide in msdn.microsoft site.

My problem above I have fixed using some logics of my head and fixed in less then 10 seconds and then tried to install SQL Server Express and it did install it without problem and generated successfull message without any errors and is working fine so far.

Now you can Delete this thread the Microsoft Admin People.
P.S. I like this TechNet forum site but the only lack of this site is that it does not allow us users to delete our own threads.
Maybe I might be misaken but I don't see anywhere a delete button besides the three or sometimes four buttons which
are: Mark as Answer, Reply, Quote and Edit.

Sincerely,
T C

|||

Tony, can you please supply your solution so that it may help others in the future? Congrats on getting it solved. :)

Sam

|||

I am replying to this only on behalf of the users which are struggling with SQL 2005.
If it would be to helping the Programmers or Administrator of MSFT, I would never reply to this blog because they got the job and should try to help people because they get paid for it.
I don't get paid for this to help Microsoft Employee to resolve thier issues.
Myself I am unemployed since last year when I got laid off from a company. Today nobody is helping me with anything, nor to get a job or any interview just because I have only 2 years of work experience.

Anyways let get to the job helping you kindly users.

Since MSFT personnnel could not help me I thought would try to resolve the issue on my own without thier help.


After instaling SQL SERVER 2005, I was missing the MSTDCPRX.dll in the computer that I was installed the SQL 2005 and one thing that I remeber I have done was this.

So I went in another computer that I had Windows XP and searched for the DLL file MSTDCPRX.dll and copy the file and then pasted to the computer that I was missing the file. For those people who do not know where to paste the file, it should be in the directory C:\WINDOWS\system32.

After I copied this file and pasted I did not have any problems anymore with SQL Spars.DLL or any other issues instaling the SQL SERVER 2005.

Hope this will help to all of you who is having problems with SQL SERVER 2005.

Wish you a good day.

Sincerely,

T

sql

Issues with Microsoft SQL Serever 2005 Express Edition and other versions of SQL Express

I have uninstalled the SQL Server Express Edition that I have installed from the CDs that were given to me during a Chicago Conference when READY TO LAUNCH Visual Studio 2005, SQL SERVER 2005, and Biz Talk 2005.

Then I went to microsoft website: http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx and downloaded and installed the so called Microsoft SQL Server 2005 Express Edition and I got the messages Error that you read below. Then I Uninstalled Microsoft SQL Server 2005 Express Edition and went again to msdn website and downloaded Microsoft SQL Server 2005 Express Edition Advanced Services SP1 and installed it. I got again the same message as below.

MESSAGE:

1. First comes a window with the title: “setup.exe – Unable to Locate Component
And it displays a message:

This application has failed to start because MSTDCPRX.dll was not found.

Re-installing the application may fix this problem.

2. After I click the OK button of this window it comes another window with the title: “Microsoft SQL Server 2005 Server Setup”

And it displays a message: Failed to load SqlSpars.dll

Does anybody can tell what is going on with the 3 times I tried to installed different SQL Server 2005 Express Edition and I get the same message?

Thanks for your help and support when you have time to respond.

Sincerely,

TonyC

MORE INFORMATION ON THE:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

1. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.txt

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 87

Aborting queue processing as nested installer has completed

Message pump returning: 87

2. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).txt Running: InvokeSqlSetupDllAction at: 2007/1/20 1:22:8

Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.

Unable to load setup helper module : 87

Message displayed to user

Failed to load SqlSpars.dll

Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0001.cab" Error Code : 2

Running: UploadDrWatsonLogAction at: 2007/1/20 1:22:17

Message pump returning: 87

3. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Datastore.xml

<

<S,<Scope Type="SetupStateScope" Id="">

<Property Id="machineName">B3-XP</Property>

<Property Id="logDirectory">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\</Property>

<Property Id="logSummaryFilename">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt</Property>

<Property Id="logSequenceNumber">1</Property>

<Property Id="primaryLogFiles">{ ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Support.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).log"] }</Property>

<Property Id="watsonFailedAction">InvokeSqlSetupDllAction</Property>

<Property Id="watsonFailedActionErrorCode">87</Property>

<Property Id="watsonFailedFunction">sqls::InvokeSqlSetupDllAction::perform</Property>

<Property Id="watsonFailedFunctionErrorCode">87</Property>

<Property Id="watsonSourceFileAndLineNo">setup\sqlsetupactions.cpp@.1709</Property>

<Property Id="watsonModuleAndVersion">setup.exe@.2005.90.3042.0</Property>

<Property Id="watsonMsi">None</Property>

<Property Id="watsonMsiAndVersion">None</Property>

<Property Id="watsonSourceFile">setup\sqlsetupactions.cpp</Property>

</<Scope>

This application has failed to start because MSTDCPRX.dll was not found.

It seems that DTS is corrupted on your computer. Would you reinstall DTC (Distributed Transaction Coordinator) and try setup.exe again?

|||

Can you be more specific because I am not familiar with what you just said.
1. Can you tell me where to find the DTC or where I can download it so I can reinstal or instal?
Does anybody else also has a different suggestion.
Thanks again

|||

I need more help with the SQL Server Express or more other responses, please.
Is anymore people out there who can tell me what to do?
I am still waiting to here from anybody, I check this forum almost twice a day and I see no answers.
I really would appreciate any of your advice if you look through my LOG files?
If you need me to look for some more code in the Log files like the one named something like log_support.txt which is a very long file I will do that as long as you tell me for what specific line or value or string to look.

Please help and thanks for your time if you try to help me.

Sincerely,
TonyCorrona

|||

Hello there,

PLEASE DELETE THIS THREAD.

Thanks and Regards,
TonyC

|||

Thanks to everybody's time reading my thread and trying to help me maybe.
Anyways, I have fixed the problem on my own without having to reinstall Microsoft Distributed Transaction Coordinator and do all the steps that Microsoft People say in their document they provide in msdn.microsoft site.

My problem above I have fixed using some logics of my head and fixed in less then 10 seconds and then tried to install SQL Server Express and it did install it without problem and generated successfull message without any errors and is working fine so far.

Now you can Delete this thread the Microsoft Admin People.
P.S. I like this TechNet forum site but the only lack of this site is that it does not allow us users to delete our own threads.
Maybe I might be misaken but I don't see anywhere a delete button besides the three or sometimes four buttons which
are: Mark as Answer, Reply, Quote and Edit.

Sincerely,
T C

|||

Tony, can you please supply your solution so that it may help others in the future? Congrats on getting it solved. :)

Sam

|||

I am replying to this only on behalf of the users which are struggling with SQL 2005.
If it would be to helping the Programmers or Administrator of MSFT, I would never reply to this blog because they got the job and should try to help people because they get paid for it.
I don't get paid for this to help Microsoft Employee to resolve thier issues.
Myself I am unemployed since last year when I got laid off from a company. Today nobody is helping me with anything, nor to get a job or any interview just because I have only 2 years of work experience.

Anyways let get to the job helping you kindly users.

Since MSFT personnnel could not help me I thought would try to resolve the issue on my own without thier help.


After instaling SQL SERVER 2005, I was missing the MSTDCPRX.dll in the computer that I was installed the SQL 2005 and one thing that I remeber I have done was this.

So I went in another computer that I had Windows XP and searched for the DLL file MSTDCPRX.dll and copy the file and then pasted to the computer that I was missing the file. For those people who do not know where to paste the file, it should be in the directory C:\WINDOWS\system32.

After I copied this file and pasted I did not have any problems anymore with SQL Spars.DLL or any other issues instaling the SQL SERVER 2005.

Hope this will help to all of you who is having problems with SQL SERVER 2005.

Wish you a good day.

Sincerely,

T

Issues with Microsoft SQL Serever 2005 Express Edition and other versions of SQL Express

I have uninstalled the SQL Server Express Edition that I have installed from the CDs that were given to me during a Chicago Conference when READY TO LAUNCH Visual Studio 2005, SQL SERVER 2005, and Biz Talk 2005.

Then I went to microsoft website: http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx and downloaded and installed the so called Microsoft SQL Server 2005 Express Edition and I got the messages Error that you read below. Then I Uninstalled Microsoft SQL Server 2005 Express Edition and went again to msdn website and downloaded Microsoft SQL Server 2005 Express Edition Advanced Services SP1 and installed it. I got again the same message as below.

MESSAGE:

1. First comes a window with the title: “setup.exe – Unable to Locate Component
And it displays a message:

This application has failed to start because MSTDCPRX.dll was not found.

Re-installing the application may fix this problem.

2. After I click the OK button of this window it comes another window with the title: “Microsoft SQL Server 2005 Server Setup”

And it displays a message: Failed to load SqlSpars.dll

Does anybody can tell what is going on with the 3 times I tried to installed different SQL Server 2005 Express Edition and I get the same message?

Thanks for your help and support when you have time to respond.

Sincerely,

TonyC

MORE INFORMATION ON THE:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

1. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.txt

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 87

Aborting queue processing as nested installer has completed

Message pump returning: 87

2. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).txt Running: InvokeSqlSetupDllAction at: 2007/1/20 1:22:8

Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.

Unable to load setup helper module : 87

Message displayed to user

Failed to load SqlSpars.dll

Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0001.cab" Error Code : 2

Running: UploadDrWatsonLogAction at: 2007/1/20 1:22:17

Message pump returning: 87

3. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Datastore.xml

<

<S,<Scope Type="SetupStateScope" Id="">

<Property Id="machineName">B3-XP</Property>

<Property Id="logDirectory">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\</Property>

<Property Id="logSummaryFilename">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt</Property>

<Property Id="logSequenceNumber">1</Property>

<Property Id="primaryLogFiles">{ ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Support.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).log"] }</Property>

<Property Id="watsonFailedAction">InvokeSqlSetupDllAction</Property>

<Property Id="watsonFailedActionErrorCode">87</Property>

<Property Id="watsonFailedFunction">sqls::InvokeSqlSetupDllAction::perform</Property>

<Property Id="watsonFailedFunctionErrorCode">87</Property>

<Property Id="watsonSourceFileAndLineNo">setup\sqlsetupactions.cpp@.1709</Property>

<Property Id="watsonModuleAndVersion">setup.exe@.2005.90.3042.0</Property>

<Property Id="watsonMsi">None</Property>

<Property Id="watsonMsiAndVersion">None</Property>

<Property Id="watsonSourceFile">setup\sqlsetupactions.cpp</Property>

</<Scope>

This application has failed to start because MSTDCPRX.dll was not found.

It seems that DTS is corrupted on your computer. Would you reinstall DTC (Distributed Transaction Coordinator) and try setup.exe again?

|||

Can you be more specific because I am not familiar with what you just said.
1. Can you tell me where to find the DTC or where I can download it so I can reinstal or instal?
Does anybody else also has a different suggestion.
Thanks again

|||

I need more help with the SQL Server Express or more other responses, please.
Is anymore people out there who can tell me what to do?
I am still waiting to here from anybody, I check this forum almost twice a day and I see no answers.
I really would appreciate any of your advice if you look through my LOG files?
If you need me to look for some more code in the Log files like the one named something like log_support.txt which is a very long file I will do that as long as you tell me for what specific line or value or string to look.

Please help and thanks for your time if you try to help me.

Sincerely,
TonyCorrona

|||

Hello there,

PLEASE DELETE THIS THREAD.

Thanks and Regards,
TonyC

|||

Thanks to everybody's time reading my thread and trying to help me maybe.
Anyways, I have fixed the problem on my own without having to reinstall Microsoft Distributed Transaction Coordinator and do all the steps that Microsoft People say in their document they provide in msdn.microsoft site.

My problem above I have fixed using some logics of my head and fixed in less then 10 seconds and then tried to install SQL Server Express and it did install it without problem and generated successfull message without any errors and is working fine so far.

Now you can Delete this thread the Microsoft Admin People.
P.S. I like this TechNet forum site but the only lack of this site is that it does not allow us users to delete our own threads.
Maybe I might be misaken but I don't see anywhere a delete button besides the three or sometimes four buttons which
are: Mark as Answer, Reply, Quote and Edit.

Sincerely,
T C

|||

Tony, can you please supply your solution so that it may help others in the future? Congrats on getting it solved. :)

Sam

|||

I am replying to this only on behalf of the users which are struggling with SQL 2005.
If it would be to helping the Programmers or Administrator of MSFT, I would never reply to this blog because they got the job and should try to help people because they get paid for it.
I don't get paid for this to help Microsoft Employee to resolve thier issues.
Myself I am unemployed since last year when I got laid off from a company. Today nobody is helping me with anything, nor to get a job or any interview just because I have only 2 years of work experience.

Anyways let get to the job helping you kindly users.

Since MSFT personnnel could not help me I thought would try to resolve the issue on my own without thier help.


After instaling SQL SERVER 2005, I was missing the MSTDCPRX.dll in the computer that I was installed the SQL 2005 and one thing that I remeber I have done was this.

So I went in another computer that I had Windows XP and searched for the DLL file MSTDCPRX.dll and copy the file and then pasted to the computer that I was missing the file. For those people who do not know where to paste the file, it should be in the directory C:\WINDOWS\system32.

After I copied this file and pasted I did not have any problems anymore with SQL Spars.DLL or any other issues instaling the SQL SERVER 2005.

Hope this will help to all of you who is having problems with SQL SERVER 2005.

Wish you a good day.

Sincerely,

T

Monday, March 19, 2012

Issues for 64 bit 2003 OS Server from Advanced 2000

Running Standard Edition SQL 2000 on Advanced Server with PAE enabled in the
boot ini (8 gig ram on Adv Svr but only two allocates for Standard)
System is migrating to a 64 bit Advanced Server with 8 GIG RAM... also
Standard Edition SQL 2000 which as we know well, can access only first two
GIG of RAM thus, I think, AWE is completely out of the question.
Is it necessary to enable PAE on the 2003 server? Are there issues that
should be considered for the 64 bit server running SQL 2000 that are
different from an instance running on Advanced Server 2000?
--
Regards,
Jamie
BOL
Configuration -Enabling AWE Memory for SQL Server (2000?)
http://msdn2.microsoft.com/en-us/library/ms190673.aspx
Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
http://msdn2.microsoft.com/en-us/library/ms179301.aspx (2000?)PAE is only useful on 32 bit systems as X64 can access the memory directly
and does not require it. With SQL2000 Std you will only ever be able to use
2GB max. So why bother going thru these motions? Most of the 8GB is wasted
and you will reap none of the benefits of X64 in this state. I highly
recommend you upgrade to SQL2005 Std X64 edition otherwise this is most
likely a waste of your time.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:B1414628-6F34-46A7-83B8-6E8EFB4241F9@.microsoft.com...
> Running Standard Edition SQL 2000 on Advanced Server with PAE enabled in
> the
> boot ini (8 gig ram on Adv Svr but only two allocates for Standard)
> System is migrating to a 64 bit Advanced Server with 8 GIG RAM... also
> Standard Edition SQL 2000 which as we know well, can access only first two
> GIG of RAM thus, I think, AWE is completely out of the question.
> Is it necessary to enable PAE on the 2003 server? Are there issues that
> should be considered for the 64 bit server running SQL 2000 that are
> different from an instance running on Advanced Server 2000?
> --
> Regards,
> Jamie
> BOL
> Configuration -Enabling AWE Memory for SQL Server (2000?)
> http://msdn2.microsoft.com/en-us/library/ms190673.aspx
> Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
> http://msdn2.microsoft.com/en-us/library/ms179301.aspx (2000?)
>|||A decision was made to wait for SP1 on SQL Server 2008. When that hits, we
upgrade.
Meanwhile...
--
Regards,
Jamie
"Andrew J. Kelly" wrote:
> PAE is only useful on 32 bit systems as X64 can access the memory directly
> and does not require it. With SQL2000 Std you will only ever be able to use
> 2GB max. So why bother going thru these motions? Most of the 8GB is wasted
> and you will reap none of the benefits of X64 in this state. I highly
> recommend you upgrade to SQL2005 Std X64 edition otherwise this is most
> likely a waste of your time.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:B1414628-6F34-46A7-83B8-6E8EFB4241F9@.microsoft.com...
> > Running Standard Edition SQL 2000 on Advanced Server with PAE enabled in
> > the
> > boot ini (8 gig ram on Adv Svr but only two allocates for Standard)
> > System is migrating to a 64 bit Advanced Server with 8 GIG RAM... also
> > Standard Edition SQL 2000 which as we know well, can access only first two
> > GIG of RAM thus, I think, AWE is completely out of the question.
> >
> > Is it necessary to enable PAE on the 2003 server? Are there issues that
> > should be considered for the 64 bit server running SQL 2000 that are
> > different from an instance running on Advanced Server 2000?
> > --
> > Regards,
> > Jamie
> > BOL
> > Configuration -Enabling AWE Memory for SQL Server (2000?)
> > http://msdn2.microsoft.com/en-us/library/ms190673.aspx
> >
> > Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
> > http://msdn2.microsoft.com/en-us/library/ms179301.aspx (2000?)
> >
> >
>|||I'm primarily concerned that there may be pitfalls unknown when we do this
move from the old server to the new. It isn't by choice that we are putting
2000 on this new 64 bit server (16 Gig Ram - 8 Processors). Our production
server is failing and we are scrambling to get it fixed and running on the
new server ASAP. I agree that it would be wiser to go with 2005.
--
Regards,
Jamie
"Andrew J. Kelly" wrote:
> PAE is only useful on 32 bit systems as X64 can access the memory directly
> and does not require it. With SQL2000 Std you will only ever be able to use
> 2GB max. So why bother going thru these motions? Most of the 8GB is wasted
> and you will reap none of the benefits of X64 in this state. I highly
> recommend you upgrade to SQL2005 Std X64 edition otherwise this is most
> likely a waste of your time.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:B1414628-6F34-46A7-83B8-6E8EFB4241F9@.microsoft.com...
> > Running Standard Edition SQL 2000 on Advanced Server with PAE enabled in
> > the
> > boot ini (8 gig ram on Adv Svr but only two allocates for Standard)
> > System is migrating to a 64 bit Advanced Server with 8 GIG RAM... also
> > Standard Edition SQL 2000 which as we know well, can access only first two
> > GIG of RAM thus, I think, AWE is completely out of the question.
> >
> > Is it necessary to enable PAE on the 2003 server? Are there issues that
> > should be considered for the 64 bit server running SQL 2000 that are
> > different from an instance running on Advanced Server 2000?
> > --
> > Regards,
> > Jamie
> > BOL
> > Configuration -Enabling AWE Memory for SQL Server (2000?)
> > http://msdn2.microsoft.com/en-us/library/ms190673.aspx
> >
> > Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
> > http://msdn2.microsoft.com/en-us/library/ms179301.aspx (2000?)
> >
> >
>|||Wow, must be nice to have wasted resources sitting around for 1 year +,
which is probably when you will be able to upgrade to SQL 2008, sp1. :)
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:B5A4ED33-8758-49C2-BFA3-5960066E5568@.microsoft.com...
>A decision was made to wait for SP1 on SQL Server 2008. When that hits, we
> upgrade.
> Meanwhile...
> --
> Regards,
> Jamie
>
> "Andrew J. Kelly" wrote:
>> PAE is only useful on 32 bit systems as X64 can access the memory
>> directly
>> and does not require it. With SQL2000 Std you will only ever be able to
>> use
>> 2GB max. So why bother going thru these motions? Most of the 8GB is
>> wasted
>> and you will reap none of the benefits of X64 in this state. I highly
>> recommend you upgrade to SQL2005 Std X64 edition otherwise this is most
>> likely a waste of your time.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
>> news:B1414628-6F34-46A7-83B8-6E8EFB4241F9@.microsoft.com...
>> > Running Standard Edition SQL 2000 on Advanced Server with PAE enabled
>> > in
>> > the
>> > boot ini (8 gig ram on Adv Svr but only two allocates for Standard)
>> > System is migrating to a 64 bit Advanced Server with 8 GIG RAM... also
>> > Standard Edition SQL 2000 which as we know well, can access only first
>> > two
>> > GIG of RAM thus, I think, AWE is completely out of the question.
>> >
>> > Is it necessary to enable PAE on the 2003 server? Are there issues
>> > that
>> > should be considered for the 64 bit server running SQL 2000 that are
>> > different from an instance running on Advanced Server 2000?
>> > --
>> > Regards,
>> > Jamie
>> > BOL
>> > Configuration -Enabling AWE Memory for SQL Server (2000?)
>> > http://msdn2.microsoft.com/en-us/library/ms190673.aspx
>> >
>> > Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
>> > http://msdn2.microsoft.com/en-us/library/ms179301.aspx (2000?)
>> >
>> >
>>|||You are probably talking close to a year away for that. Oh well.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:B5A4ED33-8758-49C2-BFA3-5960066E5568@.microsoft.com...
>A decision was made to wait for SP1 on SQL Server 2008. When that hits, we
> upgrade.
> Meanwhile...
> --
> Regards,
> Jamie
>
> "Andrew J. Kelly" wrote:
>> PAE is only useful on 32 bit systems as X64 can access the memory
>> directly
>> and does not require it. With SQL2000 Std you will only ever be able to
>> use
>> 2GB max. So why bother going thru these motions? Most of the 8GB is
>> wasted
>> and you will reap none of the benefits of X64 in this state. I highly
>> recommend you upgrade to SQL2005 Std X64 edition otherwise this is most
>> likely a waste of your time.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
>> news:B1414628-6F34-46A7-83B8-6E8EFB4241F9@.microsoft.com...
>> > Running Standard Edition SQL 2000 on Advanced Server with PAE enabled
>> > in
>> > the
>> > boot ini (8 gig ram on Adv Svr but only two allocates for Standard)
>> > System is migrating to a 64 bit Advanced Server with 8 GIG RAM... also
>> > Standard Edition SQL 2000 which as we know well, can access only first
>> > two
>> > GIG of RAM thus, I think, AWE is completely out of the question.
>> >
>> > Is it necessary to enable PAE on the 2003 server? Are there issues
>> > that
>> > should be considered for the 64 bit server running SQL 2000 that are
>> > different from an instance running on Advanced Server 2000?
>> > --
>> > Regards,
>> > Jamie
>> > BOL
>> > Configuration -Enabling AWE Memory for SQL Server (2000?)
>> > http://msdn2.microsoft.com/en-us/library/ms190673.aspx
>> >
>> > Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
>> > http://msdn2.microsoft.com/en-us/library/ms179301.aspx (2000?)
>> >
>> >
>>|||Sure there is always the unknown unless you test it first. It is a whole new
OS, drivers etc. Theoretically it should work fine as long as you have all
the proper drivers and are doing just basic database operations. But I have
to assume there are other apps on the same server correct? Otherwise that
is a lot of wasted hardware since 200 Std only supports 4 procs and 2GB of
memory.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:EC033C23-2758-42D5-9BA8-BB61DF2772D2@.microsoft.com...
> I'm primarily concerned that there may be pitfalls unknown when we do this
> move from the old server to the new. It isn't by choice that we are
> putting
> 2000 on this new 64 bit server (16 Gig Ram - 8 Processors). Our
> production
> server is failing and we are scrambling to get it fixed and running on the
> new server ASAP. I agree that it would be wiser to go with 2005.
> --
> Regards,
> Jamie
>
> "Andrew J. Kelly" wrote:
>> PAE is only useful on 32 bit systems as X64 can access the memory
>> directly
>> and does not require it. With SQL2000 Std you will only ever be able to
>> use
>> 2GB max. So why bother going thru these motions? Most of the 8GB is
>> wasted
>> and you will reap none of the benefits of X64 in this state. I highly
>> recommend you upgrade to SQL2005 Std X64 edition otherwise this is most
>> likely a waste of your time.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
>> news:B1414628-6F34-46A7-83B8-6E8EFB4241F9@.microsoft.com...
>> > Running Standard Edition SQL 2000 on Advanced Server with PAE enabled
>> > in
>> > the
>> > boot ini (8 gig ram on Adv Svr but only two allocates for Standard)
>> > System is migrating to a 64 bit Advanced Server with 8 GIG RAM... also
>> > Standard Edition SQL 2000 which as we know well, can access only first
>> > two
>> > GIG of RAM thus, I think, AWE is completely out of the question.
>> >
>> > Is it necessary to enable PAE on the 2003 server? Are there issues
>> > that
>> > should be considered for the 64 bit server running SQL 2000 that are
>> > different from an instance running on Advanced Server 2000?
>> > --
>> > Regards,
>> > Jamie
>> > BOL
>> > Configuration -Enabling AWE Memory for SQL Server (2000?)
>> > http://msdn2.microsoft.com/en-us/library/ms190673.aspx
>> >
>> > Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
>> > http://msdn2.microsoft.com/en-us/library/ms179301.aspx (2000?)
>> >
>> >
>>|||I experienced a worse scenario. Listen to this:
I was setting up SQL Server Cluster on two DL580 of HPs with 4 Dual Core
CPUs and 16GB of RAMs... Nice config, yea?
There was a failed cluster node when we went to the scene. I mean, they were
using their SQL Servers for about 6 months...
Servers were x86 and non of the /PAE and AWE was being used. Even /3GB
wasn't used.
I went to the hospital's IT manager and told him about the situation. I told
him you have 16GB of RAM on your servers and your SQL Servers are using only
2GB of RAM out of 16GB and the rest of it is just sitting for months. And
guest what he said? He said, "I knew, but I didn't wanna touch it". Funny,
huh?
--
Ekrem Ã?nsoy
http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:B5A4ED33-8758-49C2-BFA3-5960066E5568@.microsoft.com...
>A decision was made to wait for SP1 on SQL Server 2008. When that hits, we
> upgrade.
> Meanwhile...
> --
> Regards,
> Jamie
>
> "Andrew J. Kelly" wrote:
>> PAE is only useful on 32 bit systems as X64 can access the memory
>> directly
>> and does not require it. With SQL2000 Std you will only ever be able to
>> use
>> 2GB max. So why bother going thru these motions? Most of the 8GB is
>> wasted
>> and you will reap none of the benefits of X64 in this state. I highly
>> recommend you upgrade to SQL2005 Std X64 edition otherwise this is most
>> likely a waste of your time.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
>> news:B1414628-6F34-46A7-83B8-6E8EFB4241F9@.microsoft.com...
>> > Running Standard Edition SQL 2000 on Advanced Server with PAE enabled
>> > in
>> > the
>> > boot ini (8 gig ram on Adv Svr but only two allocates for Standard)
>> > System is migrating to a 64 bit Advanced Server with 8 GIG RAM... also
>> > Standard Edition SQL 2000 which as we know well, can access only first
>> > two
>> > GIG of RAM thus, I think, AWE is completely out of the question.
>> >
>> > Is it necessary to enable PAE on the 2003 server? Are there issues
>> > that
>> > should be considered for the 64 bit server running SQL 2000 that are
>> > different from an instance running on Advanced Server 2000?
>> > --
>> > Regards,
>> > Jamie
>> > BOL
>> > Configuration -Enabling AWE Memory for SQL Server (2000?)
>> > http://msdn2.microsoft.com/en-us/library/ms190673.aspx
>> >
>> > Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
>> > http://msdn2.microsoft.com/en-us/library/ms179301.aspx (2000?)
>> >
>> >
>>|||Definitely a case of fear paralysis. If they didn't NEED the performance
then it was just money sitting for nothing. But if they also had poor
performance then they could have actively been losing money due to the
slowness and that is when it is really a shame!!
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
news:2B1B5E4E-A07D-4D19-9D69-93F1E0C6ADA5@.microsoft.com...
>I experienced a worse scenario. Listen to this:
> I was setting up SQL Server Cluster on two DL580 of HPs with 4 Dual Core
> CPUs and 16GB of RAMs... Nice config, yea?
> There was a failed cluster node when we went to the scene. I mean, they
> were using their SQL Servers for about 6 months...
> Servers were x86 and non of the /PAE and AWE was being used. Even /3GB
> wasn't used.
> I went to the hospital's IT manager and told him about the situation. I
> told him you have 16GB of RAM on your servers and your SQL Servers are
> using only 2GB of RAM out of 16GB and the rest of it is just sitting for
> months. And guest what he said? He said, "I knew, but I didn't wanna touch
> it". Funny, huh?
> --
> Ekrem Önsoy
> http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
> MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
>
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:B5A4ED33-8758-49C2-BFA3-5960066E5568@.microsoft.com...
>>A decision was made to wait for SP1 on SQL Server 2008. When that hits,
>>we
>> upgrade.
>> Meanwhile...
>> --
>> Regards,
>> Jamie
>>
>> "Andrew J. Kelly" wrote:
>> PAE is only useful on 32 bit systems as X64 can access the memory
>> directly
>> and does not require it. With SQL2000 Std you will only ever be able to
>> use
>> 2GB max. So why bother going thru these motions? Most of the 8GB is
>> wasted
>> and you will reap none of the benefits of X64 in this state. I highly
>> recommend you upgrade to SQL2005 Std X64 edition otherwise this is most
>> likely a waste of your time.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
>> news:B1414628-6F34-46A7-83B8-6E8EFB4241F9@.microsoft.com...
>> > Running Standard Edition SQL 2000 on Advanced Server with PAE enabled
>> > in
>> > the
>> > boot ini (8 gig ram on Adv Svr but only two allocates for Standard)
>> > System is migrating to a 64 bit Advanced Server with 8 GIG RAM... also
>> > Standard Edition SQL 2000 which as we know well, can access only first
>> > two
>> > GIG of RAM thus, I think, AWE is completely out of the question.
>> >
>> > Is it necessary to enable PAE on the 2003 server? Are there issues
>> > that
>> > should be considered for the 64 bit server running SQL 2000 that are
>> > different from an instance running on Advanced Server 2000?
>> > --
>> > Regards,
>> > Jamie
>> > BOL
>> > Configuration -Enabling AWE Memory for SQL Server (2000?)
>> > http://msdn2.microsoft.com/en-us/library/ms190673.aspx
>> >
>> > Configuration -Enabling Memory Support for Over 4 GB of Physical
>> > Memory
>> > http://msdn2.microsoft.com/en-us/library/ms179301.aspx (2000?)
>> >
>> >
>>
>

Monday, March 12, 2012

Issues about deploy Business Logic Handler to a web server for web replication.

Pocket PC 2003, SQL Compact Edition, SQL2005, IIS6.0

I implemented a business logic handler to deal with conflicts. When I deploy it on the SQL server which is also the web replication server, the logic handler seems working fine. However, if I deploy this handler to another web server. The logic handler failed to be loaded.

My enviroment settings are desribed as below.

Machine A, distributor, with database and publication. The business logic handler is deployed at C:\Program Files\Microsoft SQL Server\90\COM\BusinessLogicHandler.dll. It's registered by using sp_registercustomresolver. The @.assembly is specified as @.assembly=C:\Program Files\Microsoft SQL Server\90\COM\BusinessLogicHandler.dll';

Machine B, IIS server. The same business logic handler is deployed at C:\Program Files\Microsoft SQL Server\90\COM\BusinessLogicHandler.dll on the Machine B itself.

When I ran the web replication, the Merge Agent reported the error as below.

Error loading custom assembly "C:\Program Files\Microsoft SQL Server\90\COM\BusinessLogicHandler.dll", Error: "Could not load file or assembly 'C:\\Program Files\\Microsoft SQL Server\\90\\COM\\BusinessLogicHandler.dll' or one of its dependencies. The given assembly name or codebase was invalid.

It seemed that the Merge Agent had trouble to find my logic handler because the path reported in the error log has two backward slashes. I have no idea where did that came from. I am not sure if that's the cause of the error. Without business logic handler. I had successfully finished web replication of Machine B to sync with Machine A. If I setup web replication directly on Machine A with business logic handler, I can successfully sync as well.

Does anyone has any idea about how to correctly deploy business logic handler on a web server?

Thanks,

Nigel

It seems that if I sign the dll and install it in the global assembly of Mahine B. The problem went away. Does it mean we should deploy our assembly in the global assembly instead of the path "@.assembly" of distributor when we deploy our business logic handle to a IIS web replication server? The SQL2005 document does not specify how we should deploy the business logic handler for the web synchronization server. It would be nice if it could MS can provide more detail in business logic handler deploymont. However, it still seems to me it's a bug for the Merge Agent not be able to find the business logic handler in my previous post. Still don't know where the backward slashes come from.

If anyone has more details about this issue, please advise.

Thanks,

Nigel

Friday, February 24, 2012

Issue Resolved

Hello,

I have installed SQL Server 2005 Express edition but can not 'launch' or 'invoke' the application. When I look under ' SQL Server Configuratin Manager' there are 2 files, SQL Server and SQL Server Browser which the status of both is 'Running'. I do not see any other files or icons to launch the application. Can anyone tell me what other steps I need to take or install to run the application and start working with it?

Thank you.

SQL Server is a 'backend' database server. There is no user application to 'launch' or 'invoke'.

However, I suspect from the nature of your posting, that you are wanting a way to interact with the data server. You can download a free copy of SQL Server Management Studio Express from here. And a tutorial about how to use it is available here.

Here are some additional resources that may be helpful.

http://www.microsoft.com/sql/editions/express/default.mspx

http://msdn.microsoft.com/vstudio/express/sql/default.aspx

http://msdn.microsoft.com/vstudio/express/sql/learning/default.aspx

|||

Thank you for your response, Arnie.

The links you provided are actually the links where I downloaded SQL 2005. Let me simplify my question: How can I query a file using SQL 2005 in Windows environment?

Thanks.

|||

I guess I don't understand what you are asking.

To retreive data from SQL Server, you MUST have a client application.

Client applications include

SQL Server Management Studio

SQLCmd.exe

Custom Applications

Pruchased Applications

|||

If you are online, let's get on the messenger for a few minutes to discuss this.

Thanks

|||

Time differences may not allow that.

Try to describe your situation, and what you are atttempting to accomplish.

(Also, Use the [Reply] button on this post INSTEAD of starting a new thread.)

|||

Thank you for gettin back to me Arnie. The issue is resolved now. I had to download one more file in order to proceed.

Thanks again.

Issue installing SQL Server Express on Visual Studio Beta 2

Hi,

I have installed VS 2005 Beta 2 (Team System) using a DVD available from MS TEch Ed. This also installs SQL Server 2005 Express edition along with other tools. This installation is done on a vpc.

However when I try to install SQL Server Express Manager over this installation, I get "The installer package could not be opened. Contact the vendor to make sure to verify that the Windows installer package is valid".

Is there a solution to get this resolved ?

Thanks in advance !
It likely that you need to download the file again. Also not that you may need to uninstall the .Net Framework and re-install the version that SQL Server shipped in its June CTP as the NetFx version between Vs Beta 2 and SQL CTP June is different.

-Euan

Monday, February 20, 2012

Issue

Anyone know this answer?
[New].[Configuration:]
O/S: Windows XP Service Pack2 on a machine named MERCURY
SQL Server Developer's Edition SP4
[Old].[Configuration]
O/S: Windows 2000 on a machine called PIONEER
SQL Server Developer's Edition SP4
[Problem].[ Description:]
1. Created 25 clean, functional DTS packages on PIONEER. On that machine,
any task in DTS designer which allows the user to select a single table name
from a drop-down list (Combo Box) (such as Bulk Insert Tasks), have Square
Delimited Indentifiers. For example:
[DBO].[TABLENAME1]
[DBO].[TABLENAME1]
[DBO].[TABLENAME1]
[DBO].[TABLENAME1]
2. Packages were then moved to a new computer, running the configuration
shown at the top.On that computer, the ODBC Administrator has default
settings for each new connection. These settings include the check box for
ANSI Quoted Identifiers which are ON (Checked). That is the same default as
Windows 2000 ODBC. We unchecked the box for every new connection.
3. When the packages from the PIONEER machine with square bracketed
identifiers in the Drop down lists were opened then square brackets
disappeared from the first display item as soon as you click the button of
the drop-down list. The drop down functionality apparently dropped the list
items from the old package, required the database with the same name on
PIONEER, repopulated the list, but this time, EVERY SINGLE IDENTIFIER WAS
DELIMITED WITH DOUBLE-QUOTES, and, worst of all, the correct name was
replaced with the first alphabetical name.The new list looked like this:
"DBO"."TABLENAME1"
"DBO"."TABLENAME1"
"DBO"."TABLENAME1"
"DBO"."TABLENAME1"
Doesn't that JUST BLOW!
Also, it appears that no connections can recognize the objects anymore.
Robert

> Anyone know this answer?
> [New].[Configuration:]
> O/S: Windows XP Service Pack2 on a machine named MERCURY
> SQL Server Developer's Edition SP4
> [Old].[Configuration]
> O/S: Windows 2000 on a machine called PIONEER
> SQL Server Developer's Edition SP4
> [Problem].[ Description:]
> 1. Created 25 clean, functional DTS packages on PIONEER. On that machine,
> any task in DTS designer which allows the user to select a single table
> name from a drop-down list (Combo Box) (such as Bulk Insert Tasks), have
> Square Delimited Indentifiers. For example:
> [DBO].[TABLENAME1]
> [DBO].[TABLENAME1]
> [DBO].[TABLENAME1]
> [DBO].[TABLENAME1]
> 2. Packages were then moved to a new computer, running the configuration
> shown at the top.On that computer, the ODBC Administrator has default
> settings for each new connection. These settings include the check box for
> ANSI Quoted Identifiers which are ON (Checked). That is the same default
> as Windows 2000 ODBC. We unchecked the box for every new connection.
> 3. When the packages from the PIONEER machine with square bracketed
> identifiers in the Drop down lists were opened then square brackets
> disappeared from the first display item as soon as you click the button of
> the drop-down list. The drop down functionality apparently dropped the
> list items from the old package, required the database with the same name
> on PIONEER, repopulated the list, but this time, EVERY SINGLE IDENTIFIER
> WAS DELIMITED WITH DOUBLE-QUOTES, and, worst of all, the correct name was
> replaced with the first alphabetical name.
>
>
>

Isqlw for sql server mobile edition (sql ce 3)

In sql ce 2.0 in window ce 2003, I use isqlw20.exe to create database and table. Developed application with eVC++ 4.0

Now I have to use window mobile 5, VS 2005 for native C++ development, sql server mobile edition, but I can't found isqlw for this version of sql. I do not have sql server install in my desktop PC. So how could I create database and table with the pocket pc's database ?

Thanks.

ISQLW30.EXE is available from SQL Mobile 3.0 for Pocket PC and Pocket PC Phone Edition Devices/Emulators.

If you have installed SQL Mobile 3.0 cabs, you should find a shortcut getting created automatically in Start Menu.

Thanks,

Laxmi Narsimha Rao ORUGANTI, SQL Mobile, Microsoft Corporation