Do you want to import on a scheduled basis or do you just want to link and then create a view which shows everything dynamically in real time?

CREATE INDEX [NewIndexName] ON [ViewName]([ColumnName])

One option would be to create linked servers and then to create a view where you could do a union all to link tables together.

Create a linked server:

sp_addlinkedserver

@server='Target1',

@srvproduct='',

@provider='SQLNCLI',

@datasrc='SERVER'

Create...

Ells,

The AWE settings and the Min & Max memory settings are seperate. You do not need to turn AWE on to be able to set these.

For more explanation on AWE...

These OR branches are doing slightly different things and therefore i dont think i can do this using 1 statement.

This branch is bringing back the first byte from the columns...

Success. See what you think of this.

SELECT

su2.name as 'Owner',

so.name AS 'Object',

su.name AS 'Grantee',

su3.name AS 'Grantor',

'ProtectType'=

CASE sp.protecttype

WHEN 204 THEN 'GRANT_W_GRANT'

WHEN 205 THEN 'GRANT'

WHEN 206 THEN 'DENY'

END,

'Action'=

CASE sp.action

WHEN 26 THEN 'REFERENCES'

WHEN 178...

By the looks of things to fix this issue i cannot use the power function as that specifically returns an int value based upon the data type of the input...

Yep your right it falls over on the 32nd. Have been working on this since about 5 mins after posting the entire script. Will try and intgrated the new code...

Or the entire script to get all object based permissions is...

SELECT

su2.name as 'Owner',

so.name AS 'Object',

su.name AS 'Grantee',

su3.name AS 'Grantor',

'ProtectType'=

CASE sp.protecttype

WHEN 204 THEN 'GRANT_W_GRANT'

WHEN 205 THEN 'GRANT'

WHEN 206 THEN 'DENY'

END,

'Action'=

CASE sp.action

WHEN...

I tried you code but i didnt get the result i expected. Though thanks to the ideas put forward in your script i have managed to get what i think...

Cool thanks.

How would i join this to the varbinary value and also offset it as the first binary bit is the all permission setting?

Hi,

I have found the issue. I was given the package to troubleshoot without the knowledge that there was a custom dll in use. By adding this custom dll into the...

Have a look at this link and see if it helps.

http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1214330952654+28353475&threadId=180196

Have you tried looking at the history tab in the SQL Server Agent properties? This may be clearing some of the history information out.