Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | T-SQL.dk - - A blog on code, coffee & |
Description | A blog on code, coffee & curiosities |
Keywords | SQLServer, SQL Server, Business Intelligence, BI, SSDT, Visual Studio, Data Tools, SQLSaturday, SQLPass, #SQLFamily, Analysis Services, SQL Server, IoT, Internet of Things, Community, Jens, Vestergaard |
WebSite | t-sql.dk |
Host IP | 94.231.108.221 |
Location | Denmark |
Site | Rank |
US$335,096
Last updated: 2023-05-10 19:34:17
t-sql.dk has Semrush global rank of 31,585,920. t-sql.dk has an estimated worth of US$ 335,096, based on its estimated Ads revenue. t-sql.dk receives approximately 38,665 unique visitors each day. Its web server is located in Denmark, with IP address 94.231.108.221. According to SiteAdvisor, t-sql.dk is safe to visit. |
Purchase/Sale Value | US$335,096 |
Daily Ads Revenue | US$310 |
Monthly Ads Revenue | US$9,280 |
Yearly Ads Revenue | US$111,355 |
Daily Unique Visitors | 2,578 |
Note: All traffic and earnings values are estimates. |
Host | Type | TTL | Data |
t-sql.dk. | A | 1799 | IP: 94.231.108.221 |
t-sql.dk. | NS | 86400 | NS Record: ns4.bdm.microsoftonline.com. |
t-sql.dk. | NS | 86400 | NS Record: ns1.bdm.microsoftonline.com. |
t-sql.dk. | NS | 86400 | NS Record: ns2.bdm.microsoftonline.com. |
t-sql.dk. | NS | 86400 | NS Record: ns3.bdm.microsoftonline.com. |
t-sql.dk. | MX | 3600 | MX Record: 0 tsql-dk0c.mail.protection.outlook.com. |
t-sql.dk. | TXT | 1800 | TXT Record: MS=ms36744446 |
t-sql.dk. | TXT | 1800 | TXT Record: mscid=VWi+WyT1TG8WGazlfjMHVQS7XUJP/fkamUYikRl4s6A1Y0h6uKDbLmcZ3QS9WXKrEKOKHxD9vO8+9+aMV4Ac1A== |
t-sql.dk. | TXT | 1800 | TXT Record: v=spf1 include:spf.protection.outlook.com -all |
T-SQL.dk A blog on code, coffee & curiosities Home Delivering BI Continuously Contact Volunteering Engagements Unexplainable behavior’s with DefaultAzureCredential() Posted by Jens Vestergaard on 31/03/2023 in Programming 0 Comment Long story, short (2 days later) While implementing an Azure Function that is designed to fetch secrets from Azure KeyVault , I ran into a funny and odd issue. I am not able to explain why and what is going on, but I have tried every trick a google search can conjure, at least until page 30 in the search results. It was by coincidence I came across some of the parameters in the DefaultAzureCredentialOptions class that got me going, at least locally. The idea, as far as I have understood, is that whenever you invoke the Azure.Identity.DefaultAureCredential class, it provides a flow for attempting authentication using one of the following credentials, in listed order: EnvironmentCredential WorkloadIdentityCredential ManagedIdentityCredential |
HTTP/1.1 406 Not Acceptable Date: Wed, 03 Nov 2021 08:17:02 GMT Server: Apache Content-Type: text/html; charset=iso-8859-1 |
# # # # Domain: t-sql.dk DNS: t-sql.dk Registered: 2011-08-02 Expires: 2022-08-31 Registration period: 1 year VID: no DNSSEC: Unsigned delegation, DNSSEC disabled, no records Status: Active Nameservers Hostname: ns1.bdm.microsoftonline.com Hostname: ns2.bdm.microsoftonline.com Hostname: ns3.bdm.microsoftonline.com Hostname: ns4.bdm.microsoftonline.com |