SQL Server 2008 Dump Transaction

I used SQL Server 2005 before and used "DUMP TRANSACTION ... WITH NO_LOG" statement, i tried to do same  thing in SQL Server 2008 and it doesn't work. How can i use it in SQL Server 2008?

The shrinking of  TL process is changed in SQL Server 2008. You just need to
(a) set the database to simple recovery model
(b) Shirnk the file
(c) Set back to Full (If required). ie. If you are not taking TL backup let it be in Simple recovery model only
Also check this
Discontinued Database Engine Functionality in SQL Server 2008
Madhu

Similar Messages

  • SQL Server 2008 R2 Transaction Replication Tracer Tokens always pending

    On a new transaction replication publiciation/subscription, the tracer tokens I generate always show pending for publisher to distributor and distributor to subscriber.  The log reader agent is running and last action continues to update.   The
    Performance column in the repl monitor shows Excellent with a 00:00:03 latency.  Distribution cleanup, agent history clean up, and replication agents checkup all show job succeeded and a resent last start time and their running times are usualy around
    a second or show 00:00:00.  On the subscriber, the "view synchronization status"  is being updated with number of transactions and commands being delivered.  I can confirm that updates are making it to the subscriber database.  On
    the surface, everything apears ok but I'm bothered by the tracker tokens not working.
    this is SQL Server 2008 R2 10.50.1600.1 - OS is Windows Server 2008 R2 SP1.
    -Larry
    -Larry

    In this case run sp_replcounters at the published db to see if the log reader delivers commands from the published db to the distribution db.
    Yaniv Etrogi
    site |
    blog | linked in |
    mail
    Please click the Mark as Answer button if a post solves your problem! or
    Vote As Helpful

  • Distributed transaction using linked server not working in SQL Server 2008 64 bit

    Hi. I have had an issue trying to get distributed transactions to work in SQL Server 2008 using a linked server. The error message I get is
    OLE DB provider "SQLNCLI10" for linked server "pod1" returned message "No transaction is active.".
    Msg 7391, Level 16, State 2, Line 3
    The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "pod1" was unable to begin a distributed transaction.
    My Environment:
    Windows Server 2008 Enterprise 64 bit, SQL Server 2008 Enterprise 64 bit
    Problem occurs with multiple different builds of SQL Server 2008 - I have been able to reproduce the problem with 10.0.1600.0, 10.0.1779.0 (CU 2), as well as 10.0.2531 (SP1)
    I am aware that other people have had this issue and have reviewed all existing posts. I have verified that the MSDTC is configured correctly on both machines. I have also used DTCTester to verify that DTC is working correctly on all machines in question.
    None of the mentioned resolutions has solved this problem for me.
    I am not seeing this problem occur on my 32 bit test machines - it is only occurring if at least one of the two machines is 64 bit.

    Hi All,
    I realise that this topic may be a little bit out-of-date but if someone gets here from some search engine trying to find a solution for DTC problems, this MAY be useful.
    So... I recently had the same issue, tried all the approaches described in KB and other articles, but it didn't help. Because my task to solve this was not of the highest priority I forgot about it for some time.
    Today I was troubleshooting some other issue and, by accident discovered source of that first problem:
    In the EventViewer I found Error entry logged by MSDTC saying:
    "The local MS DTC detected that the MS DTC on vm-server1 (other machine name that also runs DTC - my comment) has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate
    with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install'
    from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information."
    So I followed suggestion and run:
    msdtc -uninstall
    msdtc -install
    This solved my problems with DTC. Hope it will help someone.
    Piotr

  • Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

    I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
    "Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
    Nor will the query execute; I get a transport-level error 0. Any thoughts?

    Hi Davidmhjr,
    >>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
    Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
    If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
    with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
    So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
    More information about configuration requirement to run T-SQL debugger as below, please refer:
    There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
    Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
    On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
    •Add TCP port 135 to the exceptions list.
    •Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
    any named instance.
    •If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
    On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
    •Add TCP port 135 to the exceptions list.
    •Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
    Hope it is helpful.
    Regards, Amber zhang

  • Dump of SQL Server 2008 R2 Enterprise

    Hi,
       How can I download the Dump of SQL Server 2008 R2 Enterprise Edition? I have the License Details. But I missed the CDs. Could you please help for the Dump collection?
    ! ! Thank You Very much ! !
    Best Regards
    +91 9871843884

       How can I download the Dump of SQL Server 2008 R2 Enterprise Edition? I have the License Details. But I missed the CDs. Could you please help for the Dump collection?
    Hi,
    If you have license key with yourself. You can download SQL Server 2008 R2 Evaluation edition. When you are installing SQL Server eval edition on license key page you would have option to select free  edition or provide License key for Enterprise edition.
    Provide License key and it would be enterprise edition after your installation finishes
    PS: if above does not helps please speak to MS personal
    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 Article
    MVP

  • Sql server 2008 R2 sp2 keeps crashing with ntdll.dll

    Our sql server 2008 r2 on windows 2008 r2 crashes once a day with this error
    Faulting application name: sqlservr.exe, version: 2009.100.4290.0, time stamp: 0x52007306
    Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c40f2
    Faulting process id: 0x11b8
    Faulting application start time: 0x01cf59e47c2e9f9a
    Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 93d8ef8b-c70c-11e3-b572-002564fcc042
    Here is the dump
    Version=1
    EventType=APPCRASH
    EventTime=130423078596029680
    ReportType=2
    Consent=1
    ReportIdentifier=93d8ef8c-c70c-11e3-b572-002564fcc042
    IntegratorReportIdentifier=93d8ef8b-c70c-11e3-b572-002564fcc042
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=sqlservr.exe
    Sig[1].Name=Application Version
    Sig[1].Value=2009.100.4290.0
    Sig[2].Name=Application Timestamp
    Sig[2].Value=52007306
    Sig[3].Name=Fault Module Name
    Sig[3].Value=StackHash_259d
    Sig[4].Name=Fault Module Version
    Sig[4].Value=6.1.7601.17725
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=4ec4aa8e
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000374
    Sig[7].Name=Exception Offset
    Sig[7].Value=00000000000c40f2
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.274.10
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=259d
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=259dc7d033214d7478a8b078fa9c6fc4
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=a970
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=a9707a254613322c29b1185c564c54e6
    UI[2]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
    UI[5]=Check online for a solution (recommended)
    UI[6]=Check for a solution later (recommended)
    UI[7]=Close
    UI[8]=SQL Server Windows NT - 64 Bit stopped working and was closed
    UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
    UI[10]=&Close
    LoadedModule[0]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\system32\kernel32.dll
    LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[5]=C:\Windows\system32\msvcrt.dll
    LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[8]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\MSVCR80.dll
    LoadedModule[9]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\MSVCP80.dll
    LoadedModule[10]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlos.dll
    LoadedModule[11]=C:\Windows\system32\Secur32.dll
    LoadedModule[12]=C:\Windows\system32\SSPICLI.DLL
    LoadedModule[13]=C:\Windows\system32\pdh.dll
    LoadedModule[14]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[15]=C:\Windows\system32\GDI32.dll
    LoadedModule[16]=C:\Windows\system32\USER32.dll
    LoadedModule[17]=C:\Windows\system32\LPK.dll
    LoadedModule[18]=C:\Windows\system32\USP10.dll
    LoadedModule[19]=C:\Windows\system32\USERENV.dll
    LoadedModule[20]=C:\Windows\system32\profapi.dll
    LoadedModule[21]=C:\Windows\system32\WINMM.dll
    LoadedModule[22]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[23]=C:\Windows\system32\NSI.dll
    LoadedModule[24]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[25]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\opends60.dll
    LoadedModule[26]=C:\Windows\system32\NETAPI32.dll
    LoadedModule[27]=C:\Windows\system32\netutils.dll
    LoadedModule[28]=C:\Windows\system32\srvcli.dll
    LoadedModule[29]=C:\Windows\system32\wkscli.dll
    LoadedModule[30]=C:\Windows\system32\LOGONCLI.DLL
    LoadedModule[31]=C:\Windows\system32\SAMCLI.DLL
    LoadedModule[32]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\BatchParser.dll
    LoadedModule[33]=C:\Windows\system32\IMM32.DLL
    LoadedModule[34]=C:\Windows\system32\MSCTF.dll
    LoadedModule[35]=C:\Windows\system32\psapi.dll
    LoadedModule[36]=C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll
    LoadedModule[37]=C:\Windows\system32\cscapi.dll
    LoadedModule[38]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\sqlevn70.rll
    LoadedModule[39]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[40]=C:\Windows\system32\rsaenh.dll
    LoadedModule[41]=C:\Windows\system32\CRYPTBASE.dll
    LoadedModule[42]=C:\Windows\system32\BROWCLI.DLL
    LoadedModule[43]=C:\Windows\system32\AUTHZ.DLL
    LoadedModule[44]=C:\Windows\system32\MSCOREE.DLL
    LoadedModule[45]=C:\Windows\system32\ole32.dll
    LoadedModule[46]=C:\Windows\system32\credssp.dll
    LoadedModule[47]=C:\Windows\system32\msv1_0.DLL
    LoadedModule[48]=C:\Windows\system32\cryptdll.dll
    LoadedModule[49]=C:\Windows\system32\kerberos.DLL
    LoadedModule[50]=C:\Windows\system32\MSASN1.dll
    LoadedModule[51]=C:\Windows\system32\schannel.DLL
    LoadedModule[52]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[53]=C:\Windows\system32\security.dll
    LoadedModule[54]=C:\Windows\system32\WS2_32.dll
    LoadedModule[55]=C:\Windows\system32\SHELL32.dll
    LoadedModule[56]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[57]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\ftimport.dll
    LoadedModule[58]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\MSFTE.DLL
    LoadedModule[59]=C:\Windows\system32\VERSION.dll
    LoadedModule[60]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\dbghelp.dll
    LoadedModule[61]=C:\Windows\system32\WINTRUST.dll
    LoadedModule[62]=C:\Windows\system32\ntmarta.dll
    LoadedModule[63]=C:\Windows\system32\WLDAP32.dll
    LoadedModule[64]=C:\Windows\system32\ncrypt.dll
    LoadedModule[65]=C:\Windows\system32\bcrypt.dll
    LoadedModule[66]=C:\Windows\system32\mswsock.dll
    LoadedModule[67]=C:\Windows\System32\wship6.dll
    LoadedModule[68]=C:\Windows\System32\wshtcpip.dll
    LoadedModule[69]=C:\Windows\system32\ntdsapi.dll
    LoadedModule[70]=C:\Windows\system32\DNSAPI.dll
    LoadedModule[71]=C:\Windows\system32\rasadhlp.dll
    LoadedModule[72]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[73]=C:\Windows\system32\bcryptprimitives.dll
    LoadedModule[74]=C:\Windows\system32\SAMLIB.dll
    LoadedModule[75]=C:\Windows\system32\CLBCatQ.DLL
    LoadedModule[76]=C:\Windows\system32\sqlncli10.dll
    LoadedModule[77]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_a4d6a923711520a9\COMCTL32.dll
    LoadedModule[78]=C:\Windows\system32\COMDLG32.dll
    LoadedModule[79]=C:\Windows\system32\1033\SQLNCLIR10.RLL
    LoadedModule[80]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
    LoadedModule[81]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\51a23687fdafc32b697f5a719e364651\mscorlib.ni.dll
    LoadedModule[82]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorsec.dll
    LoadedModule[83]=C:\Windows\system32\imagehlp.dll
    LoadedModule[84]=C:\Windows\system32\GPAPI.dll
    LoadedModule[85]=C:\Windows\system32\cryptnet.dll
    LoadedModule[86]=C:\Windows\system32\SensApi.dll
    LoadedModule[87]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SqlAccess.dll
    LoadedModule[88]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
    LoadedModule[89]=C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll
    LoadedModule[90]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\6be6efa1e2ffc9d46e99839edac5c5a8\System.ni.dll
    LoadedModule[91]=C:\Windows\assembly\GAC_64\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll
    LoadedModule[92]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Security\15270ef5168ba4d4185515789a08655d\System.Security.ni.dll
    LoadedModule[93]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\xpstar.dll
    LoadedModule[94]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SQLSCM.dll
    LoadedModule[95]=C:\Windows\system32\ODBC32.dll
    LoadedModule[96]=C:\Windows\WinSxS\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_8a1a02152edb659b\ATL80.DLL
    LoadedModule[97]=C:\Windows\system32\odbcint.dll
    LoadedModule[98]=C:\Windows\system32\clusapi.dll
    LoadedModule[99]=C:\Windows\system32\resutils.dll
    LoadedModule[100]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\xpstar.rll
    LoadedModule[101]=C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll
    LoadedModule[102]=C:\Windows\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll
    LoadedModule[103]=C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll
    LoadedModule[104]=C:\Windows\system32\COMRES.DLL
    LoadedModule[105]=C:\Windows\system32\XOLEHLP.DLL
    LoadedModule[106]=C:\Windows\system32\MSDTCPRX.DLL
    LoadedModule[107]=C:\Windows\system32\MTXCLU.DLL
    LoadedModule[108]=C:\Windows\system32\ktmw32.dll
    LoadedModule[109]=C:\Windows\system32\RpcRtRemote.dll
    LoadedModule[110]=C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xp_greta_64.dll
    LoadedModule[111]=C:\Windows\system32\apphelp.dll
    LoadedModule[112]=C:\Windows\system32\dsrole.dll
    LoadedModule[113]=C:\Program Files\Microsoft SQL Server\80\COM\sqlvdi.dll
    LoadedModule[114]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\odsole70.dll
    LoadedModule[115]=C:\Windows\system32\scrrun.dll
    LoadedModule[116]=C:\Windows\system32\SXS.DLL
    LoadedModule[117]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\odsole70.RLL
    LoadedModule[118]=C:\Program Files\Microsoft SQL Server\90\Shared\instapi.dll
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=SQL Server Windows NT - 64 Bit
    AppPath=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
    Can help me fixed this
    Thanks

    Thank you for your responses.  This server is on a dell poweredge T710 with 192 gb of memory.  All the hardware drivers are up to date and so is sql.  No memory errors.  The only error I get is when sql crashes.  The only 3rd party
    dll what is on the server would be xp_greta_64.dll.  We are looking into that.
    I have a question about setting up a link server with 'out of process'  We only use sql server link connections with other sql servers.  When I try to setup 'out of process' unchecking allow inprocess under SQLNCLI all of my link servers end up
    failing and giving me errors.  I had to switch it back since this is a production machine. Is there a way to just set up 'out of process' on one link server with SQLNCLI, it seems it is all or nothing.  Do I have to delete all the current link
    servers and recreate them?
    The only other thing that we have changed is that we have added Python 3.3 and ActivePerl 5.16.3 but not on this server.  Only on all of our other sql servers. 
    Here is our last dump from yesterday.  Thanks again, If I have too I will open a case up with Microsoft.
    Version=1
    EventType=APPCRASH
    EventTime=130444796758798656
    ReportType=2
    Consent=1
    ReportIdentifier=3b3973c8-dacd-11e3-a1c5-002564fcc042
    IntegratorReportIdentifier=3b3973c7-dacd-11e3-a1c5-002564fcc042
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=sqlservr.exe
    Sig[1].Name=Application Version
    Sig[1].Value=2009.100.4302.0
    Sig[2].Name=Application Timestamp
    Sig[2].Value=52f5d194
    Sig[3].Name=Fault Module Name
    Sig[3].Value=StackHash_9f88
    Sig[4].Name=Fault Module Version
    Sig[4].Value=6.1.7601.18247
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=521eaf24
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000374
    Sig[7].Name=Exception Offset
    Sig[7].Value=00000000000c4102
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.274.10
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=9f88
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=9f887580f62df3cb4138fc685cae8618
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=d54e
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=d54ee610c7110c152675c4fdbbef635a
    UI[2]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
    UI[5]=Check online for a solution (recommended)
    UI[6]=Check for a solution later (recommended)
    UI[7]=Close
    UI[8]=SQL Server Windows NT - 64 Bit stopped working and was closed
    UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
    UI[10]=&Close
    LoadedModule[0]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\system32\kernel32.dll
    LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[5]=C:\Windows\system32\msvcrt.dll
    LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[8]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\MSVCR80.dll
    LoadedModule[9]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\MSVCP80.dll
    LoadedModule[10]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlos.dll
    LoadedModule[11]=C:\Windows\system32\Secur32.dll
    LoadedModule[12]=C:\Windows\system32\SSPICLI.DLL
    LoadedModule[13]=C:\Windows\system32\pdh.dll
    LoadedModule[14]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[15]=C:\Windows\system32\GDI32.dll
    LoadedModule[16]=C:\Windows\system32\USER32.dll
    LoadedModule[17]=C:\Windows\system32\LPK.dll
    LoadedModule[18]=C:\Windows\system32\USP10.dll
    LoadedModule[19]=C:\Windows\system32\USERENV.dll
    LoadedModule[20]=C:\Windows\system32\profapi.dll
    LoadedModule[21]=C:\Windows\system32\WINMM.dll
    LoadedModule[22]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[23]=C:\Windows\system32\NSI.dll
    LoadedModule[24]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[25]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\opends60.dll
    LoadedModule[26]=C:\Windows\system32\NETAPI32.dll
    LoadedModule[27]=C:\Windows\system32\netutils.dll
    LoadedModule[28]=C:\Windows\system32\srvcli.dll
    LoadedModule[29]=C:\Windows\system32\wkscli.dll
    LoadedModule[30]=C:\Windows\system32\LOGONCLI.DLL
    LoadedModule[31]=C:\Windows\system32\SAMCLI.DLL
    LoadedModule[32]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\BatchParser.dll
    LoadedModule[33]=C:\Windows\system32\IMM32.DLL
    LoadedModule[34]=C:\Windows\system32\MSCTF.dll
    LoadedModule[35]=C:\Windows\system32\psapi.dll
    LoadedModule[36]=C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll
    LoadedModule[37]=C:\Windows\system32\cscapi.dll
    LoadedModule[38]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\sqlevn70.rll
    LoadedModule[39]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[40]=C:\Windows\system32\rsaenh.dll
    LoadedModule[41]=C:\Windows\system32\CRYPTBASE.dll
    LoadedModule[42]=C:\Windows\system32\BROWCLI.DLL
    LoadedModule[43]=C:\Windows\system32\AUTHZ.DLL
    LoadedModule[44]=C:\Windows\system32\MSCOREE.DLL
    LoadedModule[45]=C:\Windows\system32\ole32.dll
    LoadedModule[46]=C:\Windows\system32\credssp.dll
    LoadedModule[47]=C:\Windows\system32\msv1_0.DLL
    LoadedModule[48]=C:\Windows\system32\cryptdll.dll
    LoadedModule[49]=C:\Windows\system32\kerberos.DLL
    LoadedModule[50]=C:\Windows\system32\MSASN1.dll
    LoadedModule[51]=C:\Windows\system32\schannel.DLL
    LoadedModule[52]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[53]=C:\Windows\system32\security.dll
    LoadedModule[54]=C:\Windows\system32\WS2_32.dll
    LoadedModule[55]=C:\Windows\system32\SHELL32.dll
    LoadedModule[56]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[57]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\ftimport.dll
    LoadedModule[58]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\MSFTE.DLL
    LoadedModule[59]=C:\Windows\system32\VERSION.dll
    LoadedModule[60]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\dbghelp.dll
    LoadedModule[61]=C:\Windows\system32\WINTRUST.dll
    LoadedModule[62]=C:\Windows\system32\ntmarta.dll
    LoadedModule[63]=C:\Windows\system32\WLDAP32.dll
    LoadedModule[64]=C:\Windows\system32\ncrypt.dll
    LoadedModule[65]=C:\Windows\system32\bcrypt.dll
    LoadedModule[66]=C:\Windows\system32\mswsock.dll
    LoadedModule[67]=C:\Windows\System32\wship6.dll
    LoadedModule[68]=C:\Windows\System32\wshtcpip.dll
    LoadedModule[69]=C:\Windows\system32\ntdsapi.dll
    LoadedModule[70]=C:\Windows\system32\DNSAPI.dll
    LoadedModule[71]=C:\Windows\system32\rasadhlp.dll
    LoadedModule[72]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[73]=C:\Windows\system32\bcryptprimitives.dll
    LoadedModule[74]=C:\Windows\system32\SAMLIB.dll
    LoadedModule[75]=C:\Windows\system32\CLBCatQ.DLL
    LoadedModule[76]=C:\Windows\system32\sqlncli10.dll
    LoadedModule[77]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.dll
    LoadedModule[78]=C:\Windows\system32\COMDLG32.dll
    LoadedModule[79]=C:\Windows\system32\1033\SQLNCLIR10.RLL
    LoadedModule[80]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\xpstar.dll
    LoadedModule[81]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SQLSCM.dll
    LoadedModule[82]=C:\Windows\system32\ODBC32.dll
    LoadedModule[83]=C:\Windows\WinSxS\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_8a1a02152edb659b\ATL80.DLL
    LoadedModule[84]=C:\Windows\system32\odbcint.dll
    LoadedModule[85]=C:\Windows\system32\clusapi.dll
    LoadedModule[86]=C:\Windows\system32\resutils.dll
    LoadedModule[87]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\xpstar.rll
    LoadedModule[88]=C:\Windows\system32\COMRES.DLL
    LoadedModule[89]=C:\Windows\system32\XOLEHLP.DLL
    LoadedModule[90]=C:\Windows\system32\MSDTCPRX.DLL
    LoadedModule[91]=C:\Windows\system32\MTXCLU.DLL
    LoadedModule[92]=C:\Windows\system32\ktmw32.dll
    LoadedModule[93]=C:\Windows\system32\RpcRtRemote.dll
    LoadedModule[94]=C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xp_greta_64.dll
    LoadedModule[95]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
    LoadedModule[96]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\bb750d3baf928f94ea3977e96af9769f\mscorlib.ni.dll
    LoadedModule[97]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorsec.dll
    LoadedModule[98]=C:\Windows\system32\imagehlp.dll
    LoadedModule[99]=C:\Windows\system32\GPAPI.dll
    LoadedModule[100]=C:\Windows\system32\cryptnet.dll
    LoadedModule[101]=C:\Windows\system32\SensApi.dll
    LoadedModule[102]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SqlAccess.dll
    LoadedModule[103]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
    LoadedModule[104]=C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll
    LoadedModule[105]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\350ed175b92e48f5249a1bab538872e5\System.ni.dll
    LoadedModule[106]=C:\Windows\assembly\GAC_64\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll
    LoadedModule[107]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Security\7c4199ce0470f8e4664a7ee345b31235\System.Security.ni.dll
    LoadedModule[108]=C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll
    LoadedModule[109]=C:\Windows\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll
    LoadedModule[110]=C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll
    LoadedModule[111]=C:\Windows\system32\apphelp.dll
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=SQL Server Windows NT - 64 Bit
    AppPath=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe

  • SQL Server 2008 Intellisense not working

    I've seen a post about this here: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3371737&SiteID=17
    I've installed SQL Server 2008 and for a few weeks, intellisense was working fine.  The past week, it has stopped working entirely.  I'm running version 10.0.1442.  In Tools-->Options-->Text Editor-->Transact-SQL-->Intellisense, the option to "Enable Intellisense" is turned on.  I've also made sure that SQLCMD Mode is turned off.  I've disconnected a reconnected to my database several times with no luck.  I can try to uninstall and reinstall like the guy in the post I've referenced did, but if I can help to try to find out what's wrong here, I'm willing to wait for a while before doing so.

    Hello to everyone this is my first post and I hope I'm doing right.
    Anyway, I had the same issue with the IntelliSense. I think I messed up installing the Express Edition over SQLServer 2008 R2.
    I'm not an expert, but I think this corrupted my environment. 
    This was driving me crazy and even if it's not an essential tool, I was looking for another solution, I didn't want to install again everything.  
    So I started to look at the Option window and I played with its settings.
    For the ones who don't know...
    Tool > Options > Text Editor > Transact-SQL > IntelliSense.
    But 'Enable IntelliSense' was ticked, so I unticked and saved.
    I opened the view again and I ticked them again.
    Magically my IntelliSense started again to work fine.
    Hope to be helpful.
    Cheers.
    J 

  • Msg 8631 Internal error: Server stack limit has been reached on SQL Server 2012 from T-SQL script that runs on SQL Server 2008 R2

    I have an Script mostly that is generated by SSMS which works with-out issue on SQL Server 2008, but when I attempt to run it on a new fresh install of SQL Server 2012 I get an Msg 8631. Internal error: Server stack limit has been reached. Please look for
    potentially deep nesting in your query, and try to simplify it.
    The script itself doesn't seem to be all that deep or nested.  The script is large 2600 lines and when I remove the bulk of the 2600 lines, it does run on SQL Server 2012.  I'm just really baffled why something that SQL Server generated with very
    few additions/changes AND that WORKS without issue in SQL Server 2008 R2 would suddenly be invalid in SQL Server 2012
    I need to know why my script which is working great on our current SQL Server 2008 R2 servers suddenly fails and won't run on an new SQL Server 2012 server.  This script is used to create 'bulk' Replications on a large number of DBs saving a tremendous
    amount of our time doing it the manual way.
    Below is an 'condensed' version of the script which fails.  I have removed around 2550 lines of specific sp_addarticle statements which are mostly just copy and pasted from what SQL Management Studio 'scripted' for me went I when through the Replication
    Wizard and told it to save to script.
    declare @dbname varchar(MAX), @SQL nvarchar(MAX)
    declare c_dblist cursor for
    select name from sys.databases WHERE name like 'dbone[_]%' order by name;
    open c_dblist
    fetch next from c_dblist into @dbname
    while @@fetch_status = 0
    begin
    print @dbname
    SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
    use ['+@dbname+']
    exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
    use ['+@dbname+']
    exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
    -- Adding the transactional publication
    use ['+@dbname+']
    exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
    '''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
    = N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
    @immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
    exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
    @frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
    -- There are around 2400 lines roughly the same as this only difference is the tablename repeated below this one
    use ['+@dbname+']
    exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script =
    null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509F, @identityrangemanagementoption = N''manual'', @destination_table = N''TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false'', @ins_cmd = N''CALL sp_MSins_dboTABLE_ONE'',
    @del_cmd = N''CALL sp_MSdel_dboTABLE_ONE'', @upd_cmd = N''SCALL sp_MSupd_dboTABLE_ONE''
    EXEC sp_executesql @SQL
    SET @dbname = REPLACE(@dbname, 'dbone_', 'dbtwo_');
    print @dbname
    SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
    use ['+@dbname+']
    exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
    use ['+@dbname+']
    exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
    -- Adding the transactional publication
    use ['+@dbname+']
    exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
    '''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
    = N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
    @immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
    exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
    @frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
    -- There are around 140 lines roughly the same as this only difference is the tablename repeated below this one
    use ['+@dbname+']
    exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''DB_TWO_TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''DB_TWO_TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script
    = null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509D, @identityrangemanagementoption = N''manual'', @destination_table = N''DB_TWO_TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false''
    EXEC sp_executesql @SQL
    fetch next from c_dblist into @dbname
    end
    close c_dblist
    deallocate c_dblist
    George P Botuwell, Programmer

    Hi George,
    Thank you for your question. 
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. 
    Thank you for your understanding and support.
    If you have any feedback on our support, please click
    here.
    Allen Li
    TechNet Community Support

  • SQL Server 2008 R2 { An Error occured when attaching database(s) }

    Hello Guys!
    I just installed SQL Server 2008 R2 a couple of days ago, on the first day use i can attach database(.mdf) with out any problem.
    on the day 2, i keep getting this error:
    http://img515.imageshack.us/img515/14/1212i.png
    TITLE: Microsoft SQL Server Management Studio
    An error occurred when attaching the database(s).  Click the hyperlink in the Message column for details.
    BUTTONS:
    OK
    after clicking the Hyperlink this window open:
    http://img34.imageshack.us/img34/8766/hyperg.png
    TITLE: Microsoft SQL Server Management Studio
    Attach database failed for Server 'STARGAZER-PC\SQLSTARMAX'.  (Microsoft.SqlServer.Smo)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1539+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
    ADDITIONAL INFORMATION:
    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
    Unable to open the physical file "E:\New folder\DataBase.MDF". Operating system error 5: "5(Access is denied.)". (Microsoft SQL Server, Error: 5120)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=5120&LinkId=20476
    BUTTONS:
    OK
    in that day i reinstall SQL Server 2008 R2, because I'm so confused. after that i try to attach i still got the same error, what i did is i share the folder where the database is.
    i open SSMS and try to attach and i attached without any error...
    i think this is the 4rth day, untill now everytime i want to attach a database i got this error, and even i try to share the folder where the database is i still got that error.
    any advice guys?
    Thanks a lot
    jhules
    if you want to be happy, find something you love to do and do it for free, then find someone to to you for it.

    The Error clearly shows that MDF files and LDF files are not matching or LDF file is corrupted.
    You can follow either of the one option below
    1. Restore a recent backup rather attaching the MDF file
    2. Attach  single MDF file without LOG File( Warning: All the log transactions will be gone and new log file will be created)
    EXEC sp_attach_single_file_db @dbname = 'AdventureWorks2008R2',
        @physname = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\AdventureWorks2008R2_Data.mdf';
    Thanks, Aditya Badramraju, _______________________________________________________ Please mark answered if your question is completely answered; vote it as helpful to help others find a solution quicker. This posting is provided AS IS with no warranties
    and confers no rights. _______________________________________________________

  • Data Committed instead of Rollback after Deadlock Error in SQL Server 2008 R2 (SP2)

    We're having a strange issue which is occurring only with one Customer having SQL Server 2008 R2 (SP2).
    Basically we have multiple threads uploading data and when an error occurs (like deadlock or any other error). The deadlock victim (process/transaction) is rolledback (from .NET). However the rollback command is not reaching SQL Server as it doesn't show
    in the trace (through SQL Profiler).
    To make things worse, not only the transaction is not being rolled back but the INSERTs executed before the error are being somehow committed, leaving the database in an inconsistent state.
    This is only produced in one environment.
    Any idea what the issue could be?

    All statements are executed with in a Transaction. Under the same scenario this code works perfectly fine for 1000s of customers. Only one customer has this issue.
    You need to capture profiler to check transaction scope.
    Balmukund Lakhani
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    | Facebook
    Author: SQL Server 2012 AlwaysOn -
    Paperback, Kindle

  • SQL Server 2008 Express - timeout issues, "This SqlTransaction has completed; it is no longer usable."

    Good morning all!   I work for a small business that uses a robust Accounting/Inventory database called Traverse (or Open Systems) and is run on a desktop computer using SQL Server 2008 Express.
    We don't have an IT department, but I have a bit of knowledge, so I've been the go-to person to handle any tech support issues in our tiny 5 person office.  I've been reading up on SQL Server 2008 Express, but am completely stumped on this issue.
    Our database would work consistently well for quite a while - sometimes getting disconnected from the server and requiring a restart of either the SQL Server itself or the Traverse License Server.
    About two weeks ago, I noticed that nobody had ever run Windows Update on the desktop that we have SQL Server on, so I spent the better part of a day updating everything, hoping it would help some of the little buggy issues we've been having.   Unfortunately,
    by applying the updates, I think it may have altered settings - or updated appropriately and our functionality is diminished.
    Basically, we have 3 users connecting into the server to use the database at any time.  Sometimes we might not be accessing information constantly, and it appears we're getting a timeout message in the SQL Server Log - stating the system was awoken
    by user activity after around 25-30 minutes.  When this happens, the system is painfully slow and locks up, giving SQL Server Connection errors, or the "This SqlTransaction has completed; it is no longer usable." message.   I noticed that
    there is a connection timeout of 15 seconds set for our SQL Server, but it's greyed out in the dialog box I saw it in, and am not sure if that's even a culprit.
    I'd just like to get this working again to where we can continue to use the database throughout the day without waiting for it to seemingly load all of the data after "waking up".  It's to a point that one of my employees is coming into my
    office every 5 minutes complaining that she can't do anything in Traverse.  I'm about to lose my mind!  
    If anyone has any clue what could be the issue, I'd be so grateful for help.  If you need any logs, messages, etc.. please let me know which and I will share them.  Thank you again!

    This is known as the Zombie Check exception. It is generally caused by trying to commit a transaction twice or trying to roll back a committed transaction. It can also be caused by a connection closing before the transaction is complete. In you case I would
    suspect the latter.
    See this article on setting the default timeout.
    Andy Tauber
    Data Architect
    The Vancouver Clinic
    Website | LinkedIn
    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
    "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

  • Error attaching Adventureworks 2008 db to SQL Server 2008 [not R2]

    Hi ppl,
    I have SQL Server 2008[NOT R2] installed in my laptop [Windows Vista Home Premium, 64 bit].
    There are 2 issues:
    1. Downloaded the AdventureWorks 2008_SR4 from the link :
     http://msftdbprodsamples.codeplex.com/releases/view/37109 .
    but wasn't able to install it due to an error - database Installer stopped working and had to close the program.
    Hence my friend installed it his laptop and sent me the .mdf and .ldf files.
    2. I tried attaching the databases using SSMS2008, but it is showing Error:
    TITLE: Microsoft SQL Server Management Studio
    Attach database failed for Server 'xxxxxx'.  (Microsoft.SqlServer.Smo)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.0.1600.22+((SQL_PreRelease).080709-1414+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
    ADDITIONAL INFORMATION:
    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
    The database 'AdventureWorksDW2008' cannot be opened because it is version 661. This server supports version 655 and earlier. A downgrade path is not supported.
    Could not open new database 'AdventureWorksDW2008'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=948&LinkId=20476
    BUTTONS:
    OK
    I have checked the version of sql server opened in SSMS and it is 2008 itself
    I cannot find any other Non R2 AdventureWorks file for 2008.
    Any help would be appreciated greatly.
    Thanks,
    Chips.

    I have SQL Server 2008[NOT R2] installed in my laptop [Windows Vista Home Premium, 64 bit].
    The database 'AdventureWorksDW2008' cannot be opened because it is version
    661. This server supports version 655 and earlier.
    Hello Chips,
    database version 655 is SQL Server 2008, 661
    is SQL Server 2008 R2, so your friend send you a database file of a newer version, which you can't attach to a older version. I guess your friend uses 2008R2, the database is upgraded automatically to this version.
    Have a deeper look at CodePlex, Version 2008 is still available there.
    Olaf Helper
    * cogito ergo sum * errare humanum est * quote erat demonstrandum *
    Wenn ich denke, ist das ein Fehler und das beweise ich täglich
    Blog
    Xing

  • Problem attaching mdf file in sql server 2008

    hi...!
    I have an mdf file of sql server 2005 database now i want it to attach in sql server 2008 R2 but when i try to attach it, it gave me error saying.
       Fail to retrieve data for this request. 
     An exception occur while executing a Transact-SQL statement or batch.(Microsoft.sqlServer.connectionInfo)
    C:\program files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\file6.mdf is not a primary database file. (Microsoft SQL Server, Error:5171)
    Thanks in advance

    hi...!
    I have an mdf file of sql server 2005 database now i want it to attach in sql server 2008 R2 but when i try to attach it, it gave me error saying.
       Fail to retrieve data for this request. 
     An exception occur while executing a Transact-SQL statement or batch.(Microsoft.sqlServer.connectionInfo)
    C:\program files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\file6.mdf is not a primary database file. (Microsoft SQL Server, Error:5171)
    Thanks in advance
    Hello,
    As the message says the file is not primary data file ,i guess it must be ndf(secondary data file) or some other file you might have selected by mistake.PLease select primary data file and try attching you will succed
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • DeadLocks on Query Notifications with SQL Server 2008 SP3

    Hello,
    according to this article https://support.microsoft.com/kb/975090 the issue with deadlocks on query notifications should be fixed with SQL Server 2008 SP3 (10.0.5500.0). But we still get deadlocks in the following manner:
    <resource-list>
    <keylock hobtid="72057598393909248" dbid="5" objectname="MyDB.sys.query_notification_1411013420" indexname="cidx" id="lock1731c1f00" mode="RangeX-X" associatedObjectId="72057598393909248">
    <owner-list>
    <owner id="process573dc8" mode="RangeX-X"/>
    </owner-list>
    <waiter-list>
    <waiter id="process58ddc8" mode="RangeS-U" requestType="wait"/>
    </waiter-list>
    </keylock>
    <keylock hobtid="72057598372872192" dbid="5" objectname="MyDB.sys.query_notification_253437289" indexname="cidx" id="lock800c8780" mode="RangeS-U" associatedObjectId="72057598372872192">
    <owner-list>
    <owner id="process58ddc8" mode="RangeS-U"/>
    </owner-list>
    <waiter-list>
    <waiter id="process573dc8" mode="RangeS-U" requestType="wait"/>
    </waiter-list>
    </keylock>
    </resource-list>
    Is there any need to install another fix?
    Thanks in Advance!

    Hello,
    SQL Server 2008 SP4 and all cumulative updates of SP3 do not have fixes related to deadlocks.
    Maybe the following workarounds and solutions can help in your scenario.
    http://stackoverflow.com/questions/3707137/understanding-deadlocks-with-sql-server-query-notifications
    Deadlock Prevention. In case you need to lock multiple conversation groups in a transaction, you need to take the same order to lock the different conversation groups in all transactions, otherwise you will have a deadlock issues.
    Source:
    http://blogs.msdn.com/b/kangmo/archive/2008/12/17/a-brief-guide-on-sql-server-service-broker.aspx
    Try to may transactions more simple and shorter.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • I cannot debug with SQL server 2008 SSMS asks for Firewall permission?

    hi friends,
    I run SQL server 2008 R2 developer edition on windows 8 basic edition. SQL server is installed in my local machine. when I tried to debug a sql script it asked the firewall permission as show on image
    when googled I found this
    Article from MSDN with fix tool but it cannot installed on my Windows 8 OS, is there way to fix it without giving any unauthorized access to my system?
    thanks
    I use Visual studio 2012 Ultimate and SQL server 2008 developer edition!

    Hi,
    The hotfix you provide applies for Windows Server 2008.
    The windows firewall on this machine is currently blocking remote debugging.
    According the message, the following ports need to be enabled for remote debugging. Use the procedure that is described in the section
    Configuring a Port in Windows Firewall to enable the following ports through Windows Firewall:
    Ports
    Protocol
    135
    TCP
    Required
    500, 4500
    UDP
    Required if your domain policy requires   network communication to be performed through IPSec.
    See the below article for more information:
    How to: Enable Transact-SQL Debugging
    http://msdn.microsoft.com/en-us/library/vstudio/s0fk6z6e(v=vs.100).aspx
    Thanks.
    Tracy Cai
    TechNet Community Support

Maybe you are looking for