Jeff Moden (8/28/2015)

---

ScottPletcher (8/28/2015)

---

The point is to run a business, not have a perfect environment for the db itself.

Yes, much care needs to be taken before allowing anyone to run...

IF OBJECT_ID('tempdb.dbo.#db_sizes') IS NOT NULL

DROP TABLE #db_sizes

CREATE TABLE #db_sizes (

db_name varchar(100) NOT NULL,

data_size_kb bigint NULL,

...

DECLARE @sqlVersion smallint;

DECLARE @UserName nvarchar(100);

SELECT @sqlVersion = LEFT(ProductVersion, CHARINDEX('.', ProductVersion) - 1)

FROM (

SELECT CAST(SERVERPROPERTY('ProductVersion') AS varchar(30)) AS ProductVersion

) AS system_value

--get all user/login names that need removed...

Look at the query plan, and see if it is scanning the clustered index or doing keyed lookups by joining to a table of constants. If it's a scan,...

Maybe you could create a dummy user in the db, have the main user EXECUTE AS that user to give him/herself permission, then REVERT back to their own id for...

Ed Wagner (8/28/2015)

---

Scott, I agree with you that the point is to run a business. You raise a good point about perspective. It may be that cutting off...

The point is to run a business, not have a perfect environment for the db itself.

Yes, much care needs to be taken before allowing anyone to run ad-hoc queries. ...

Lowell (8/28/2015)

---

my example i provided made sure the valuewas converted to date type. As Luis pointed out, converting the date to a string in this format:2015-04-01 is now ten characters,...

aleksandra 81219 (8/28/2015)

---

Ok, know what was wrong with executing but data is also not proper :doze:

I put some PRINT commands, look at this

WeeksOnStart

20150406,20150401

val_in_cursor

2015-04-06

Warning: Null value is eliminated by...

Yes, if I had done the synonym names in the correct order :-D. I think I got them backwards in the script:

Edit: That is, after you run this code:

CREATE...

Nah, I was thinking of something like this to generate the commands to run. If you want, you could even actually run the code instead of just generating it.

DECLARE...

To me it seems fairly easy to match single rows. Maybe you can just output those matches to a table and then consolidate the like ids using that result.

SELECT...

Since you literally can't add enough values here to make a cursor all that bad, you might want to use a cursor just to have better control over the processing...

DECLARE @database_name NVARCHAR(50)

SELECT @database_name=DB_NAME()

WHILE 1 = 1

BEGIN

IF EXISTS(

SELECT 1

FROM msdb.dbo.backupmediafamily

INNER JOIN msdb.dbo.backupset ON...

No, you'd need to use a synonym for each object. But it's easy enough to generate the code to create the synonyms for all tables in the current db.