{"id":208,"date":"2020-01-30T11:51:00","date_gmt":"2020-01-30T08:51:00","guid":{"rendered":"http:\/\/www.ozgurguler.net\/?p=208"},"modified":"2026-09-23T10:32:10","modified_gmt":"2026-09-23T07:32:10","slug":"sql-yuklemesinde-f10-pencereleri-hata-veriyor-calismiyor","status":"publish","type":"post","link":"https:\/\/www.ozgurguler.net\/blog\/sql-yuklemesinde-f10-pencereleri-hata-veriyor-calismiyor\/","title":{"rendered":"Sql Y\u00fcklemesinde F10 Pencereleri Hata veriyor &#8211; \u00c7al\u0131\u015fm\u0131yor"},"content":{"rendered":"<h1>SQL Server Yeniden Kurulum Sonras\u0131 CLR Ayarlar\u0131n\u0131n Yap\u0131land\u0131r\u0131lmas\u0131<\/h1>\n<p>Web \u00dcyelik Hizmetiniz bulunmuyor ve SQL Server sisteminizi yeniden kurduysan\u0131z, <strong>SQL Server s\u00fcr\u00fcm\u00fcn\u00fcz\u00fc de\u011fi\u015ftirmedi\u011finiz s\u00fcrece<\/strong> a\u015fa\u011f\u0131daki sorgular ile gerekli CLR ayarlar\u0131n\u0131 yeniden yap\u0131land\u0131rabilirsiniz.<\/p>\n<p>Bu i\u015flem \u00f6zellikle SQL Server yeniden kurulduktan sonra, daha \u00f6nce \u00e7al\u0131\u015fan baz\u0131 uygulama veya veri i\u015flemlerinde <strong>CLR (Common Language Runtime)<\/strong> kaynakl\u0131 hatalarla kar\u015f\u0131la\u015f\u0131ld\u0131\u011f\u0131nda kullan\u0131labilir.<\/p>\n<blockquote><p><strong>\u00d6nemli:<\/strong> \u0130\u015fleme ba\u015flamadan \u00f6nce SQL Server s\u00fcr\u00fcm\u00fcn\u00fcz\u00fcn \u00f6nceki kurulumla ayn\u0131 oldu\u011fundan emin olun.<\/p><\/blockquote>\n<hr \/>\n<h2>1. CLR \u00f6zelli\u011fini etkinle\u015ftirme<\/h2>\n<p>\u00d6ncelikle SQL Server \u00fczerinde CLR \u00f6zelli\u011fini aktif hale getirelim.<\/p>\n<p>SQL Server Management Studio&#8217;yu (<strong>SSMS<\/strong>) a\u00e7arak a\u015fa\u011f\u0131daki sorguyu \u00e7al\u0131\u015ft\u0131rabilirsiniz:<\/p>\n<pre><code class=\"language-sql\">USE master;\r\nGO\r\n\r\nEXEC sp_configure 'clr enabled', 1;\r\nRECONFIGURE WITH OVERRIDE;\r\n<\/code><\/pre>\n<p>Bu i\u015flem SQL Server \u00fczerindeki <strong>CLR deste\u011fini etkinle\u015ftirir<\/strong>.<\/p>\n<hr \/>\n<h2>2. SQL Server 2016 ve \u00fczeri i\u00e7in CLR Security ayar\u0131<\/h2>\n<p>SQL Server 2016 ve sonraki s\u00fcr\u00fcmlerde, \u00f6zellikle <strong>UNSAFE assembly<\/strong> kullan\u0131larak veri olu\u015fturulmas\u0131 veya \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131 s\u0131ras\u0131nda g\u00fcvenlik kaynakl\u0131 hatalarla kar\u015f\u0131la\u015f\u0131labilir.<\/p>\n<p>\u00d6rne\u011fin a\u015fa\u011f\u0131daki tipte bir hata al\u0131nabilir:<\/p>\n<blockquote><p>Assembly olu\u015fturulurken veya \u00e7al\u0131\u015ft\u0131r\u0131l\u0131rken UNSAFE permission\/security hatas\u0131.<\/p><\/blockquote>\n<p>Bu durumda a\u015fa\u011f\u0131daki ayarlar kontrol edilebilir:<\/p>\n<pre><code class=\"language-sql\">USE master;\r\nGO\r\n\r\nEXEC sp_configure 'show advanced options', 1;\r\nRECONFIGURE;\r\n\r\nEXEC sp_configure 'clr strict security', 0;\r\nRECONFIGURE;\r\n<\/code><\/pre>\n<p>Burada:<\/p>\n<ul>\n<li><code>show advanced options<\/code> \u2192 Geli\u015fmi\u015f SQL Server ayarlar\u0131n\u0131n g\u00f6r\u00fcnt\u00fclenmesini sa\u011flar.<\/li>\n<li><code>clr strict security<\/code> \u2192 CLR assembly g\u00fcvenlik kontrol\u00fcn\u00fcn yap\u0131land\u0131r\u0131lmas\u0131n\u0131 sa\u011flar.<\/li>\n<li><code>0<\/code> de\u011feri, CLR strict security kontrol\u00fcn\u00fc devre d\u0131\u015f\u0131 b\u0131rak\u0131r.<\/li>\n<\/ul>\n<hr \/>\n<h2>3. T\u00fcm i\u015flemleri tek seferde yapmak<\/h2>\n<p>Yukar\u0131daki i\u015flemleri ayr\u0131 ayr\u0131 \u00e7al\u0131\u015ft\u0131rmak yerine, gerekli ayarlar\u0131 tek bir SQL sorgusunda da uygulayabilirsiniz:<\/p>\n<pre><code class=\"language-sql\"><\/code><\/pre>\n<pre><span class=\"token comment\">-- Geli\u015fmi\u015f se\u00e7enekleri a\u00e7 (clr strict security'yi g\u00f6rebilmek i\u00e7in gerekli)<\/span>\r\n<span class=\"token keyword\">EXEC<\/span> sp_configure <span class=\"token string\">'show advanced options'<\/span><span class=\"token punctuation\">,<\/span> <span class=\"token number\">1<\/span><span class=\"token punctuation\">;<\/span>\r\n<span class=\"token keyword\">RECONFIGURE<\/span><span class=\"token punctuation\">;<\/span>\r\nGO\r\n\r\n<span class=\"token comment\">-- CLR'yi etkinle\u015ftir<\/span>\r\n<span class=\"token keyword\">EXEC<\/span> sp_configure <span class=\"token string\">'clr enabled'<\/span><span class=\"token punctuation\">,<\/span> <span class=\"token number\">1<\/span><span class=\"token punctuation\">;<\/span>\r\n<span class=\"token keyword\">RECONFIGURE<\/span><span class=\"token punctuation\">;<\/span>\r\nGO\r\n\r\n<span class=\"token comment\">-- SQL 2017'nin kat\u0131 g\u00fcvenlik k\u0131s\u0131tlamas\u0131n\u0131 kapat<\/span>\r\n<span class=\"token keyword\">EXEC<\/span> sp_configure <span class=\"token string\">'clr strict security'<\/span><span class=\"token punctuation\">,<\/span> <span class=\"token number\">0<\/span><span class=\"token punctuation\">;<\/span>\r\n<span class=\"token keyword\">RECONFIGURE<\/span><span class=\"token punctuation\">;<\/span>\r\nGO\r\n\r\n<span class=\"token comment\">-- Geli\u015fmi\u015f se\u00e7enekleri tekrar kapat (temizlik, opsiyonel)<\/span>\r\n<span class=\"token keyword\">EXEC<\/span> sp_configure <span class=\"token string\">'show advanced options'<\/span><span class=\"token punctuation\">,<\/span> <span class=\"token number\">0<\/span><span class=\"token punctuation\">;<\/span>\r\n<span class=\"token keyword\">RECONFIGURE<\/span><span class=\"token punctuation\">;<\/span>\r\nGO\r\n\r\n<\/pre>\n<p class=\"ds-markdown-paragraph\"><strong><span class=\"\">Servisi yeniden ba\u015flatmak i\u00e7in:<\/span><\/strong><\/p>\n<div class=\"md-code-block md-code-block-dark\">\n<div class=\"md-code-block-banner-wrap\">\n<div class=\"md-code-block-banner md-code-block-banner-lite\">\n<div class=\"_121d384\">\n<div class=\"d2a24f03\"><span class=\"d813de27\">powershell<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n<pre><span class=\"token function\">Restart-Service<\/span> <span class=\"token operator\">-<\/span>Name MSSQLSERVER<\/pre>\n<\/div>\n<pre><code class=\"language-sql\"><\/code><\/pre>\n<p>Sorgu tamamland\u0131ktan sonra SQL Server \u00fczerindeki ilgili CLR ayarlar\u0131 yap\u0131land\u0131r\u0131lm\u0131\u015f olacakt\u0131r.<\/p>\n<hr \/>\n<h2>Dikkat edilmesi gerekenler<\/h2>\n<p>Bu i\u015flemi uygulamadan \u00f6nce a\u015fa\u011f\u0131daki noktalar\u0131 kontrol etmenizi \u00f6neririz:<\/p>\n<ol>\n<li>SQL Server s\u00fcr\u00fcm\u00fcn\u00fcz\u00fcn \u00f6nceki sistem ile ayn\u0131 oldu\u011fundan emin olun.<\/li>\n<li>\u0130\u015flemleri <strong>SQL Server Management Studio (SSMS)<\/strong> \u00fczerinden, yeterli yetkiye sahip bir kullan\u0131c\u0131 ile ger\u00e7ekle\u015ftirin.<\/li>\n<li><code>clr strict security<\/code> ayar\u0131n\u0131n g\u00fcvenlik a\u00e7\u0131s\u0131ndan bir etkisi oldu\u011funu unutmay\u0131n. Bu nedenle bu ayar yaln\u0131zca ger\u00e7ekten ihtiya\u00e7 duyulan sistemlerde uygulanmal\u0131d\u0131r.<\/li>\n<li>\u0130\u015flem sonras\u0131nda uygulaman\u0131z\u0131n veya ilgili veri i\u015fleminin tekrar kontrol edilmesi \u00f6nerilir.<\/li>\n<\/ol>\n<h3>K\u0131saca<\/h3>\n<p>SQL Server yeniden kurulmu\u015f ancak <strong>versiyon de\u011fi\u015fikli\u011fi yap\u0131lmam\u0131\u015fsa<\/strong>, CLR ayarlar\u0131n\u0131n yeniden yap\u0131land\u0131r\u0131lmas\u0131 i\u00e7in temel olarak a\u015fa\u011f\u0131daki sorgular kullan\u0131labilir:<\/p>\n<pre><code class=\"language-sql\">EXEC sp_configure 'clr enabled', 1;\r\nRECONFIGURE WITH OVERRIDE;\r\n<\/code><\/pre>\n<p>SQL Server 2016 ve \u00fczeri s\u00fcr\u00fcmlerde gerekli olmas\u0131 durumunda:<\/p>\n<pre><code class=\"language-sql\">EXEC sp_configure 'show advanced options', 1;\r\nRECONFIGURE;\r\n\r\nEXEC sp_configure 'clr strict security', 0;\r\nRECONFIGURE;\r\n<\/code><\/pre>\n<p>Bu \u015fekilde SQL Server yeniden kurulumu sonras\u0131nda gerekli CLR yap\u0131land\u0131rmalar\u0131 tekrar uygulanabilir.<\/p>\n<p>&nbsp;<\/p>\n<h2>SQL Server&#8217;\u0131 yeniden ba\u015flatmak gerekir mi?<\/h2>\n<p>Yukar\u0131daki <code>sp_configure<\/code> ve <code>RECONFIGURE<\/code> komutlar\u0131 \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131nda, yap\u0131lan ayarlar SQL Server \u00e7al\u0131\u015fma ortam\u0131na uygulan\u0131r. Bu nedenle normal \u015fartlarda <strong>SQL Server servisini yeniden ba\u015flatmak zorunlu de\u011fildir<\/strong>.<\/p>\n<p>Ancak yap\u0131lan ayarlara ra\u011fmen CLR veya assembly ile ilgili hata devam ediyorsa, \u00f6zellikle SQL Server yeniden kurulumu sonras\u0131nda, <strong>SQL Server hizmetinin yeniden ba\u015flat\u0131lmas\u0131<\/strong> \u00f6nerilebilir.<\/p>\n<p>SQL Server hizmetini yeniden ba\u015flatt\u0131ktan sonra ilgili uygulama veya i\u015flemi tekrar kontrol edin.<\/p>\n<blockquote><p><strong>Not:<\/strong> SQL Server hizmetini yeniden ba\u015flatmadan \u00f6nce, sistem \u00fczerinde \u00e7al\u0131\u015fan uygulamalar\u0131n ve kullan\u0131c\u0131lar\u0131n etkilenebilece\u011fini g\u00f6z \u00f6n\u00fcnde bulundurun.<\/p>\n<p><a href=\"https:\/\/www.ozgurguler.net\/blog\/sql-2017-clr-strict-security-hatasi\/\">SQL 2017 Clr strict security hatas\u0131 \u2013 \u00d6zg\u00fcr G\u00dcLER \u2013 White Eagles \u2013 BLOG<\/a><\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>SQL Server Yeniden Kurulum Sonras\u0131 CLR Ayarlar\u0131n\u0131n Yap\u0131land\u0131r\u0131lmas\u0131 Web \u00dcyelik Hizmetiniz bulunmuyor ve SQL Server sisteminizi yeniden kurduysan\u0131z, SQL Server s\u00fcr\u00fcm\u00fcn\u00fcz\u00fc de\u011fi\u015ftirmedi\u011finiz s\u00fcrece a\u015fa\u011f\u0131daki sorgular ile gerekli CLR ayarlar\u0131n\u0131 yeniden yap\u0131land\u0131rabilirsiniz. Bu i\u015flem \u00f6zellikle SQL Server yeniden kurulduktan sonra, daha \u00f6nce \u00e7al\u0131\u015fan baz\u0131 uygulama veya veri i\u015flemlerinde CLR (Common Language Runtime) kaynakl\u0131 hatalarla kar\u015f\u0131la\u015f\u0131ld\u0131\u011f\u0131nda kullan\u0131labilir. [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":1637,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,243],"tags":[297,294,296,295],"class_list":["post-208","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mikro-yazilimevi","category-one-cikan","tag-net-fremework-is-disabled","tag-clr-strict-security","tag-mikro-hata","tag-sp_configure"],"_links":{"self":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/208","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=208"}],"version-history":[{"count":16,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/208\/revisions"}],"predecessor-version":[{"id":4673,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/208\/revisions\/4673"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/media\/1637"}],"wp:attachment":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/media?parent=208"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/categories?post=208"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/tags?post=208"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}