I can choose synchronization direction for articles: a) Bidirectional b) one way
1) Is that possible somehow to replicate the schema only of an article but no synchronization / zero direction :-)/
2) Same question about columns, I should replicate schema only for few columns, but without data synch. These columns are freely updateable at anywhere (publisher and subscribers), but the data changes shouldn't be replicated.
I need to replicate data from an Access (95-97) database to my SQL Server 7.0. There is a lot of different techniques availible, unfortanly none of them are easy and performance is also often bad. Suggestion for a way to do it will be appreciated. The following considerations exist. * Data only to be transferred from access database to MS SQL Server * Tables in Access database contains a large number of records (, that might change. * Development of a program in VC60 or VB60 is OK
Not sure if this is the right forum, if wrong please point me some where else.
I have a legacy applicatioin using Access97 which relies on users being able to synchronise their data I would like to move the current Synchronise in to c# Visual Studio 2005/8
is this possible? if so what are the new methods called and how can I access them
Is there any reason why an application running on a 32-bit O/S that works with a SQL Server 2K database would not work with a SQL Server 2K5 64-bit database running on a 64-bit O/S?
It is my understanding that the connection layer (be it ODBC, OLEDB, ADODB, etc) would obfuscate any details regarding the underlying architecture... I wouldn't think the instructions sent would need to be any different, unless there is some deprecated call that is no longer supported.
I have installed in a workstation (windows xp pro) sql 7 server (database engine + client tools). After that I installed sql server 2005 with named instance (hostmyinstance).But I didn't end this installation. I had a message saying me that there are problems on clients tools. moreover when I open a dos window and type "sqlcmd", I have the same message (client problems). I then change my sql7 port to 1434 (which isn't the default port).But even with that my sql 2005 sqlcmd don't work correctly. My question is :
can one install sql 7 (server + client tools) and sql 2005 (server + client tools) in the same machine ( a workstation [windows xp pro] )?
For a SQL/2005 DB Server do I need the /3GB switch or not? I will have IIS running on the server; however, it won't be doing very much as the SQL Database is the main thing:
Windows 2003 R2 Enterprise w/16 GIG RAM 4 CPU (Virtual Machine) SQL/2005 Enterprise Edition
Hardware: Dell Server 8 CPU w/32 GIG RAM running VM ESX V3
I know I need the /PAE switch to utilize Memory over 4 GB - the question is do I need the /3GB switch along with the /PAE switch?
I need tyo move tables from Oracle 9.2 or 10.2 version to SQL server 2005.Can any one give me some good hints, scripts etc.I try to look into the Business Intellegent Studio, but I only see Report,Analaysis or Integration services - NO DTS.Can someone tell me where to find it. It used to be so easy in 2000.Thanks,Nasir
I have a partition view named StudentRequest with underlying tables StudentRequest_T1 and StudentRequest_T2.
Primary Key is on NumericSchoolDBN, SchoolYear, TermId, StudentID, CourseCode
Partition View
Create View dbo.StudentRequestPartView with SchemaBinding as Select NumericSchoolDBN, SchoolYear, TermId, StudentID, CourseCode, AssignedCourseCode, AssignedSectionId, LockAssignedRequest, UpdatedByPID, UpdatedDate, CreatedByPID, CreatedDate, AuditCommentId, DebugTrace from dbo.[StudentRequest_T1]
union all
Select NumericSchoolDBN, SchoolYear, TermId, StudentID, CourseCode, AssignedCourseCode, AssignedSectionId, LockAssignedRequest, UpdatedByPID, UpdatedDate, CreatedByPID, CreatedDate, AuditCommentId, DebugTrace from dbo.[StudentRequest_T2] go
Partition Tables
CREATE TABLE [dbo].[StudentRequest_T1]( [NumericSchoolDBN] [int] NOT NULL, [SchoolYear] [smallint] NOT NULL, [TermId] [tinyint] NOT NULL Check ([TermID] = 1), [StudentID] [int] NOT NULL, [CourseCode] [varchar](10) NOT NULL, : )
CREATE TABLE [dbo].[StudentRequest_T2]( [NumericSchoolDBN] [int] NOT NULL, [SchoolYear] [smallint] NOT NULL, [TermId] [tinyint] NOT NULL Check ([TermID] = 2), [StudentID] [int] NOT NULL, [CourseCode] [varchar](10) NOT NULL, : )
I am able to insert, update and delete records in the StudentRequest view using simple DML SQL statements i.e.
e.g. Insert into Student Request (NumericSchoolDBN, SchoolYear, TermId,€¦) Values(12345, 2006, 1,€¦)
Delete from StudentRequest Where NumericSchoolDBN = 12345 and TermId = 1
But when I use complex SQL statements using self-joins€¦
Insert into Student Request (NumericSchoolDBN, SchoolYear, TermId,€¦) Select NumericSchoolDBN, SchoolYear, TermID,€¦. From Student Request sr1 left outer join Student Request sr2 on Sr1.NumericSchoolDBN = Sr1.NumericSchoolDBN and Sr1.SchoolYear = Sr2.SchoolYear and Sr1.TermId = Sr2.TermId and Sr1.StudentID = Sr2.StudentID and Sr1.CourseCode = Sr2.CourseCode
I get the following error and I can€™t seem to find any documentation that this is a limitation!!!...
Msg 4439, Level 16, State 6, Procedure Course_UpdateCoursePromotion, Line 232 Partitioned view 'STARS.dbo.StudentRequest' is not updatable because the source query contains references to partition table '[STARS].[dbo].[StudentRequest_T1]'.
We recently migrated from a SQL 2K to 2K5. We had an automatic DTS scheduled every night that would transfer data to a MySQL server on one of our client€™s machine. It worked like a charm in SQL 2K.
I am trying to figure out how I can connect to a MySQL data source using SSIS in 2K5 as I don€™t see an ODBC Destination anywhere in the Data Flow Task; and run the same transfer using 2K5.
Do I have to add a reference of some kind or does 2K5 doesn€™t support ODBC destinations?
Having problems installing SQL 2005 Developers Edition on a Terminal Services Server that already has SQL 2000 Developers Edition on it. I keep getting this error, no matter in what order I install packages:
Failed to install and configure assemblies M:Program FilesMicrosoft SQL Server90DTSTasksMicrosoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2147024894 Error message: The system cannot find the file specified. Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
The help link says to set the DTC service up to run as a network service and start it, but it already is and is already running. Restarting the DTC and then clicking on retry yields the same error.
Any ideas? I've been beating my head against this machine for a couple of days now.
I need to get a server built for a client today. He has sent me the proof of purchase for his SQL2005. He is working on getting me the licence / cd key today (if thats even possible?).
I have our SQL 2005 server CD here that I wanted to use however when I get to the company name stage of the install the CD-key/licence code is greyed out. Any ideas on how I can change the embedded cdkey/licence to the clients so I can use our media today but with our clients cdkey?
This needs to be done today, its extremly important but due to a problem with logistics the media from the client was delayed untill mid next week.
I continue to have issues with SP-2 for SQL 2005 suite. It has now gotten so bad, I have multiple installations, including the TOOLS ONLY on my laptop failing, that I am going to stop ALL future installations of SP-2. The COM+ failures have not been resolved that I can determine. I have tried uninstalling, I have tried SP-1 before SP-2, every combination one can find. HELP.
Time: 05/07/2007 13:24:05.631 KB Number: KB921896 Machine: GA029-MDGRAVES OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.00.1399.06 x86 SQL Server Native Client ENU 9.00.3042.00 x86 Client Components ENU RTM 9.00.1399.06 x86 STANDARD MSXML 6.0 Parser ENU 6.00.3883.8 x86 Backward Compatibility ENU 8.05.1054 x86
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID
********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : SQL Server Native Client Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Client Components Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log Error Number : 29549 Error Description : MSP Error: 29549 Failed to install and configure assemblies c:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087 Error message: Unknown error 0x80131501 Error description: MSDTC was unable to read its configuration information. (Exception from HRESULT: 0x8004D027) ---------------------------------------------------------------------------------- Product : MSXML 6.0 Parser Product Version (Previous): 3883 Product Version (Final) : 6.10.1129.0 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_msxml6.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Backward Compatibility Product Version (Previous): 1054 Product Version (Final) : 2004 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SQLServer2005_BC.msi.log Error Number : 0 Error Description : ----------------------------------------------------------------------------------
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 29549
I installed SP1 for SS 2005 on a quasi-production server, which is why I didn't mind rebooting the server. Unfortunately, it's been 5 hours and the server still hasn't rebooted. (I see a gray screen and a pointer, and that's it... but there's still disk access happening. I'm not really sure what it's doing.)
What's the best way to avoid the 5 hour reboot in the future?
In a nutshell, I want to do a merge replication with a SQL Server and several Access databases. I haven't been able to find anything in the documentation or 3rd party books.
does anyone know whether a SQL Server 2005 Everywhere database can be replicated with a common MS Access database? Is there any possibility to synch a database on a mobile device (SQL Everywhere) with a central database on a server computer (like MS Access or SQL Express) without having to use a full version of SQL Server? Replication is just needed for merging a small database (4-5 tables) so I think the full version of SQL Server is a little bit oversized for this issue (and too expensive, too).
Is it possible to convert a SQL2K datafile to SQL2K5? I have a 2K database that I need to easily convert to 2K5, I apprecaite any insight on this issue.
Hello All: From my previous post it seems that the general consensus is for me to use backup and Restore to upgrade a dB from SQL2K to SQL2K5.
Could anyone refer me to some explicit instructions for doing this?
I have SQL2K5 and SQL2K on separate servers and I cannot back the dB up to SQL2K5. I also can't access the drives for SQL2K from SQL2K5. I'm hoping it's a simple mistake.
I want to copy a SQL2005 database to a SQL2000 environment? I created a backup from the DB in SQL2005 and moved the file to the other server but SQL2000 says the BAK file is invalid since the backup has structure version 611 while the server supports version 539. Any solution?
I've populated reporting DB's in the past using different techniques:
1. Have Transactions in Data Tier Write to OLTP AND Reporting DB Simultaneously
2. Log Shipping
3. Restore BAckups Nightly
4. Replication
5. DTS
My question is what is the BEST Practice in SQL2k5.
I'm all gung ho about using Mirroring but am not certain that this will be the best way to go.
My thoughts are something along the lines of this
1. have OLTP Mirrored to what I'll call a "Staging" DB. This is NOT to be used for Failover just as a means of accessing read only data for the Reporting DB
2. Have 2 DBs on another box that are flattened (Denormalized) for reporting (ReportA and ReportB)
3. Use SSIS to Populate the Report DBs in alternating sequences every XXX minutes (60 minutes let say)
4. Use Logic to let the Reporting Application Figure out which of the Two reporting DB's is "live". The Currently loading DB will be offline while it's being loaded and we'll alternate between the two (Exact method TBD but this wont be rocket science)
Now, I know this will "Work" but is this the best way to go about this ?
I do NOT want to use SSIS to populate the Reporting system directly from our OLTP system due to contention issues etc.
I got following error when try to expand msdb under SSIS in SSMS, the SSIS I connected to is on clustered server. The windows account used is member of local admin on both nodes in the cluster and sysadmin in sql. I tried with host name that SSIS runs on and virtual sql server name for connection, tried connect from remote client machine and server itself, got same error:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
Login timeout expired An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
Login timeout expired An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
Executing the statement: select * from test2.database.dbo.table
gives the following error:
Server: Msg 7356, Level 16, State 1, Line 1 OLE DB provider 'SQLNCLI' supplied inconsistent metadata for a column. Metadata information was changed at execution time. OLE DB error trace [Non-interface error: Column 'IsActive' (compile-time ordinal 2) of object '"database"."dbo"."table"' was reported to have changed. The exact nature of the change is unknown].
If i change the statement to
select * from openquery(test2,'select * from database.dbo.table')
It works. I don't really want to have to go and refactor all the SQL though!
I've seen similar posts related to Oracle and SQL2k5 64bit but they don't seem to be relevant to this situation.
Here's the version info:
2000 server (SP3):
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2005 mirrored servers (SP2 3054):
Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86) Mar 23 2007 16:28:52 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
I've also tried applying the following to the 2005 servers: sp2(3159) sp2(3161) but makes no difference.
Well I will be developing SSIS package which source will be MySql and destination will be SQL Server 2005. As i noticed, there is significant difference between MySQL and SQL data types; I would to have you guys' opinion that is SSIS smart enough to handle those differences or I should plan some strategy to deal?