Foros del Web » Programación para mayores de 30 ;) » Bases de Datos General » SQL Server »

Problema con SQL Server

Estas en el tema de Problema con SQL Server en el foro de SQL Server en Foros del Web. Hola a todos: Tengo un servidor SQL y tengo una instancia del mismo, en teoria entra bien se ejecuta y todo el asunto. Yo puedo ...
  #1 (permalink)  
Antiguo 07/06/2012, 09:51
 
Fecha de Ingreso: agosto-2007
Mensajes: 268
Antigüedad: 16 años, 8 meses
Puntos: 2
Problema con SQL Server

Hola a todos:

Tengo un servidor SQL y tengo una instancia del mismo, en teoria entra bien se ejecuta y todo el asunto. Yo puedo entrar al SQL Server Management Studio y todo esta perfecto, pero cuando expando el arbol de base de datos de inicio se tarda mucho. Ya que por fin abrio el arbol y seleccionó una base de datos en particular, se queda "colgado" luego pone la base en recuperacion y tengo que darle "actualizar" varias veces para que la base ya este modo correcto.

¿Alguien sabe a que se debe o que puedo hacer? Anexo el Log, haber si alguien pudiera echarme la mano con él.

Saludos...

2012-06-07 09:59:44.85 Server Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (Intel X86)
Jun 17 2011 00:57:23
Copyright (c) Microsoft Corporation
Express Edition on Windows NT 6.1 <X86> (Build 7601: Service Pack 1)
2012-06-07 09:59:44.90 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SERVER_DES\MSSQL\Log\ERRORLOG'.
2012-06-07 09:59:45.66 spid6s Starting up database 'master'.
2012-06-07 09:59:46.72 spid6s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2012-06-07 09:59:46.82 spid6s Error: 5596, Severity: 16, State: 2.
2012-06-07 09:59:46.82 spid6s FILESTREAM feature configuration might be inconsistent. Use the sp_filestream_configure stored procedure to reset the configuration.
2012-06-07 09:59:46.82 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SERVER_DES'.
2012-06-07 09:59:46.88 spid6s SQL Trace ID 1 was started by login "sa".
2012-06-07 09:59:46.88 spid6s Starting up database 'mssqlsystemresource'.
2012-06-07 09:59:46.89 spid6s The resource database build version is 10.50.2500. This is an informational message only. No user action is required.
2012-06-07 09:59:47.19 spid6s Server name is 'MIPC\SERVER_DES'. This is an informational message only. No user action is required.
2012-06-07 09:59:47.19 Server Warning: Support for the VIA protocol is deprecated and will be removed in a future version of Microsoft SQL Server. If possible, use a different network protocol and disable VIA.
2012-06-07 09:59:47.19 spid10s Starting up database 'model'.
2012-06-07 09:59:47.19 Server Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server.
2012-06-07 09:59:47.53 spid6s Informational: No full-text supported languages found.
2012-06-07 09:59:47.55 spid6s Starting up database 'msdb'.
2012-06-07 09:59:48.28 spid10s Clearing tempdb database.
2012-06-07 09:59:51.67 Server A self-generated certificate was successfully loaded for encryption.
accept connection on [ \\.\pipe\SQLLocal\SERVER_DES ].
2012-06-07 09:59:51.86 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SERVER_DES\sql\query ].
2012-06-07 09:59:51.86 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2012-06-07 09:59:51.86 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2012-06-07 09:59:51.86 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2012-06-07 09:59:55.66 spid10s Starting up database 'tempdb'.
2012-06-07 09:59:56.46 spid13s The Service Broker protocol transport is disabled or not configured.
2012-06-07 09:59:56.46 spid13s The Database Mirroring protocol transport is disabled or not configured.
2012-06-07 09:59:56.46 spid13s Service Broker manager has started.
2012-06-07 10:00:04.44 spid6s Recovery is complete. This is an informational message only. No user action is required.
2012-06-07 10:11:07.28 spid51 Starting up database 'BD1'.
2012-06-07 10:11:14.37 spid51 Starting up database 'BD2'.
2012-06-07 10:11:15.08 spid51 Starting up database 'BD3'.
2012-06-07 10:11:17.02 spid51 Starting up database 'BD4'.
2012-06-07 10:11:19.81 spid51 Starting up database 'BD5'.
2012-06-07 10:11:21.35 spid51 Starting up database 'BD6'.
2012-06-07 10:14:08.32 spid52 Starting up database 'BD6'.
2012-06-07 10:14:32.13 Logon Error: 18456, Severity: 14, State: 38.
2012-06-07 10:14:32.13 Logon Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: 10.39.140.138]
2012-06-07 10:14:39.34 Logon Error: 18456, Severity: 14, State: 38.
2012-06-07 10:14:39.34 Logon Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: 10.39.140.138]
2012-06-07 10:14:45.52 spid51 Starting up database 'BD1'.
2012-06-07 10:15:33.71 spid52 Recovery completed for database BD6 (database ID 6) in 1 second(s) (analysis 21 ms, redo 0 ms, undo 1209 ms.) This is an informational message only. No user action is required.
2012-06-07 10:15:52.89 spid51 Recovery completed for database BD1 (database ID 10) in 1 second(s) (analysis 237 ms, redo 0 ms, undo 261 ms.) This is an informational message only. No user action is required.
2012-06-07 10:15:56.60 spid51 Starting up database 'BD2'.
2012-06-07 10:15:59.62 spid51 Recovery completed for database BD2 (database ID 5) in 1 second(s) (analysis 1 ms, redo 0 ms, undo 1000 ms.) This is an informational message only. No user action is required.
2012-06-07 10:16:03.86 spid51 Starting up database 'BD3'.
2012-06-07 10:16:09.12 spid51 Starting up database 'BD4'.
2012-06-07 10:16:24.68 spid51 Recovery completed for database BD4 (database ID 7) in 2 second(s) (analysis 1337 ms, redo 0 ms, undo 411 ms.) This is an informational message only. No user action is required.
2012-06-07 10:16:31.98 spid51 Starting up database 'BD5'.
2012-06-07 10:16:51.07 spid51 Recovery completed for database BD5 (database ID 8) in 2 second(s) (analysis 580 ms, redo 0 ms, undo 819 ms.) This is an informational message only. No user action is required.
2012-06-07 10:19:00.05 spid52 Starting up database 'BD6'.
2012-06-07 10:19:49.73 spid51 Starting up database 'BD1'.
2012-06-07 10:19:51.15 spid52 Recovery completed for database BD6 (database ID 6) in 1 second(s) (analysis 270 ms, redo 0 ms, undo 21 ms.) This is an informational message only. No user action is required.
2012-06-07 10:20:15.32 spid52 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2012-06-07 10:20:16.80 spid52 Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2012-06-07 10:20:34.08 spid52 Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\Windows\Microsoft.NET\Framework\v2.0.50727\.
2012-06-07 10:20:35.42 spid51 Recovery completed for database BD1 (database ID 10) in 1 second(s) (analysis 242 ms, redo 0 ms, undo 29 ms.) This is an informational message only. No user action is required.
2012-06-07 10:20:43.09 spid16s AppDomain 2 (mssqlsystemresource.dbo[ddl].1) unloaded.
2012-06-07 10:20:44.30 spid51 Starting up database 'BD2'.
2012-06-07 10:20:44.42 spid21s AppDomain 3 (mssqlsystemresource.dbo[ddl].2) unloaded.
2012-06-07 10:20:44.78 spid52 AppDomain 4 (mssqlsystemresource.dbo[runtime].3) created.
2012-06-07 10:20:45.12 spid26s AppDomain 5 (mssqlsystemresource.dbo[ddl].4) unloaded.
2012-06-07 10:20:45.46 spid25s AppDomain 6 (mssqlsystemresource.dbo[ddl].5) unloaded.
2012-06-07 10:20:47.05 spid52 Unsafe assembly 'microsoft.sqlserver.mpusqlclrwrapper, version=10.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 4 (mssqlsystemresource.dbo[runtime].3).
2012-06-07 10:20:48.31 spid17s AppDomain 7 (mssqlsystemresource.dbo[ddl].6) unloaded.
2012-06-07 10:20:59.56 spid51 Starting up database 'BD3'.
2012-06-07 10:21:06.21 spid51 Starting up database 'BD4'.
2012-06-07 10:34:51.07 spid52 Starting up database 'BD6'.
2012-06-07 10:35:20.47 spid52 Starting up database 'BD6'.
  #2 (permalink)  
Antiguo 07/06/2012, 09:51
 
Fecha de Ingreso: agosto-2007
Mensajes: 268
Antigüedad: 16 años, 8 meses
Puntos: 2
Respuesta: Problema con SQL Server

Quiero comentar que edite algunas lineas del LOG
  #3 (permalink)  
Antiguo 07/06/2012, 11:20
Avatar de iislas
Colaborador
 
Fecha de Ingreso: julio-2007
Ubicación: Mexico, D.F.
Mensajes: 6.482
Antigüedad: 16 años, 9 meses
Puntos: 180
Respuesta: Problema con SQL Server

¿El protocolo que estas utilizando en TCP/IP?, ¿Haces uso de la cuenta SA como usuario comun?
__________________
MCTS Isaias Islas
  #4 (permalink)  
Antiguo 07/06/2012, 11:29
 
Fecha de Ingreso: agosto-2007
Mensajes: 268
Antigüedad: 16 años, 8 meses
Puntos: 2
Respuesta: Problema con SQL Server

Hola IIslas:

El equipo sobre el que estoy trabajando es de desarrollo, no es un servidor como tal. Es una lap. Y respondiendo a tus preguntas:

1. Si uso el protocolo TCP/ IP
2. Si, el usuario sa es usuario comun

Saludos...
  #5 (permalink)  
Antiguo 07/06/2012, 14:14
Avatar de iislas
Colaborador
 
Fecha de Ingreso: julio-2007
Ubicación: Mexico, D.F.
Mensajes: 6.482
Antigüedad: 16 años, 9 meses
Puntos: 180
Respuesta: Problema con SQL Server

Te lo comento por estos mensajes:

Server Warning: Support for the VIA protocol is deprecated and will be removed in a future version of Microsoft SQL Server. If possible, use a different network protocol and disable VIA.

Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SERVER_DES\sql\query]

En cuanto a los errores de login, consulta esta liga:

http://sql-articles.com/articles/tro...d-error-18456/
__________________
MCTS Isaias Islas

Etiquetas: server, sql
Atención: Estás leyendo un tema que no tiene actividad desde hace más de 6 MESES, te recomendamos abrir un Nuevo tema en lugar de responder al actual.
Respuesta




La zona horaria es GMT -6. Ahora son las 19:06.