Jump to content
Araştır
  • Diğer seçenekler ...
Sonuçları bul ...
Sonuçları bul ...

Genel Araştırma

'şişme' etiketi için arama sonuçları.

  • Etiketlere Göre Ara

    Aralarına virgül koyarak ekleyin
  • Yazara Göre Ara

İçerik Türü


Forum

  • PvP Serverlar
    • Server Tanıtımı
    • Server Kurulumu
    • Server Muhabbeti
  • Forum Genel
    • Forum Kuralları
    • Duyurular
    • Şikayet ve Öneriler
    • Geliştirici Paylaşımları
    • English Forum
  • Satış
    • Alım & Satım
  • Mini KO Forum (Yardım & İstek)
    • Genel Yardım
    • Genel İstek
  • KO Development
    • Geliştirme (Yeni)
    • Paketler
    • Özel Paylaşımlar
    • Projeler
    • Knight Online Kaynak Kod Paylaşımı
  • Knight OnLine Paylaşım Forum
    • Genel Paylaşımlar
    • Client Paylaşımları
    • Database Paylaşımları
    • Server Dosyası Paylaşımları
    • Prosedür & Query Kod Paylaşımları
    • Web Dosyası Paylaşımları
    • Yardımcı Program Paylaşımları
    • Gerekli Bilgi Paylaşımları
  • Hile paylaşımları
  • Programlama
  • Online Oyunlar
  • Ticaret
  • Webmaster
  • KO Developers Gazinosu
  • Kişisel
  • Diğer

Sonuçları bul ...

Sonuçları bul ...


Oluşturma Tarihi

  • Start

    End


Son Güncelleme

  • Start

    End


Filter by number of...

Katılım

  • Start

    End


Üye Grubu


Hakkımda

Araştırmada 3 sonuç bulundu

  1. Bildiniz gibi arkadaşın birisi Forumumuz da Bu Database paylaştı şişme sorunları ve tabloları doluydu bununla ilgili sorunlar yaşayan bazı arkadaşlarımız vardı onlar için temizleyip şişme problemi çözüp yardımcı olmak istedim. [Gizli İçerik] Öneri Notu: Bir şeyi yapmak istiyorsanız hazıra koşmayın orjinal KnightOnline Databaseleri mevcut indirip 0 dan başlayın saygılar kolay gelsin Sql 2014 de test edilmiştir. Zone Sorunu vardı map hatası veriyordu standart zone export edilmiştir.
  2. EVET ARKADAŞLAR yaklaşık 1 haftadır forumda paylasılmıs olan OldSchoolKO'nun databesinin aşırı şişme sorunuyla ılgılı ugrasıyorum ancak ne yaptıysam şişmeye devam ettı. Ancak az önce aklıma bırsey geldı ve SQL'de managementte SQL SERVER loglara bakayım dedım ve gözüme birşey çarptı. Sanırım şişmenin sebebide asagıda paylasacagım olay. Her 1 sanıyede sureklı tekrar edıyor ve sanırım loglara kayıtlanıyor ve o kayıtlandıkca database şişiyor. Şimdi esas can alıcı nokta bu sorunu nasıl duzeltıcez. Haydı aslansınız yaparsınız koclarım opuyorum sizleri :D @ espandot Edit (MOMENTUM) Konu başlıklarını açıklayıcı ve düzgün şekilde yazalım, iyi forumlar. KOD: 04/24/2018 20:07:03,spid55,Unknown,Setting database option RECOVERY to SIMPLE for database 'kn_online'. 04/24/2018 20:06:56,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:56,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:54,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:54,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:53,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:53,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:51,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:51,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:49,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:49,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:48,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:48,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:46,Logon,Unknown,Login failed for user 'su'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:46,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:44,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:44,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:42,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:42,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:41,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:41,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:39,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:39,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:37,Logon,Unknown,Login failed for user 'sysdba'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:37,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:36,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:36,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:34,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:34,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:32,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:32,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:31,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:31,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:29,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:29,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:27,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:27,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:26,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:26,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:24,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:24,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:22,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:22,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:20,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:20,Logon,Unknown,Error: 18456 Severity: 14 State: 58. 04/24/2018 20:06:19,Logon,Unknown,Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 111.194.168.235] 04/24/2018 20:06:19,Logon,Unknown,Error: 18456 Severity: 14 State: 58. -- mesaja ek olarak -- Unutmadan bunlar sadece %1lık bır kısmı bu verdıgı sorun sayfalarca surup gıdıyor ancak hepsı aynı -- mesaja ek olarak -- Ayrıca Database paylasılmadan 3 gun once son yapılmaya calısılan degısıklıkler bunlar sorunu cozmede yardımcı olabılır dıye paylasıyorum bunlarıda bu hata alınan degısıklıkler yapıldıktan sonra az once paylasmıs oldugum hata kodunu sureklı cevırıyor SQL her sanıye gene 10/27/2017 tarıhınde bu paylastıgım hatlardan sonrasında aynı hatayı sureklı cevırıyor. 10/27/2017 20:13:02,Server,Unknown,Software Usage Metrics is enabled. 10/27/2017 20:12:34,Server,Unknown,Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\. 10/27/2017 20:12:34,spid7s,Unknown,Recovery is complete. This is an informational message only. No user action is required. 10/27/2017 20:12:33,spid20s,Unknown,Service Broker manager has started. 10/27/2017 20:12:33,spid20s,Unknown,The Database Mirroring endpoint is in disabled or stopped state. 10/27/2017 20:12:33,spid20s,Unknown,The Service Broker endpoint is in disabled or stopped state. 10/27/2017 20:12:33,spid11s,Unknown,The tempdb database has 1 data file(s). 10/27/2017 20:12:32,spid11s,Unknown,Recovery completed for database tempdb (database ID 2) in 1 second(s) (analysis 1937 ms redo 0 ms undo 0 ms.) This is an informational message only. No user action is required. 10/27/2017 20:12:30,spid11s,Unknown,Starting up database 'tempdb'. 10/27/2017 20:12:29,spid7s,Unknown,1 transactions rolled back in database 'kn_online' (5:0). This is an informational message only. No user action is required. 10/27/2017 20:12:29,spid19s,Unknown,653 transactions rolled forward in database 'kn_online' (5:0). This is an informational message only. No user action is required. 10/27/2017 20:12:28,spid11s,Unknown,Clearing tempdb database. 10/27/2017 20:12:28,spid7s,Unknown,0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required. 10/27/2017 20:12:28,Server,Unknown,The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WIN-7AG784RAQN6:1433 ] for the SQL Server service. Windows return code: 0xffffffff state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 10/27/2017 20:12:28,Server,Unknown,The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WIN-7AG784RAQN6 ] for the SQL Server service. Windows return code: 0xffffffff state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 10/27/2017 20:12:28,spid17s,Unknown,1 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required. 10/27/2017 20:12:28,Server,Unknown,SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required. 10/27/2017 20:12:28,spid15s,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required. 10/27/2017 20:12:28,spid11s,Unknown,Starting up database 'model'. 10/27/2017 20:12:28,Server,Unknown,Dedicated admin connection support was established for listening locally on port 1434. 10/27/2017 20:12:28,Server,Unknown,Server is listening on [ 127.0.0.1 1434]. 10/27/2017 20:12:28,Server,Unknown,Server is listening on [ ::1 1434]. 10/27/2017 20:12:28,spid15s,Unknown,Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ]. 10/27/2017 20:12:28,spid15s,Unknown,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. 10/27/2017 20:12:28,spid15s,Unknown,Server is listening on [ 'any' 1433]. 10/27/2017 20:12:28,spid15s,Unknown,Server is listening on [ 'any' 1433]. 10/27/2017 20:12:28,spid15s,Unknown,A self-generated certificate was successfully loaded for encryption. 10/27/2017 20:12:27,spid11s,Unknown,The resource database build version is 12.00.5000. This is an informational message only. No user action is required. 10/27/2017 20:12:27,spid19s,Unknown,Starting up database 'kn_online'. 10/27/2017 20:12:27,spid11s,Unknown,Starting up database 'mssqlsystemresource'. 10/27/2017 20:12:27,spid17s,Unknown,Starting up database 'msdb'. 10/27/2017 20:12:27,spid7s,Unknown,Server name is 'WIN-7AG784RAQN6'. This is an informational message only. No user action is required. 10/27/2017 20:12:27,spid7s,Unknown,SQL Trace ID 1 was started by login "sa". 10/27/2017 20:12:26,spid7s,Unknown,SQL Server Audit has started the audits. This is an informational message. No user action is required. 10/27/2017 20:12:26,spid7s,Unknown,SQL Server Audit is starting the audits. This is an informational message. No user action is required. 10/27/2017 20:12:25,spid7s,Unknown,Resource governor reconfiguration succeeded. 10/27/2017 20:12:25,Server,Unknown,CLR version v4.0.30319 loaded. 10/27/2017 20:12:24,spid7s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required. 10/27/2017 20:12:24,spid7s,Unknown,0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required. 10/27/2017 20:12:24,spid7s,Unknown,3 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required. 10/27/2017 20:12:24,spid7s,Unknown,Starting up database 'master'. 10/27/2017 20:12:24,Server,Unknown,Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required. 10/27/2017 20:12:24,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 10/27/2017 20:12:24,Server,Unknown,Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 10/27/2017 20:12:24,Server,Unknown,The maximum number of dedicated administrator connections for this instance is '1' 10/27/2017 20:12:24,Server,Unknown,This instance of SQL Server last reported using a process ID of 1036 at 9/30/2017 2:15:38 PM (local) 9/30/2017 11:15:38 AM (UTC). This is an informational message only; no user action is required. 10/27/2017 20:12:20,Server,Unknown,Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033) 10/27/2017 20:12:18,Server,Unknown,Using conventional memory in the memory manager. 10/27/2017 20:12:18,Server,Unknown,Detected 4095 MB of RAM. This is an informational message; no user action is required. 10/27/2017 20:12:18,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 10/27/2017 20:12:18,Server,Unknown,SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 10/27/2017 20:12:17,Server,Unknown,Command Line Startup Parameters: -s "MSSQLSERVER" 10/27/2017 20:12:17,Server,Unknown,Registry startup parameters: -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf 10/27/2017 20:12:17,Server,Unknown,The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required. 10/27/2017 20:12:17,Server,Unknown,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'. 10/27/2017 20:12:17,Server,Unknown,Authentication mode is WINDOWS-ONLY. 10/27/2017 20:12:17,Server,Unknown,System Manufacturer: 'VMware Inc.' System Model: 'VMware Virtual Platform'. 10/27/2017 20:12:17,Server,Unknown,Server process ID is 1036. 10/27/2017 20:12:17,Server,Unknown,All rights reserved. 10/27/2017 20:12:17,Server,Unknown,(c) Microsoft Corporation. 10/27/2017 20:12:17,Server,Unknown,UTC adjustment: 3:00 10/27/2017 20:12:17,Server,Unknown,Microsoft SQL Server 2014 (SP2-GDR) (KB4019093) - 12.0.5207.0 (X64) Jul 3 2017 02:25:44 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)
  3. Arkadaşlar SQL serverda kurdugum database ilk kuruluşta yaklasık 3-4 dakıka suruyor ve 4-5 gb gibi bir yer tutuyor ancak aradan 3-4 gün gectıkten sonra harddısk tamamen doluyor, sorun nerede olabılır? database sürekli şişme halinde -- mesaja ek olarak -- akşama kadar şişme olur hıc oynama yapmadan db uzerınde akşam tekrar SS alıp atacagım arkadaşlar -- mesaja ek olarak -- -- mesaja ek olarak -- https://hizliresim.com/p6lzDL
×
×
  • Yeni Oluştur...