If you can get an ODBC driver from Intersystems Cache then you can setup a linked server to the remote systems then yes. If you can’t get an ODBC driver for it then no.
Follow the below article for step by step guide for upgrading the windows server from 2003 to 2008 while maintaining the data & AD http://blogs.technet.com/b/omers/archive/2010/06/30/step-by-step-guide-for-upgrading-active-directory-from-microsoft-windows-2003-to-microsoft-windows-server-2008.aspx Also you can recover your AD in previous state refer this article for the same http://gallery.technet.microsoft.com/Tracking-Controlling-4dafc8a2
In SQL 2008 yes you can have bi-directional transactional replication. You have to set it up manually using the stored procedures as you need to set the @loopback_detection parameter when running sp_addsubscritpion. Depending on your requirements peer to peer replication might be a better choice.
Sounds like you installed the eval license on your desktop but the actual licensed copy on the server (hopefully). You’ll need to uninstall management studio on your workstation and reinstall it from the CD/DVD that it came on.
As far as the SAN is concerned SQL Server database files are just files stored on the array. It will transfer them just like it will any other file. Typically SAN to SAN replication is used along with geographically distributed clusters in order to have a single Windows (and SQL) cluster built in two [...]
It is hard to see exactly what you are doing. Looks like a RUNSQLSTM If so, can you just paste the source code. BTW, if it is RUNSQLSTM and all you are doing is a SELECT, then that is the problem. With RUNSQLSTM, you can Update, Delete, Insertt, Create, everything except a simple SELECT.
A stored procedure is a set of SQL statements that can be shared by multiple programs. You can find more of an explanation here: ”Stored procedure“
Use an EXCEPTION JOIN to only insert/update those records that do not already exist in the table.
After the install is complete, Open SQL Server Management Studio and connect to the instance that you just installed. From there, you can do anything you need to do in the instance. Configuration, Create Databases, Set up security.
Odds are you’ll need to look at index usage and find your missing indexes and create the ones that are missing. A lot more information needs to be provided before we can recommend a specific solution.
It sounds like you need to look into some sort of high availability solution. With SQL Server 2008 you can look at database mirroring which would handle all the resyncing of data between the primary and secondary server automatically when the failed server comes back online. There’s a wealth of information available on the net [...]
We’ve seen this question before, so this thread should help you: Acquiring the AdventureWorks database for SQL Server 2005 (downloads can be found via MSDN and Codeplex).
Encrypted File Service or EFS ? I do not think BCP has any way to encrypt the data that it is pulling out of a table. I think you will have to use a third party tool in order to encrypt the file that you have created with the BCP operation.
Based on what you’ve provided (and given that I can’t really read the samples you provided) you’ll want an inner join like this. select {your columns} from contracts inner join (select distinct calltype, controlnumber from Equiptment where calltype is not null) equiptment on contracts.calltype = equiptment.calltype
select status, city, COUNT(*)*100./(select count(*) from tab t2 where t1.city =t2.city ) from tab t1 group by status, city
The reason that this is happening is because you are forcing the user to change their password on the first login, but the ODBC DSN creator doesn’t support this. You need to have your application correctly prompt the user to connect. On a separate note you’d be better off not requiring that the DSN be [...]
Just a single table with 3 columns (name,project,hours), the following works fine, but is there a better way to right this? SELECT DISTINCT name FROM WorksOn a WHERE NOT EXISTS (SELECT * FROM WorksOn b WHERE b.name = ‘Smith’ AND NOT EXISTS (SELECT * FROM WorksOn c WHERE a.name = [...]
P4HT that is about in year 2004
Temporary tables will be deleted automatically when the connection that was using them is disconnected. If there are normal tables those will be deleted automatically when the SQL Server instance is restarted.
A quick Goggle search gave the answer as iPhone and iPad. Here is the web address that you can read further: http://itunes.apple.com/us/app/sql-server-mobile-database/id387301608?mt=8





