Update SQL Server 2008 R2 CLUSTER To SP1 With TFS 2010

Hi,
I have Cluster SQL Server 2008 R2 configured to store Team Foundation Server 2010 DBs
I want to Update this Cluster to SP1 to support Sharepoint DBs
So i want to see if this update can impact my TFS DBs
Thnx
vote if you think useful

Hello,
I which way is this "Database Design" related, the Topic of this forum?
You can install the SP 1 without any harm to your TFS 2010 database; we host them on SQL Server 2012 and also this work.
But instead of the old SP1 you should go with the last SP 3 for SQL Server 2008 R2.
Olaf Helper
[ Blog] [ Xing] [ MVP]
thank you for your reply
I want to test it in a lab environment
vote if you think useful

Similar Messages

Installed SQL Server 2008 R2 Express ADV SP1 (with advanced services), but installed 2005 Express

My English - bad =)
Download SQL Server 2008 R2 Express ADV SP1 from
http://www.microsoft.com/en-us/download/details.aspx?id=26729
this
SQLEXPRADV_x64_ENU.exe
Installed, opened Management Studio,
made the request
print @@version
result:
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.1 (Build 7600: )
How to install the 2008 R2 Express ADV?? =)
I can't open the database version 661, because SQL Server 2005 - 612

Hi,
You just installed SQl server management studio I guess and when you connected the system already had SQL Server 2005 and it connected to it.
If you are sure you installed express with advanced services (2008 r2) you need to go to Start..all program..can you see SQL server 2008 r2 listed ?
Now open SSMS for 2008 r2 and instead of connecting with default instance look for other instances in drop down in server name you would fine that for SQL Server 2008 r2 connect to that
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

Question about updating SQL Server on failover cluster

Hi all,
I would like to better understand the update process of SQL Server (2008 r2) in a failover cluster environment.
In our cluster we have 4 instances of SQL running, where two of them I am able to at anytime stop the instance and update it.
The question is... Applying the latest update, will update forcibly all instances installed on that node, or do I have the ability to choose which instance I want to update?
This way, I could "test" the update process in those two SQL Instances, as described in http://support.microsoft.com/kb/958734 and after finishing I would update the remaining instances.
Please let me know.
Thanks in advance.
Nuno Silva

Hi Nuno,
It's a failover cluster issue, I moved it to SQL Server High Availability and Disaster Recovery. So that you can get better help.
Regards,
Charlie Liao
TechNet Community Support

MSDTC set up in SQL Server 2008 failover cluster

Hi Guys,
I am in the process of setting up failover cluster using SQL Server 2008 (64Bit) Enterprise on Windows Server 2008 R2 (64Bit) I have completed almost all the works but I got few questions regarding MSDTC configuration whether the MSDTC disk should
be assigned from SAN or it should be local to the disk , Separate disk for each nodes in the cluter or 1 disk to be used across all the servers for MSDTC in windows fail over cluster.
With regards, Gopinath.

Hi Gopinath,
Please review the following similar blogs to get more details about configuring MDTC and pros & cons of different options.
How to Configure Multiple Instances of Distributed Transaction Coordinator (DTC) on a Windows Server Failover Cluster 2008
http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
How to configure DTC for SQL Server in a Windows 2008 cluster
http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Backup Restore With SQL Server 2008 R2 although it succeeded with SQL Server 2008

Dears;
I have a Full backup of some DB of around 417 GB within SQL Server 2008 R2 , and when I tried to restore it , i get stuck several times with the error below :
Restore failed for Server (Microsoft.SqlServer.SmoExtended)
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider
running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical
Although I have restored
successfully other several Full+ Deferential backups for the same DB while it was in SQL Server 2008 not 2008 R2.
And so I have rounded all different possible assumptions for such common know error by Microsoft for SQL Server 2000, 2005, 2008 but
no way as next:
1-
I have attempted to restore it within 2 environments clustered and non-clustered of SQL Server 2008 R2.
2-
I have attempted to restore verify it and it was so fine .
3-
I have attempted to restore it using Continue_after_error ,no_checksum but no way.
4-
I have attempted to move Backup file to another Storage but no way.
5-
I have scheduled jobs to DBCC
Checkdb the live DB and it wasn’t any errors since long time right now
6-
I have also DBCC check all master +msdb+model+Tempdb ,and they are so fine
7-
I have also checked all I/O subsystem of SAN and Network controllers , but they are fine evidenced much more by my trial on 2 different environments.
8-
I have also checked Memory and it is so fine all the time since I have 128 GB memory and I control it also so well.
For DB Design +Structure :
It has 20 Files containing tables partitioned horizontal +Vertically
(Schema Partitioning +File Stream partitioning ) through these 20 files.
I have Data compression of the required tables only.
I have one table of more than 300 GB alone which is partitioned as mentioned above.
I have implemented Read Committed Snapshot isolation level using row versioning integrated so well with File stream technology since it is a new feature of SQL 2008 R2.
DB is in simple recovery model for garbage collection of all file stream data as a result of much Delete /update in images themselves.
So any one has any idea about such case..How to solve it…?

Hi Ashwin,
When i searched with no answers these are listed out. So i thought this is still existing. Now on wards let me check the data and time of latest reply. Thanks for guidance.
It was happening by oversight. Thanks for guidance.
Regards, Pradyothana DP. Please Mark This As Answer if it solved your issue. Please Mark This As Helpful if it helps to solve your issue. ========================================================== http://www.dbainhouse.blogspot.in/

SQL Server 2008 R2 Standard - Compatibility issues with Windows Server 2012 R2

Hello,
We used as a test a box on which we installed Windows Server 2012 R2 and SQL Server 2008 R2 Standard Edition. No Service pack was installed. It worked perfect.
Now we try to do it on another box and all of the sudden there is compatibility issue when we try to instal SQL Server. We can still install SQL Server by clicking "Continue without getting help".
Where can this come from? If it is hardware related what are the thing I should look at?
Thanks all

Hello,
Adding to Shanky suggestion, you can perform a slipstream installation of SQL Server 2008 R2 + SP3 to make SQL Server
2008 R2 compatible with the newer operating system, as explained on the following post.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
https://support.microsoft.com/en-us/kb/955392/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

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

MS SQL Server 2008 Metro Cluster with same subnet

Hi All,
I want to setup SQL 2008 Active / Passive Cluster for OCS 2007 between two Data centers, Both DCs are same location which building 1(DC1) and building 2(DC2).
I am planning to use Hyper-V cluster between two DCs and then create SQL 2008 VMs then create another windows 2008 with SQL clusters.
For the above solution, I need to use ISCSI based EMC VNX-e storages on both DCs and do the replication.
Is there any other better solution to perform? Please help me to provide more infromation.

Hi,
Additional, we recommend that your clustered servers be member servers. If they are, you need an additional server that acts as the domain controller in the domain that contains
your failover cluster.
The related KB:
Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster
http://technet.microsoft.com/en-us/library/cc731844(v=ws.10).aspx
Windows Server 2008 Multi-Site Clustering Technical Decision-Maker White Paper
http://download.microsoft.com/download/3/B/5/3B51A025-7522-4686-AA16-8AE2E536034D/WS2008%20Multi%20Site%20Clustering.doc
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Applying Service Pack on multiple instance SQL Server 2008 R2 Cluster and Standalone.

Friends,
Its my first time I am applying Service pack to both Standalone and Clustered SQL 2008 R2 servers. I have multiple instances running on both stand alone and Clustered environment. I don't know how to apply pack with multiple instances. Do I need to apply
the service pack each instance one by one or I can just run the pack to each node of cluster and each box of stand alone server? Will I get any multi instance selection option during the installation process so that I can select multiple instances at once??

When installing service pack for multiple instances in a standalone machine, you just run the installer and it lists all the instances eligible for the update. You could do it one by one or do it at the same time. Doing it at the same time saves time and
energy. If you selected multiple instances then you dont have to do anything else.
In case of cluster, if you have multiple instances then you need to be little careful.
Eg: Assume you have a 2 node cluster Node 1 and Node 2. Two instances Instance 1 active on Node 1 and Instance 2 active on Node 2. What I would do in this case is to first failover any one instance to the passive node. Assume I failed over Instance 2 to
Node 1. Now Node 1 is active node for both instance 1 and instance 2 and Node 2 is passive for both instances. At this point I run the service pack on Node 2. Once patching is done, I reboot the node and then failover the instaces one by one to Node
2. At this point both instances 1 and 2 would get upgraded and will be active in Node2. Now Node 1 is passive and so run the update there. Once the service pack is installed, reboot and then fail back Instance 1 back to Node 1. Note: I would also failover
Instance 2 to Node 1 just to confirm that failover works completely after service pack update.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

SQL Server 2008:hide any row associate with original ticket when Status is cancel

How can I say to hide any "original ticket" when the column status is Cancel?
Date Date Stamp Original Ticket Trade Number Status
01 jan 01 jan 123 130 Modify
01 jan 02 jan 123 140 Cancel
03 jan 03 jan 145 150 Modify
04 jan 04 jan 160 200 Cancel05 jan 05 janv 210 210 (empty because some trade are not modify)i wanna get this result: hide original ticket witch status are cancel Date Date Stamp Original Ticket Trade Number Status
03 jan 03 jan 145 150 Modify05 jan 05 janv 210 210 Tks a lot

Hello,
You can try to create a View to filter the recoder you don't need. Please refer to the following statement:
Create table ticket
([Date] date ,[Date Stamp] date, [orginial ticket] int, [trade number] int, [status] varchar(20))
insert into ticket values
('2014-01-01', '2014-01-01' , 123, 130,'Modify'),
('2014-01-01', '2014-01-02' , 123, 140,'Cancel'),
('2014-01-03', '2014-01-03', 145, 150, 'Modify'),
('2014-01-04', '2014-01-04',160, 200, 'Cancel'),
('2014-01-05', '2014-01-05',210, 210,NULL)
go
create view v_ticket as
with cte as(
select [orginial ticket], [Date],[Date Stamp],[trade number],status,
row_number() over (partition by [orginial ticket] order by [date stamp] desc ) as rn
from ticket )
select * from cte
where rn = 1 and (status <>'Cancel' or status is null)
go
select * from v_ticket
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Sql server 2008 standard edition cluster adding 3rd node

we have a 2 node active passive sql server 2008 r2 cluster. We plan to add a third node on temp basis to the cluster. As one old nodes will be removed. As standard edition of sql support 2 nodes, can we add third node to it ??

Hi,
There is no way to add a 3rd node without doing an EDITION UPGRADE from Standard to Enterprise. It is by design.
Microsoft SQL Server 2008 R2 Standard Edition supports up to two nodes in a failover cluster.
Check out the following MSDN article for more information:
Features Supported by the Editions of SQL Server 2008 R2
http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).ASPX
Thanks.
Tracy Cai
TechNet Community Support

SQL SERVER 2008 R2 SP2 APPLYING AFTER GEETING ERROR

HI,
I had updated 2008 R2 (RTM) VERSION to sp2.After that I was unable to open the SQL server instance and getting error messege
Like "Error: 18401
Login failed for user '<abc><login name><abc>'. Reason: Server is in script upgrade mode. Only administrator can connect at this time."
note : here i am the Administrator.

Hello,
The following post may be useful:
http://blogs.msdn.com/b/sqlserverfaq/archive/2010/03/31/unable-to-connect-to-sql-server-2008-instance-after-applying-sp1.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How to install SQL server 2008 express on Windows server 2008 R2 standard OS

Hi,
I have Windows server 2008 R2 Standard edition (64-bit) and trying to install SQL server 2008 express edition since I do not have SQL server 2008. When I install it I am unable to see Management Studio so I am trying to install management studio as well
but still I am facing issue. Please let me know whether SQL server 2008 express edition is compatible with Windows server 2008 R2 Standard. If not then pls let me know the proper steps to install it.
Regds

Hello,
Service Pack 1 for SQL Server 2008 is required to be compatible with Windows Server 2008 R2.
Please download QL Server 2008 Express with SP1 included from the following link:
http://www.microsoft.com/en-us/download/details.aspx?id=25052
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

ODBC function SQLDriverConnect() crashes with SQL Server 2008 R2

When calling the SQLDriverConnect() function from a 64-bit process and selecting a system DSN with a SQL Server Native Client 10.0 ODBC driver with SQL Server 2008 R2 SP3, then this call crashes here:
    sqlncli10.dll!SNIMemRegion::Pop() + 0x77 bytes
    sqlncli10.dll!SNIPacketAllocateEx2() + 0xa8 bytes
    sqlncli10.dll!Np::ReadSync() + 0x7e bytes
    sqlncli10.dll!Ssl::HandshakeReadToken() - 0x1b bytes
    user32.dll!InternalDialogBox() + 0x132 bytes
    user32.dll!DialogBoxIndirectParamAorW() + 0x56 bytes
    user32.dll!DialogBoxParamW() + 0x85 bytes
    sqlncli10.dll!SQLDriverConnectW() + 0x34f23 bytes
    odbc32.dll!SQLInternalDriverConnectW() + 0x17c bytes
    odbc32.dll!SQLDriverConnectW() + 0xa15b bytes
Am I calling SQLDriverConnect() correctly (see below)? Or is this a bug in the 64-bit version of the ODBC driver?
In the 32-bit version, everything works fine.
Here is a test program:
int _tmain(int argc, _TCHAR* argv[])
SQLHENV hEnv = NULL;
SQLHDBC hDbc = NULL;
SQLRETURN ret = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &hEnv);
assert(ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO);
ret = SQLSetEnvAttr(hEnv, SQL_ATTR_ODBC_VERSION, (SQLPOINTER) SQL_OV_ODBC3, 0);
if (ret != SQL_SUCCESS && ret != SQL_SUCCESS_WITH_INFO)
fprintf(stderr, "SQLSetEnvAttr failed\r\n");
return EXIT_FAILURE;
ret = SQLAllocHandle(SQL_HANDLE_DBC, hEnv, &hDbc);
assert(ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO);
SQLTCHAR szConnection[2048];
SQLSMALLINT cbChars;
ret = SQLDriverConnect(hDbc, ::GetDesktopWindow(), (SQLTCHAR*) _T(""), SQL_NTS,
szConnection, _countof(szConnection)-1, &cbChars, SQL_DRIVER_PROMPT);
if (ret != SQL_SUCCESS && ret != SQL_SUCCESS_WITH_INFO && ret != SQL_NO_DATA)
fprintf(stderr, "SQLDriverConnect failed\r\n");
return EXIT_FAILURE;
else
fprintf(stdout, "Success\r\n");
return 0;
The stdafx.h contains the following includes:
#include "targetver.h"
#include <stdio.h>
#include <tchar.h>
#include <Windows.h>
#include <sql.h>
#include <sqlext.h>
#include <assert.h>
Steps to reproduce the crash: compile program with Visual Studio 2010 as 64-bit console application; run it and select a 64-bit SQL Server DSN.
If the crash does not occur, try using the "AllocationPreference" registry entry set to 0x100000 (see https://msdn.microsoft.com/en-us/library/windows/hardware/Dn613975%28v=vs.85%29.aspx for details); don't forget to reboot Windows. This registry
helps to find 64-bit portability issues.

Hi T.holt,
Personally, I don’t believe SQL 2008 R2 with ADMT 3.2 is supported. From the guidelines of install the Active Directory Migration Tool (ADMT), ADMT v3.2 requires a preconfigured instance of SQL Server for its underlying data store. We
should use SQL Server Express and install ADMT v3.2 on a member server. ADMT installation enforces the following service pack requirements:
• SQL Server 2005 Express must be installed with Service Pack 3 (SP3) or later.
• SQL Server 2008 Express must be installed with Service Pack 1 (SP1) or later.
If you use full versions of SQL Server 2005 or SQL Server 2008. In this case, you need to install and run the ADMT console on a remote computer, and you can run multiple ADMT consoles on different remote computers. If
you use a full version of SQL Server, ADMT installation does not enforce any service pack requirements.
For more information about installing ADMT in the target domain, you can review the following article.http://technet.microsoft.com/en-us/library/cc974370(v=ws.10).aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

MS SQL Server 2008 R2 Enterprise Edition on Windows Server 2008 R2 Standard Edition

Hello Team,
Is there any issue/conflicts/limitationn to install MS SQL Server 2008 R2 Enterprise Edition on Windows Server 2008 R2 Standard Edition.
OR their is nothing to worry about it I guess their is memory limitation between both of them. Please suggest
Regards
Naveed Amir

Hi,
Here you can find the officially Hardware and Software Requirements for SQL Server 2008 R2:
http://msdn.microsoft.com/en-us/library/ms143506(v=sql.105).aspx
There should be NO problem as much as I know if the basic limitation fit you (as shanky mentioned).
I had (an clients still have) several servers with Windows Server 2008 R2 Standard & SQL
Server 2008 R2 Enterprise and Standard with no problem (today I have one old developing server with this exact installations work great for several years).
[Personal Site] [Blog] [Facebook]

Update SQL Server 2008 R2 CLUSTER To SP1 With TFS 2010

Similar Messages

Maybe you are looking for