Browse by Tags
Sorry, but there are no more tags available to filter with.
-
-
After looking around a lot, I found this article that is really accurate, when you changed the server name, and not the SQL Server Instance name... http://www.coderjournal.com/2008/02/how-to-change-instance-name-of-sql-server/ -f.
-
-
I had this, and found a lot of posts for it... here is an other “simple” solution: change de provider name to Named Pipe, it this case the SSPI context is generating correctly. -f.
-
-
10000 rows at a time. DECLARE @i INT SET @i = 1 SET ROWCOUNT 10000 WHILE @i <> 0 BEGIN DELETE FROM dbo. table SELECT @i = @@ROWCOUNT END SET ROWCOUNT 0 -f.
-
-
w3wp!processing!5!03/27/2009-15:24:24:: a ASSERT: Assertion failed! Call stack: Microsoft.ReportingServices.ReportProcessing.ReportProcessing.UpdateTimingInformation(RunningJobContext jobContext, Int64 totalDurationMs...
-
-
I already posted a way to truncate log, so that they do not grow indefinitly. Here a little routine found on the Mark Brown's Blog. A generic way to truncate all the log files. See the disclaimer it's important. http://blogs.msdn.com/mab/archive...
-
-
SQL Server - SQL Example about cursors http://jackdonnell.com/articles/SQL_CURSOR.htm -f.
-
-
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer LoginMode =2 ... and restart the service. -f.
-
-
To troubleshoot a replication scenario that had a replication error 18773, The process could not execute 'sp_replcmds' on 'SERVER'. After profiling the database, and re-executing the statements, I had this problem... Could not locate text information...
-
-
I had... During upgrade, database raised exception 211, severity 23, state 46, address 019C646E. Use the exception number to determine the cause. The cause was pretty dark, so to diagnose, I tried to restore the database using the hard way . The result...