Thanks for the info on the SQL version. I have the SELECT as you described with the following result:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
So...
...SCHEMA CACHE FALSE
SCHEMA CACHE DIR
ENABLE BCD FALSE
ROWSET SIZE 20
BLOBS TO CACHE 64
DB INFO
TYPE Microsoft Access Driver (*.mdb)
PATH
Excel Files
DB OPEN
DATABASE NAME
USER NAME
ODBC DSN Excel Files
OPEN MODE READ/WRITE
SCHEMA CACHE SIZE 8
SQLQRYMODE...
Sorry, I need to clarify on the SQL client tools installed on the workstations:
We DO have the client tools installed: SQL Server 2000 Client tools with SP4.
Take Care,
Mike
Our specs are:
Goldmine SQL Server Version: 8.0.194 (SP4)
Workstation SQL Client: None, we run Goldmine off the server install (on db server).
Protocols / ports: Runs on the db server (local).
Server OS: Windows NT 5.2 Build 3790 (Windows 2003 SP1)
Thanks for taking the time to help on this...
Thanks for the reply. We run database maintenance on a nightly basis, which does a backup, shrinks the logs, and checks the integrity.
Additionally, I have run many DBCC tests of my own on the various tables that the Goldmine errors list. (Un?)Fortunately they don't report any issues.
However...
...by the actions we tool to attempt to resolve it:
General SQL error.
Native SQL error: 10025
Context: SQLQuery: GM_GMBase:
set rowcount 1 SELECT * FROM dbo.CAL (NOLOCK) WHERE ALARMFLAG = 'Y' AND USERID = 'PKHANDJI' AND (ALARMDATE <= '01/28/2008') ORDER BY ALARMFLAG ASC, USERID ASC...
Thanks so much for your help! You pointed me in the right direction. The actual problem is not with the database settings, but the developers of the database. There are only two "rogue" stored procedures that use the double-quotes (erroneously). I am assuming these are unused stored procedures...
Following this thought through, I should theoretically then turn QUOTED_IDENTIFIER off in the replication scripts. Is there any way to do that? I have not see a flag that enables this setting under the various replication areas.
Take Care,
Mike
Looking at this article (http://doc.ddart.net/mssql/sql70/set-set_30.htm), it seems that QUOTED_IDENTIFIERS should be turned off, as otherwise the quoted text will be interpreted as a database object (i.e. column or table).
Take Care,
Mike
...filtrar por @PK (-1 no hace filtro)
@strVALOR AS VARCHAR(10) -- Valor para filtrar por @PK ('-1' no hace filtro)
AS
----------------------
-- * COMENTARIOS * --
----------------------
-- El que no haya homogeneidad en cuanto a los campos clave de las tablas según el tipo y
-- tamaño...
As a follow-up: the error references HD_Problemas_Productos_437.sch. Here's the content of that script:
SET QUOTED_IDENTIFIER ON
GO
drop table [HD_Problemas_Productos]
GO
SET ANSI_PADDING OFF
GO
CREATE TABLE [HD_Problemas_Productos] (
[IdProblemaProducto] [int] NOT NULL ,
[IdProblema] [int]...
Hi All,
I have set up a pull subscription, but everytime I run it, I receive the following error (I have captured this to an output file):
I have been absolutely unable to find any help googling the error. Does anyone have any ideas?
Thanks!
Take Care,
Mike
Hi All,
I am developing some reports in VS2005 in a Reporting Service project using the integrated report designer. The query runs just fine in the data tab and returns about 5000 rows. However, when I run the report in the preview tab, set my applicable report parameters (which should further...
Hey All!
I've been reading up on the UPDATETEXT functionality, and it seems like a step in the right direction, however: I am unable to find any examples that update text fields based on query results.
I'm looking for something like this:
UPDATE target_table SET target_field =...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.