Viewing 15 posts - 211 through 225 (of 359 total)
PS. there is a report that you can run that will also show what schema changes have been made against your database but it will only show you the information...
***The first step is always the hardest *******
June 19, 2012 at 7:46 am
if your looking for schema changes then you can create a DDL trigger on the database thats what i use to audit SP, Table, Trigger and index creations amendments etc
***The first step is always the hardest *******
June 19, 2012 at 7:44 am
Try this
create proc somename
(@paramname int
)
as
begin
select what ever
from some table
where id=@paramname
end
I sure you get the jist:w00t:
***The first step is always the hardest *******
June 19, 2012 at 6:08 am
Inner join your table on its self on booking_ID next select the columns you want from table a and then concatenate a+b like so
select A.BOOKING_ID , ...
***The first step is always the hardest *******
June 19, 2012 at 6:03 am
if your using SQL2008 then you need to set your database to SIMPLE mode
here is what i use to clear all my transaction logs on my test servers, bear...
***The first step is always the hardest *******
June 19, 2012 at 4:18 am
define complicated, what i may think is complicated other may think simple download adventure works database and have a look in there
***The first step is always the hardest *******
June 16, 2012 at 3:38 pm
are those values you added the actual string? can you provide some example DDL ?
***The first step is always the hardest *******
June 13, 2012 at 7:42 am
As already mentioned it would be better to run this in batches however, is your database used on an evening? are there any downtime periods of the application as to...
***The first step is always the hardest *******
June 13, 2012 at 7:37 am
Exellent Marvelouse "Excrament Marvaloid"
***The first step is always the hardest *******
June 13, 2012 at 7:09 am
sounds to me like its an automated SQL job or maintenance plan have you tried to look at the current sql jobs and maintenance plans
***The first step is always the hardest *******
June 12, 2012 at 1:06 pm
Bring your results into an CTE also add row_number() to your select and then select from cte where row_number =1 like for example
;with duplicates (rn,one,two,three)
As
(select row_number() over(partition by one,two,three...
***The first step is always the hardest *******
June 12, 2012 at 5:24 am
:ermm: from what a read as i understand you then you only need to replace * with ID sorry if im misunderstanding you but looking at your tables am not...
***The first step is always the hardest *******
June 11, 2012 at 2:34 pm
PS i also have several version of each script but i name and version control them accordingly like company,customer,scriptname,version
***The first step is always the hardest *******
June 11, 2012 at 2:29 pm
Like you i use a system of folders that a split in to categories, Performance, indexing etc
***The first step is always the hardest *******
June 11, 2012 at 2:28 pm
Hi yup your thread is interesting, assuming that in your table all the varchar values are in order as per your DDL then you could just inner join the table...
***The first step is always the hardest *******
June 11, 2012 at 2:23 pm
Viewing 15 posts - 211 through 225 (of 359 total)