New answers tagged sql-server-2005
update a set a.CHK = 1 from tableA a join tableB b on b.IDA = a.IDA and b.IDB = a.IDB
I tilted on your "data loss could have legal ramifications here" comment. Then, you definitely want to get a powerful 3rd party tool (like DPM) that can handle backups (and recover from catastrophics events in a flash and minimal fussing around) alot faster and alot better than any script you can pull off the Internet. Having backups is one thing. Knowing ...
you can create a table variable(or temp table) and insert all the .bak file metadata in that table and then fetch the row with max value of modified time. DECLARE @FileMeta table (columns nvarchar(200)); INSERT INTO @FileMeta EXEC sys.xp_cmdshell 'dir D:\FolderName\*.bak'; SELECT * FROM @FileMeta WHERE columns not like '%volume%' AND columns is not ...
You could consider raising a connect item (Microsoft bug report) as you have a reliable "repro", but then there are a number of workarounds for the problem - eg there is no real need for the APPLY, eg ;WITH TableA AS ( SELECT 101 as A_ID ), TableB AS (SELECT 1 as B_ID, 101 as B_A_ID , 'xxx' as B_Courses UNION ALL SELECT 2 , 101 , 'YYY' ...
There are a number of them, a lot of articles on the topic if you have google at it. Some of them: Default Schema for Windows Groups User Defined Server Roles Enhancments to Auditing User Contained Databases, authentication without logins. TDE - Transparent Data Encryption Hashing Functions - improved.
Since you have downtime, best is to use this powershell script- with backup restore option This script will take care of moving databases, logins, jobs,etc on the new server. make sure to use backup restore switch as opposed to detach/attach.
I'm currently working on this same issue. Here is what I'm thinking about doing to keep the entries in the database low. id | item_id | time_period | time_stamp | count id = unique, auto increment id item_id = the id of the item you are counting for time_period = the time period that you want to hold that count for options would be something like: ...
There is no built-in way to backup all the databases into a single file, and even if there was, that file would probably become impractically big. I would go with the ideas you got from your original question, and implement those in an automated script that loops through all your databases; One script to back every database up, one script to restore those ...
You mentioned you have 200 source tables and 225 databases. I am assuming the 200 source tables is a count of all tables from all the 225 databases (cause if you had 200 tables in each database that will put your total table count to 45000). You also mentioned that the schema of the database is the same for the 225 databases. You could build the SSIS ...
Top 50 recent answers are included