Viewing 15 posts - 2,086 through 2,100 (of 2,387 total)
I have few databases with same logical name after the restoration and never experience any problems. If you really don't like that, you always can change the logical name with...
March 27, 2003 at 6:14 pm
I would upgrade the MDAC in client machine to MDAC 2.7 SP1 which is the version in your server first. If it doesn't work, SQL Server 2000 client connective tools...
March 27, 2003 at 2:08 pm
Which MDAC version are on both your SQL Server and client machine? Do you see same problem if you run the same query from QA?
March 27, 2003 at 1:38 pm
You could use TSQL command BEGIN TRANSACTION and COMMIT in your main stored procedure that will calls the other three stored procedure. Be sure to make your three stored procedures...
March 27, 2003 at 1:32 pm
Very good suggestion. In order for your client to work with named instance, you have to upgrade client MDAC to version 2.6 at least.
March 27, 2003 at 1:23 pm
Are you running SQL Server and Agent services with local system account? If you are, you can't simply deny 'BUILTIN\Administators' account. You have to grant 'NT Authority\System' account to access...
March 27, 2003 at 1:19 pm
SQL Server 2000 does not allow text, ntext, or image column references in the inserted and deleted tables for AFTER triggers; however, these column references are allowed for INSTEAD OF...
March 27, 2003 at 10:07 am
Upgrade from 7.0 to 2000 will upgrade all program files and all data stored in SQL Server 7.0 databases is preserved. If you want to come back 7.0, make sure...
March 27, 2003 at 9:52 am
I have seen process sqlmaint.exe hung during the execution of jobs that are created by maintenance plan and jobs seem to run endless and can't be stopped from SQL Agent...
March 27, 2003 at 8:03 am
Did you see any errors in your SQL Server errorlog? There is an explanation in BOL for error 913 but it seems not relevant to database restoration directly.
Cash,
Try DBCC SHRINKFILE...
March 27, 2003 at 7:48 am
I would run same stored procedure from QA when the error message occurs from your Aceess to see any possible issues between these two SQL Server.
And ask your netwrok administrators...
March 26, 2003 at 7:20 am
I am confused by the term 'linked server' here. Are you running Access 2000 as front end to access linked tables via OLEDB/ODBC to database in SQL Server? How do...
March 25, 2003 at 2:41 pm
How stable is your network? Check whether you are able to login to SQL Server from QA each time you have this issue and ensure SQL Server is up.
March 25, 2003 at 2:13 pm
select col.name as ColName, obj.name as TableName, typ.name as DataType
from syscolumns col, systypes typ, sysobjects obj
where col.xtype = typ.xtype
and col.id = obj.id
...
March 25, 2003 at 1:59 pm
Do you run SQL Server default instance or named instance?
The MDAC version is 2.5 in W2K and it may be sp1 or sp2 depending on which W2K service pack...
March 25, 2003 at 1:17 pm
Viewing 15 posts - 2,086 through 2,100 (of 2,387 total)