An organization wants to shift back from 2008 to 2005: I can't influence this.
What would be the most significant problems based on your experience that I could face?
I have noticed that the data type Date is going to affect the shift back.
Related
I have been using a SQL Server 2008 Express R2 database for a few months now. Recently, one of my tables started timing out if I try to make an UPDATE through code or through Management Studio. I have tried making changes via the designer in management studio as well, and the same thing.
What can cause a single table to time out like this? My other tables are instant response to my changes, but this one just refuses to let me make any changes.
It sounds like your bad table has some kind of trigger attached to it. I suggest firing up SQL Profiler to see exactly what queries are being sent to the table.
A friend recently asked me to help him to change an application to allow multiple instances connecting to the same back end database. However, he has very limited understanding toward the inner work of the application or CS in general, and the guy who had developed the application for him has left.
My guess is that it is possible to get it done by making some simple changes to the application's database connection properties. The problem is that I have no idea how the database was set up. A note left by the previous developer mentioned that the database was created in SQL Server 2000. I do not have SQL Server 2000 around though. Is it possible at all to open/migrate the SQL Server 2000 database to SQL Server 2008 Express, and if so, how can I do it? If not, what the reasonable approach for the DB migration?
Thanks a lot for your help!
--Angler Y.
Yes, you can migrate the database using simple detach-attach method or backup-restore method
BUT
if the database size exceeds 4 Gb it woun't work on Sql Express 2008
When I provision a scope for synchronization in an SQL 2008 database like this:
SqlSyncScopeProvisioning sqlServerProv = new SqlSyncScopeProvisioning(sqlServerConn, myScope);
if (!sqlServerProv.ScopeExists(scopeName))
{
sqlServerProv.Apply(); // Apply the scope provisioning.
}
i see a bunch of change tracking tables, stored procedures and triggers created.
Why is this not using the "Change Tracking" feature of SQL 2008, which is much cleaner and everything gets tracked behind the scenes?
I thought that the "Change Tracking" feature of SQL 2008 was designed precisely to simplify these scenarios.
Now turning the question around: Is there a way to do a 2-way synchronization between two SQL Server 2008 databases just using Change Tracking in both of them instead of provisioning the triggers/auxiliary tables ?
See Syncing SQL Server 2008 Databases over HTTP using WCF & Sync Framework
I would like to know the easiest and fastest way to retrieve data from SQL Server 2008 R2 via Sharepoint 2010.
I am new to sharepoint but have been able to create an external content type using Sharepoint designer which connects to the database in SQL Server but I have not been able to use the business web chart to relay the data gotten from the database.
I want to relay information from a customer service database into sharepoint and want it to be consistent.
Is this the best way to go about it or is there a better way?
Many thanks for your usual cooperation and response.
Cheers,
Tunde
Your best bet is SQL Server Reporting Services, which will need to be installed in Sharepoint integrated mode. It does not have to be 2008 R2, it can be 2008, and the good news is that if you run reporting services on the same server as your SQL databases, you're already licenced for it.
Take a look at http://www.bidn.com/ for more answers, or ask questions using the #SQLHelp tag on twitter for SSRS, or #SPHelp for sharepoint
I found this extremely old document which appears to say that many of the web client features are not availiable when running on express edition--scheduling, subscription, etc--as well as no access to the report builder. Is that information still current, and are there any other features which are unavailable?
Subscriptions and scheduling are indeed absent in both MSSQLEx2005 and MSSQLEx2008, but I have never found this to be much of a problem. The underlying platform has a scheduler and the web service will do all the rendering, so you can recreate the missing elements without too much trouble.
The report builder is also absent, and this is non-trivial to replicate. You could always install SQLEx locally and let them use BIDS. Or you could stop being cheap. It's pretty good for free.
I recommend you use SSRS2008 rather than 2005 because it no longer requires IIS, and there are several sexy new capabilities in the report engine. In particular it now supports flow-based rich text with inline fields for mail-merge type reports.
Compatibility is excellent but some applications reject a newer database engine version. If this is a problem, continue to use SQLExpr2005 for the database.
So, are you saying that A) SSRS 2005
requires IIS whereas 2008 does not,
and that B) SSRS2008 is backwards
compatible with a SQL2005 database?
(It sounds like you might be saying
that SSRS 2008 could be used with
somebody running 2005 DBs
Yes, I am indeed saying that
SSRS 2005 requires IIS whereas 2008 does not
SSRS 2008 is backwards compatible with a SQL2005 database
SSRS 2008 could be used with somebody running 2005 DBs, or even 2000 DBs.
You can use SSRS with any database server for which ADO.NET drivers are available, including Oracle and MySQL.
I've caught somewhere the idea about rich text in SSRS 2008.
As I see it will allow me to make such static text
"Some test with some text in bold and some italic text"
with a single text box which was impossible in RS 2005. (even don't know good way to make it there)
You wrote it doesn't require SQL Server 2008 to be installed.
What about IDE for reports development ?
Looking forward with big hopes for SSRS 2008,
thanks for attention in advance,
Alex