I'm not at my computer right now, but you should check sp_executesql to use parameters with dynamic sql

vamsi.341 (11/3/2015)

---

Hi Luis,

If you see the storedprocedure parameters, i am passing the USER as a parameter to the storedprocedure..

I tried using cursor instead of SP_MSForeachDB, same issue it's not accepting...

Of course it's not accepting the variable as you don't send it as a parameter, nor you declare it inside your dynamic code.

My suggestion is to avoid the undocumented procedure...

Why are you doing additional work?

set nocount on

DECLARE

@AlterAuthorizationStatement nvarchar(MAX) = N''

, @db_user nvarchar(10)

set @db_user='test'

SELECT @AlterAuthorizationStatement = @AlterAuthorizationStatement + N'ALTER AUTHORIZATION ON SCHEMA::'...

I've never used SQL Nexus before, so I can't help, but I just wanted to suggest to post your issue on the discussions for that tool. https://sqlnexus.codeplex.com/discussions

I hope that you...

You should also use QUOTENAME( @fieldName) which would fix any problems causing SQL Injection. Or you could also validate its value against system views.

-- Your Parameters

DECLARE @fieldName varchar(128),

...

Eirikur Eiriksson (11/2/2015)

---

Lynn Pettis (11/2/2015)

---

It was awesome to get to meet some of the denizens of The Thread last week. Too bad Jeff Moden wasn't able...

SQL Server doesn't use the syntax CREATE TABLE...AS... Instead, it uses SELECT...INTO...

This should be what you're looking for.

SELECT mecase.CASETYPE AS [Case#],

mecase.mannerappears AS [Appearstobe],

...

TomThomson (11/2/2015)

---

I got this one wrong because I reckoned that when there is no concurrent activity the saving from not requesting shared locks is so small as to be absolutely...

Probably something like this:

DECLARE @cmd varchar(8000),

@protectType varchar( 6),

@action varchar(8000),

@object varchar(128) = 'sysdbfrag',

@grantee varchar(128);

IF @protectType...

It makes sense to generate reports that show data per date. It won't make sense to generate additional data that will be simply duplicating rows.

Here's an example I did playing...

It's possible by using a calendar table, but it doesn't make sense to duplicate rows when you're not adding anything special. Why do you want to have 3 ranges instead...

I'm not sure what you mean. What would be the problem?

INSERT INTO #TempTable(StringColumn) VALUES( @StringVariable);

--OR

INSERT INTO #TempTable(StringColumn) SELECT @StringVariable;

Jason A. Long (10/30/2015)

---

Luis Cazares (10/30/2015)

---

Ian Scarlett (10/30/2015)

---

Really? I understand the grief nulls can cause, but...

Do you mean one column or one row?

For one...