Database

.NET Enthusiast wrote:

but why isn't Name on the keywords list

CREATE DATABASE database_name
[ ON [PRIMARY]         [ <filespec> [,...n] ]
        [, <filegroup> [,...n] ]
]
[ LOG ON { <filespec> [,...n]  ]
[ FOR LOAD | FOR ATTACH ] 
<filespec> ::=

  ( [ NAME = logical_file_name, ]
  FILENAME = 'os_file_name'
  (and more)

  select *   
    from sysobjects   
   where type = 'U'  
order by name

I are Troll

declare @itemcount int
set @itemcount = (select isnull(count(*),0) from tablename where columnname=conditionvalue)

DECLARE @InputParam int,
        @OutputParam int

EXECUTE sp_executesql 'query', 
                      N'@DynamicInputParam int, @DynamicOutputParam int OUTPUT', 
                      @DynamicInputParam = @InputParam,
                      @DynamicOutputParam = @OutputParam OUTPUT

Hema Bairavan wrote:

its not working for me?

DECLARE @ABC VARCHAR(50)
DECLARE @SQL VARCHAR(1000)
SET @ABC = '%test%'
SET @SQL = 'SELECT * FROM table WHERE lower(column) LIKE (''' + @ABC + ''')'
EXEC (@SQL)

create procedure InsertUser
@username varchar(200)
as
Begin
if(select count(*) from users where username=@username) = 0)
begin

insert into users values(column1,column2......)

end
end

create function InsertUser
@username varchar(200)
as
Begin

return 0 --By default user is not inserted and return value have value 0

if(select count(*) from users where username=@username) = 0)
begin

insert into users values(column1,column2......)
return 1 --User is inserted and return value have value 1

end

end

Ray Cassick wrote:

Things that address naming conventions across various industry\business segments so that I can look to normalize a set of tables for a generalized system that could cross industry boundaries and still manage to keep some standardization across industry expectations would be great.

I are Troll