you could do this by declaring your statement as a variable....

declare @sqlcmd varchar(max)

set @sqlcmd = 'INSERT INTO myTable ('+@FieldVariable1+','+@FieldVariable2+')

VALUES ('+@FieldValue1+','+@FieldValue2+')'

exec (@sqlcmd)

or somethinglike that

you might also consider just granting execute to stored procedures on the database.

USE your_database

go

CREATE ROLE db_executor

USE your_database

go

GRANT EXECUTE TO db_executor

that way, whenever a Dev or someone drops a procedure...

select convert(varchar(2), month(getdate())) + '/'

+ convert(varchar(2), day(getdate())) + '/'

+ RIGHT(convert(varchar(4), year(getdate())),2)

you would also want to look at your indexes. if they are missing or the stats are out of date, that would be a problem too.

here is a working examples of Full Text Search on a Test database;

WARNING, if you have a database called Test, do not run the statement.....

USE [master]

GO

IF EXISTS (SELECT name...

yes, i see that....

you would have to implement Full Text Search and use the CONTAINS statement i think.

you could something like this;

declare @MyTable table (MyColumn varchar(255))

insert into @MyTable

select 'India is My country'

declare @variable varchar(255)

set @variable = 'India'

select MyColumn from @MyTable

where MyColumn like '%'+@variable+'%'

and have the application set...

are you trying to do this from a SQL Agent job? because then the account that runs the Agent would need the permissions.

Standard does have the repeat function on the daily settings. Didn't think of that because the term Daily threw me... thanks.

sounds like you only need one.

you need a license to run SQL Server Reporting Services.

the mangement of the reports (or the creating / authoring of them) can occur anywhere BIDS...

it sounds like you might be dealing with developers that are "long in the tooth".

possibly developers that primarly developed on ISAM databases.

there will be no arguing with them... 😛

i've seen the "never patch" approach at very large fortune 500 companies.

it is usually the practice when the vendor that provided the software no longer exists.

as far as applying...

its because your query (SELECT SUBSTRING(lname,1,2)+ SUBSTRING(fname,1,2) +

replace(convert(varchar,dob,10),'-','') from client

WHERE uniqueID IS NULL) returns more than 1 result.

if Jamie Moyer can do it at 49, then Mariano can too. he stil has 7 years left. 😛

SELECT T1.[job_id]

,T1.[category_id], T2.name

FROM [msdb].[dbo].[sysjobs] T1 join msdb.dbo.syscategories T2

on T1.category_id = T2. category_id