Skip to main content

Searching Hard Coded Values

Searching Hard Coded Values from Entire Database-Objects is very Interesting Task for me. My last Blog (Search Dynamic Values) was for Dynamic Values from Tables. Today I want to show how I am searching Hard Coded values (E-mail Ids and Mobile numbers) from all Procedures or Views from our Database.We should avoid the Hard codes in objects.
To manages Hard codes in objects  i was simply Converting all procedures and Views in script and after that using find -replace i was managing changes...It was very time consuming and bothering work form me... Below Query help and save my lot of time for learning extras.....

declare @text varchar(100)
declare @dbname varchar(100) 
  set @text = 'sumank'
  set @dbname = 'masterdatabase'

if @dbname is null
--enumerate all databases.
DECLARE #db CURSOR FOR Select Name from master..sysdatabases
declare @c_dbname varchar(64)

OPEN #db FETCH #db INTO @c_dbname
while @@FETCH_STATUS <> -1 --and @MyCount < 500
     execute find_text_in_sp @text, @c_dbname
     FETCH #db INTO @c_dbname
 end --if @dbname is null
 begin --@dbname is not null
  declare @sql varchar(250)
  --create the find like command
  select @sql = 'select ''' + @dbname + ''' as db,,m.definition '
  select @sql = @sql + ' from '+@dbname+'.sys.sql_modules m '
  select @sql = @sql + ' inner join '+@dbname+'..sysobjects o on'
  select @sql = @sql + ' where [definition] like ''%'+@text+'%'''
  execute (@sql)
 end --@dbname is not null

Result :-



Post a Comment

Plz dont forget to like Facebook Page..

Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription