Different versions of SQL Server 2005 Developer Edition

Some of our business processes still use SQL Server 2005 and I need to install Developer Edition on my desktop.
I have following downloads available in my MSDN subscription (other than Itanium):
SQL Server 2005 Developer Edition - DVD (English) - 1 DVD ISO
SQL Server 2005 Developer Edition - 64-bit Extended - 2x CD ISO
SQL Server 2005 Developer Edition - 32-bit - 2x CD ISO
The desktop is running 64-bit OS, so I definitely want to install 64-bit version. However, I am not sure what this "Extended" version available on CD-s is. Is this the only 64-bit version in existence? Or are there 2 different 64-bit versions
- "Extended" and "Non-Extended" (with non-extended possibly available on DVD - I haven't downloaded any images yet)?

SQL Server 2005 Developer Edition - DVD (English) - 1 DVD ISO
SQL Server 2005 Developer Edition - 64-bit Extended - 2x CD ISO
SQL Server 2005 Developer Edition - 32-bit - 2x CD ISO
The desktop is running 64-bit OS, so I definitely want to install 64-bit version. However, I am not sure what this "Extended" version available on CD-s is. Is this the only 64-bit version in existence? Or are there 2 different 64-bit versions - "Extended"
and "Non-Extended" (with non-extended possibly available on DVD - I haven't downloaded any images yet)?
SQL server 2005 is outdated so sorry if my answer is not to the point . First DVD version seems to me like installable which has both database engine and client tools present in it for installation
For second, SQL server 2005 installable was available in 2 CD's 1st CD was to install database engine/SSIS/SSAS/ SSRS features while second CD was to install specifically clint tools,books online legacy support . Its not possible to comment further without
looking at contents but I guess you can use 2nd one. CD 1 would have one part of installable and CD 2 would have second
And of course 3rd one is 32 bit of 2nd one.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Similar Messages

MS SQL Server 2005 Developer Edition

Hi,
We are developing a legal management product on SAP platform
We would have SQL Server to be used as a database for SAP ECC 6.0 in DEVELOPEMENT environment
The landscape of the planned development environment has a total of 8 servers. We understand that a separate MS SQL Server 2005 ( Question :- Enterprise / standard / Developer ??? ) edition is required for all the servers Each server will run its own instance. Each server will have 2 Intel Xeon CPUs with quad cores.
We understand that there will not be any users accessing the database directly. Instead, the SAP ECC software will create its own schema and users ( at most 4).
1) Please let us know which edition is best suitable for us for above scenario .
2) Does SAP ECC work on SQL Server 2005 Developer edition ?
3) Can we have one instance of SQL Server be used and multiple databases for dev, qa and prod be created from it
Your prompt response will much be appreciated
Thanks a ton !

1) Please let us know which edition is best suitable for us for above scenario .
SAP ONLY supports Enterprise edition.
2) Does SAP ECC work on SQL Server 2005 Developer edition?
No SAP willnot work on SQL Server 2005 edition.
3) Can we have one instance of SQL Server be used and multiple databases for dev, qa and prod be created from it.
Yes, technically it is possoble. But not at all recommended by SAP.
Regards,
SK

SQL Server 2005 Developer Edition

Hello Experts,
We have SQL Server 2005 Developer Edition, does it work fine with SBO 2007A or SBO 8.8. Is there any problem in using SQL Server 2005 Developer Edition / any body has experienced any problem before ?
kindly help!

Dear,
Check the below link:
https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000705857&_SCENARIO=01100035870000000183&_ADDINC=011000358700001192682007E&
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1434624&nlang=E&smpsrv=https%3a%2f%2fwebsmp110%2esap-ag%2ede
Thanks,
Neetu

SQL Server 2014 Developer Edition

Microsoft is no longer offering version 2012 developer edition. So, is SQL Server 2014 developer edition ok to use with SQL Server 2012? Thanks.

AFAIK you can ask/purchase developer edition in local MS office.. But it is certainly OK to use SQL Server 2012 Dev Edition to manage servers from different versions.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Installation of SQL Server 2005 Express Edition with Mobile Sales 5.0 SP07

Dear gurus,
I have the following question for you: is it possible to run Mobile Sales 5.0 SP07 with SQL Server 2005 Exp Edition? The specifications that I have found for both applications are:
- MOBILE CLIENT:
Installation of Mobile Client with CRM release 5.0 requires the installation of Microsoft .NET framework 1.1. (OSS note 879643)
- SQL Server Express Edition: Microsoft .NET framework 2. 0
Has anyone installed it this way?
Thank you in advance,
Judit.

Hello Judith,
It is possible to have 5.0 SP07 Mobile Client installed on machine with SQL Server Express edition. For more information on this, you may refer the installation guide for 5.0 SP07 (Software Pre-requisites section, SQL Server versions). However, please note, you cannot install 5.0 SP07 Mobile Development Workstation on Express edition due to the large repository size.
You may feel free to get back to me in case of any further concerns/comments.
Thanks and Best Regards,
Niranjan
(Reward points will be appreciated if you feel this issue is resolved).
N

Installing SQL Server 2012 Developer Edition or wait for SP2?

Hi everyone,
I just received my copy of SQL Server 2012 Developer Edition I ordered. As usual, before installing, I searched the web for any hint or other stuff on the subject.
I first found that SP1 was already available. Honestly I prefer installing using the last version available instead of upgrading. I found the SP1 install package using the following web address:
http://www.microsoft.com/fr-ca/download/details.aspx?id=35575
Is this the right install package to use?
Now, still reading everything I could find on that SP1, I found stories about major issues with SP1.
Two examples I remember:
http://connect.microsoft.com/SQLServer/feedback/details/770630
http://support.microsoft.com/kb/2793634/en-us?wa=wsignin1.0
Two others (not specifically related to SP1):
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/a0da3372-ab3d-4af0-b4c4-0d47163e0e03/
http://www.sqlperformance.com/2012/11/system-configuration/2012-cal-problems
My question. Should I wait for SP2? If so, any target date when it should be available?
If not, what would you recommend as the logic install sequence? Should I look for any cumulative update(s)? Any other "manual settings" I should consider?
Finally, can someone guide me regarding what options I should choose while installing. My main goal is to program/build C++, C# applications using VS2010 that will interface with SQL Server for data storage purposes (add/update/delete,
batch update/delete) and reports.
Hope to hear from someone.
Stephane
BTW: My current setup is the following:
Intel(R) Core(TM)2 CPU [email protected]
3.00 Go
Vista Ultimate SP2 32bits
Visual Studio 2010 Professional Edition (which will be upgraded to last SP once installed)

Hi again,
I proceeded with download of CU7. On Microsoft's webpage, there are several files we can download:
2012_SP1_DAC_CU7_2894115_11_0_3393_x86
2012_SP1_AOrcleDes_CU7_2894115_11_0_3393_x86
2012_SP1_AOrcleSer_CU7_2894115_11_0_3393_x86
2012_SP1_PPExcel_CU7_2894115_11_0_3393_x86
SQLServer2012_SP1_CU7_2894115_11_0_3393_x86
Which one I should choose?
Also, some people reported having problems installing this update.
http://blogs.msdn.com/b/sqlreleaseservices/archive/2013/11/19/cumulative-update-7-for-sql-server-2012-sp1.aspx
Can you comment?
Thanks again for helping,
Stéphane

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Log File Issue In SQL server 2005 standard Edition

We have database of size 375GB .The data file has 80 GB free space within .When trying to rebuild the index we had 450 GB free space on the disk where Log file is residing.The rebuild index activity failed due to space issue.added more space and got the
job done successfully
The Log file has grow up to 611GB to complete the rebuild index.
version :SQL server 2005 Standard Edition .Is ther a way to estimate the space required for rebuild index in this version.
I am aware we notmaly allocate 1.5 times of data file.But in this case It was totaly wrong.
Any suggestion with examples would be appreciated.
Raghu

OK, there's a few things here.
Can you outline for everybody the recovery model you are using, the frequency with which you take full, differential and transaction log backups.
Are you selectively rebuilding your indexes or are you rebuilding everything?
How often are you doing this? Do you need to?
There are some great resources on automated index maintenance, check out
this post by Kendra Little.
Depending on your recovery point objectives I would expect a production database to be in the full recovery mode and as part of this you need to be taking regular log backups otherwise your log file will just continue to grow. By taking a log backup it will
clear out information from inactive VLF's and therefore allow SQL Server to write back to those VLF's rather than having to grow the log file. This is a simplified version of events, there are caveats.
A VLF will be marked as active if it still has an open transaction in it or there is a HA option that still requires that data to be available as that data has not been copied to another node yet.
Most customers that I see take transaction log backups every 15 - 30 minutes, but this really does depend upon how much data your company can afford to lose. That's another discussion for another day.
Make sure that you take a transaction log backup prior to your job that does your index rebuilds (hopefully a smart job not a sledge hammer job).
As mentioned previously swapping to bulk logged can help to reduce the size of the amount of information logged during index rebuilds. If you do this make sure to swap back into the full recovery model straight after and perform a full backup. There are
problems with the ability to do point in time restores whilst in the bulk logged recovery model, so you need to reduce the amount of time you use it.
Really you also need to look at how your indexes are created does the design of them lead to them being fragmented on a regular basis? Are they being used? Are there better indexes out there that can help performance?
Hopefully that should put you on the right track.
If you find this helpful, please mark the post as helpful,
If you think this solves the problem, please propose or mark it an an answer.
Please provide details on your SQL Server environment such as version and edition, also DDL statements for tables when posting T-SQL issues
Richard Douglas
My Blog: Http://SQL.RichardDouglas.co.uk
Twitter: @SQLRich

ColdFusion and MS SQL Server 2005 Enterprise Edition

Trying to get ColdFusion (Developers Edition) to communicate
with MS SQL Server 2005 (Enterprise Edition). I have ColdFusion
running on username = admin; password = as set up when installed.
Have also tried setting up a user account with my Windows desktop
username and password in case ColdFusion needed to be logged on as
the same user as the SQL server. I have full admin permissions on
the SQL Server (with Windows authentication), and am the database
"owner" of the database on the server. In either ColdFusion login
case, when I try to "add a data source", with driver = Microsift
SQL Server, I get.....
Connection verification failed for data source: CFtoVolcano
java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver][SQLServer]Login failed for user 'kewing'.
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC Driver][SQLServer]Login failed for user
'kewing'.
Went to help files (troubleshooting area) and verified that
the local web browser (IIS) and Cold Fusion ARE running. Next step
takes me to "Change ColdFusion user account" which starts with
"Open Control Panel and select ColdFusion 8 App Server and click
Startup". I don't see that choice in MyComputer/ControlPanel. Not
even sure if this is going to ba another dead end anyway!!!
HELP! This shouldn't be this difficult! I'm not using some
weird version of SQL!

To use the default SQL drivers bundled with CF you need to
use SQL authentication (which is disabled by default I think) in
SQL Server 2005. If you enable SQL (mixed mode) authentication and
create a user you can then add the data source in the CF admin.
Alternatively, in order to use integrated windows
authentication with SQL server your CF service needs to run as
specific user. (It sounds like you've already done this) and you
will need to use Microsoft's JDBC driver
Driver download (MS JDBC Driver)
http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C 1BA&displaylang=en
Connecting with Integrated authentication (MS JDBC Driver)
http://msdn2.microsoft.com/en-us/library/ms378428.aspx#Connectingintegrated

MS SQL Server 2005 - Express Edition?

I am interested to learn about database development for use
with CF dynamic development. Before I make any significant
financial investments I'm wondering if
MS SQL Server 2005
Express Edition is a reasonable place to start learning
about db development.
The Adobe ColdFusion 8 SYSTEMS SUPPORT MATRI X indicates
compatibility with: MS SQL Server 7.0, 2000, 2005 - Does this
compatibility include the FREE
MS SQL Server 2005
Express Edition ?
Does it bother MS that folks may want to use their db
solutions with a competitor's dynamic-development solutions? In
other words, are the compatible db products fully functional with
CF?

personally i like ms sql as i have always used it and am
familiar with it. I think mysql is the choice more for PHP
developers and I think CF works better with MS SQL. A definate
choice of preference though, i ilke the way i can install as many
instances as I like.
eg 1 for websites
1 for applications etc
there is merit in both but here in UK/Ireland mysql is not as
popular as MS SQL.

Installing SharePoint 2013 with SQL Server 2012 Developer Edition

Hi,
Can we use SQL Server 2012 Developer edition with SharePoint 2013? One thing that came to my mind was setting max degree of parallelism, is that supported in Developer edition? Looking forward to your assistance here.
Thanks,
kashif

I'm slightly incorrect. See http://download.microsoft.com/download/6/4/A/64A1EC8F-F575-41E1-9D34-821FA9F98F8E/SQL_Server_2012_Licensing_Reference_Guide.pdf.
Licensing SQL Server for Non-production Use
The SQL Server 2012 Developer Edition is a full-function version of the SQL Server software—with all the
features and capabilities of the Enterprise edition—licensed under the Developer Tools model, which is a “per
user” model. One license is required for each person that accesses or uses the software.
When using SQL Server software for development, test or demonstration purposes, only the users are licensed
and there is no need for a corresponding license for the actual server systems running SQL Server software in
this case.
As long as only licensed users have access to the software, customers can install as many copies of the software
on any number of servers that are used exclusively for development, test or demonstration purposes. This
is significant, because it allows customers to run the software on multiple devices (for testing purposes, for
example) without having to license each non-production server system.
But no, as you can see above, you'll have no issues with the software (Developer Edition is Enterprise Edition with licensing restrictions, but no functionality restrictions).
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SQL Server 2005 Workgroup Edition compatibility for SAP B1 2005B

Hi Experts,
Please advise SQL Server 2005 Workgroup Edition can be used as the backend for SAP Business One 2005B.
Thanks,
Shakeel

Hi
Please go to:SAP service portal-product availability-supported platform-database platform
For 2005 B version we could get the following supportted information:
Microsoft?SQL Server 2005 SP2
- 32 Bit / 64 Bit (x64)
- Express (3), Workgroup (4), Standard & Enterprise Edition
Please read SAP Note 928839 on how to order SQL 2005 for upgrade purposes.
(3)SQL 2005 Express Edition is only supported with the SAP Business One Evaluation Versions and only in 32 Bit mode.
(4)SQL 2005 Workgroup Edition is only supported with Windows Small Business Server (SBS) 2003 and only in 32 Bit mode
For more detailed information regarding the supportted platform you could refer to the webpage from the above path.
Best Regards
Helen Sun
SAP Business One Forums Team

Upgrading from SQL Server 2005 Compact Edition [ENU] to SQL Server 2008 Express Edition OR HIGHER for Microsoft Security Compliance Manager

I have downloaded the MS Security Compliance Manager, which is in two parts: MS SQL Server 2008 Express Edition & the SCM. The install instructions state the the server needs to be install before the SCM. So as the install continues I get
an error message, which cancels the installation. So, I am trying to install SQL 2008 EE separate from SCM. My question is:
Can I upgrade from my current SQL Server 2005 Compact Edition [ENU]
directly to SQL Server 2008 Express Edition (or higher)?

So as the install continues I get an error message, which cancels the installation.
And which error message did you got?
SQL Server Compact Edition is something different then SQL Server Express (or Standard) Edition, you can't upgrade it as you asked for,.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Compatibility of Toplink with SQL SERVER 2005 Enterprise edition

Hi All,
We have J2EE application developed using TopLink ORM, which is running on SQL server 2000 standard edition, and now we are planing to migrate the SQL server 2000 to SQL server 2005 Enterprise edition, so please let me know whether TopLink supports for SQL server 2005 Enterprise edition or is there any disadvantages.
Looking for your advice earliest
Thanks in advance.
Anand Siddacharya.

Yes, TopLink supports any SQL compliant database with a JDBC compliant driver.
As long as you have a JDBC driver that works correctly, I can't see any issues in the upgrade.
James : http://www.eclipselink.org

DG4MSQL v11.2.0.1 certified with Sql Server 2005 Express Edition?

We are working on a proof of concept and need to use Oracle Database Gateway for MS Sql Server - DG4MSQL version 11.2 - on 64bit Linux to connect to a Windows database that is using SQL Server 2005 Express Edition. I reviewed the certification matrix for the database gateways and it lists that SQL Server 2005 is certified - but does not specify which editions.
We are having some problems connecting to the SQL Server database and want to make sure that we should be able to connect to the express edition.
Thanks.

Yes, DG4MSQL 11 is certified with SQL Server Express Edition.

Different versions of SQL Server 2005 Developer Edition

Similar Messages

Maybe you are looking for