Wednesday, April 16, 2025

美国百年零息债换债传闻:相当于倒债、非常危险

 市场传闻美国总统川普可能迫使一些外国债权人,将手中持有的美债转换为超长期债券,以减轻美国的债务负担。对此,中央银行总裁杨金龙15日说,此举相当于倒债,非常的危险,美国恐会因此发生金融上的混乱及危机。


外界忧虑,美国是否可能逼迫外国债权人将所持美国国债换成100年期零息债券,倘若发生,要如何面对?杨金龙说 ,这个议题好像已谈论了很久,不过背后必须了解一件事,如果做这样的转换,相当于“美债的倒债”。

杨金龙直言,如果美债都倒债的话,当然就是非常的危险,因为美国公债市场是各个金融商品定价的基础,之前他曾大胆地说,美国恐怕会因此发生金融上的混乱、金融上的危机。

杨金龙表示,虽然这个议题在市场谈论很久,不过据自己了解,国外金融市场好像没有像台湾一样谈论的这麽热烈。

杨金龙续指,台湾握有外汇存底中,美债大约佔8成以上,事实上台湾握有的美债数量是佔全球第十一位,约为2,900多亿美元,这当中也包括民间的部分。政府对于债券都随时在调整、观察市场的变化。

TMDX stock | Short interest

 



Tuesday, April 15, 2025

Business Central's underlying database in Azure is not a NoSQL database.

 Business Central's underlying database in Azure is not a NoSQL database. It is a relational database using the SQL Server database engine. While Business Central utilizes various cloud services like Azure SQL Database, these services still provide a relational database infrastructure. 

Here's why: 
  • SQL Server Engine:
    Business Central relies on the SQL Server database engine, which is a foundation for relational databases.
  • Relational Data Model:
    Relational databases, like SQL Server, store data in tables with rows and columns, which is the standard approach for structured data.
  • Azure SQL Database:
    Azure SQL Database is a managed SQL Server database service in Azure, offering a fully managed relational database platform for various use cases.
While Azure offers NoSQL database options like Azure Cosmos DB, Business Central is not designed to use them as its primary database. 

急性心肌梗死...

患者三十多岁,姓刘,我们就叫他小刘吧。

小刘因为近期总是腰痛去医院就诊,医生顺着小刘的腰部检查一圈,寻找压痛点,以排除是否是坐骨神经痛或者腰椎间盘突出,结果发现病因不是这些。

由于临床上不少患者的腰痛和泌尿系统结石有关,为了排除这种可能性,医生建议小刘去完善检查。小刘虽然不情愿,但还是照做了,结果显示小刘并没有结石。

此时医生发现小刘在说话时会经常揉自己的胸口和胃部,再加上其嘴唇发白,难不成是心梗?为了证实这个猜想,医生建议小刘去做个心电图看看,谁知这一建议却换来对方的破口大骂,他觉得医生这是在诅咒自己...

在医生的不放心和一再挽留下,小刘还是骂骂咧咧回家了,心电图等检查也没完善,因为直到此刻,小刘还是觉得自己的腰痛只需要贴点止痛膏药就行了,根本没那么严重。

谁知第二天一早,刚吃完早饭准备出门上班,小刘突然感到呼吸急促、心慌,被家人紧急送往医院。然而等到医院时,他已经失去了意识,虽然医护人员全力抢救,但他最终还是去世了,死因为急性心肌梗死...

看到这里,可能很多人都觉得不可思议,甚至有点天方夜谭。明明只是腰痛,怎么和心梗联系上的?甚至最后把命都丢了?

殊不知,这个世界上每时每刻都有许许多多悲催且让人意想不到的病例发生着。世界很大,有些东西我们没见过,但这并不代表它就不会发生。 

后背疼,可能是这些疾病发出的信号

后背疼,主要分为生理性和病理性两种,生理性很好理解,比如我们平时长时间使用手机或电脑、长时间保持同一个姿势、长时间穿高跟鞋或人字拖以及文胸佩戴不合身等等。

生理性原因我们一般只要将习惯改变,疼痛即可得到缓解消失。而病理性原因就比较复杂了,可能是一些疾病乃至癌症引起的后背疼。

①左背疼痛

左背疼痛首先要考虑的是心绞痛或者心梗,因为人的心脏一般在左边。如果胸骨后压榨性疼痛,伴随着胸闷憋气、心慌气短和大汗淋漓等症状,可能是心绞痛发出的信号。当然,心绞痛有时候还会放射到左肩部和左背部等,很容易让人忽视。

如果疼痛十分剧烈,且持续存在,并且有濒死感,那极有可能是心梗。

另外左背疼痛还可能是主动脉夹层,这种一般有剧烈刀割样、撕裂样疼痛。加上主动脉贴近背部,所以有时也会有左背疼痛的症状,需要注意的是主动脉夹层致死率很高,一旦破裂基本上连抢救都来不及,所以一定要重视。

②右背疼痛

右背疼痛很大可能是胆囊疾病引起的,比如胆囊炎的典型症状就是右上腹部疼痛,而有些人的疼痛会向右肩背部放射,进而出现后背疼。

这里要提醒的是,胆囊疾病导致的后背疼痛,往往和进食有很大关系,尤其是在吃了一些油腻食物后更加容易发生。

③腰部两侧

由于肾脏和输尿管感觉神经纤维经内脏神经传递到腰神经和胸神经,因此当输尿管与肾脏出现问题后,下背部便会有明显疼痛。

特别是急性肾炎导致的疼痛,常表现为腰部酸痛与钝痛,疼痛可能会沿着输尿管延伸到会阴部。另外这个部位疼痛,还要考虑肾结石、肾积水以及肾结核等可能。

④背中心疼

如果患有十二指肠溃疡,那么就有可能刺激到腹腔神经丛,并引起疼痛,这种痛感会放射到背部,尤其是背中心的位置。

当然,还要警惕胰腺炎的可能,因为95%的胰腺炎患者会出现持续性腹痛,而其中超半数以上可能出现后背疼,疼痛在仰卧时加重,弯腰屈膝时有所减轻,一般还会伴随着全腹胀满、恶心呕吐和持续性发热等症状。

胰腺炎一定要重视,一旦发展成重症,可能会引起全身器官炎症反应,致死率更是高达30-50%。

后背疼,还要警惕这三种癌症

①肺癌

早期肺癌一般不会导致背疼,但随着病灶发展,肿瘤可能侵犯到胸膜,肿瘤骨转移到胸椎等,就会出现背疼。

这里的背疼常表现为隐痛或钝痛,可能会持续性疼痛,就算休息后也不会有明显缓解,且用药后效果依然不明显。如果肿瘤进一步增大并且压迫到周围组织脏器时,便会出现后背压迫性疼痛。

②肝癌

肝癌引起的疼痛常出现在肝区,而随着病情发展,癌细胞可能会侵犯到肝脏周围器官或组织,导致右后背疼痛,常表现为放射性或牵涉性,多数时候会有其他症状,比如黄疸、浑身乏力、食欲不振以及体重不明原因骤降等。

③胰腺癌

因为胰腺处于腹腔身处,周围有很多神经与血管,因此在肿瘤生长扩散时,便会刺激压迫到周围神经或血管,侵犯到后背的相关神经,并导致背部疼痛。

其实胰腺癌最常见的症状是腹部不适或者腹痛,但随着病情加重便会演变成中上腹疼痛或者背部持续性剧痛,疼痛呈持续性、进行性加重,尤其是在夜间或者仰卧时会更为明显,而当俯卧或者弯曲身体时,疼痛又会得到缓解甚至是消失。

Scotia RRSP | ETFs | April 15 2025

 


Azure SQL | Linkedin Learning | Jeremy Villeneuve

 

Course details

  • 1h 25m
  • Beginner
  • Released: 5/12/2023
(74)

Azure SQL allows you to go live within minutes, using a cloud-hosted database. It provides a great way to begin your journey of learning SQL for data processing and analytics. In this course, Jeremy Villeneuve guides you through the process of getting started. Jeremy goes over what SQL is, as well as common statements and differences in SQL engines. He presents an Azure SQL quick start guide, then shows you how to create new records using the Azure Query Editor. Jeremy explains how to read data in Azure SQL database records, as well as how to update existing data. Each chapter in this course includes a challenge and sample solution, so you can test your understanding of what you learn.

Upgrading from Dynamics NAV to Dynamics 365 Business Central

 Upgrading from Dynamics NAV to Dynamics 365 Business Central requires a phased approach and involves several steps. While it's generally possible to upgrade from NAV to Business Central, the specific upgrade path depends on your current NAV version and whether your application is customized or not. You may need to upgrade through intermediate versions before reaching the target Business Central release. 

Here's a more detailed breakdown:
1. Prerequisites and Considerations:
  • Check Compatibility:
    Ensure your current NAV version is compatible with the target Business Central release. Refer to the Dynamics 365 Business Central Upgrade Compatibility Matrix for specific information. 
  • Customizations:
    If your NAV solution has customizations, you'll need to convert them to extensions for Business Central, which can involve significant work. 
  • Data Encryption:
    If you're using data encryption on your NAV deployment, you'll need to disable it before upgrading and re-enable it after the upgrade. 
  • .NET Framework:
    Consider the impact of .NET framework changes. Business Central Server runs on .NET 6.0, which might require updating references in your code. 
  • Plan for a full upgrade:
    Learn Microsoft recommends a full upgrade (platform and application) instead of just a technical upgrade to version 22 or later to save time and benefit from the latest features. 
2. Upgrade Process:
  • Install the new version:
    Download and install the new Business Central release on a test server, keeping your existing NAV installation active. 
  • Code/Object Upgrade:
    Use the provided migration tools to upgrade your code and objects to the new Business Central version. 
  • Reproduce Customizations:
    If you have customizations, convert them to extensions and add-ons. 
  • Validation and Testing:
    Thoroughly test the upgraded solution to ensure it functions correctly and meets your business requirements. 
  • User Acceptance Testing:
    Involve end users in the testing process to ensure the upgraded system meets their needs. 
  • Data Upgrade:
    Perform data upgrades to ensure your data is compatible with the new Business Central version. 
3. Important Considerations:
  • Intermediate Upgrades:
    You might need to upgrade through intermediate versions to reach your target Business Central release. 
  • Application Compatibility:
    Ensure your application is compatible with the Business Central release you are upgrading to. Learn Microsoft provides guidance on upgrading customized C/AL applications to the latest version. 
  • Documentation:
    Refer to the Business Central Upgrade Compatibility Matrix for specific upgrade paths and prerequisites. 
  • Support:
    Learn Microsoft provides details on upgrading Microsoft System and Base Applications, including extensions. 
  • Control Add-ins:
    If your solution uses control add-ins, you'll need to upgrade them to the latest version. 

Catapult | Navision upgrade | Business central

 As a certified Microsoft Partner, Catapult supports customers with diverse business models ranging from multi-company finance to supply chain automation, non-profit finance and member service, to retail and commercial services.

Marjorie Taylor Greene Republican / House / Georgia

Here is the link.