just to clarify, if you run the script above, ti doesn't do anything except add a stored procedure...

if you call the procedure, ie EXEC sp_AddMyTrace, that creates/starts the trace and...

just once. run it just once.

sp_AddMyTrace creates a log for all statements in all databases.

it is limited to 100 meg of data before it starts rolling over to reuse the...

duplicate post.

no need to post the same question in multiple forums, the "Recent Posts>>Posts Added Today" makes sure your question will be seen.

follow the thread and answers posted so far...

I know if you had done it the opposite way, where you granted the user or role minimum rights like db_datareader and db_datawriter, then you had to do GRANT VIEW...

something like this should get you started; you have to join the table against itself to get the date differences.

SELECT game_id,DATEDIFF(day,MinSet.date,MaxSet.date)

From (select home as x, min(date) as date from YourTable...

i currently have to support both SQL and Oracle at the shop that I work.

because even little things like naming conventions for parameters(SQL requires parameters to start with @, Oracle...

encrypted fields have to be nvarchar or sometimes varbinary data types for any encryption to work, depending on the encryption method. they also have to typically be much larger than...

not an expert on SSIS, but as you identified,the row_number function can do what you want, for sure...maybe stick everything in a table and do the row_number in a Script...

running profiler to create a trace is resource intensive, but a server side trace has minimal impact, and can help track down your deletes. search for trace on this site,...

still not clear to me either, can you give a non-pseudo code, concrete example of the expected results?

isn't Crystal still client-server based, so you have to install Crystal on every machine that will run a report, vs SSRS which is a web server HTML based reporting system?...

two single quotes in a row are the "escape" sequence to insert into a quote delimited string:

SET @sqlquery = 'UPDATE Allotuser SET ' + QUOTENAME(@accno) + '=''' + @acc +...

a rewrite of your proc to have better error messaging:

ALTER PROCEDURE [dbo].[USP_UpdateAllotUser]

(

@accno NVARCHAR(5),

@acc NVARCHAR(50),

@userid NVARCHAR(50)

)

AS

BEGIN

SET NOCOUNT ON

BEGIN TRY

IF (@accno '' OR...

ahh now i see; it's kind of obvious.

best practice is to always print your sql before you execute it:

this is the SQl statement your code creates:

UPDATE Allotuser SET ([Acc5])=hello where...

oops... researching now...what was the erro message specifically...error numbers not much help.