Viewing 15 posts - 14,551 through 14,565 (of 49,552 total)
If the user needs to see the definitions of the objects, grant them the view definition permission.
January 30, 2013 at 3:04 am
Wow, two ways to mismanage the log. If you don't care about recovering to a point in time then put the DB in simple recovery model and leave it alone.
Deleting...
January 30, 2013 at 3:00 am
No magic bullets.
And no, adding the pk column to NC indexes is not going to fix lookups, and is probably a waste of time.
January 30, 2013 at 2:26 am
Jason-299789 (1/30/2013)
Sorry I spotted that, and just changed them to work. Theres still a problem with the ISNULL though.this is the isnull
SELECT ID,COLOR
FROM #TBLCOLOR
WHERE ISNULL(COLOR,'')=ISNULL(@COLOR,ISNULL(COLOR,''))
Just bear in mind that can't...
January 30, 2013 at 1:41 am
karthik.catchme (1/29/2013)
The reason for shrinking the log is"a drive could have log files of multiple databases. If, one log file has over grown due to a big transaction
If...
January 30, 2013 at 12:44 am
Put in a request for an exception to that policy (you have a damn good reason).
What I suggest is a procedure with EXECUTE AS a higher privileged user (perhaps...
January 29, 2013 at 11:49 pm
@SQLFRNDZ (1/29/2013)
Could you please tell me what about it?
It contains the definition of all procedures, views and functions in your DB, which is what I thought you wanted out.
January 29, 2013 at 11:42 pm
Can you run CheckDB on the 2005 database? Or do you not have a pre-upgrade copy?
Did the DB switch into emergency mode without error?
January 29, 2013 at 3:26 pm
Check the 3rd party backup tool's log. That's not a native SQL backup, so whatever is running that backup should have the detailed log (the backup application log)
January 29, 2013 at 1:55 pm
January 29, 2013 at 1:23 pm
No clean backup I assume...
Script all objects (some will fail)
Export all data (some will fail)
Recreate the database.
January 29, 2013 at 1:20 pm
Don't even need a subquery. This should be perfectly legal code
select
S.agentNumber,
max(S.auditdate) as auditdate,
A.agencyName,
A.state,
A.region,
A.Parent
from
tblAudit_Auditschedule S
left outer join
tblAgents A
OnA.agentNumber = s.agentNumber...
January 29, 2013 at 1:17 pm
Problem 2 is reasonably easy
CREATE PROCEDURE FixMemory
AS
EXEC sp_configure 'max server memory', 3000
RECONFIGURE
GO
EXEC FixMemory AT <linked server name>
January 29, 2013 at 1:09 pm
Backing up and restoring will never fix corruption, because the corruption is included with the backup and restored with it.
Don't suppose there's a backup from before this started?
Can you query...
January 29, 2013 at 1:06 pm
Viewing 15 posts - 14,551 through 14,565 (of 49,552 total)