What changes do I need to make to get my entity data model to a new database instance on another server running SQL Server 2008 R2? I have changed the connection string in the Web.config and changed ProviderManifestToken="2008". If I try to refresh or make any changes I am given errors stating that nothing is mapped any more. Thank you for your help!
Just some general advice: first migrate the model with data from SQL Server 2005 to SQL Server 2008 R2 (use any approach, for example, this or this).
After this create a brand new entity model on SQL Server 2008. Compare the models' XML, make necessary changes in the model created for SQL Server 2005 (maybe you made a mistake in the ProviderManifestToken spelling).
Check that the data types are correspond, and actually that's all.
Related
Versions in use:
SQL Server 2016
Azure Data Studio 1.36.2
SQL Server Schema Compare 1.13.1
Problem: there is something wrong with my Azure Data Studio apply schema to SQL Server 2016.
It say I'm not the login manager but there is no login manager role in SQL Server.
And it has worked before updating Azure Data Studio to v1.36.X
https://imgur.com/a/JFWFOtn
Finally, I found the problem
Misused sqllinlinetablevaluedfunction and sqlmultistatementtablevaluedfunction
In my project There are many function use sqllinlinetablevaluedfunction instead of sqlmultistatementtablevaluedfunction but It's should be used sqlmultistatementtablevaluedfunction
so I change to Correct Type then It's worked. The error never show
I have made a relational diagram in Oracle Data Modeler. Now I want to use it in microsoft sql server to write queries on it. How should I do?! I know I have to import it but I couldn't find how...
Set the relational model properties to 'SQL Server' for site type - SQL 2008 is the highest we support at this time.
Now create a physical model, of type SQL Server.
Now export your model to SQL - use this button
Set your options, and go.
We won't create a database for you. You'll need your own SQL Server already up and running, but then you can have your objects created.
Our clients wnat us to retreive data from SQL Server 2000. It is unknown whether they have any service packs installed for that SQL Server. Assuming the worst (no sp), will there be a problem using OleDb driver to work with SQL Server 2000?
OleDb is working fine without any sp.
Once your databases are converted from SQL Server 2000 to SQL Server 2005, is there any way to compare DTSs on two servers to see if they are still essentially the same? I need to see if my dev and prod are the same, and comparing them manually is really time consuming.
If they were still in 2000, I could use the Red-Gate tool DTS Compare, but that doesn't work in 2005. I can save each as a Visual Basic file, and then compare those (and that kind of works), but the steps may be output in a different order. Is there something out there that is better?
I would say, don't use DTS jobs in SQL Server 2005.
There are a complete new and reworked method to do those things: SSIS.
Here you find an introduction:
http://www.accelebrate.com/sql_training/ssis_tutorial.htm
Yes, maybe you can't compare it perfectly, but DTS Jobs are run out of support since SQL 2005 (remember, we are in 2009 :) )
Is there a way to get SQL Server 2005 to query 3 or more separate Access databases (each returning 1 record) in one SQL statement?
Yes, but it will require you to create a Linked Server instance for each Access database. See here for details about creating Linked Server instances on SQL Server 2005 to MS Access.
Once you have those in place, you can query SQL Server and it will pass on the queries to the respective Access databases based on using the Linked Server instance notation when specifying tables in your SQL Server queries.
What you want is a Linked Server for each of the Access databases.
Just be aware that in SQL 2005 64-bit you won't be querying current versions of Access or Excel through linked servers any time soon.
Yes, set them up as linked servers using sp_addlinkedserver.