Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Fuzzy searching Expand / Collapse
Author
Message
Posted Friday, July 26, 2013 3:01 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, December 12, 2014 1:02 AM
Points: 823, Visits: 753
/PAE is needed to be able to use AWE. However, not always. Books Online says:

In Windows Server 2003, PAE is automatically enabled only if the server is using hot-add memory devices. In this case, you do not have to use the /pae parameter on a system that is configured to use hot-add memory devices. In all other cases, you must use the /pae parameter in the Boot.ini file to take advantage of memory over 4 GB.


But maybe your server is configured for that. Because all other output indicates that everything is OK. Just for a check, can you post the the first five minutes of the current ERRORLOG for this instance?

This CLR dll you are having problem, from where did you get it? Is it something you can share? Also source code?


Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Post #1478213
Posted Monday, July 29, 2013 8:42 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, August 12, 2013 12:41 PM
Points: 5, Visits: 26
Here's the first 5 mins of my current log:

2013-07-29 07:59:04.53 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)

2013-07-29 07:59:04.53 Server (c) 2005 Microsoft Corporation.
2013-07-29 07:59:04.53 Server All rights reserved.
2013-07-29 07:59:04.53 Server Server process ID is 400.
2013-07-29 07:59:04.53 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2013-07-29 07:59:04.53 Server This instance of SQL Server last reported using a process ID of 240 at 7/26/2013 3:02:46 PM (local) 7/26/2013 7:02:46 PM (UTC). This is an informational message only; no user action is required.
2013-07-29 07:59:04.53 Server Registry startup parameters:
2013-07-29 07:59:04.53 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2013-07-29 07:59:04.53 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2013-07-29 07:59:04.53 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2013-07-29 07:59:04.79 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-07-29 07:59:04.79 Server Detected 2 CPUs. This is an informational message; no user action is required.
2013-07-29 07:59:07.07 Server 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.
2013-07-29 07:59:07.21 Server Database Mirroring Transport is disabled in the endpoint configuration.
2013-07-29 07:59:07.24 spid4s Starting up database 'master'.
2013-07-29 07:59:07.42 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2013-07-29 07:59:07.65 spid4s SQL Trace ID 1 was started by login "sa".
2013-07-29 07:59:07.76 spid4s Starting up database 'mssqlsystemresource'.
2013-07-29 07:59:08.67 spid8s Starting up database 'model'.
2013-07-29 07:59:08.68 spid4s Server name is 'HNA-002297\SQLEXPRESS'. This is an informational message only. No user action is required.
2013-07-29 07:59:08.70 spid4s Starting up database 'msdb'.
2013-07-29 07:59:08.79 Server Error: 17190, Severity: 16, State: 1.
2013-07-29 07:59:08.79 Server FallBack certificate initialization failed with error code: 1.
2013-07-29 07:59:08.79 Server Warning:Encryption is not available, could not find a valid certificate to load.
2013-07-29 07:59:08.79 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2013-07-29 07:59:08.79 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2013-07-29 07:59:08.79 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2013-07-29 07:59:08.82 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2013-07-29 07:59:09.43 spid8s Clearing tempdb database.


I don't think this specific dll is the problem. I say this because it worked for a few days until all of the CLR functions stopped working. I've tried implementing the same functionality, but I get the same error when I try to install the dll on the server. I can't even install a quick one-liner function. Here's the dll I'm looking to use: http://anastasiosyal.com/post/2009/01/11/Beyond-SoundEx-Functions-for-Fuzzy-Searching-in-MS-SQL-Server. It doesn't give the C# source, just the dll unfortunetly.

Thanks again for your help.
Post #1478623
Posted Monday, July 29, 2013 10:24 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, December 12, 2014 1:02 AM
Points: 823, Visits: 753
The log you posted, disagrees with the output you posted from "SELECT @@version":

Microsoft SQL Server 2005 - 9.00.5069.00 (Intel X86) Aug 22 2012 16:01:52 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)


The log file you posted is something else:

2013-07-29 07:59:04.53 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)


Maybe that's a local Express instance running on your local machine. (And to which you have not applied any service packs!).

I was of course interesting in the errorlog for the SQL Server where you have problem with running the CLR.

If this is happening to any CLR module, maybe your DBA should try restarting SQL Server?


Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Post #1478667
Posted Monday, July 29, 2013 10:52 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, August 12, 2013 12:41 PM
Points: 5, Visits: 26
Erland Sommarskog (7/29/2013)
The log you posted, disagrees with the output you posted from "SELECT @@version":

Microsoft SQL Server 2005 - 9.00.5069.00 (Intel X86) Aug 22 2012 16:01:52 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)


The log file you posted is something else:

2013-07-29 07:59:04.53 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)


Maybe that's a local Express instance running on your local machine. (And to which you have not applied any service packs!).

I was of course interesting in the errorlog for the SQL Server where you have problem with running the CLR.


Oops, of course. I wasn't thinking and grabbed the log file off my laptop...
Here's the first 5 mins of the current log file on my server:

2013-07-14 05:50:55.54 Server Microsoft SQL Server 2005 - 9.00.5069.00 (Intel X86)
Aug 22 2012 16:01:52
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

2013-07-14 05:50:55.62 Server (c) 2005 Microsoft Corporation.
2013-07-14 05:50:55.65 Server All rights reserved.
2013-07-14 05:50:55.67 Server Server process ID is 2936.
2013-07-14 05:50:55.70 Server Authentication mode is MIXED.
2013-07-14 05:50:55.71 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2013-07-14 05:50:55.78 Server This instance of SQL Server last reported using a process ID of 2940 at 7/14/2013 5:47:19 AM (local) 7/14/2013 9:47:19 AM (UTC). This is an informational message only; no user action is required.
2013-07-14 05:50:55.82 Server Registry startup parameters:
2013-07-14 05:50:55.84 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2013-07-14 05:50:55.85 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2013-07-14 05:50:55.85 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2013-07-14 05:50:56.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-07-14 05:50:56.65 Server Detected 16 CPUs. This is an informational message; no user action is required.
2013-07-14 05:50:58.01 Server Address Windowing Extensions is enabled. This is an informational message only; no user action is required.

If this is happening to any CLR module, maybe your DBA should try restarting SQL Server?

Indeed. We've restarted the server, but it doesn't fix the problem. Everything looks good, besides the fact that we can't use or install CLR functions.
Post #1478672
Posted Monday, July 29, 2013 11:33 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, December 12, 2014 1:02 AM
Points: 823, Visits: 753
AWE is definitely enabled.

Adding the startup option -g512 should not be a problem, and I recommend that you try that. This is a quite common thing to do.

When this problem started to occur, had their been any changes to the server, like installing some new software or extended stored procedure?

Another story is that your entire server is somewhat antiquated. It's running Windows 2003 which has gone out of support, and SQL 2005 which is in extended support. And you are running 32-bit SQL Server. Wity 64-bit SQL Server, SQL 2005 or a later version, it is unlikely that you would have this problem.


Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Post #1478682
Posted Monday, July 29, 2013 12:51 PM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 12:28 PM
Points: 4,611, Visits: 4,067
Some time ago, we had problems with memory pressure that seemed to come from CLR assemblies. After quite a bit of reading, we installed SP3 and the problem magically went away.

I'd also completely agree with Erland and recommend moving up to a 64-bit version.



Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions
Post #1478715
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse