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

Similar Messages

  • 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/

  • 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

  • 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

  • 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

  • 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

  • I Am Getting Failed Notifications When Installing SQL SERVER 2008 can any one suggest me Wt can i do

    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068643839
      Exit facility code:            1203
      Exit error code:               1
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2014-03-07 08:24:10
      End time:                      2014-03-07 09:07:13
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xC71AA851%400x73BA6908
    Machine Properties:
      Machine name:                  HOME
      Machine processor count:       1
      OS version:                    Windows XP
      OS service pack:               Service Pack 3
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         E:\Projects\Sqlserver2008\x86\setup\
      Installation edition:          ENTERPRISE
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            HOME\Administrator
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\ConfigurationFile.ini
      ENABLERANU:                    False
      ERRORREPORTING:                False
      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      MEDIASOURCE:                   E:\Projects\Sqlserver2008\
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           HOME\Administrator
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
      MSI error description:         
      Configuration status:          Failed: see details below
      Configuration error code:      0xEEBAE95A
      Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
      MSI error description:         
      Configuration status:          Failed: see details below
      Configuration error code:      0xEEBAE95A
      Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
      MSI error description:         
      Configuration status:          Failed: see details below
      Configuration error code:      0xEEBAE95A
      Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      Feature:                       Analysis Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_as_Cpu32_1.log
      MSI error description:         
      Configuration status:          Failed: see details below
      Configuration error code:      0xEEBAE95A
      Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_as_Cpu32_1.log
      MSI error description:         
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
      MSI error description:         
      Configuration status:          Failed: see details below
      Configuration error code:      0xEEBAE95A
      Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      Feature:                       Integration Services
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Books Online
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Microsoft Sync Framework
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\SystemConfigurationCheck_Report.htm

    Hello,
    Please check below link
    http://support.microsoft.com/kb/955403/en-gb
    SQL Server enterprise edition is not supported on Windows XP.You can install but its not supported by Microsoft.
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • 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

  • Add does not run with sql server 2008

    Hi all,
    My add on in the development environment does not run with SQL SERVER 2008. It ran well with SQL Server 2005 and sap b1 2207 B.
    On executing the project file system throws an error "YOU ARE NOT CONNECTED TO THE COMPANY"
    we are trying this scenario on a test machine where SAP B1 2007B with temporary license for one month and SQL server 2008
    is installed.
    Help needed.
    Thanking you
    Pradnya

    Hi Use this
    Dim i as integer
    i=oCompany.Connect()
    if i<> 0 Then
    msgbox(ocompany.GetLastErrorDescription ())
    end if
    the you will get the error description also use try catch wherever necessary
    Alternatively you can use
    Dim SboGuiApi As SAPbouiCOM.SboGuiApi
    Dim sConnectionString As String
    Set SboGuiApi = New SAPbouiCOM.SboGuiApi
    sConnectionString = Command
    SboGuiApi.Connect sConnectionString
    Set SBO_Application = SboGuiApi.GetApplication()
    Set ocompany = New SAPbobsCOM.Company 'initialate DI company object
      ocompany = SBO_Application.Company.GetDICompany
    HTH,
    Atul

  • 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]

  • "the feature you are trying to use is on a network resource that is unavailable", SQL Server 2008

    when I try to install SQL Server enterprise 2008, during the installation processing, an error information occurs, it said that 'the feature you are trying to use is on a network
    resource that is unavailable', it is missing this file "sql_engine_core_shared.msi".
    Even I locate an available file with the same version for the installation, it still alert this error information. But actually  the file exists in the directory that belong to the whole installation directory. 
    Because of this problem, I can`t complete the whole SQL Server installation. My computer OS is windows 7 Enterprise SP1, 32-bit, with .Net Framework 4.0. And I has installed Visual Stdio 2008, could this program impact the installation of SQL Server 2008?
    Any good ideas, Thanks.

    Hi,
    SQL Server 2008 Enterprise dose not support Windows
    7. You can try SQL Server Standard, or SQL
    Server Developer, or SQL Server Express. Please
    check this link:
    http://msdn.microsoft.com/en-us/library/ms143506.aspx
    [Personal Site] [Blog] [Facebook]

  • Free Ebook: Introducing Microsoft SQL Server 2008

    Hello,
    I am about to start studying for the upgrade to SQ Lserver 2008 exam 70-453. i completed my MCITP SQL server 2005 cert last year.
    I have read a few forums on the topic, and some have suggested reading the free ebook entitled "Introducing Microsoft SQL Server 2008" (not to be confused with "Introducing Microsoft SQL Server 2008 R2")
    Microsoft and other sites link the book here:-
    http://csna01.libredigital.com/?urss1q2we6
    I cannot access this link without receiving errors. (possibly firewall related)
    I have successfully found the 2008 (R2) free ebook however i need the 2008 book to read for the 70-453 exam.
    Could somebody please either send me the .pdf file (i will provide email) or send me a link that works?
    Alternatively, will the R2 book suffice for my 70-453 studies? are there SQL 2008 features that are not repeated in the writings of the R2 book?
    Thanks,
    Any other tips fro exam 70-453 are welcomed.

    The book is linked here:
    http://www.computerbooksonline.com/n2tech/index.php/free-ebook-offer-introducing-microsoft-sql-server-2008
    But if you follow the link, which points to
    http://go.microsoft.com/fwlink/?LinkId=189147, it actually downloads the R2 version instead of the original book depicted on that page. I suspect that the original book has been superseded, and the free download only applies to the latest version.
    I have taken a look at the book, and it seems to concentrate on "what's new in the R2 version", so I'm afraid that it won't be terribly useful for your goal of preparing 70-453.
    I suggest that you consider the Self-Paced Training Kit for 70-432, which should cover the knowledge that you require for the TS part of the 70-453 upgrade exam:
    http://www.microsoft.com/learning/en/us/Book.aspx?ID=12858&locale=en-us

  • Can I install SQL Server 2008 on Server 2012R2?

    <v:shapetype coordsize="21600,21600" filled="f" id="_x0000_t75" o:preferrelative="t" o:spt="75" path="m@4@5l@4@11@9@11@9@5xe" stroked="f">
     <v:stroke joinstyle="miter">
    <v:formulas>  <v:f eqn="if lineDrawn pixelLineWidth 0">
    </v:f></v:formulas></v:stroke></v:shapetype>When trying to install SQL 2008 on server 12R2 I get an error msg stating "This program has compatibility issues" (Microsoft SQL Server (2008 or 2008 R2).  Any ideas
    or thoughts.....
    Thanks
    Z<v:shapetype coordsize="21600,21600" filled="f" id="_x0000_t75" o:preferrelative="t" o:spt="75" path="m@4@5l@4@11@9@11@9@5xe" stroked="f"><v:stroke
    joinstyle="miter"><v:formulas><v:f eqn="if lineDrawn pixelLineWidth 0"><v:f eqn="sum @0 1 0"><v:f eqn="sum 0 0 @1"><v:f eqn="prod @2 1 2"><v:f eqn="prod @3 21600 pixelWidth">
      <v:f eqn="prod @3 21600 pixelHeight">
      <v:f eqn="sum @0 0 1">
      <v:f eqn="prod @6 1 2">
      <v:f eqn="prod @7 21600 pixelWidth">
      <v:f eqn="sum @8 21600 0">
      <v:f eqn="prod @7 21600 pixelHeight">
      <v:f eqn="sum @10 21600 0">
     </v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:formulas>
     <v:path gradientshapeok="t" o:connecttype="rect" o:extrusionok="f">
     <o:lock aspectratio="t" v:ext="edit">
    </o:lock></v:path></v:stroke></v:shapetype><v:shape alt="" id="Picture_x0020_2" o:spid="_x0000_i1025" style="width:304.5pt;height:237.75pt;" type="#_x0000_t75">
    <v:imagedata o:href="cid:[email protected]" src="file:///C:\Users\zshams\AppData\Local\Temp\msohtmlclip1\01\clip_image001.png">
    </v:imagedata></v:shape>

    Hello,
    Based on the following article, you must apply SP3 or SP4 for SQL Server 2008 to make it compatible with on Windows Server
    2012 R2.
    https://support.microsoft.com/kb/2681562/?wa=wsignin1.0
    You can either perform a slipstream using the following Support article.
    http://support.microsoft.com/kb/955392
    or ignore the warning and continue with SQL Server 2008 setup, and when SQL Server installation is finished apply SP3 or SP4.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Login fails when connecting to SQL Server 2008

    There were 3 databases and a report server database on sql server 2008 r2. All were renamed.  Now, when trying to connect to sql server I am getting a login failed error for default database. I'm guessing because the default db name was changed. How
    can I fix this so that I can connect to the db server\instance?
    Thanks

    Hi ,
    According to your description, I do a test in SQL Server 2008R2. If you use windows system admin account to log in the instance via Windows authentication, even if you change all use database name, you can still log in successfully. However, if you create
    a SQL Server login name to connect to instance via SQL Server authentication, when you change the default database name, it will
     occur the error which just like at follows .
    //Cannot open user default database. Login failed.
    Login failed for user '***'. (.Net SqlClient Data Provider), Error Number: 4064//
    I recommend you change the default database any existing database on your server like master via clicking on Option , or you can run following statement for username
     to replace your original database name with master.
    ALTER LOGIN [login name] WITH DEFAULT_DATABASE = master
     GO
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Linked Server - SQL Server 2008 R2

    I want to use AD groups which I have given access to SQL Server to utilitize a linked server but it does not allow this.  It gives "Anonymous Login not allowed".  I have checked the box - "Be made using the login's current security
    context".  The group is setup on both servers (Running SQL Server 2008).
    Any help is appreciated!

    Please check below link:
    http://www.sqlservercentral.com/Forums/Topic807231-1526-1.aspx
    None of the parameters are accepting windows group.
    from BOL also:
    [ @locallogin = ] 'locallogin'
    Is a login on the local server. locallogin is sysname, with a default of NULL. NULL specifies that this entry applies to all local logins that connect tormtsrvname.
    If not NULL, locallogin can be a SQL Server login or a Windows login. The Windows login must have been granted access to SQL Server either directly, or through its membership in a Windows group granted access.
    [ @rmtuser = ] 'rmtuser'
    Is the remote login used to connect to rmtsrvname when @useself is FALSE. When the remote server is an instance of SQL Server that does not use Windows Authentication, rmtuser is
    a SQL Server login. rmtuser is sysname, with a default of NULL.
    Best Wishes, Arbi; Please vote if you find this posting was helpful or Mark it as answered.

Maybe you are looking for

  • Attachments not opeing defaulting to video

    attachments not opeing defaulting to video what can i do to open my email attachments

  • My iphone 4s is not recognized by my pc after update IO5

    I updated my iphone 4s to the IO5 and since then it has been stuck on the connect to itunes screen, then when i went to connect to itunes on my PC the device is not recognized and my iphone is still stuck on the same screen.  Please help!

  • How to install cs4 on new computer without disks?

    Originally purchased CS4 in 2009 by download, not disk, and want to move it to a new computer (Windows 7). Can't find a file on Adobe.com to download, install, and activate. Adobe website says no chat or phone support for a product that old. Help, pl

  • Best way to remotely update data in iPhone game?

    I'm thinking of developing an iPhone game, and one of the things I definately want to be able to do is update values in the game remotely from a server, without having to re-submit the IPA file to apple, so I was wondering what would be the best appr

  • Contact Saving Problem

    Hi all, I just got the Blackberry Peal and I am trying to save contacts into my address book, and I enter all the information of my contacts, and then click the trackball, and then save.  It seems as if they are saving, but then upon return to the ad