I was wondering if there are any problems with having a SQL Server 2012 replication publisher together with some SQL Server 2005 replication subscribers?
Does anybody have some documentation from Microsoft regarding this?
I'm asking because a colleague of mine keeps telling us that it will not work.
Does it also go the other way around? (2012 = Subscriber & 2005 = Publisher)
Thanks
Zarkos
Depends on the type of replication that you're using...
From MSDN:
A Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example: a SQL
Server 2005 Publisher running can have SQL Server 2012 Subscribers;
and a SQL Server 2012 Publisher can have SQL Server 2005
Subscribers.
A Subscriber to a merge publication can be any version less than or equal to the Publisher version.
Related
Are these functions available in SQL Server 2012 or older?
select IS_ROLEMEMBER ('db_owner');
select IS_SRVROLEMEMBER ('sysadmin');
I can not find any compatibility information in the online documentation here: https://learn.microsoft.com/en-us/sql/t-sql/functions/is-rolemember-transact-sql?view=sql-server-ver15
Is_RoleMember was introduced in SQL Server 2012.
Is_SrvRoleMember was introduced in SQL Server 2005 itself.
You can see when a particular feature was introduced by going through below links. These changes are coming under Database Engine Enhancements => Database Engine Security Enhancements
What is New in SQL 2005
What is New in SQL 2012
To see all the historical information about SQL Server versions, below link is very helpful: https://www.sqlshack.com/history-sql-server-evolution-sql-server-features/
I have two SQL Server 2008 instances, one running Workgroup Edition (publisher) and the other Standard (subscriber)
I am trying to replicate a database but I am getting errors when it tries to create the database at the subscriber because it thinks it is running SQL Server 2005 for some reason.
Has anyone had this issue before?
I am getting this error
Column Location in object Members contains type Geography, which
is not supported in the target server version, SQL Server 2005.
Have you checked compatibility mode for the databases?
For example:
SELECT compatibility_level
FROM sys.databases WHERE name = 'YourDBName';
I have a star schema but SQL Server 2005 always uses the clustered indexes to access a table. What parameters do I have to set to enable this optimization.
According to http://blogs.msdn.com/sqlqueryprocessing/archive/2007/04/09/how-to-check-whether-the-final-query-plan-is-optimized-for-star-join.aspx and the DWH datasheet of SQL Server 2005 both claim, that SQL Server 2005 support this feature.
What edition do you use? IIRC star query optimization is ONLY in the enterprise version of SQL Server 2005.
I'm working with a client who had a SQL Server 2008 converted from a SQL Server 2000 DB and one of the queries has quite dramatically increased in time since it was on SQL Server 2000.
However, if I change the compatibility level to 2008 in the DB, the query goes like a rocket (40-50 times faster).
The query does use a number of UDFs.
My questions:
- are there issues with running SQL2000 compatibility in SQL Server 2008
- has SQL Server 2008 improved the performance when using UDFs?
There are some other things you might want to do after upgrading. See the "After upgrading..." section here: http://msdn.microsoft.com/en-us/library/bb933942.aspx
I believe its possible to run SQL 2000 DTS packages on 2008 with a compatability layer. But is it possible to do the same with DTS packages created on SQL 7? Is there any MS KB or note that points out if this is even a possibility.
Haven't found the KB article at Microsoft yet, but here's a bit more info. Doesn't look like you can do what you want w/o moving to SSIS.
Version of SQL Server that can be reverted to can be one of the following:
60 = SQL Server 6.0
65 = SQL Server 6.5
70 = SQL Server 7.0
80 = SQL Server 2000
90 = SQL Server 2005
100 = SQL Server 2008
Note: Compatibility level 60, 65, and 70 [are] no longer available in SQL Server 2008. And future version[s] of SQL Server will support only two (2) prior version[s] of backward compatibility.
Maybe 2005 but not SQL Server 2008. Can you not move it to SSIS?