c# – ReportView visual studio 2017

Estou desenvolvendo uma aplicação no qual estou usando os dados de uma view do meu sql dentro de um ReportView pra gerar uma nota, eu queria trazer sempre a última linha da view e não a tabela toda. Usei o SELECT TOP 1, funcionou, mas no meu formulário de vendas o usuário pode adicionar mais de um produto dentro da compra, porém o formulário de consulta trás a mesma compra em diferentes linhas, então, acredito que não seria trazer sempre a última linha, mas sim a ultima venda, alguém poderia me dar uma luz de como fazer isso?

inserir a descrição da imagem aqui

sql server 2017 – Backup Restore, CPU usage and Extended Events

I’m working on measuring the performance impact of Backups on CPU. I would like to capture all the backup operations and CPU usage. I’m running a weekly full backup, daily diff, and 15 min log backup. Are there any options in Extended Events we can use to capture CPU usage?

CREATE EVENT SESSION (Backup_Events_Trace) ON SERVER ADD EVENT sqlserver.backup_restore_progress_trace (ACTION(sqlserver.client_hostname, sqlserver.database_name))
    ,ADD EVENT sqlserver.databases_backup_restore_throughput (ACTION(sqlserver.client_hostname, sqlserver.database_name)) ADD TARGET package0.event_file (SET filename = N'L:XEBackup_Events_Trace.xel')
    WITH (STARTUP_STATE = OFF)
GO

macos – Why did my 2017 12” MB go into kernel panic (page fault)?

I was just browsing using safari, had word, notes, chrome and maybe some other light apps open in the background but nothing heavy. Suddenly my mac shutdown and restarted with the “restarted because of a problem” message. I’ve definitely put this macbook into much more stress so I’m lost. It’s a two year old 12 inch Macbook. I just booted pressing D and the report says No problems were found, code ADP0000.

The crash report is as follows; I don't know how to interpret it. I’m really worried.

   panic(cpu 0 caller 0xffffff800824aa3a): Kernel trap at 0xffffff7f8b0cfbf4, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000008, CR3: 0x0000000256d0015c, CR4: 0x00000000003626e0
RAX: 0x0000000000000002, RBX: 0xffffff91555f0038, RCX: 0x0000000040014000, RDX: 0x0000000040014000
RSP: 0xffffff914d2838f0, RBP: 0xffffff914d283940, RSI: 0xffffff8032977b08, RDI: 0xffffff803151a000
R8:  0xffffff804beafa40, R9:  0x0000000000000080, R10: 0xffffff914ae4d030, R11: 0x0000000000000000
R12: 0x0000000000000004, R13: 0x0000000000000000, R14: 0xffffff8032976e50, R15: 0xffffff8032976800
RFL: 0x0000000000010206, RIP: 0xffffff7f8b0cfbf4, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0x0000000000000008, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 0

Backtrace (CPU 0), Frame : Return Address
0xffffff914d283350 : 0xffffff800811f5cd 
0xffffff914d2833a0 : 0xffffff800

8258b05 
0xffffff914d2833e0 : 0xffffff800824a68e 
0xffffff914d283430 : 0xffffff80080c5a40 
0xffffff914d283450 : 0xffffff800811ec97 
0xffffff914d283550 : 0xffffff800811f087 
0xffffff914d2835a0 : 0xffffff80088c27cc 
0xffffff914d283610 : 0xffffff800824aa3a 
0xffffff914d283790 : 0xffffff800824a738 
0xffffff914d2837e0 : 0xffffff80080c5a40 
0xffffff914d283800 : 0xffffff7f8b0cfbf4 
0xffffff914d283940 : 0xffffff7f8b0cef3f 
0xffffff914d2839a0 : 0xffffff7f8afe251e 
0xffffff914d2839e0 : 0xffffff7f8afe2a4f 
0xffffff914d283a10 : 0xffffff7f8b0cf3de 
0xffffff914d283a40 : 0xffffff7f8afe000b 
0xffffff914d283ac0 : 0xffffff800885695e 
0xffffff914d283b10 : 0xffffff8008854be7 
0xffffff914d283b60 : 0xffffff800885dcb3 
0xffffff914d283ca0 : 0xffffff80082082b2 
0xffffff914d283db0 : 0xffffff8008125328 
0xffffff914d283e10 : 0xffffff80080fbcc5 
0xffffff914d283e70 : 0xffffff8008112aa2 
0xffffff914d283f00 : 0xffffff8008230d05 
0xffffff914d283fa0 : 0xffffff80080c6226 
  Kernel Extensions in backtrace:
     com.apple.iokit.IOAcceleratorFamily2(438.5.4)(D695D9DA-7C20-35D6-910F-E7A332A0F515)@0xffffff7f8afd9000->0xffffff7f8b09dfff
        dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)(E35D090D-DB9E-3DD0-9723-651FA730AA13)@0xffffff7f891e2000
        dependency: com.apple.iokit.IOPCIFamily(2.9)(BE052F4D-9B80-3FCD-B36D-BACB7DEE0DF2)@0xffffff7f88b31000
        dependency: com.apple.iokit.IOSurface(269.11)(F1E7389D-2807-3C5D-8A7F-5422542E867F)@0xffffff7f8961f000
        dependency: com.apple.iokit.IOGraphicsFamily(576.1)(B1C0006F-E1F5-37D9-9548-5F918E92B422)@0xffffff7f89535000
        dependency: com.apple.iokit.IOReportFamily(47)(1FB49168-0280-3F04-A99A-F830C915E994)@0xffffff7f88f11000
     com.apple.driver.AppleIntelKBLGraphics(14.0.6)(E09E2681-5119-37A7-9975-B87BC4E1AA8F)@0xffffff7f8b0b2000->0xffffff7f8b1a7fff
        dependency: com.apple.iokit.IOPCIFamily(2.9)(BE052F4D-9B80-3FCD-B36D-BACB7DEE0DF2)@0xffffff7f88b31000
        dependency: com.apple.iokit.IOSurface(269.11)(F1E7389D-2807-3C5D-8A7F-5422542E867F)@0xffffff7f8961f000
        dependency: com.apple.iokit.IOGraphicsFamily(576.1)(B1C0006F-E1F5-37D9-9548-5F918E92B422)@0xffffff7f89535000
        dependency: com.apple.iokit.IOAcceleratorFamily2(438.5.4)(D695D9DA-7C20-35D6-910F-E7A332A0F515)@0xffffff7f8afd9000

BSD process name corresponding to current thread: com.apple.photos

Mac OS version:
19F101

Kernel version:
Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64
Kernel UUID: 54F1A78D-6F41-32BD-BFED-4381F9F6E2EF
Kernel slide:     0x0000000007e00000
Kernel text base: 0xffffff8008000000
__HIB  text base: 0xffffff8007f00000
System model name: MacBook10,1 (Mac-EE2EBD4B90B839A8)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 25359580732118
last loaded kext at 22180958337014: >!AXsanScheme   3 (addr 0xffffff7f8bd8a000, size 32768)
last unloaded kext at 433015797039: >usb.!UHostPacketFilter 1.0 (addr 0xffffff7f8988e000, size 24576)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp  6.1.4
org.virtualbox.kext.VBoxNetFlt  6.1.4
org.virtualbox.kext.VBoxUSB 6.1.4
org.virtualbox.kext.VBoxDrv 6.1.4
@fileutil   20.036.15
>AudioAUUC  1.70
>AGPM   111.4.4
>!APlatformEnabler  2.7.0d0
>X86PlatformShim    1.0.0
@filesystems.autofs 3.0
>!AHDA  283.15
>!AUpstreamUserClient   3.6.8
>!AGraphicsDevicePolicy 5.2.4
@AGDCPluginDisplayMetrics   5.2.4
>!AHV   1
|IOUserEthernet 1.0.1
|IO!BSerialManager  7.0.5f6
>!ABacklight    180.3
>pmtelemetry    1
>!A!IPCHPMC 2.0.1
>!ASMCLMU   212
>!AMCCSControl  1.14
@Dont_Steal_Mac_OS_X    7.0.0
>!A!IKBLGraphics    14.0.6
>eficheck   1
>!A!ISlowAdaptiveClocking   4.0.0
>!ACameraInterface  7.6.0
>!A!IKBLGraphicsFramebuffer 14.0.6
@filesystems.apfs   1412.120.2
>!AVirtIO   1.0
@filesystems.hfs.kext   522.100.5
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
@BootCache  40
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
>!ATopCaseHIDEventDriver    3430.1
>AirPort.BrcmNIC    1400.1.1
@private.KextAudit  1.0
>!ASmartBatteryManager  161.0.0
>!AACPIButtons  6.1
>!ARTC  2.0
>!ASMBIOS   2.1
>!AACPIEC   6.1
>!AAPIC 1.7
$!AImage4   1
@nke.applicationfirewall    303
$TMSafetyNet    8
@!ASystemPolicy 2.0.0
|EndpointSecurity   1
>!AXsanScheme   3
|IOUSBUserClient    900.4.2
@kext.triggers  1.0
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
>!AGraphicsControl  5.2.4
|IOAVB!F    850.1
>!ASSE  1.0
>!ABacklightExpert  1.1.0
>!AHDA!C    283.15
|IOHDA!F    283.15
>!ASMBus!C  1.0.18d1
|IO!BHost!CUARTTransport    7.0.5f6
|IO!BHost!CTransport    7.0.5f6
@!AGPUWrangler  5.2.4
|IONDRVSupport  576.1
|IOSlowAdaptiveClocking!F   1.0.0
>X86PlatformPlugin  1.0.0
>IOPlatformPlugin!F 6.0.0d8
@!AGraphicsDeviceControl    5.2.4
|IOAccelerator!F2   438.5.4
|IOGraphics!F   576.1
>!A!ILpssUARTv1 3.0.60
>!A!ILpssUARTCommon 3.0.60
>!AOnboardSerial    1.0
@plugin.IOgPTPPlugin    840.3
|IOEthernetAVB!C    1.1.0
|IOAudio!F  300.2
@vecLib.kext    1.2.0
|IOSerial!F 11
|IOSurface  269.11
@filesystems.hfs.encodings.kext 1
>!AActuatorDriver   3440.1
>!AHIDKeyboard  209
>!AHS!BDriver   3430.1
>IO!BHIDDriver  7.0.5f6
|IO!B!F 7.0.5f6
|IO!BPacketLogger   7.0.5f6
>!AMultitouchDriver 3440.1
>!AInputDeviceSupport   3440.8
>!AHSSPIHIDDriver   59
>!AHSSPISupport 59
|IO80211!F  1200.12.2b1
>mDNSOffloadUserClient  1.0.1b8
>corecapture    1.0.4
|IOSkywalk!F    1
>!A!ILpssSpi!C  3.0.60
|IONVMe!F   2.1.0
>!AHPM  3.4.4
|IOThunderbolt!F    7.6.1
>!A!ILpssI2C!C  3.0.60
>!A!ILpssDmac   3.0.60
>!A!ILpssGspi   3.0.60
>!A!ILpssI2C    3.0.60
>usb.!UXHCIPCI  1.2
>usb.!UXHCI 1.2
|IOUSB!F    900.4.2
>!AEFINVRAM 2.1
>!AEFIRuntime   2.1
|IOSMBus!F  1.1
|IOHID!F    2.0.0
$quarantine 4
$sandbox    300.0
@kext.!AMatch   1.0.0d1
>DiskImages 493.0.0
>!AFDEKeyStore  28.30
>!AEffaceable!S 1.0
>!AKeyStore 2
>!UTDM  489.120.1
|IOSCSIBlockCommandsDevice  422.120.3
>!ACredentialManager    1.0
>KernelRelayHost    1
>!ASEPManager   1.0.1
>IOSlaveProcessor   1
|IOUSBMass!SDriver  157.121.1
|IOSCSIArchitectureModel!F  422.120.3
|IO!S!F 2.1
|IOUSBHost!F    1.2
>!UHostMergeProperties  1.2
>usb.!UCommon   1.0
>!ABusPower!C   1.0
|CoreAnalytics!F    1
>!AMobileFileIntegrity  1.0.5
@kext.CoreTrust 1
|IOTimeSync!F   840.3
|IONetworking!F 3.4
|IOReport!F 47
>!AACPIPlatform 6.1
>!ASMC  3.1.9
>watchdog   1
|IOPCI!F    2.9
|IOACPI!F   1.4
@kec.pthread    1
@kec.corecrypto 1.0
@kec.Libm   1

bootcamp – MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports) running Mojave (10.14.3 (18D42)) is does not recognize external boot drive

I just got a new Macbook Pro, I was previously using an MBP (13-inch, Mid 2012) running Mojave. I have a 1TB SSD that has a partition with a Windows 10 installation (I followed this tutorial: https://blog.macsales.com/40947-tech-tip-how-to-use-boot-camp-on-an-external-drive/) and another MacOS Journaled partition that I use for general file storage. This setup has worked for me on my old MBP (I can hold option to boot into windows). However, the Startup Manager does not recognize my external drive and only display my internal drive. Using System Preferences startup disk leads to this error: The bless tool was unable to set the current boot disk. I’ve tried resetting NVRAM as well.

Here is some disk information that may help:

$ diskutil list

...

/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *1.0 TB     disk2
   1:               Windows_NTFS BOOTCAMP                353.1 GB   disk2s1
   2:                  Apple_HFS VECTOTECHS              671.1 GB   disk2s2

$ sudo fdisk /dev/disk2
Disk: /dev/disk2    geometry: 124519/255/63 (2000409264 sectors)
Signature: 0xAA55
         Starting       Ending
 #: id  cyl  hd sec -  cyl  hd sec (     start -       size)
------------------------------------------------------------------------
*1: 07 1023 254  63 - 1023 254  63 (         2 -  689689262) HPFS/QNX/AUX
 2: AF 1023 254  63 - 1023 254  63 ( 689690624 - 1310715904) HFS+
 3: 00    0   0   0 -    0   0   0 (         0 -          0) unused
 4: 00    0   0   0 -    0   0   0 (         0 -          0) unused

My guess is that I need an EFI partition for the newer mac to recognize my drive. Would this entail restarting the entire installation process? Any information would be greatly appreciated 🙂

Error while upgrading SQL server 2012 to SQL 2017 : Failed to create a new folder ‘X:\xxxx’. The specified path is invalid

Failed to create a new folder ‘X:MSSQLDATAMSSQL11.MSSQLSERVERMSSQLLOG’. The specified path is invalid (for example, it is on an unmapped drive).

I checked there is no X drive present in the server. I verified that all the default files for data and log points to the drives which are available in the server.

Not sure , how do I resolve this as i don’t see X drive mentioned in any of the properties.

I have checked in Facets and database properties to verify the path.

SQL Server 2017 Backup strategy

RTO is 8 hours

RPO is 24 hours

Retention Period: 5 days

Based on above values I have plan to configure below backup stratgey for Production. Please suggest if there is any changes required in below backup policy.

Full Backup – Daily

Log Backup – every 30 minutes (this is just to prevent log grwoth/low disk problems during index rebuild job)

SQL DB size is approx 500-650 GB.

HA/DR solution for above DB: Configured Distributed Always-ON AG from DC1 to DC2 on top of WSFC (DC1- two DB serevrs and DC2-two DB servers)

temperature – 2017 MBP has started to degrade in performance – dreaded kernel_task

All –
My normally stable mbp 2017 has started slowing down with kernel_thread dominating the CPU in recent weeks. This condition persists across reboots. My primary concern is that the machine is overheating (please see troubleshooting to date).

Any ideas? The wildest idea I have at the moment is that Firefox had some sort of deep JS hack; Zoom has rolled out crappier code in 5.X series (nothing to do with heat); and the thermal throttling is normal.

Are there any alternative troubleshooting steps I can take short of returning my mac for service? I don’t have a backup and really can’t be without a computer for 5+ days for work. I’ve also thought about buying a new machine but Apple pricing is just spectacular.

Things I’ve tried:

  • Restarting the machine
  • Restarting / running diags (nothing found)
  • Re-installing key apps
  • Air-blowing out the exhaust ports

Symptoms:

  • Until I re-installed Firefox (user profiles preserved) – connecting MBP to the internet would result in immediate spike in kernel_threads
  • Zoom meetings also trigger the

Data I’ve been using:

  • iStats Menu for detailed graphs
  • pmset -g thermal

Observations:

  • No observable memory pressure
  • Temperatures on thunderbolt port, cpu etc seem nominal but pmset is showing thermal throttling

This has triggered a conversation about refreshing to a MBP 2016 or macmini, but its an awfully expensive “fix” if there are other ways to root cause the behaviour.

SSRS 2017 add datasource “Something went wrong”

when trying to add, view or change data source(s) in SSRS 2017 I get popup saying “Something went wrong, please try later”.

Setup os SSRS is as follows:

three SSRS instances behind KEMP load balancer. Communication from clients to KEMP is done over SSL (port 443) and from kemp to SSRS instances over HTTP (port 80). rsreportserver.config file has this tags on all three SSRS servers, where SSRS.domain.com points to the KEMP virtual IP (for client access).

SSRS.domain.com
https://SSRS.domain.com/reportserver

When I try to add, view or change data source(s) I get this error in RSPortal.log

ERROR: OData exception occurred: System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.2.17.11:443
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
— End of inner exception stack trace —

10.2.17.11 is the IP of the one of SSRS instances buth what baffles me is why is connection trying to be made using port 443 (TLS) when KEMP is configured to communicate with SSRS instances over port 80.

SSRS instances don’t have port 443 configured, only port 80.

Everything else works fine, only datasources are the problem.

SSRS version in question is 14.0.600.1109, native mode.

Any help would be appreciated.

SQL Server 2017 SSIS Package Export failure

Upgrading from SQL Server 2008 R2 to SQL Server 2017. Using SQL Server Business Intelligence Development Studio. I am able to publish to one SQL Server 2017, but fail to publish to another SQL Server 2017 with error “An OLE DB error 0x80004005 (Client unable to establish connection) ocurred while enumerating packages. A SQL statement was issued and failed.” I have compared server settings and permissions without success. I must be missing something…

Link Displays Between Two iMacs (Late-2015 Retina running Sierra and 2017 running Mojave) Using Thunderbolt-to-Thunderbolt

I’m hoping someone can help me (and that this is possible, considering I just spent an arm and a leg to facilitate this setup).

I have a late-2015 iMac (27″ Retina 5K display, running Sierra) and a 2017 iMac (21.5″, running Mojave) and am hoping that I can connect them for dual display. I have them connected via Thunderbolt-to-Thunderbolt with the TB2 to TB3 adapter. For whatever reason, I’m not able to use Target Display mode on my 2015 iMac, and I’m suspecting it’s because the model doesn’t support it. ETA: The other mac doesn’t show up in either System Preferences > Displays menu

I’m hoping someone can offer advice as to what I’m doing wrong or a possible workaround for this issue, as I have no use for both iMacs separately but would greatly benefit from using one as an additional display – even if the answer is simply that I can’t do it, it will at least allow me to stop spinning my wheels and give up on this pipe dream.

Any suggestions are welcome!