What I have found on the 'net seems a little ambiguous whether or not something needs to be installed on the server to use the Sync Framework with SQL Server 2005.
My interpretation is no, that the ADO.NET'ness of the product reaches out to the server (assuming appropriately trackable tables exist).
My goal is to use SQL Compact on the client and Sync with SQL Server 2005 with no install on the server.
A little help would be great!
Thanks,
rusty
Other than the change tracking infrastructure (SQL Server 2008 Change Tracking or Triggers etc), you will not need to install any Sync Framework components on the SQL Server machine to be able to include it in a Sync topology.
Cheers,
Scott
As far as I know, SQL Server 2005 does not need the Microsoft Sync Framework installed.
Related
Is it possible to use Microsoft Sync framework with SQL Server 2000?
I tried, one way is working fine... from server to client. Bidirectional is not working. Changes made on the client are not updated to server.
Please let me know if there is any changes need to be done on server side to make it work.
Thanks Karthik
According to Microsoft Sync Framework on MSDN:
Sync Services for ADO.NET supports databases in the following ways:
In offline scenarios, the client database must be SQL Server Compact 3.5 version 3.5 or later. The server can be any database for
which an ADO.NET provider is available.
In collaborative scenarios, each peer database must be SQL Server 2000 Service Pack 4 or a later version.
So: do you have SP4 for SQL Server 2000 installed?
am assuming you used the Local Database Cache Wizard and you simply change the sync direciton to Bidirectional...
its not enough to just change the sync direction...try the steps here: Walkthrough: Extending the Local Database Cache to Support Bidirectional Synchronization
I was wondering if we could backup the database that we currently host on regular SQL Server, and put it onto our clients computer when we setup SQL Server Express for them.
Is this possible?
Thanks,
Matt
Yes, it's possible to restore a database backup from the Standard edition to the Express edition. It's not possible to restore a SQL Server 2008 to a SQL Server 2005 version, though.
However, there a some minor differences between versions. I've noticed an issue in SQL Server Express 2005 when calling .NET SQL CLR functions across databases, so your mileage may vary. I haven't been able to find a good overview of the exact differences between the various SQL Server editions.
It's always best to keep the development platform as close as possible to the release platform. I can only recommend that you use the Express edition of SQL Server for development as well; and re-test your application.
When in 'SQL Server Configuration Manager' I see, under 'SQL Server Services', 2 items that look like SQL Server's:
SQL Server (sqlexpress)
SQL Server (mssqlserver)
Does that mean I have 2 versions installed at the same time? The 'SQL Server (mssqlserver) is currently stopped).
You have two instances. They might or might not be the same version (meaning 2005/2008).
Express is just an SKU / edition from the myriad of different editions.
You can have the same version or multiple versions/SKUs installed as different instances on the same machine.
So unless someone wittingly set up a new instance with the name "sqlexpress", you probably have two kinds of products installed (both can be 2008 or both can be 2005 or they can be different - it is just that one of them is presumably the Express SKU while the other is say Standard.)
You can get more information on the instances by using ##VERSION.
It looks like you got SQL Server Express installed with Visual Studio and then later installed SQL Server 2008. I've done this before and the best solution I found was to completely uninstall SQL Server Express and SQL Server 2008. Remove all the files in the Microsoft SQL Server directory in Program Files, then reinstall SQL Server 2008. If you still have problems getting the 2008 instance to be the default, you may also need to uninstall Visual Studio.
In the future, if you're going to install the development (or other) version of SQL Server locally, I suggest making sure you install it before Visual Studio. The VS install won't install SQL Server Express if it detects an existing SQL Server instance on the system.
BTW, you can verify if this is true by using the Add/Remove Programs Control Panel item.
SQLExpress is the light/free edition, usually used for developers or very lightweight applications.
MSSQLServer is the full blown SQL install.
So yes you have 2 "SQL Server" installs, but they are different products, I can't say which versions based on your provided data.
You have two SqlServer instances installed on your system. One is SqlServer Express Edition and the other one a Sql Server. I can't say which version or edition.
Maybe you can find some more information in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft).
I'd vote against removing either one--SQL server does fine with multiple instances and they are good for different things. For example, lots of open source projects presume a local copy of sql express at .\SQLEXPRESS for development use. Whereas you can't write analysis service stuff with SQL Express.
Or, its not a problem. Those aren't the droids your looking for. Move along.
we have a local staging server running sql server 2000 and a remote public version also running sql server 2000. The remote version will be upgraded to 2005 and I am wondering if the DTS packages we have in place will continue to function between the two machines?
If not, what would be the simplest, most efficient way to sync between the two?
We will not be upgrading the local server, and the upgrade of the remote one will be taking place very soon (not in our control).
Thank you!
If your DTS packages reside on the local server, there shouldn't be an issue (aside from obvious changes to SQL itself (I.E. the old-school joins not working anymore)), and in fact, I've even seen developers save DTS packages on SQL 2005 databases though I'm sure it's not a very good idea.
EDIT: It might also be worthwhile to check out this link for the tools to design/modify DTS packages with SQL Server Management Studio.
I'm wondering if anybody has had any experience in trying to install SQL Server 2008 Express along side with SQL Server 2000. We have a production server running 2000 which all of our current stuff is running on. However, something new is in the pipeline that uses SQL Server 2008 Express.
Hitting Google thus far has given me nothing concrete. There was an obvious no from a preview release of 2008 but nothing about RTM 2008.
I could try installing it but would like to find out as much as I can before doing so. I can see the 2008 install failing, eating 2000 in the process.
The alternative paths that I have include having the 2008 db be turned into a 2000 format (which I'd like to avoid as we only have a 5 connection licenses) and building a new server (we already have enough and it seems overkill). Redoing the 2008 DB is viable as it doesn't use any new whiz-bang features from 2008.
Virtualization can be an option as well, but it's not quite in our cultural yet.
Any insights here will be appreciated.
Keith
yes you can, you have to make the 2008 version a named instance if the 2000 version is a default instance