Comments
Sort by recent activity
I tried the restore with another account with sysadmin rights but I got the same results. I am trying it with the SA account and it looks like it is working. What rights do I need to give these other accounts in order to do the restore? / comments
I tried the restore with another account with sysadmin rights but I got the same results. I am trying it with the SA account and it looks like it is working. What rights do I need to give these ...
Sorry, I'm having the memory problem. AWE is on. Min Memory =0 Max Memory 3072 MB. Today I set the Min to 256 MB to see if that would help.
Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 7/12/2007
Time: 2:10:03 PM
User: N/A
Computer: SCS10PSSQL02
Description:
SQLVDI: Loc=BufferAreaManager::MapBuffers. Desc=Out Of Address Space. ErrorCode=(8)Not enough storage is available to process this command.
. Process=512. Thread=2500. Server. Instance=SQL2000. VD=Global\SQLBACKUP_690D9E54-3147-4530-B037-7BA589B1B005_SQLVDIMemoryName_0.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. / comments
Sorry, I'm having the memory problem. AWE is on. Min Memory =0 Max Memory 3072 MB. Today I set the Min to 256 MB to see if that would help.
Event Type: Error
Event Source: SQLVDI
Event Category:...
I have the same problem on one server. The server has one instance of SQL 2000 and one instance of SQL 2005. I use Red Gate to backup both. The 2000 instance frequently has this same problem but the 2005 instance doesn't. I recently upgraded to v5 of SQLBackup but it is still happening.
I had a problem before when DBMS_VER <> SYS_SPROC_VERSION but I'm not sure if they will be the same with hot fixes. I reran
osql -E -S <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
several times.
select * from spt_server_info
attribute_id attribute_name attribute_value
1 DBMS_NAME Microsoft SQL Server
2 DBMS_VER Microsoft SQL Server 2000 - 8.00.2040 (Intel X86) May 13 2005 18:33:17 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
10 OWNER_TERM owner
11 TABLE_TERM table
12 MAX_OWNER_NAME_LENGTH 128
13 TABLE_LENGTH 128
14 MAX_QUAL_LENGTH 128
15 COLUMN_LENGTH 128
16 IDENTIFIER_CASE MIXED
17 TX_ISOLATION 2
18 COLLATION_SEQ charset=iso_1 sort_order=nocase_iso charset_num=1 sort_order_num=52
19 SAVEPOINT_SUPPORT Y
20 MULTI_RESULT_SETS Y
22 ACCESSIBLE_TABLES Y
100 USERID_LENGTH 128
101 QUALIFIER_TERM database
102 NAMED_TRANSACTIONS Y
103 SPROC_AS_LANGUAGE Y
104 ACCESSIBLE_SPROC Y
105 MAX_INDEX_COLS 16
106 RENAME_TABLE Y
107 RENAME_COLUMN Y
108 DROP_COLUMN Y
109 INCREASE_COLUMN_LENGTH Y
110 DDL_IN_TRANSACTION Y
111 DESCENDING_INDEXES Y
112 SP_RENAME Y
113 REMOTE_SPROC Y
500 SYS_SPROC_VERSION 8.00.2039
Restarting the sql service fixes the problem for me. / comments
I have the same problem on one server. The server has one instance of SQL 2000 and one instance of SQL 2005. I use Red Gate to backup both. The 2000 instance frequently has this same problem but...
No, I'm not sure if I want to since it is a production server. Any idea when/if there will be a sp5? / comments
No, I'm not sure if I want to since it is a production server. Any idea when/if there will be a sp5?
We have the same situation but on a ia64 production box. Has anyone heard if/when MS will release a sp5?
We have 2 ia64 production servers and it works on one and not the other. / comments
We have the same situation but on a ia64 production box. Has anyone heard if/when MS will release a sp5?
We have 2 ia64 production servers and it works on one and not the other.
No, it worked on one of the ia64 boxes without needing any fix. The only difference in the two, that I can think of, is the box that works has sql 2005 installed on it too. / comments
No, it worked on one of the ia64 boxes without needing any fix. The only difference in the two, that I can think of, is the box that works has sql 2005 installed on it too.
That works. I didn't know what would happen when you say install on all nodes when it was already installed on 2 of them.
Thank you. / comments
That works. I didn't know what would happen when you say install on all nodes when it was already installed on 2 of them.
Thank you.
I have the same problem when I run the GUI on the server. / comments
I have the same problem when I run the GUI on the server.
I'm still have the problem after changing it to remove the history over 80 days. something must be blocking in the redgate file. / comments
I'm still have the problem after changing it to remove the history over 80 days. something must be blocking in the redgate file.
That is all of the log. The sql job is involved but the call to the backup is at the top of the log. Give me your email and I can mail it to you. / comments
That is all of the log. The sql job is involved but the call to the backup is at the top of the log. Give me your email and I can mail it to you.