SQL Server Express checking DB Size

Hello,
I frequently connect to customers using Sage 300 with SQL Express. Many times for a quote I need to check the SQL database size.
Many times I am connecting to a workstation and the customer either does not have access to their SQL server to access SQL Studio Manager and other times they just do not know their password.
Is there a way to check the size of a DB from a workstation that is using local programs but accessing SQL on a server if I do not have access to the SQL Server, I do have the SQL server name, but often am unable to even see the SQLDATA.mdf's from the local
machine ?
Thanks,
Debbie

Hello,
Please read about a few options:
http://blogs.technet.com/b/heyscriptingguy/archive/2010/11/02/use-powershell-to-obtain-sql-server-database-sizes.aspx
You can also use Performance Monitor tool (or System Monitor), inside the set of counters named “SQL Server: Databases” you will find
the counter “Data File(s) Size (KB)”.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

SQL Server Express - Size limitations

Hi,
I am currently using the SQL Server Express edition with the intention of upgrading to the full version in the future.
I know the size limitation on the Database is 4GB - however does this include the log file as well? Nothing I read says the log file is included however if anyone can give the definitive answer I would be grateful.
Also my log file maximum is set to 2GB what issues are there with reducing this to say 500MB? I assume SQL Server automatically drops the old log data to add new data when the maximum is reached.
Thanks for your help.
Andrew

The 4GB limit only applies to data files, not log.
The maxsize for your log files should only be relevant if something in your workload is going to require more then the size so that the log will have to grow. Ideally, your log is appropriately sized for your workload so that autogrow will not
need to occur.
Hello, am using ms sqlserver 2005 express edition..now it is giving out of memory exception while starting the service.. may i know the reason.. please help me.

Problem with Datasource for SQL Server Express

I have set up a development environment to develop some processes for the HCSO client and have a question. I have a turnkey install on my laptop with MYSQL. The liveCycle databases are in MYSQL. I have also installed SQL Server Express on this machine and created a table to query that will control workflow. I added a datasource configuration in the adobe-ds.xml configuration file. That configuration is:
<local-tx-datasource>
            <jndi-name>HCSO</jndi-name>
            <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=DBName</connection-url>
            <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
            <user-name>username</user-name>
            <password>password</password>
            <min-pool-size>1</min-pool-size>
            <max-pool-size>30</max-pool-size>
            <blocking-timeout-millis>60000</blocking-timeout-millis>
            <autoReconnect>true</autoReconnect>
            <idle-timeout-minutes>15</idle-timeout-minutes>
            <prepared-statement-cache-size>100</prepared-statement-cache-size>
            <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
            <new-connection-sql>Select id from HCSOUser.eric</new-connection-sql>
            <check-valid-connection-sql>Select id from HCSOUser.eric</check-valid-connection-sql>
            <metadata>
                  <type-mapping>MS SQLSERVER2000</type-mapping>
            </metadata>
      </local-tx-datasource>
In SQL Server, I created a user and a schema with the same name in a database. I created a simple table called "eric" with one column called "id". The user was given the appropriate default schema and given full permissions on the database and table.
In workbench, I added a JDBC query single row activity. I have configured the datasource as java:/HCSO and also tried java:HCSO. I then entered the query as "Select id from HCSOUser.eric" and hit test. Nothing appears in the results area. I see the following in the server.log:
2009-09-24 14:44:26,437 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException in method: public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterLocal.doBMT(com.ad obe.idp.dsc.transaction.TransactionCallback) throws com.adobe.idp.dsc.DSCException:
java.lang.RuntimeException: A result set was generated for update.
      at com.adobe.idp.dsc.jdbc.JDBCService.testExecute(JDBCService.java:616)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:592)
      at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
      at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:140)
      at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
      at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
      at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterBean.doBMT(EjbTran sactionBMTAdapterBean.java:197)
      at sun.reflect.GeneratedMethodAccessor573.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:592)
      at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
      at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:214)
      at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:149)
      at org.jboss.webservice.server.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor. java:54)
      at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
      at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:106)
      at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:1 58)
      at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:62)
      at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:154)
      at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:153)
      at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
      at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:122)
      at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
      at org.jboss.ejb.Container.invoke(Container.java:873)
      at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:415)
      at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:88)
      at $Proxy270.doBMT(Unknown Source)
      at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:95)
      at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
      at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
      at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
      at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
      at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
      at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
      at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:132)
      at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
      at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
      at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
      at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
      at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:118)
      at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.invoke(AbstractMessageReceiv er.java:315)
      at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invokeCall(SoapSdkEndpoint. java:138)
      at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invoke(SoapSdkEndpoint.java :81)
      at sun.reflect.GeneratedMethodAccessor710.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:592)
      at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
      at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
      at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
      at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
      at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
      at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
      at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
      at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
      at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
      at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
      at com.adobe.idp.dsc.provider.impl.soap.axis.InvocationFilter.doFilter(InvocationFilter.java :43)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:202)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
      at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:202)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
      at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
      at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.ja va:159)
      at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
      at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11P rotocol.java:744)
      at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
      at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
      at java.lang.Thread.run(Thread.java:595)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: A result set was generated for update.
      at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
      at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
      at com.microsoft.sqlserver.jdbc.SQLServerStatement$StatementExecutionRequest.executeStatemen t(Unknown Source)
      at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source)
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unknown Source)
      at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeUpdate(Unknown Source)
      at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:161)
      at com.adobe.idp.dsc.jdbc.helper.SqlHelper.executeTestUpdate(SqlHelper.java:117)
      at com.adobe.idp.dsc.jdbc.JDBCService.testExecute(JDBCService.java:610)
      ... 82 more

Thanks fot the tip, but now I got a different message in the "Test" results of "Query Single Row":
Exception: Could not create connection; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect))
My datasource xml is like this:
<?xml version="1.0" encoding="UTF-8"?>
        <datasources>
        <local-tx-datasource>
        <jndi-name>MSSQL</jndi-name>
        <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=ADOBE</connection-url>
          <use-java-context>false</use-java-context>
        <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
        <user-name>sa</user-name>
        <password>adobe</password>
          <min-pool-size>10</min-pool-size>
          <max-pool-size>50</max-pool-size>
          <blocking-timeout-millis>60000</blocking-timeout-millis>
          <idle-timeout-minutes>15</idle-timeout-minutes>
          <prepared-statement-cache-size>100</prepared-statement-cache-size>
          <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
        <check-valid-connection-sql>SELECT 1 FROM sysobjects</check-valid-connection-sql>
        <metadata>
          <type-mapping>MS SQLSERVER2005</type-mapping>
        </metadata>
        </local-tx-datasource>
        </datasources>
Where is the problem and how to fix it?
Thank you.

SQL Server Express 2012 SP2 installation hangs during extract phase

Greetings!
I am having an issue with trying to silent install SQL Server Express 2012 SP2 (x86).
I have a proprietary installation framework, which is calling the SQL Server Express installer.
The SQL Server Express installer starts extracting files to c:\{some guid}. The folder reaches about 11 mb in size, and then nothing further happens. No activity on the machine, CPU or disk - I have waited up to 15 minutes to verify this. On the normal installation,
the size of this folder is ~650 mb.
Here are the things I've also tested:
- I'm experiencing these symptoms on both Windows 7 and Windows Server 2012 R2 (haven't tested other platforms)
- If I launch exactly the same command from the command prompt, the installation goes through as normal
- If I replace the SQL Server Express 2012 SP2 with SQL Server Express 2012 SP1, and install via our installation framework, the installation goes through as normal
- I have checked and double-checked that our installation framework is started with administrative privileges.
- From my previous search attempts, I have seen issues where the installer would hang or fail when launched from inside an msi, which would result in a log in C:\Program Files (x86)\Microsoft SQL Server\<something something>. These are not the symptoms
I am experiencing. The C:\Program Files (x86)\Microsoft SQL Server\ folder is not even created!
Any suggestions, or places I can look to figure out why it's not proceeding? For now, I have worked around the issue by including SP1 instead of SP2, but ideally I'd like to base my solution on the most recent service pack.

Hello Alberto!
The installation framework does check for this. I'm also certain that these prerequisites are fulfilled.
When the SQL Server process hangs, I can kill the process, copy/paste the exact command that was executed from the installation framework's log files, and execute that command in a command prompt - and then the installation runs as expected.
The installation framework installs SQL Server Express correctly if I use the 2008 R2 SP1 express or the 2012 SP1 Express installer. It's just the SP2 installer that is giving me problems.
The only difference I can think of is that the installation framework is a 32-bit process, which calls the SQL Server installer, while the command prompt is a 64-bit application. I am installing the SQLEXPR_x86_ENU.exe
from http://www.microsoft.com/en-us/download/details.aspx?id=43351, so it should be compatible with my 32 bit environment -
"SQLEXPR_x86 is the same product but supports installation onto both 32-bit and 64-bit (WoW) operating systems"
Tomorrow, I will try:
- Installing on Windows 7 32-bit
- Trying to launch the SQL Server installer from a powershell (x86) prompt, to emulate a 32-bit environment on a 64-bit machine

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 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 2008 and WOW64

Our software requires SQL Server Express 2008 to be installed on various computers. We have run into a problem with systems that have WOW64. When the SQL installer is going through it's check list, it marks the WOW64 as the reason that it cannot continue. In other cases I get a notification that tells me that windows installer 4.5 or higher is required but when I try to install windows installer 4.5 it tells me that the it is not the correct verson of windows installer for the system. I try a few different versions and get the same problem. I am confused as to why one windows software would not work with another.

Hi,
- Which version of Windows installer 4.5 are you trying to install ? For X86, X64 or IA64 ?
- Which version of your operation system ? Windows 2003 ? 2008 ? 2008 R2 ? .....
For information
Download the file that is appropriate for your operating system version and platform.
For Windows Vista, Windows Vista Service Pack 1 and Windows Server 2008:
x86 Platform: Windows6.0-KB942288-v2-x86.msu
x64 Platform: Windows6.0-KB942288-v2-x64.msu
IA64 Platform: Windows6.0-KB942288-v2-ia64.msu
For Windows XP Service Pack 2 and Windows XP Service Pack 3 (32-bit platforms):
x86 Platform: WindowsXP-KB942288-v3-x86.exe
For Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2 and Windows XP 64-bit Editions:
x86 Platform: WindowsServer2003-KB942288-v4-x86.exe
x64 Platform: WindowsServer2003-KB942288-v4-x64.exe
IA64 Platform: WindowsServer2003-KB942288-v4-ia64.exe
Extract of the documentation :
Windows Installer 5.0 will be released with, and require Windows Server 2008 R2 or Windows 7. Versions earlier than Windows Installer 5.0 were released with Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, and Windows 2000.
Windows Installer 4.5 requires Windows Server 2008, Windows Vista, Windows XP with Service Pack 2 (SP2) and later, and Windows Server 2003 with Service Pack 1 (SP1) and later.
Cheers,
Michel.
Michel DEGREMONT , my blog SQL Server

SQL Server Express 2008 instance fails to start

I've installed SQL Server Express with a named instance 'SQLSERVER2'. I was able to connect to it and reference it in the management studio. There was a problem though with Visual Studio 9 when running an ASP.NET web application that required connecting to the same instance. So, I went into the configuration manager to change the security level of the instance from network to local service. The change went through but could not restart the instance. That is what has created my next round of problems. I can't go in and change it back to network because the instance is permanently stopped. I cannot start it with the services manager. How can I fix this?
Here is the connection log:
2009-12-21 11:36:32.20 Server      Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
Jul 9 2008 14:43:34
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)
2009-12-21 11:36:32.50 Server      (c) 2005 Microsoft Corporation.
2009-12-21 11:36:32.51 Server      All rights reserved.
2009-12-21 11:36:32.51 Server      Server process ID is 21856.
2009-12-21 11:36:32.51 Server      Authentication mode is MIXED.
2009-12-21 11:36:32.53 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\Log\ERRORLOG'.
2009-12-21 11:36:32.89 Server      This instance of SQL Server last reported using a process ID of 3216 at 12/18/2009 6:06:56 PM (local) 12/19/2009 2:06:56 AM (UTC). This is an informational message only; no user action is required.
2009-12-21 11:36:32.89 Server      Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\DATA\mastlog.ldf
2009-12-21 11:36:33.26 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-12-21 11:36:33.29 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2009-12-21 11:36:35.15 Server      Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-12-21 11:36:36.64 Server      Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2009-12-21 11:36:37.42 spid6s      Starting up database 'master'.
2009-12-21 11:36:38.98 spid6s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS2'.
2009-12-21 11:36:39.40 spid6s      SQL Trace ID 1 was started by login "sa".
2009-12-21 11:36:39.50 spid6s      Starting up database 'mssqlsystemresource'.
2009-12-21 11:36:39.59 spid6s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2009-12-21 11:36:40.14 spid10s     Starting up database 'model'.
2009-12-21 11:36:40.17 spid6s      Server name is 'USER-F19E13BA9B\SQLEXPRESS2'. This is an informational message only. No user action is required.
2009-12-21 11:36:40.56 spid6s      Informational: No full-text supported languages found.
2009-12-21 11:36:40.57 spid6s      Starting up database 'msdb'.
2009-12-21 11:36:40.60 Server      Error: 17190, Severity: 16, State: 1.
2009-12-21 11:36:40.60 Server      FallBack certificate initialization failed with error code: 1.
2009-12-21 11:36:40.70 Server      Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2009-12-21 11:36:40.71 Server      Error: 17182, Severity: 16, State: 1.
2009-12-21 11:36:40.71 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2009-12-21 11:36:40.71 Server      Error: 17182, Severity: 16, State: 1.
2009-12-21 11:36:40.71 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2009-12-21 11:36:40.71 Server      Error: 17826, Severity: 18, State: 3.
2009-12-21 11:36:40.71 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2009-12-21 11:36:40.71 Server      Error: 17120, Severity: 16, State: 1.
2009-12-21 11:36:40.71 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Hi,
This problem can occur if the new Service Account does not have a profile on the machine. To resolve the issue connect to the SQL Server machine using the New Service account. This will create a profile for the user.
SQL Server creates a self-generated certificate if a certificate is not explicitly specified and/or is not installed. This information is saved in the profile for the SQL Server service account. If the profile has not been created then SQL cannot register the self-generated certificate.
If there are any more questions, please let me know.
Thanks.
***Xiao Min Tan***Microsoft Online Community***
What 'New Service account' are you referring to? SQL Server Express resides on my PC where I'm logged on as administrator. I don't know what you mean by connecting to the server. I only know about connecting to the database instance which is the root of the this problem because it can't be started. Sorry for my confusion...

How to restore SQL Server 2008 database to SQL Server Express 2012

How to restore SQL Server 2008 database to SQL Server Express 2012.
I BACKED UP a SQL Server 2008 database from work, which runs the enterprise version of 2008, and I tried to RESTORE it to my new 64-Bit home PC which is running the new SQL Server Express 2012 64-Bit (Advanced Edition).
But if fails. I get the following message text.
Can anyone help me please. I thought restoring a 2008 database to the later version 2012 would be possible.
Here is the error message. Thanks.
TITLE: Microsoft SQL Server Management Studio
Restore of database failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the backup, or use a
backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)

ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the
backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)
Are you sure your database is SQL server 2008 from error message it seems your SQL server version is 2000.I guess you have multiple versions of SQL server.
AFAIK you cannot restore backup of SQL server 2000 to 2012 directly .Restore it first to SQL 2008/2008R2 or 2005 then take backup again of new database created and then you would be able to restore it on 2012.Its kind of intermediate way
Also make sure your DB size is less than 10 G as max DB size supported by Express edition is 10 G and if your DB size is more than 10 G restore will fail.
You are also trying to restore enterprise DB backup on express edition so you will loose enterprise features on express edition
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Anyone else having issues writting string "memo" fields to Access 2007-2010 or SQL Server Express 2008-2012?

I have a data cluster that I am working to write to either Access 2007 thru 2010 and/or SQL Server Express 2008 thru 2012 all on a Windows 7 64 bit OS. Some of the elements are long strings that I put delimited data for the raw trace data. The fields can be 10's of KB long. With Access I cannot stuff any string >255char into the memo field. With SQL Server Express 2008R2 - 2012 I found that if the strings are >32767 they again fail to fill the memo fields. The Access write or reads work fine otherwise, just not the listed offending fields in the cases mentioned. Anyone else having the issue or a solution?

If the long string field has repetitive data, you might be able to compress it using GZIP to reduce it's size below the 32K limitation you mentioned.
GZIP compress/uncompress of string using .NET
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

SQL Server Express 2008 - 1617 versus 1600

Hello,
My SQL Server Express 2008 R2 version is 10.50.1617.0. Two of my instances (SQLEXPRESS and SQLEXPRESS2) are also version 10.50.1617.0.
However, when I install a new instance, the version is 10.50.1600.0 (SQLEXPRESS3).
How can I install a new instance with the same version as the othe two instances, eg 10.50.1617.0?
Thanks in advance,
S.J. Westra

Hi S.J,
The version 10.50.1600.0 is SQL Server 2008 R2 RTM with no Service Pack. The version 10.50.1617.0 is GDR Security Update.
You will see the size of GDR relatively small .Secondly GDRs increase the build number to a very small margin
(as you can see from 1600 its 1617).
You could use SQL Server setup file to upgrade the SQL Server to a higher version.
Hope this helps.
Maggie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

SQL SERVER EXPRESS DATABASE CONNECTION Parameters

Hi,
I am using the Database called " SQL Server Express"
Can you give idea about connection parameters in JDBC Sender and JDBC Receiver.
Connection Parameters are:
JDBC Driver:
Connection:
Advance Thanks,
Sateesh

Hi Sateesh,
Basis persons are configure the drivers in XI system to u r database.Once installation is complted u have check the following location whether drvers are install succesfull or not.
1)The location is D:usrsapD31DVEBMGS00SDM
ootoriginsap.comcom.sap.aii.af.jmsproviderlibSAP AG37.0014.20071029095337.0000aii_af_jmsproviderlib.sda.zip
In this ZIP file u have to check Sqljdbc.jar whether installed or not.
2)Check in VISUAL Adminstrator.Select JDBC adapter->Drivers->Sqljdbc.jar
Please check this url for DRivers configuartion
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/60237e74-ef19-2b10-5a9b-b35cc6a28e83
3)Configuer the JDBC sender/Reciever Adapter.
JDBC Driver:com.microsoft.sqlserver.jdbc.SQLServerDriver
CONNECTION:jdbc:sqlserver://IP ADDRESS:PORT;Database=HOST NAME;
USER NAME:sa
PWD:XXXXXXXx
Thanks
Ravi

Is it possible to transfer a database from SQL Server 2012 to SQL Server Express 2012?

Is it possible to transfer a database from SQL Server 2012 to
SQL Server Express 2012? Ideally I would like to backup the database from SQL Server 2012 and restore it on SQL Server Express 2012. Is that possible?

Is it possible to transfer a database from SQL Server 2012 to
SQL Server Express 2012? Ideally I would like to backup the database from SQL Server 2012 and restore it on SQL Server Express 2012. Is that possible?
Yes it is possible but database size should not be greater than 10 G as max databse size supported for Express 2012 is 10 G
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Convert Existing MDB database files to SQL Server Express

Hi All,
Can some one please help me on this:
1) What is the current version of SQL Server Express?
2) HOw much SQL Server Express costs (figure about 500 branch servers)
3)Are there any Tools from Microsoft to convert Access 97 directly to SQL Server express, and how much do they cost?
4)Server Hardware requirements to run SQL Server Express - disk size, memory size, security settings, pre-requisite, service needed.
5)Maximum capacity / capabilities of SQL Server Express-max # of simultaneous users,tables,rows,database size.
6)Any installation instruction for SQL Server Express.
Thanks in Advance, Pls help
Thanks
Tony

Hi Tony,
Besides Bruce’s post, firstly, SQL Server Express is a free SQL Server edition,
you can download SQL Server 2014 Express directly from
this link and install it on your computer. For how to install SQL Server 2014 Express, please follow the steps in this similar
blog.
Secondly, for more information about hardware and software requirements for Installing SQL Server 2014 Express, please review this article:
https://msdn.microsoft.com/en-us/library/ms143506.aspx .
Thirdly, SQL Server Express has the following limitations:
• 1 physical processor
• 1 GB of RAM
• 4 GB database size per database in SQL Server 2005 Express and SQL Server 2008 Express , 10 GB database size per database in SQL Server 2008 R2 Express and higher versions of SQL Server Express.
However, there is no limit to the numbers of databases in SQL Server Express. And there is no technical limit to the number of connection that SQL Express can handle.
In addition, there are several methods to convert an Access database to SQL Server, such as using
SQL Server Import and Export Wizard and
SQL Server Migration Assistant for Access, they are both free tools. For more information about convert an Access database to SQL Server, please review this
KB article.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Upgrade from SQL Server 2005 to SQL Server Express 2014 Enterprise

I was just wondering if it is possible to upgrade from SQL Server 2005 to SQL Server Express or will I have to build the environment and then migrate the database?
Thanks for any help

Hi Lance_Romance,
As others’ posts, you don’t have to build new environment and then migrate databases between SQL Server instances, you can use the in-place upgrade strategy to upgrade from SQL Server 2005 to SQL Server 2014 .Please note that SQL Server 2005 SP4 is required
in this case.
Before upgrading , I recommend you to use
upgrade advisor, it can help to analyze your existing SQL Server deployment and inform you of issues that need to be addressed. In addition, please perform a full server backup prior to performing the in-place upgrade, which will be an important way
to revert your SQL Server to its previous state if the upgrade does not go as planned. For more details, please review this blog:
Upgrading to SQL Server 2014: A Dozen Things to Check.
Thanks,
Lydia Zhang

SQL Server Express checking DB Size

Similar Messages

Maybe you are looking for