If you want thenlogin to see data then youd have to add a user for the login and grant it either specific select permissions or db_datareader.

sounds like there's a problem with the logic in your process.

a job should change...

the above are not necessary to make other objects...

take a look at this post i made a few years ago, it's got a nice example of a couple of schemas you can fiddle with.

http://www.sqlservercentral.com/Forums/Topic1216364-1550-1.aspx#bm1216431

sysadmin overrules all; any restrictions that you add on a sysadmin are ignored/cancelled out by that ring of power.

normal users, then yes, the most restrictive wins, but you can't add...

probably using FOR XML to concatenate the values is what you want.

here's an example:

declare @skills table (sys int, TeamId varchar(20))

insert into @skills

SELECT '100','Team-1' UNION ALL

SELECT '100','Team-2' UNION ALL

SELECT '100','Team-3'...

sounds like the user inherits a sysadmin permission due toi the windows groups the login belongs to.

this will enumerate all users in windows groups, and then join them to see...

sram24_mca (2/14/2014)

We have an stored procedure to create/execute the job automatically, now we are looking for auto refreshing the job if there is any problem[Data changes] while running...

YB1D (2/13/2014)

In SQL Server 2008 is there a way a user can view everything (all databases, all logins, storage, et al) at server level and each database level, while being...

really? that is not what i'd be expecting.

o you have a lot of tables that are HEAPS, that get a lot of updates? HEAP tables never release space unless...

my first guess is that you have a runaway log file, because the database is set to full recovery, and you are not doing LOG backups.

select

recovery_model

from...

knives the fix is rediculously easy;

the Tally table needs to start at zero instead of one.

so this tiny subsection changes:

TALLY (N) AS (SELECT ROW_NUMBER() OVER (ORDER BY (SELECT 0)) FROM...

the isnull or coalesce functions can help there:

coalesce lets you grab more than one alternative, and even finish with a default if all columns were null.

SELECT

ISNULL(Send_To_Address,Bill_To_Address) AS Bill_To_Address,

COALESCE (Send_To_Address,Bill_To_Address,Mail_To_Address, 'Missing')...

i've found that files that contain INSERT INTO ....statements are painfully slow in SSMS once they hit, say 40K rows or more, stretching simple inserts into minutes of waiting.

i'd prefer...

ownership chaining is what is happening, i'm pretty sure.

i believe that in this case, because all the objects are owned by the same schema(dbo), it's the same logic that follows...