SQL Server Express LocalDB Features

Is there documentation pointing out what's new in LocalDB in v2014 from v2012?
kkamii

Is there documentation pointing out what's new in LocalDB in v2014 from v2012?
kkamii
Below link would get you started. Change version for different VS versions
http://msdn.microsoft.com/library/ms233817%28VS.110%29.aspx
additionally
support.microsoft.com/lifecycle/search/?sort=PN&alpha=sql
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

How to convert sql server database to SQL Server Express LocalDB??

How do I convert sql server database 2008 to SQL Server Express LocalDB??
Thanks
Aru

Hello,
Please read the following article:
http://msdn.microsoft.com/en-us/library/hh873188.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Microsoft SQL Server Express LocalDB / Windows Azure Powershell install fail - SQL writer failed to start

I'm trying to install Windows Azure PowerShell on my Windows 7 SP1 Enterprise laptop. As a prerequisite, it needs to install Microsoft SQL Server 2012 Express LocalDB, I but keep receiving an error:
Service 'SQL Server VSS Writer' (SQLWriter) failed to start. Verify that you have
sufficient privileges to start system services.
The service that it tries to use by default is the Local Service. I verified that it has log on as a service privileges and even did a restart. Same error.
any ideas?
Cross posted in Windows
Azure

Hi ,
According to your description, when you install SQL Server 2012 Local DB , it encounter the error about SQLWriter. We need to verify if you invoke SQLLOcalDB.msi directly, and check
MSSQL service is running and other service’s status.In addition, you can go to event viewer and check the error logs for analysis.
There is a similar issue about Service SQL Server VSS Writer and troubleshooting SQL Server 2012 Express LocalDB, you can review the following article.
http://blog.andreloker.de/post/2008/07/17/SQL-Server-hotfix-KB948109-fails-with-error-1920.aspx#!
http://social.technet.microsoft.com/wiki/contents/articles/4609.troubleshoot-sql-server-2012-express-localdb.aspx
Thanks,
Sofiya Li
Your Name
TechNet Community Support

Trying to upload rds in sql server express 2014; feature not supported in this version

I'm trying to preview sql server 2014 and report builder capabilities; I created a rds and am trying to upload it to ssrs and I get the message that this is not supported? Is this only available in versions beyond express?
Thanks

Scroll down to the "Reporting Services" section, you'll see Remote Data Sources only become supported in Standard Edition and up...
http://msdn.microsoft.com/en-us/library/cc645993.aspx

SQL Server Express with SS Management Studio. Which version is lightest/smallest?

I’m looking to download the smallest/lightest version of SQL Server Express with SS Management Studio.
Which option should I choose?
http://www.microsoft.com/en-us/download/details.aspx?id=29062
Knowledge is the only thing that I can give you, and still retain, and we are both better off for it.

Hello,
What's the main propuse you use SQL Server Express edition? If you just use SQL Server in development. You can try to use SQL Server 2012 Express LocalDB.
LocalDB is a lightweight version of Express that has all its programmability features.SQL Server Express LocalDB runs in user mode, and you can install it more quickly with fewer prerequisites (a minimal set of files necessary to start the SQL Server Database
Engine) and no configuration.
Reference:
Introducing LocalDB, an improved SQL Express
SQL Express v LocalDB v SQL Compact Edition
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

SSRS 2013 Native Mode - Cannot See Report Builder Button after Installing on my Desktop Computer - SQL Server Express

I have installed SQL Server Express 2013 on my home PC, which runs Windows 7. I used the advanced installation, which includes Reporting Services. The install seemed to go okay but when I open SSRS, I cannot see the Report Builder button on the
screen. I have spent a lot of time trying to figure this out, including installing and reinstalling the program. I am not sure what I am doing wrong. Also, I cannot connect to the report server through SQL Server Management Studio.
If anyone has any straightforward assistance, it would be greatly appreciated. I have spent a lot of time looking for answers. In the meanwhile I'll continue seeing if I can get this to work.

Hello,
See
Features Supported by Reporting Services in SQL Server Express => Unsupported Features:
Ad hoc reporting through semantic models and Report Builder is not supported.
But you can try to install & use the Report Builder as stand-alone Installation; you can get it here:
Microsoft® SQL Server® 2012 Report Builder
Olaf Helper
[ Blog] [ Xing] [ MVP]

SQL Server Express 2014 CTP2 LocalDB

I just installed 2014 SQL Express and everything looked like it worked just fine.
Too fine for my own good because it updated the database files to version 782 and now I am stuck.
I cannot get SQL Server Management Studio nor VS 2013 Express to connect to LocalDB v12.0, only to LocalDB v11.0, but the latter does not read version 782 data base files.
The Discovery Report shows that LocalDB v.12 has been configured. But when I try to connect with "(LocalDB)\v12.0" I get "Cannot connect..." It can still connect with "(LocalDB)\v11.0" but than cannot open the v.782
data bases.
And when I try to open an SQLexpress database in VS 2013 Express it comes back with "An incompatible SQL Server version was detected."

Hello ,
Do you know these links ?
http://msdn.microsoft.com/en-us/library/hh510202(v=sql.120).aspx
http://social.technet.microsoft.com/wiki/contents/articles/4609.troubleshoot-sql-server-2012-express-localdb.aspx
You may have problems with access permissions on the files of the database ( see at the end of the 2nd link ). The user must be added to the list of authorized users to connect and so on.
There was also a similar problem of connection for applications created with VS 2010 towards localdb 2012.
See also the articles from the SQL Server Express Weblog ( for 2012 but the remarks could be always interesting )
http://blogs.msdn.com/b/sqlexpress/archive/2011/11/28/using-localdb-in-visual-studio-2010.aspx
http://blogs.msdn.com/b/sqlexpress/archive/2011/10/28/localdb-where-is-my-database.aspx
http://blogs.msdn.com/b/sqlexpress/archive/2011/10/27/net-framework-4-now-supports-localdb.aspx
Please , could you explain how you have created your localdb on the users computers ?
I am surprised by your short error message ( I think that you have not provided the full error message ).
Have a nice day
PS : as you are using a SQL Server Express 2014 CTP2 , it is possible that the RTM version could solve your problem. I have applied always a rule : I never install an application using a new version of SQL Server before the release of the SP1.
Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

SQL Server Express Edition or LocalDb

Can I have free access to SQL Server Express Edition or LocalDb with General Purpose Basic Tier and Standard Tier?
Regards,
Vivekanand

Hi Vivekanand,
Thanks for posting here.
Have a glance at this document hope you get the detailed information.
http://azure.microsoft.com/en-us/documentation/articles/data-management-azure-sql-database-and-sql-server-iaas/
Girish Prajwal

SQL Server Express 2014 on Win8.1: Could not find the Database Engine startup handle

Hello,
I tried to follow all the similarly titled posts in this forum, yet no solution seems to work, so I hope I can find some up-to-date suggestion here (most of the older posts refer to versions from 2008 to 2012...).
I have installed Visual Studio 2013 (with the latest Update 2 RC) on a freshly installed development workstation with Win 8.1 with all its updates. Now I'd want to install SQL Server 2014 Express, but the setup keeps failing with the dreaded "Could
not find the Database Engine startup handle" error (the log follows below).
What I tried:
1) download again and repair. Same error.
2) completely uninstall by launching setup.exe /Action=uninstall (success), then rebooting the OS, then installing again. Same error. I did this twice, the second time I also manually removed any directory left out in C:\Program Files etc.
When I launch the setup, I select all the components for installation in the package SQLEXPRADV_x64_ENU.exe (1.12 GB, last downloaded today -Apr 3, 2014-), and accept all the defaults including the proposed services accounts. There is no preexisting
SQL Server instance, as expected.
The setup takes its time, and finally fails with the error quoted above. I really do not want to reformat my HD and fully reconfigure my workstation, which took about 3 days... Could anyone suggest a solution to have SQL Server 2014 setup so I can start
developing instead of wasting time in administering the system?
Thanks to all! The log follows.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2014-04-03 18:30:58
End time: 2014-04-03 19:04:41
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 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: DIOMEDES
Machine processor count: 4
OS version: Windows 8
OS service pack:
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 Configured
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Daniele\Downloads\SQLEXPRADV_x64_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, LOCALDB
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SQLEXPRESS
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
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: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SQLEXPRESS
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: DIOMEDES\Daniele
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_183057\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: 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: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
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: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
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: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
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: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_183057\SystemConfigurationCheck_Report.htm

Thank you, it worked! I suppose that it was really your nr.3 which made the difference. I changed NT Service\MSSQL$SQLEXPRESS to NT AUTHORITY\System for the Data service. I'll then change it again as suggested (any suggestion about a "standard"
account to be used here?), even if this is a development workstation using SQL Server Express only as a local database for debugging, so security is not really a big concern.
Thanks for the feedback.Ya I know No3 was real step but just added more info so as to rule out any other possibility.
No not as such, you wont believe,quite few pf my clients I have worked for keep it with local system and they have not complained yet ,they are afraid to change account as few of them faced issue SQL Server not coming online due to logon failure( after changing
startup account to some domain a and that was happening due to some AD policy.But if you have nay plans to move Critical database in production which would be act as Database to some Internet facing application please follow my suggestion
of running SQL Server with Least privileged domain account.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Server Express 2014 Installation Completes with Failures and Repair Does Nothing to Help

I am attempting to install SQL Server Express 2014 on a development machine and as usual old versions of SQL and the remnants of them are a plague to the installation.
I have used to Revo Uninstaller to scrub the old installations and with my first attempt after some additional work on the registry I was able to get an instance to install and remarkably I was able to connect to the instance. However, I removed an application
reference to SQL Server 2008 after the SQL Express 2014 installation (through Control Panel > Programs > Programs and Features) and it stopped working immediately.
So I removed (uninstalled using Revo Uninstaller) every reference to any SQL Server application as well as removed all of the registry references (using Revo) and I can now install SQL Server Express 2014 with
"Feature" failures [Reporting Services, Database Engine Services, Full-Text and Semantic Extractions for Search and SQL
Server Replication] and of course it doesn't work.
Now when I attempt "Repair" the installation the process ends normally (no errors) and reports "Success" however SQL still has no instance and the services are not running nor are they visible when I open the "SQL Server Configuration
Manager".
This is the "Repair" log:
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Start time: 2014-12-21 17:21:37
End time: 2014-12-21 17:29:10
Requested action: Repair
Machine Properties:
Machine name: EDWARD-PC2
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: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2014 Management Tools - Basic 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Management Tools - Complete 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools Connectivity 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools Backwards Compatibility 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools SDK 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 LocalDB 1033 Express Edition 12.0.2000.8 No Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Edward\Downloads\SQLEXPRADV_x86_ENU\x86\setup\
Installation edition:
User Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASCONFIGDIR: Config
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
ENU: true
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
QUIET: false
QUIETSIMPLE: false
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
UIMODE: AutoAdvance
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141221_172135\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 Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141221_172135\SystemConfigurationCheck_Report.htm
However this is what the "SQL Sever Configuration Manager" look like:
Why does this appear to not be working properly? I can not connect the the "local" instance and I would guess that the service either does not exist or is not running.
Edward Walker

Hello,
To my knowledge, Revo is not a supported way to uninstall SQL Server.
Please try to uninstall all you can using Control Panel -> Programs and Features, then perform a manual uninstall to
remove remnants. Try the following procedure:
1. Uninstall all SQL Server 2012 components you can using Control Panel -> Programs and Features
2. Backup the registry.
3. Delete the following keys in regedit:
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing
SQL Server.
5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
6. Rename all the SQL Server folders in the computer like C:\Program Files\Microsoft SQL Server and subfolders.
After performing above procedure, try to reinstall SQL Server again.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Error Installing SQL Server Express 2008: '' is not a valid login or you do not have permission.

I have tried installing SQL Server 2008 multiple times on my machine, and I always receive this error about 3/4 of the way through: '' is not a valid login or you do not have permission.
I have tried installing both SQL Server Express 2008 with Tools and SQL Server Express 2008 with Advanced Services, and they both fail the same way. I am trying to do a new stand-alone installation.
I'm running Windows XP Home Edition SP3.
Looking into the error, some forums say I have to install it from THE Administrator account, and not an account with administrator permissions; it also cannot be in Safe Mode, because then the Windows Installer won't work. Unfortunately, I haven't been able to login to the Administrator account. I can go to the home login screen, do ctrl+alt+del twice, and attempt to login to the Administrator account, but I receive this error: Unable to Log You on because of an Account Restriction.
Other forums say that in the Server Configuration section, all you have to do is provide the username and a strong password from an administrative account on the computer, and it doesn't have to be THE Administrator. Well, I did that, but for some reason it doesn't recognize my username and password, it says something like "The credentials you provided for the SQL Server Agent are invalid". BUT THOSE ARE THE CORRECT CREDENTIALS FOR MY ADMINISTRATIVE USER! So I'm forced to use one of the accounts without a password, like NT AUTHORITY\SYSTEM. That's the only way I can get past this step.
Also, just FYI, on the next step, which is Database Engine Configuration, I am using Mixed Mode for the Security Mode. I AGAIN provide a password, and then add my current user (who IS an administrator on my machine!) to the SQL Server Administrators box.
But yet, it fails every single time.
This is pathetic and ridiculous. I must have tried to install this thing 15 times, that is not an exaggeration. I'm posting this on several other forums as well, maybe an MVP or Bill Gates himself can help me.
I have one of the log files from a failed installation. If someone would like to see it, I will post it.

Papy Normand wrote:
Hello,
Please, could you have a look on the excellent answer of Mike Wachal you will find here :
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=4160294&SiteID=1
Don't hesitate to post again for more help or explanations
Have a nice day
PS : if you are talking about the Sql Server Agent Service, it is disabled for Sql Server Express. It is enabled only for the Workgroup/Standard/Dev and Entreprise Editions
Sorry, but I've tried the suggestion in that link, and it hasn't helped me.
For anyone wonder, the link is talking about the problem in Server Configuration where I enter my Windows user account and password (which is in the Administrative group), but it says the credentials are invalid. The link suggests that you need to either enter your Windows account (which I did, and it wouldn't let me go to the next step), or to use one of the built in accounts (which I also tried, but it gave me the " '' is not a valid login" error during the installation).
Any other ideas?
I haven't had any answers from any other forums either, so I'll just post my log file in case anyone wants to look at this:
Overall summary:
Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal):           -2068643839
Exit facility code:            1203
Exit error code:               1
Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time:                    2008-11-17 11:13:47
End time:                      2008-11-17 12:17:25
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xBE029E38%400x12C2466D
Machine Properties:
Machine name:                  STEVEN
Machine processor count:       2
OS version:                    Windows XP
OS service pack:               Service Pack 3
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x86
Process architecture:          32 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008
SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName:                   SQL2008
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         D:\x86\setup\
Installation edition:          DEVELOPER
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  NT AUTHORITY\SYSTEM
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            STEVEN\Steven
ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\ConfigurationFile.ini
ENABLERANU:                    False
ERRORREPORTING:                False
FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    MSSQLSERVER
INSTANCENAME:                  MSSQLSERVER
ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
MEDIASOURCE:                   D:\
NPENABLED:                     0
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSINSTALLMODE:                 DefaultNativeMode
RSSVCACCOUNT:                  NT AUTHORITY\SYSTEM
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           STEVEN\Steven
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature:                       SQL Client Connectivity SDK
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature:                       Analysis Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature:                       Integration Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools SDK
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Server Books Online
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Microsoft Sync Framework
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\SystemConfigurationCheck_Report.htm

SQL Server Express 2008 Installation error. PLEASE HELP.

Hey guys anyone know what I should do to install SQL Server Express 2008?
Im running Vista Home Premium SP1 32bit
These are folders i got on framework folder:
    *      v3.5
    *      v3.0
    *      v2.0.50727
    *      v1.1.4322
    *      v1.0.3705
Installing SQL Server 2008 Express (run time only)
And this is the error I get during the process
"Attributes do not match. Present Attributes (Directory, Compressed), included attributes (0), excluded attributes (Archive, Compressed, Encrypted)."
I have downloaded and installed all Visual Studio 2008 SP1 Express Ed (C++, C#, VB, WebDev) and all worked well
I get this error during the "Feature Selection" setup process.
I also noticed when I tried to use Windows Update, I saw Microsoft SQL Server 2008 Service Pack 1 (KB968369) suddenly available (I have updated windows and installed all important updates before installing Microsoft Visual Studio and SQL). Then I used Windows Update to install SQL Server 2008 SP1 and I still got this error:
Error
Code 84B40000 Unknown error....
I also get this downloading error on SQL Server while installing all 4 Visual Studio Express Editions (C#, C++, VB, WebDev).
"The following cannot be downloaded:"
I've already tried the troubleshooting guide about BITS but the tool fix seems to only supports Windows XP Operating Systems.
Please please please Help Me (^_^).. thanks to all.
P.S.
I think this might have some connections to why I get errors on a simple 'Hello World' Website.
I was just trying to simply make a 'Hello World' Website .. Just THAT on my website.
A simple Website for me to start. Just showing those text on the website. But when I tried to run (debug) the program. This error shows...
'Firefox can't establish a connection to the server at localhost:5903.'
I have Build the Web Site and there was no error. Since it was just simply 'Hello World' text.
Im sure there's some problem but I'm completely stuck here. I dunno if its connected to the problem above.
Please help me solve this problem. Thank you so much.
I appreciate everyone's help.

In my case I had to uncheck "Allow files in this folder to have contents indexed in addition to file properties"
Right click on C:\Program Files\Microsoft SQL Server
Click Advanced on General Tab
Uncheck "Allow files in this folder to have contents indexed in addition to file properties"

SQL Server Express intermittent installation issue

Have been seeing this error for several months trying to duplicate and troubleshoot. SQL Server 2008 R2 SP2 Express being installed on Windows 7 (x86 or x64) Professional, various processors, various execution environments (VM and non-VM). Yesterday duplicated
on x86 Win7 Pro VM clean install (installed Win7 Pro, loaded all updates except .NET 4.5, and installed my application). App installer copies .NET 4, Visual Studio 2010 C++ run-time, and then SQL Server 2008 R2 SP2. Below is portion of detail.txt from
setup failure log:
2014-07-12 18:22:17 Slp: ----------------------------------------------------------------------
2014-07-12 18:22:17 Slp: Running Action: SqlEngineDBStartConfigAction_install_configrc_Cpu32
2014-07-12 18:22:17 Slp: Action Data:
2014-07-12 18:22:17 Slp:   Feature = SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu32
2014-07-12 18:22:17 Slp:   Scenario = install
2014-07-12 18:22:17 Slp:   Timing = ConfigRC
2014-07-12 18:22:17 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig
2014-07-12 18:22:17 Slp:   FeatureName = SQL_Engine_Core_Inst
2014-07-12 18:22:17 Slp:   FeatureCpuType = Cpu32
2014-07-12 18:22:17 Slp:   FeaturePackageId = sql_engine_core_inst
2014-07-12 18:22:17 Slp:   SlipstreamInstall = 1
2014-07-12 18:22:17 SQLEngine: --SqlEngineDBStartConfig: Install: SqlEngineDBStartConfig Configuration
2014-07-12 18:22:17 SQLEngine: : Action Scenario: Install, Feature Scenario: Install, Resolved Scenario Install
2014-07-12 18:22:17 Slp: Sco: Attempting to get network service account name
2014-07-12 18:22:17 Slp: Sco: Attempting to get NT account from sid S-1-5-20
2014-07-12 18:22:17 Slp: Sco: Attempting to get account from sid S-1-5-20
2014-07-12 18:22:17 Slp: Sco: Attempting to get network service account name
2014-07-12 18:22:17 Slp: Sco: Attempting to get NT account from sid S-1-5-20
2014-07-12 18:22:17 Slp: Sco: Attempting to get account from sid S-1-5-20
2014-07-12 18:22:17 Slp: Sco: Attempting to get account sid for user account NT AUTHORITY\NETWORK SERVICE
2014-07-12 18:22:17 Slp: Sco: Attempting to get sid for user account NT AUTHORITY\NETWORK SERVICE
2014-07-12 18:22:17 Slp: Sco: GetSidForAccount normalized accountName NT AUTHORITY\NETWORK SERVICE parameter to NT AUTHORITY\NETWORK SERVICE
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.ActiveNode =
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.IsActiveNodeUpgraded = False
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.Version =
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.IsDefaultInstance = False
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.InstanceId = MSSQL10_50.SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.ReferenceInstanceId = MSSQL10_50.SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.InstanceName = SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.SqlServerServiceName = MSSQL$SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --ProductProperties: Retrieving product properties from local node.
2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value ProductCode
2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value Language
2014-07-12 18:22:17 SQLEngine: --GroupProperties: Loading group properties from local machine.
2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value SQLGroup
2014-07-12 18:22:17 Slp: Sco: Attempting to get account from sid S-1-5-21-3076291671-3154185214-3698330068-1005
2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value SQLPath
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: Dumping Effective Properties for new instance.
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: InstanceId = MSSQL10_50.SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: InstanceName = SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: IsDefaultInstance = False
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: SqlServerServiceName = MSSQL$SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: IsExpressSku = True
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: IsWorkgroupSku = False
2014-07-12 18:22:17 SQLEngine: --InstallProperties: Dumping Install Properties
2014-07-12 18:22:17 SQLEngine: --InstallProperties: EnableRanu = True
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SecurityMode =
2014-07-12 18:22:17 SQLEngine: --InstallProperties: LoginMode = 1
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlCollation = SQL_Latin1_General_CP1_CI_AS
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlAdminAcounts =
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlServiceStartupType = Automatic
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlAccount = NT AUTHORITY\NETWORK SERVICE
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlDomainGroup =
2014-07-12 18:22:17 SQLEngine: --InstallProperties: AddCurrentUserAsSQLAdmin = True
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: Dumping Registry Properties
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: SqlServiceRelativeRegPath = System\CurrentControlSet\Services\MSSQL$SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: CompleteInstanceRegPathByName = SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: CompleteInstanceRegPathById = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: ReferenceInstanceRegPathById = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: MSSQLServerInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQLServer
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: ReferenceMSSQLServerInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQLServer
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: SetupInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: ReferenceSetupInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 SQLEngine: --ProductProperties: Dumping Product Properties
2014-07-12 18:22:17 SQLEngine: --ProductProperties: ProductCode = b5153233-9aee-4cd4-9d2c-4faac870dbe2
2014-07-12 18:22:17 SQLEngine: --ProductProperties: LCID = 1033
2014-07-12 18:22:17 SQLEngine: --GroupProperties: Dumping Group Properties
2014-07-12 18:22:17 SQLEngine: --GroupProperties: SqlEngineGroupSid = S-1-5-21-3076291671-3154185214-3698330068-1005
2014-07-12 18:22:17 SQLEngine: --GroupProperties: SqlEngineGroupNameFromSid = WIN-EAD5VG4PBDE\SQLServerMSSQLUser$WIN-EAD5VG4PBDE$SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --GroupProperties: SqlEngineGroupNameFromSidNoDomain = SQLServerMSSQLUser$WIN-EAD5VG4PBDE$SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: Dumping Directory Propreties
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: DataRootDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: SystemDataDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: InstallSqlInstanceDir = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: DefaultDataDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: DefaultLogDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: BackupDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Backup
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: TempDbDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: TempDbLogDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: ErrorLogDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: TemplateDataDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Template Data
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: SqlInstanceBinnDir = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Binn
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: SqlInstanceTemplatesDir = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Binn\Templates
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: MasterDbPath =
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: MasterLogPath =
2014-07-12 18:22:17 SQLEngine: --SqlEngineDBStartConfig: ConfigRC : SqlEngineDBStartConfig Configuration
2014-07-12 18:22:18 Slp: Sco: Attempting to set directory full path
2014-07-12 18:22:18 Slp: Sco: Attempting to normalize directory path c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:18 Slp: Sco: Attempting to set directory full path
2014-07-12 18:22:18 Slp: Sco: Attempting to normalize directory path c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:18 Slp: Sco: Attempting to set directory full path
2014-07-12 18:22:18 Slp: Sco: Attempting to normalize directory path c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:18 SQLEngine: --SqlServerStartup: SQLEngine: Slipstream case: Enable traceflag -T902
2014-07-12 18:22:18 SQLEngine: : Checking Engine checkpoint 'StartEngineService'
2014-07-12 18:22:18 SQLEngine: --SqlServerServiceSCM: Starting SQL via SCM (-mSqlSetup -f -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T4010 -T3659 -T3610 -T902 -dc:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Template Data\master.mdf -lc:\Program
Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf)...
2014-07-12 18:22:18 Slp: Sco: Attempting to start service MSSQL$SQLEXPRESS
2014-07-12 18:22:20 Slp: Sco: Service MSSQL$SQLEXPRESS started
2014-07-12 18:22:20 Slp: Sco: Attempting to get service process id for service MSSQL$SQLEXPRESS
2014-07-12 18:22:20 Slp: Invoking QueryServiceStatusEx Win32 API
2014-07-12 18:22:20 Slp: Sco: Returning service process id 3480
2014-07-12 18:22:20 SQLEngine: : Checking Engine checkpoint 'GetSqlServerProcessHandle'
2014-07-12 18:22:22 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete$SQLEXPRESS' to be created
2014-07-12 18:22:24 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete$SQLEXPRESS' or sql process handle to be signaled
2014-07-12 18:22:24 SQLEngine: : Checking Engine checkpoint 'WaitSqlServerStartEvents'
2014-07-12 18:22:59 Slp: Sco: Attempting to initialize script
2014-07-12 18:23:01 Slp: Sco: Attempting to initialize default connection string
2014-07-12 18:23:03 Slp: Sco: Attempting to set script connection protocol to NotSpecified
2014-07-12 18:23:03 Slp: Sco: Attempting to set script connection protocol to NamedPipes
2014-07-12 18:23:03 SQLEngine: --SqlDatabaseServiceConfig: Connection String: Data Source=\\.\pipe\SQLLocal\SQLEXPRESS;Initial Catalog=master;Integrated Security=True;Pooling=False;Network Library=dbnmpntw;Application Name=SqlSetup
2014-07-12 18:23:03 SQLEngine: : Checking Engine checkpoint 'ServiceConfigConnect'
2014-07-12 18:23:03 SQLEngine: --SqlDatabaseServiceConfig: Connecting to SQL....
2014-07-12 18:23:03 Slp: Sco: Attempting to connect script
2014-07-12 18:23:04 Slp: Connection string: Data Source=\\.\pipe\SQLLocal\SQLEXPRESS;Initial Catalog=master;Integrated Security=True;Pooling=False;Network Library=dbnmpntw;Application Name=SqlSetup
2014-07-12 18:24:16 Slp: Sco: Connection error code from SqlException is : -2
2014-07-12 18:24:30 Slp: Watson Bucket 1
Original Parameter Values
2014-07-12 18:24:30 Slp: Parameter 0 : SQL Server 2008
R2@RTM@
2014-07-12 18:24:30 Slp: Parameter 2 : System.Data.SqlClient.SqlInternalConnection.OnError
2014-07-12 18:24:30 Slp: Parameter 3 :
Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1
2014-07-12 18:24:30 Slp: Parameter 4 :
System.Data.SqlClient.SqlException@-2146232060
2014-07-12 18:24:30 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
2014-07-12 18:24:30 Slp:
Final Parameter Values
2014-07-12 18:24:30 Slp: Parameter 0 : SQL Server 2008
R2@RTM@
2014-07-12 18:24:30 Slp: Parameter 2 : 0x1BBF2F31
2014-07-12 18:24:30 Slp: Parameter 3 : 0x0A2FBD17@1211@1
2014-07-12 18:24:30 Slp: Parameter 4 : 0x3906094D
2014-07-12 18:24:30 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
2014-07-12 18:24:36 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-07-12 18:24:36 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-07-12 18:24:36 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-07-12 18:25:26 Slp: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
2014-07-12 18:25:32 Slp: Watson bucket for exception based failure has been created
2014-07-12 18:25:32 SQLEngine: Copying 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' to 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt' ...
2014-07-12 18:25:32 Slp: Sco: Attempting to set file full path to 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
2014-07-12 18:25:32 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' exists
2014-07-12 18:25:32 Slp: Sco: Attempting to copy file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' to file 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' exists
2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to set file full path to 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to check if directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' is equal to path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to check if directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' is equal to path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to get security descriptor for file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
2014-07-12 18:25:32 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' exists
2014-07-12 18:25:32 Slp: Sco: Returning security descriptor O:NSG:NSD:AI(A;ID;FA;;;NS)(A;ID;FA;;;SY)(A;ID;FA;;;BA)(A;ID;FA;;;S-1-5-21-3076291671-3154185214-3698330068-1005)(A;ID;0x1201ff;;;S-1-5-21-3076291671-3154185214-3698330068-1006)
2014-07-12 18:25:32 Slp: Sco: Attempting to dispose script
Please note that this is NOT a question about fixing this one installation. This is an SQL Server Express install as part of my application install and MUST WORK FIRST TIME, EVERY TIME. Please direct me.
Paul T.

Here are the parameters used with the SQL Server Express installer EXE (both x86 and x64):
/q /hideconsole /action=Install /features=SQL /instancename=SQLEXPRESS /enableranu=1 /sqlsvcaccount="NT Authority\Network Service" /AddCurrentUserAsSqlAdmin /skiprules=RebootRequiredCheck /IAcceptSQLServerLicenseTerms
I presume that TCP/IP is not enabled by default for Express installs. I THINK that named pipe should be enabled.
Summary.txt is copied below:
Overall summary:
Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal):           -2068119551
Exit facility code:            1211
Exit error code:               1
Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time:                    2014-07-12 18:06:14
End time:                      2014-07-12 18:25:44
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.4000.0%26EvtType%3d0x1BBF2F31%400x3906094D
Machine Properties:
Machine name:                  WIN-EAD5VG4PBDE
Machine processor count:       1
OS version:                    Windows 7
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x86
Process architecture:          32 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
Installation location:         c:\b610200f3dc88995d16c2effd8b6ac\x86\setup\
Installation edition:          EXPRESS
Slipstream:                    True
SP Level                       2
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      True
AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Disabled
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\ConfigurationFile.ini
CUSOURCE:
ENABLERANU:                    True
ENU:                           True
ERRORREPORTING:                False
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SQLENGINE,REPLICATION
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    SQLEXPRESS
INSTANCENAME:                  SQLEXPRESS
ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
NPENABLED:                     0
PASSPHRASE:                    *****
PCUSOURCE:                     c:\b610200f3dc88995d16c2effd8b6ac\PCUSOURCE
PID:                           *****
QUIET:                         True
QUIETSIMPLE:                   False
ROLE:                          AllFeatures_WithDefaults
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 NT Authority\Network Service
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
UIMODE:                        AutoAdvance
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x0A2FBD17@1211@1
Configuration error description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Detail.txt
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x0A2FBD17@1211@1
Configuration error description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Detail.txt
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SystemConfigurationCheck_Report.htmd
The entire contents of the installation log can be found in ZIP format here:
https://onedrive.live.com/redir?resid=8E983C44B610198D!3984&authkey=!AFbuZaCG3Lm38Pw&ithint=folder%2c.zip
Paul T.

SQL Server Express is being a real pain

I've been messing with this SQL Server Express installation
since Friday and still can't get this application and database to
work together correctly. The program is written in ColdFusion, but
the errors seem to be permissions related to me but I just can't
figure it out.
I've created a user within SQL Server Management Express
program and all goes well. I then assign it as database owner for
the particular database I'm using. I've created the datasource from
within the ColdFusion administrator and it says the connection is
being made.
When trying to access the script, I get the error below.
In the SQL Management system I have tried everything that I
know to do - from adding this particular account as a user for the
"tUsers" table and giving it "Select" permissions to re-creating
the account and making it owner of the entire database. I tried
adding the schema to the front and surrounding the table name in
brackets [ ].
The database was restored from a backup on another server.
Would that cause problems at all? I just tried deleting the
database, creating it again, then restoring it from the file and
setting the owner as this user during the import process. I'm still
not having any luck though.
I've searched Google and almost every result is a forums post
from people having this same problem who have fixed it by giving
the account permission to access the database and/or table. For
some reason that isn't working for me - or I'm an idiot and missing
something.
Does anyone have any ideas?

At first, no, I couldn't perform any queries at all against
the database.
I fixed the problem by editing the "server" in the CF admin
for this datasource and making it:
localhost/SQLEXPRESS
CF Admin says it doesn't verify, but if I attach the username
and password to each CFQUERY statement they work!
Very strange problem. I'm not sure if this is a 'feature' or
a known bug, but I don't see any reason why that connection doesn't
verify. Especially since if it would've I could have saved myself
countless hours of work.
Oh well - thanks everyone for your suggestions and
help!

SQL Server Express Performance Limitations With OGC Methods on Geometry Instances

I will front load my question. Specifically, I am wondering if any of the feature restrictions with SQL Server Express cause performance limitations/reductions with OGC methods on geometry instances, e.g., STIntersects? I have spent time reading
various documents about the different editions of SQL Server, including the Features Supported by the Editions of SQL Server 2014, but nothing is jumping out at me. The
limited information on spatial features in the aforementioned document implies spatial is the same across all editions. I am hoping this is wrong.
The situation.... I have roughly 200,000 tax parcels within 175 taxing districts. As part of a consistency check between what is stored in tax records for taxing district and what is identified spatially, I set up a basic point-in-polygon query
to identify the taxing district spatially and then count the number of parcels within in taxing district. Surprisingly, the query took 66 minutes to run. As I pointed out, this is being run on a test machine with SQL Server Express.
Some specifics.... I wrote the query a few different ways and compared the execution plans, and the optimizer always choose the same plan, which is good I guess since it means it is doing its job. The execution plans show a 'Clustered Index Seek
(Spatial)' being used and only costing 1%. Coming in at 75% cost is a Filter, which appears to be connected to the STIntersects predicate. I brute forced alternate execution plans using HINTS, but they only turned out worse, which I guess is also
good since it means the optimizer did choose a good plan. I experimented some with changing the spatial index parameters, but the impact of the options I tried was never that much. I ended up going with "Geometry Auto Grid" with 16 cells
per object.
So, why do I think 66 minutes is excessive? The reason is that I loaded the same data sets into PostgreSQL/PostGIS, used a default spatial index, and the same query ran in 5 minutes. Same machine, same data, SQL Server Express is 13x slower than
PostgreSQL. That is why I think 66 minutes is excessive.
Our organization is mostly an Oracle and SQL Server shop. Since more of my background and experience are with MS databases, I prefer to work with SQL Server. I really do want to understand what is happening here. Is there something I can
do different to get more performance out of SQL Server? Does spatial run slower on Express versus Standard or Enterprise? Given I did so little tuning in PostgreSQL, I still can't understand the results I am seeing.
I may or may not be able to strip the data down enough to be able to send it to someone.

Tessalating the polygons (tax districts) is the answer!
Since my use of SQL Server Express was brought up as possibly contributing to the slow runtime, the first thing I did was download an evaluation version of Enterprise Edition. The runtime on Enterprise Edition dropped from 66 minutes to 57.5 minutes.
A reduction of 13% isn't anything to scoff at, but total runtime was still 11x longer than in PostgreSQL. Although Enterprise Edition had 4 cores available to it, it never really spun up more than 1 when executing the query, so it doesn't seem
to have been parallelizing the query much, if at all.
You asked about polygon complexity. Overall, a majority are fairly simple but there are some complex ones with one really complex polygon. Using the complexity index discussed in the reference thread, the tax districts had an average complexity
of 4.6 and a median of 2.7. One polygon had a complexity index of 120, which was skewing the average, as well as increasing the runtime I suspect. Below is a complexity index breakdown:
Index
NUM_TAX_DIST
1
6
<2
49
<3
44
<4
23
<5
11
<6
9
<7
9
<8
4
<9
1
<10
4
>=10
14
Before trying tessellation, I tweaked the spatial indexes in several different ways, but the runtimes never changed by more than a minute or two. I reset the spatial indexes to "geometry auto grid @ 32" and tried out your tessellation functions
using the default of 5000 vertices. Total runtime 2.3 minutes, a 96% reduction and twice as fast as PostgresSQL! Now that is more what I was expecting before i started.
I tried using different thresholds, 3,000 and 10,000 vertices but the runtimes were slightly slower, 3.5 and 3.3 minutes respectively. A threshold of 5000 definitely seems to be a sweet spot for the dataset I am using. As the thread you referenced
discussed, SQL Server spatial functions like STIntersect appear to be sensitive to the number of vertices of polygons.
After reading your comment, it reminded me of some discussions with Esri staff about ArcGIS doing the same thing in certain circumstances, but I didn't go as far as thinking to apply it here. So, thanks for the suggestion and code from another post.
Once I realized the SRID was hard coded to 0 in tvf_QuarterPolygon, I was able to update the code to set it to the same as the input shape, and then everything came together nicely.

SQL Server Express LocalDB Features

Similar Messages

Maybe you are looking for