{"id":4740,"date":"2026-10-06T12:35:16","date_gmt":"2026-10-06T09:35:16","guid":{"rendered":"https:\/\/www.ozgurguler.net\/blog\/?p=4740"},"modified":"2026-10-07T13:11:43","modified_gmt":"2026-10-07T10:11:43","slug":"2022-ve-uzeri-kurmadan-once-mutlaka-okuyun","status":"publish","type":"post","link":"https:\/\/www.ozgurguler.net\/blog\/2022-ve-uzeri-kurmadan-once-mutlaka-okuyun\/","title":{"rendered":"SQL Server 2022 ve \u00dczeri: Kurmadan \u00d6nce Mutlaka Okuyun"},"content":{"rendered":"

Ticari Yaz\u0131l\u0131mlarda SQL Server 2022 ve \u00dczeri<\/span><\/h1>\n

* Kurmadan \u00d6nce Mutlaka Okuyun<\/span><\/h1>\n

Kapsam:<\/span><\/strong> Logo, Mikro ve benzeri yerel ticari ERP\/\u00f6n muhasebe yaz\u0131l\u0131mlar\u0131<\/span><\/p>\n

\n

Neden Bu Makale Var?<\/span><\/h2>\n

Bu makale, s\u00fcrekli tekrarlayan ve ayn\u0131 hatalara yol a\u00e7an SQL Server s\u00fcr\u00fcm uyumluluk sorunlar\u0131na kal\u0131c\u0131 bir \u00e7\u00f6z\u00fcm getirmek amac\u0131yla haz\u0131rlanm\u0131\u015ft\u0131r.<\/span><\/p>\n

Sahada kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z tablo nettir: SQL Server 2022 veya 2025 kurulumu yap\u0131lan yerlerde, k\u0131sa s\u00fcre i\u00e7inde ticari yaz\u0131l\u0131mlarda hatalar al\u0131nmaya ba\u015flanmakta, veri b\u00fct\u00fcnl\u00fc\u011f\u00fc sorunlar\u0131 ya\u015fanmakta ve \u00e7\u00f6z\u00fcm i\u00e7in tekrar bize d\u00f6n\u00fclmektedir.<\/span><\/p>\n

\u00d6nemli:<\/span><\/strong> Bu makale <\/span>“SQL Server 2022\/2025 kurmay\u0131n”<\/span><\/em> demiyor. <\/span>“Kurmadan \u00f6nce a\u015fa\u011f\u0131daki ko\u015fullar\u0131 sa\u011flay\u0131n; sa\u011flayam\u0131yorsan\u0131z kurmay\u0131n”<\/span><\/strong> diyor. <\/span><\/p>\n

Karar sizindir, ancak sorumluluk da sizdedir.<\/span><\/p>\n

\n

Riskli 5 Kritik Nokta<\/span><\/h2>\n

1. Collation \u2014 1254 (T\u00fcrk\u00e7e) Kod Sayfas\u0131 \u015eartt\u0131r<\/span><\/h3>\n

Yerel ticari yaz\u0131l\u0131mlar\u0131n veritaban\u0131 yap\u0131s\u0131, <\/span>1254 (T\u00fcrk\u00e7e) kod sayfas\u0131n\u0131<\/span><\/strong> kullan\u0131r ve \u00e7, \u011f, \u0131, \u0130, \u00f6, \u015f, \u00fc gibi T\u00fcrk\u00e7e karakterlerin do\u011fru s\u0131ralanmas\u0131n\u0131 ve kar\u015f\u0131la\u015ft\u0131r\u0131lmas\u0131n\u0131 sa\u011flar.<\/span><\/p>\n

SQL Server kurulumunda varsay\u0131lan olarak gelen <\/span>Latin1_General_CI_AS<\/span><\/strong> ise <\/span>1252 kod sayfas\u0131n\u0131<\/span><\/strong> kullan\u0131r. <\/span><\/p>\n

Bu harmanlama ile <\/span>varchar<\/code> alanlarda T\u00fcrk\u00e7e karakterler bozulur; raporlarda ve sorgularda hatal\u0131 sonu\u00e7lar al\u0131rs\u0131n\u0131z.<\/span><\/p>\n

Do\u011fru se\u00e7im:<\/span><\/strong> Kurulumda <\/span>Turkish_CI_AS<\/span><\/strong> veya <\/span>Turkish_100_CI_AS<\/span><\/strong> (gerekirse <\/span>_SC<\/code> sonekli) se\u00e7ilmelidir.<\/span><\/p>\n

Kontrol komutu:<\/span><\/strong><\/p>\n

\n
\n
\n
\n
\n
— Sunucu harmanlamas\u0131<\/span><\/div>\n
SELECT<\/span> SERVERPROPERTY<\/span>(<\/span>‘Collation’<\/span>)<\/span> AS<\/span> SunucuHarmanlamasi<\/span>;<\/span><\/div>\n<\/blockquote>\n<\/div>\n<\/div>\n<\/div>\n
\n
-- Logo veritabanlar\u0131<\/span>\r\nSELECT<\/span> name,<\/span> collation_name,<\/span> compatibility_level\r\nFROM<\/span> sys.<\/span>databases<\/span>\r\nWHERE<\/span> name LIKE<\/span> '%Logo%'<\/span>\r\nORDER<\/span> BY<\/span> name;<\/span>\r\n\r\n-- Mikro veritabanlar\u0131<\/span>\r\nSELECT<\/span> name,<\/span> collation_name,<\/span> compatibility_level\r\nFROM<\/span> sys.<\/span>databases<\/span>\r\nWHERE<\/span> name LIKE<\/span> '%Mikro%'<\/span>\r\nORDER<\/span> BY<\/span> name;<\/span><\/pre>\n<\/blockquote>\n<\/div>\n
2. UTF-8 Beta Ayar\u0131 \u2014 SQL Server Kurulumunda Kapal\u0131 Olmal\u0131d\u0131r<\/span><\/h3>\n
Windows’ta <\/span>“Beta: D\u00fcnya \u00e7ap\u0131nda Unicode UTF-8 deste\u011fi i\u00e7in kullan”<\/span><\/strong> se\u00e7ene\u011fi, legacy kod sayfas\u0131 (1254) bekleyen ticari yaz\u0131l\u0131mlarda <\/span>encoding \u00e7ak\u0131\u015fmas\u0131na<\/span><\/strong> yol a\u00e7ar. <\/span><\/p>\n
Sistem UTF-8’e zorland\u0131\u011f\u0131nda, uygulama ile sunucu aras\u0131nda kodlama uyumsuzlu\u011fu olu\u015fur ve karakter bozulmalar\u0131, ba\u011flant\u0131 hatalar\u0131 g\u00f6r\u00fcl\u00fcr.<\/span><\/p>\n
Bu ayar <\/span>kapal\u0131 tutulmal\u0131d\u0131r.<\/span><\/strong> Ayr\u0131ca SQL Server kurulumunda <\/span>UTF-8 collation<\/span><\/strong> (\u00f6rne\u011fin <\/span>Turkish_100_CI_AS_SC_UTF8<\/code>) <\/span>se\u00e7ilmemelidir.<\/span><\/strong><\/p>\n
UTF-8 collation deste\u011fi SQL Server 2019 (15.x) ve sonraki s\u00fcr\u00fcmlerde gelmi\u015ftir; ancak yerel ticari yaz\u0131l\u0131mlar bu yap\u0131y\u0131 hen\u00fcz kullanmamaktad\u0131r.<\/span><\/strong><\/p>\n
Kontrol:<\/span><\/strong> Windows B\u00f6lge Ayarlar\u0131 \u2192 Y\u00f6netimsel \u2192 Sistem yerel ayar\u0131n\u0131 de\u011fi\u015ftir \u2192 Beta UTF-8 se\u00e7ene\u011fi <\/span>i\u015faretsiz<\/span><\/strong> olmal\u0131d\u0131r.<\/span><\/p>\n
3. Compatibility Level \u2014 Yaz\u0131l\u0131m\u0131n Beyan Etti\u011fi Seviyede Tutulmal\u0131d\u0131r<\/span><\/h3>\n
SQL Server 2022, <\/span>compatibility level 160<\/span><\/strong> ile gelir ve 160, 150, 140, 130, 120, 110, 100 seviyelerini destekler. <\/span><\/p>\n
Ancak ticari yaz\u0131l\u0131m \u00fcreticisi resmi olarak onaylamad\u0131\u011f\u0131 s\u00fcrece veritaban\u0131 uyumluluk seviyesi bu de\u011ferde b\u0131rak\u0131lmamal\u0131d\u0131r.<\/span><\/strong><\/p>\n
Uyumluluk seviyesi y\u00fckseltildi\u011finde <\/span>cardinality estimator de\u011fi\u015fiklikleri<\/span><\/strong>, <\/span>query plan de\u011fi\u015fiklikleri<\/span><\/strong> ve <\/span>yeni sorgu i\u015fleme davran\u0131\u015flar\u0131<\/span><\/strong> devreye girer. <\/span><\/p>\n
Bu de\u011fi\u015fiklikler mevcut raporlarda ve prosed\u00fcrlerde performans d\u00fc\u015f\u00fc\u015f\u00fcne veya hatal\u0131 sonu\u00e7lara yol a\u00e7abilir.<\/span><\/strong><\/p>\n
\u00d6neri:<\/span><\/strong> Veritaban\u0131n\u0131n compatibility level’\u0131 <\/span>130 (SQL Server 2016)<\/span><\/strong> veya <\/span>140 (SQL Server 2017\/2019)<\/span><\/strong> seviyesinde b\u0131rak\u0131lmal\u0131d\u0131r. <\/span><\/p>\n
Yaz\u0131l\u0131m \u00fcreticisinin destek ekibi aksini onaylamad\u0131k\u00e7a <\/span>150 veya 160’a y\u00fckseltilmemelidir.<\/span><\/strong><\/p>\n
4. UTF-8 Beta Ayar\u0131 Sadece SQL’i De\u011fil, T\u00fcm Sistemi Etkiler<\/span><\/h3>\n
Windows’taki <\/span>“Beta: D\u00fcnya \u00e7ap\u0131nda Unicode UTF-8 deste\u011fi i\u00e7in kullan”<\/span><\/strong> ayar\u0131, yaln\u0131zca SQL Server’\u0131 de\u011fil, i\u015fletim sisteminin <\/span>temel bile\u015fenlerini<\/span><\/strong> de etkiler. <\/span><\/p>\n
Bu ayar, sistemin varsay\u0131lan <\/span>ANSI Kod Sayfas\u0131’n\u0131 (ACP)<\/span><\/strong> 65001 (UTF-8) olarak de\u011fi\u015ftirir. <\/span><\/p>\n
Bu de\u011fi\u015fiklik, eski API’leri kullanan bir\u00e7ok uygulama ve servis i\u00e7in <\/span>beklenmedik davran\u0131\u015flara<\/span><\/strong> yol a\u00e7ar.<\/span><\/p>\n
Sahada kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z sorunlar:<\/span><\/strong><\/p>\n
\n
\n
<\/div>\n<\/div>\n\n\n\n\n\n\n\n\n\n\n
Etki Alan\u0131<\/span><\/th>\nG\u00f6r\u00fclen Sorun<\/span><\/th>\n<\/tr>\n<\/thead>\n
Windows API<\/span><\/strong><\/td>\n“A” (ANSI) API’leri, bekledikleri kod sayfas\u0131n\u0131 bulamaz; karakter bozulmalar\u0131, \u00e7\u00f6kmeler<\/span><\/td>\n<\/tr>\n
Lisans Servisleri<\/span><\/strong><\/td>\nSQL Server, Logo, Mikro lisans servisleri ba\u015flamaz; “servis ba\u015flat\u0131lamad\u0131” hatalar\u0131<\/span><\/td>\n<\/tr>\n
Dosya Sistemi<\/span><\/strong><\/td>\nDosya yollar\u0131 ve i\u00e7erikleri yanl\u0131\u015f okunur; T\u00fcrk\u00e7e karakterli dosya adlar\u0131 eri\u015filemez hale gelir<\/span><\/td>\n<\/tr>\n
Kurulum\/G\u00fcncelleme Betikleri<\/span><\/strong><\/td>\nSQL Server <\/span>msdb110_upgrade.sql<\/code> gibi betikler ba\u015far\u0131s\u0131z olur; servis hi\u00e7 ba\u015flamaz<\/span><\/td>\n<\/tr>\n
\u00dc\u00e7\u00fcnc\u00fc Parti Yaz\u0131l\u0131mlar<\/span><\/strong><\/td>\nmuhasebe yaz\u0131l\u0131mlar\u0131 \u00e7\u00f6ker; karakter kodlama hatalar\u0131 raporlar<\/span><\/td>\n<\/tr>\n
Sistem Kararl\u0131l\u0131\u011f\u0131<\/span><\/strong><\/td>\nBaz\u0131 durumlarda mavi ekran ve sistem a\u00e7\u0131lmama sorunlar\u0131<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
Neden bu kadar geni\u015f etkili?<\/span><\/strong><\/p>\n
Modern uygulamalar Unicode (UTF-16) kullan\u0131rken, eski uygulamalar ve baz\u0131 sistem servisleri h\u00e2l\u00e2 <\/span>1254 (T\u00fcrk\u00e7e) kod sayfas\u0131na<\/span><\/strong> ba\u011f\u0131ml\u0131d\u0131r. <\/span><\/p>\n
UTF-8 beta ayar\u0131 etkinle\u015ftirildi\u011finde, sistem genelinde bir <\/span>uyumsuzluk zinciri<\/span><\/strong> ba\u015flar. Bu zincir, tek bir uygulamay\u0131 de\u011fil, <\/span>t\u00fcm ekosistemi<\/span><\/strong> etkiler.<\/span><\/p>\n
Kritik Uyar\u0131:<\/span><\/strong> Bu ayar, SQL Server kurulumundan <\/span>ba\u011f\u0131ms\u0131z olarak<\/span><\/strong> dahi sistemde sorun \u00e7\u0131karabilir. <\/span><\/p>\n
Yani SQL Server hi\u00e7 kurulmam\u0131\u015f bir makinede bile bu ayar a\u00e7\u0131ksa, lisans servisleri, dosya okuma i\u015flemleri ve Windows API \u00e7a\u011fr\u0131lar\u0131 bozulabilir.<\/span><\/p>\n
Kontrol ve D\u00fczeltme:<\/span><\/strong><\/p>\n
    \n
  1. \n
    Win + R<\/code> \u2192 <\/span>intl.cpl<\/code> \u2192 Enter<\/span><\/p>\n<\/li>\n
  2. \n
    “Y\u00f6netimsel”<\/span><\/strong> sekmesi \u2192 <\/span>“Sistem yerel ayar\u0131n\u0131 de\u011fi\u015ftir”<\/span><\/strong><\/p>\n<\/li>\n
  3. \n
    “Beta: D\u00fcnya \u00e7ap\u0131nda Unicode UTF-8 deste\u011fi i\u00e7in kullan”<\/span><\/strong> se\u00e7ene\u011fi <\/span>i\u015faretsiz<\/span><\/strong> olmal\u0131d\u0131r.<\/span><\/p>\n<\/li>\n
  4. \n
    \u0130\u015faretliyse kald\u0131r\u0131n \u2192 Tamam \u2192 <\/span>Sistemi yeniden ba\u015flat\u0131n.<\/span><\/strong><\/p>\n<\/li>\n<\/ol>\n
    \n
    \u00d6nemli:<\/span><\/strong> Bu ayar kapat\u0131ld\u0131ktan sonra dahi, daha \u00f6nce olu\u015fmu\u015f veri bozulmalar\u0131 (\u00f6rne\u011fin yanl\u0131\u015f kaydedilmi\u015f karakterler) <\/span>kal\u0131c\u0131 olabilir.<\/span><\/strong><\/p>\n
    Bu nedenle ayar\u0131n <\/span>kurulumdan \u00f6nce<\/span><\/strong> kapal\u0131 oldu\u011fundan emin olunmal\u0131d\u0131r.<\/span><\/p>\n<\/blockquote>\n
    5. BOM (Byte Order Mark) Sorunu ve Temiz Kurulum Gereklili\u011fi<\/span><\/h3>\n
    UTF-8 beta ayar\u0131 a\u00e7\u0131kken, baz\u0131 uygulamalar config\/ini\/xml dosyalar\u0131n\u0131 <\/span>BOM’lu UTF-8<\/span><\/strong> olarak kaydeder. <\/span><\/p>\n
    Eski servisler bu BOM’u tan\u0131maz ve <\/span>servis ba\u015flamaz.<\/span><\/strong> Bu durumda yap\u0131lmas\u0131 gerekenler:<\/span><\/p>\n
      \n
    1. \n
      Uygulamay\u0131 kald\u0131r\u0131n.<\/span><\/strong><\/p>\n<\/li>\n
    2. \n
      Data (veri) hari\u00e7 t\u00fcm dosyalar\u0131 silin.<\/span><\/strong> (Config, log, cache, temp klas\u00f6rleri)<\/span><\/p>\n<\/li>\n
    3. \n
      Windows UTF-8 beta ayar\u0131n\u0131 kapat\u0131n<\/span><\/strong> (<\/span>intl.cpl<\/code> \u2192 Y\u00f6netimsel \u2192 Sistem yerel ayar\u0131).<\/span><\/p>\n<\/li>\n
    4. \n
      Sistemi yeniden ba\u015flat\u0131n.<\/span><\/strong><\/p>\n<\/li>\n
    5. \n
      Temiz kurulum yap\u0131n.<\/span><\/strong><\/p>\n<\/li>\n<\/ol>\n
      Bu s\u0131ralama, BOM’lu dosyalar\u0131n temizlenmesini ve yeni dosyalar\u0131n do\u011fru kod sayfas\u0131yla (1254) olu\u015fmas\u0131n\u0131 sa\u011flar. <\/span><\/p>\n
        \n
      • Data klas\u00f6r\u00fcn\u00fc silmeyin;<\/span><\/strong> veri kayb\u0131 ya\u015fars\u0131n\u0131z.<\/span><\/li>\n<\/ul>\n
        Not:<\/span><\/strong> Her servis ba\u015flamama sorunu BOM kaynakl\u0131 de\u011fildir. \u00d6nce <\/span>Olay G\u00fcnl\u00fc\u011f\u00fc’n\u00fc (Event Viewer)<\/span><\/strong> kontrol edin; hata mesaj\u0131 “config”, “encoding” veya “invalid character” i\u00e7eriyorsa BOM sorunu muhtemeldir.<\/span><\/p>\n
        \n
        Gizli Tuzak: STRING_AGG ve Dok\u00fcmantasyon \u00c7eli\u015fkisi<\/span><\/h2>\n
        STRING_AGG<\/span><\/strong> fonksiyonu, SQL Server 2016’da de\u011fil, <\/span>SQL Server 2017 (14.x) ve sonraki s\u00fcr\u00fcmlerde<\/span><\/strong> kullan\u0131ma sunulmu\u015ftur. <\/span><\/p>\n
        Microsoft’un resmi dok\u00fcmantasyonu, bu fonksiyonun “SQL Server 2017 (14.x) ve sonraki s\u00fcr\u00fcmler” i\u00e7in ge\u00e7erli oldu\u011funu a\u00e7\u0131k\u00e7a belirtmektedir.<\/span><\/p>\n
        Yerel ticari yaz\u0131l\u0131mlar\u0131n baz\u0131 mod\u00fclleri STRING_AGG fonksiyonunu <\/span>yo\u011fun \u015fekilde kullanmaktad\u0131r.<\/span><\/strong> Bu durumda:<\/span><\/p>\n
          \n
        • \n
          SQL Server 2016 SP1 kurulu bir sistemde<\/span><\/strong> ilgili mod\u00fcller <\/span>“STRING_AGG is not a recognized built-in function name”<\/span><\/strong> hatas\u0131 verecektir.<\/span><\/p>\n<\/li>\n
        • \n
          Kullan\u0131c\u0131, dok\u00fcmana g\u00fcvenerek 2016 SP1 kurar; ancak program \u00e7al\u0131\u015fmaz.<\/span><\/p>\n<\/li>\n
        • \n
          Fiili minimum gereksinim SQL Server 2017’dir<\/span><\/strong>; dok\u00fcmanlar ise 2016 SP1 demektedir.<\/span><\/p>\n<\/li>\n<\/ul>\n
          Sonu\u00e7:<\/span><\/strong> Yaz\u0131l\u0131m \u00fcreticilerinin dok\u00fcmantasyonu bu konuda <\/span>g\u00fcncellenmemi\u015ftir<\/span><\/strong> ve fiili gereksinim <\/span>SQL Server 2017 ve \u00fczeridir.<\/span><\/strong><\/p>\n
          \n
          Karar A\u011fac\u0131: Hangi Durumda Ne Yapmal\u0131s\u0131n\u0131z?<\/span><\/h2>\n
          \n
          \n
          <\/div>\n<\/div>\n\n\n\n\n\n\n\n\n\n
          Durumunuz<\/span><\/th>\nYapman\u0131z Gereken<\/span><\/th>\n<\/tr>\n<\/thead>\n
          Yeni SQL Server kurulumu yap\u0131yorsan\u0131z<\/span><\/strong><\/td>\nTurkish_CI_AS + UTF-8 beta kapal\u0131 + compatibility level 130\/140<\/span><\/td>\n<\/tr>\n
          Mevcut SQL Server 2016 SP1 kullan\u0131yorsan\u0131z<\/span><\/strong><\/td>\nSTRING_AGG hatas\u0131 al\u0131yorsan\u0131z 2017+’a y\u00fckseltme plan\u0131 yap\u0131n<\/span><\/td>\n<\/tr>\n
          SQL Server 2022\/2025 kurmak istiyorsan\u0131z<\/span><\/strong><\/td>\nYukar\u0131daki 5 kritik noktay\u0131 sa\u011flayabiliyorsan\u0131z kurun; sa\u011flayam\u0131yorsan\u0131z <\/span>kurmaktan ka\u00e7\u0131n\u0131n<\/span><\/strong><\/td>\n<\/tr>\n
          Mevcut 2022 kurulumunuz varsa<\/span><\/strong><\/td>\nCollation, UTF-8 beta ve compatibility level’\u0131 hemen kontrol edin; gerekirse d\u00fczeltin<\/span><\/td>\n<\/tr>\n
          Servis ba\u015flam\u0131yor \/ uygulama a\u00e7\u0131lm\u0131yorsa<\/span><\/strong><\/td>\nOlay G\u00fcnl\u00fc\u011f\u00fc’n\u00fc kontrol edin; BOM\/encoding hatas\u0131 varsa B\u00f6l\u00fcm 5’i uygulay\u0131n<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
          \n
          Kontrol Listesi: Kurulum Sonras\u0131 Do\u011frulama<\/span><\/h2>\n
          A\u015fa\u011f\u0131daki sorgular\u0131 \u00e7al\u0131\u015ft\u0131rarak kurulumunuzun do\u011fru yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n:<\/span><\/p>\n
          \n
          \n
          \n
          \n
          \n
          — 1. Sunucu harmanlamas\u0131<\/span><\/div>\n
          SELECT<\/span> SERVERPROPERTY<\/span>(<\/span>‘Collation’<\/span>)<\/span> AS<\/span> SunucuHarmanlamasi<\/span>;<\/span><\/div>\n<\/blockquote>\n<\/div>\n<\/div>\n<\/div>\n
          \n
          -- Beklenen: Turkish_CI_AS veya Turkish_100_CI_AS<\/span>\r\n\r\n-- 2. Veritaban\u0131 harmanlamas\u0131 ve uyumluluk seviyesi<\/span>\r\nSELECT<\/span> \r\n    name AS<\/span> VeritabaniAdi,<\/span>\r\n    collation_name AS<\/span> Harmanlama,<\/span>\r\n    compatibility_level AS<\/span> UyumlulukSeviyesi,<\/span>\r\n    SUSER_SNAME(<\/span>owner_sid)<\/span> AS<\/span> Sahibi\r\nFROM<\/span> sys.<\/span>databases<\/span>\r\nWHERE<\/span> name LIKE<\/span> '%Mikro%'<\/span>\r\n   OR<\/span> name LIKE<\/span> '%Logo%'<\/span>\r\nORDER<\/span> BY<\/span> name;<\/span>\r\n-- Beklenen: Turkish_CI_AS \/ 130 veya 140<\/span>\r\n\r\n-- 3. tempdb harmanlamas\u0131 (sunucu harmanlamas\u0131yla uyumlu olmal\u0131)<\/span>\r\nSELECT<\/span> name,<\/span> collation_name \r\nFROM<\/span> sys.<\/span>databases<\/span> \r\nWHERE<\/span> name =<\/span> 'tempdb'<\/span>;<\/span>\r\n\r\n-- 4. STRING_AGG fonksiyonu testi (2017+ gerektirir)<\/span>\r\nSELECT<\/span> STRING_AGG(<\/span>name,<\/span> ', '<\/span>)<\/span> AS<\/span> TestSonucu\r\nFROM<\/span> sys.<\/span>databases<\/span>;<\/span>\r\n-- Hata verirse: SQL Server s\u00fcr\u00fcm\u00fc 2017'den d\u00fc\u015f\u00fckt\u00fcr<\/span><\/pre>\n<\/blockquote>\n<\/div>\n
          5. Windows UTF-8 beta kontrol\u00fc (manuel):<\/span><\/strong>
          \nWindows Ayarlar \u2192 Saat ve Dil \u2192 B\u00f6lge \u2192 Y\u00f6netimsel Dil Ayarlar\u0131 \u2192 <\/span>“Beta: Unicode UTF-8 deste\u011fi”<\/span><\/strong> i\u015faretsiz olmal\u0131d\u0131r.<\/span><\/p>\n
          6. Notepad++ ile dosya kontrol\u00fc (iste\u011fe ba\u011fl\u0131):<\/span><\/strong>
          \n\u015e\u00fcpheli config\/log dosyas\u0131n\u0131 Notepad++ ile a\u00e7\u0131n. Sa\u011f alt k\u00f6\u015fedeki kodlamay\u0131 okuyun. <\/span><\/p>\n
          ANSI<\/span><\/strong> g\u00f6r\u00fcn\u00fcyorsa \u2192 <\/span>Kodlama \u2192 Karakter K\u00fcmeleri \u2192 T\u00fcrk\u00e7e \u2192 Windows-1254<\/span><\/strong> se\u00e7erek T\u00fcrk\u00e7e karakterlerin do\u011fru g\u00f6r\u00fcn\u00fcp g\u00f6r\u00fcnmedi\u011fini test edin.<\/span><\/p>\n
          \n
          Sorumluluk Notu<\/span><\/h2>\n
          Bu makalede belirtilen yap\u0131land\u0131rma ko\u015fullar\u0131n\u0131 sa\u011flamadan SQL Server 2022 veya 2025 kurulumu yapanlar, do\u011facak veri b\u00fct\u00fcnl\u00fc\u011f\u00fc sorunlar\u0131ndan, uygulama hatalar\u0131ndan ve performans d\u00fc\u015f\u00fc\u015flerinden bizzat sorumludur.<\/span><\/strong><\/p>\n
          \n
          \u00d6zet<\/span><\/h2>\n
          \n\n\n\n\n\n\n\n\n\n\n\n\n
          Konu<\/span><\/th>\nDo\u011fru Uygulama<\/span><\/th>\n<\/tr>\n<\/thead>\n
          SQL Server s\u00fcr\u00fcm\u00fc<\/span><\/strong><\/td>\n2017+ (STRING_AGG nedeniyle); 2016 SP1 dok\u00fcmanlarda ge\u00e7se de fiilen yetersizdir<\/span><\/td>\n<\/tr>\n
          Collation<\/span><\/strong><\/td>\nTurkish_CI_AS \/ Turkish_100_CI_AS<\/span><\/td>\n<\/tr>\n
          UTF-8 beta (Windows)<\/span><\/strong><\/td>\nKapal\u0131; t\u00fcm sistemi etkiler, sadece SQL’i de\u011fil<\/span><\/td>\n<\/tr>\n
          UTF-8 beta (SQL)<\/span><\/strong><\/td>\nUTF-8 collation se\u00e7ilmemeli<\/span><\/td>\n<\/tr>\n
          Compatibility level<\/span><\/strong><\/td>\n130 (SQL 2016) veya 140 (SQL 2017\/2019); \u00fcretici onay\u0131 olmadan y\u00fckseltilmemeli<\/span><\/td>\n<\/tr>\n
          BOM sorunu<\/span><\/strong><\/td>\nConfig\/ini\/xml dosyalar\u0131 BOM’lu ise servis ba\u015flamaz; temiz kurulum gerekir<\/span><\/td>\n<\/tr>\n
          Kullan\u0131c\u0131 adlar\u0131<\/span><\/strong><\/td>\nT\u00fcrk\u00e7e karakter i\u00e7ermemeli; ASCII tercih edilmeli<\/span><\/td>\n<\/tr>\n
          2022\/2025 kurulumu<\/span><\/strong><\/td>\nKo\u015fullar sa\u011flan\u0131yorsa kurulabilir; sa\u011flanam\u0131yorsa kurulmamal\u0131<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
          \n
          Bu makale, yerel ticari yaz\u0131l\u0131m (Logo, Mikro ve benzeri) i\u00e7in kal\u0131c\u0131 bir referans kayna\u011f\u0131 olarak haz\u0131rlanm\u0131\u015ft\u0131r. SQL Server 2025 ile ilgili g\u00fcncellemeler yay\u0131nland\u0131k\u00e7a revize edilecektir.<\/span><\/em><\/p>\n
           <\/p>\n","protected":false},"excerpt":{"rendered":"
          Ticari Yaz\u0131l\u0131mlarda SQL Server 2022 ve \u00dczeri * Kurmadan \u00d6nce Mutlaka Okuyun Kapsam: Logo, Mikro ve benzeri yerel ticari ERP\/\u00f6n muhasebe yaz\u0131l\u0131mlar\u0131 Neden Bu Makale Var? Bu makale, s\u00fcrekli tekrarlayan ve ayn\u0131 hatalara yol a\u00e7an SQL Server s\u00fcr\u00fcm uyumluluk sorunlar\u0131na kal\u0131c\u0131 bir \u00e7\u00f6z\u00fcm getirmek amac\u0131yla haz\u0131rlanm\u0131\u015ft\u0131r. Sahada kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z tablo nettir: SQL Server 2022 veya 2025 […]<\/p>\n","protected":false},"author":4,"featured_media":4723,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13,10],"tags":[],"class_list":["post-4740","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft","category-sql-server-tsql"],"_links":{"self":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/4740","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/comments?post=4740"}],"version-history":[{"count":8,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/4740\/revisions"}],"predecessor-version":[{"id":4748,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/4740\/revisions\/4748"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/media\/4723"}],"wp:attachment":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/media?parent=4740"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/categories?post=4740"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/tags?post=4740"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}