doh i should have tested that: wrapped the datediff evaluation with the convert first, sorry:

select ABS(CONVERT(BIGINT,(DateDiff(minute, getdate(), '1900-01-01'))) * 60),

ABS(CONVERT(BIGINT,(DateDiff(minute,...

WayneS (8/5/2010)

---

If it's a registered server, right-click server and select properties. Go to the connection properties tab. Check the "Use Custom Color" checkbox, and select the color.

If it's a server...

the error is related to the actual data being tested/datediffed. one instance has data that is out of range.

when you use datediff with seconds, there can only be something like...

basically you have to determine that if any high ascii character(>127) exists, you want to use DESC sort order on the example i provided, but if no high ascii exists,...

things to look for:

1. the user would lose his permissions every time the database is restored to a version that did not have his permissions previously.

2. if this is object...

glad i could help; there's a lot to do in there to make it report-presentable..convert to decimal a couple of times along with the division and case statement;

much easier...

this should help you visualize; you'll need a case statement:

/*--results

KB MB GB...

this seems to do what you want...i'm doing an order by on the username, and then the username with case sensitive collation:

the desision to order by the second as DESC...

here's the visual results of my current query for reference: my expectation is that for AREAID 1887, the "buidlingindex" should be all "1", and the apartmentindex increments as seen below.

ID...

not an expert here by any means, but i think "NetAPP SnapManager ", and what it is doing behind the scenes is more than jsut a SQL Server Enterpise Snapshot;...

go to the scripting options and check "script indexes" "script "triggers" and anything else you might need scripted,a nds simply rerun the process.

in SQL Server Management Studio, have you tried right clicking on the table and selecting "Script Table As ..."

Then you can rename the table and the constraints that are part...

windows login methods are never disabled...but a domain login might not work yet, is that what you mean?

can you right click on the link to SSMS and choose Run As......

in that case, look at this article, which shows how to audit access to the databases with a server side trace:

http://www.sqlservercentral.com/articles/Administration/trace/872/

once that is in place, you can insert the results...

rather than tracking where the inapproprate acces sis coming from, you could change the passwords for those two users, or maybe use a logon trigger to prevent access for those...