All the sql text in your database is stored in system tables under each database. There are a few hardships to overcome in order to search.

1.) Text is split into 4000 character chunks. So every 4k chunk has a colID to note its position in the stack of rows .  The names are stored in sysobjects and the text is stored in syscomments. The issue is when your search hits in the second chunk. You need to pull in all chunks when any one finds a hit.

2.) Each database has it’s own system tables. For one search to check every database’s syscomments you need to loop. My example solution didn’t use a cursor.

I pulled a list of database names out of master.dbo.sysdatabases and put it in a temp table. That is what I used for my loop. I  just jet the top row, work it, delete it, and get the next one from the top.

In the loop I execute sql constructed dynamically based on the database name of in the current loop iteration. It searches for all object Ids that have text matching the search term. Then gets all chucks for that object.  To help me narrow down the search I also search on object type. V for view, p for proc  etc…Leave type ” to get all types.

If you paste this in your query window and set the search strings you should get results.  I clipped the text to 3990 because I kept getting errors that the row was too large. I should probably look into it but this will do for now.

I’m dealing with MSSql Server 2000 here and this works.  I plan to make this a stored proc and call it from asp but right now it’s 5:00pm on Friday and this can wait ’till Monday.

Create Table #dblist (NAME VARCHAR(80))

createtable #results (name nvarchar(80),text varchar(4000))

insert into #dblist

exec(’select name from master..sysdatabases order by name’)

declare @ObjectType as nvarchar(80)
declare @search as nvarchar(80)

set @search = ‘update’ –change this
set @ObjectType=‘p’  –searches only procedures
–set to ” for all types

declare @dbname as nvarchar(80)

set @dbname= (select top 1 name from #dblist)

while @dbname<>”

begin

insert into #results
exec(
’select id ‘ +
‘into #found ‘ +
‘from ['+@dbname+']..syscomments ‘+
‘where [text] like ”%’+ @search +‘%” ‘ +

’select ”’+ @dbname+‘:” + so.name as name, left(sc.text, 3990) ‘ +
‘from [' + @dbname + ']..syscomments sc ‘ +
‘inner join [' + @dbname + ']..sysobjects so on sc.id= so.id ‘ +
‘where sc.id in (select id from #found) ‘+
‘and xtype like ”%’ + @ObjectType+ ‘%” ‘+
‘order by name, colid ‘+
‘drop table #found’

)

delete from #dblist where name= @dbname

set @dbname= (select top 1 name from #dblist)

end

select * from #results

drop table #dblist

drop table #results

]]> http://www.npathweb.com/2009/10/09/search-your-entire-server-for-a-string-across-all-databases-mssql-2000/feed/ 1 http://www.npathweb.com/2009/09/29/83/ http://www.npathweb.com/2009/09/29/83/#comments Tue, 29 Sep 2009 13:34:07 +0000 B.Harding http://www.npathweb.com/?p=83 Lets say you have an  ip address in a string such as  ”127.1.2.3″

This code will store the information in an int64 (C#) or bigint (SQL) in with three places per octet.

127001002003

The highest this number could go is 255,255,255,255.00 which is too large for a 32 bit integer. Hence the Int64. In SQL an 64 bit Integer is big int so that is what you’ll need to store in an MS-SQL Database.

I worked this up as a work-around on a project and present it here for your enjoyment.

using System.Text.RegularExpressions;

public static Int64 convertIP(string sAddress) {

Match ipaddress = Regex.Match(sAddress,“^([\\d]*).([\\d]*).([\\d]*).([\\d]*)”);

Int64 iAddress = 0;

Int64 ip1 =Convert.ToInt64(ipaddress.Groups[1].ToString()) * 1000000000;
Int64 ip2 =Convert.ToInt64(ipaddress.Groups[2].ToString()) * 1000000;
Int64 ip3 =Convert.ToInt64(ipaddress.Groups[3].ToString()) * 1000;
Int64 ip4 =Convert.ToInt64(ipaddress.Groups[4].ToString());

iAddress = ip1 + ip2 + ip3 + ip4;

return iAddress;

}

Extra credit: This number is now 127,001,002,003. You can use string formating to display it as 127.001.002.003 by using the format string N0 (Number, zero decimal places) and changing the number group separator from the default comma to a period. All with the raw int64, no function required.

Int64 iAddress = convertIP(Request.UserHostAddress);

Response.Write(iAddress).ToString(“N0″, new NumberFormatInfo { NumberGroupSeparator =“.” }));

This is where the error of today’s post comes into play.  I was restoring from a .bak file on my local machine to sql express when the following error appeared:

For the Search engines:
Restore failed for Server ‘.\SQLEXPRESS’
The backup set holds a backup of a database other than the existing ‘clientDB’ database.

Was my quality of life not what I once thought it was?  Hold on a minute…

I decided to check the options on the restore. Low and behold there were a few settings that made the restore work like a charm.
First I check replace database then I made sure the filenames were in the right spot. All was right with the world. Inner peace restored.