Viewing 15 posts - 6,856 through 6,870 (of 7,498 total)
I also backup master and msdb everytime a scheduled backup is taken (full/diff/log) of any userdb.
November 17, 2004 at 11:53 pm
Can you force a table-scan on all tables of your db ?
select * from yourtable
Why : so no indexes (except clusterd) are used and only datapages are accessed. This way you...
November 17, 2004 at 1:59 pm
BACKUP DATABASE [master] TO DISK = N'\\ribackupsrv\BACKUP\masterfull.bak' WITH INIT , NOUNLOAD , NAME = N'master full backup', SKIP , STATS = 10, NOFORMAT
BACKUP DATABASE [model] TO DISK = N'\\ribackupsrv\BACKUP\modelfull.bak' WITH ...
November 17, 2004 at 1:45 pm
early in the morning
![]()
it just scripts the non sql7 stuff and haves you run into the...
November 17, 2004 at 2:59 am
Keep in mind a trigger fires every time the criteria meets insert or update (in your case) !
How many times do you predict this to happen and measure afterward...
November 17, 2004 at 2:50 am
brutforce way :
ALTER DATABASE yourdb Set READ_only WITH ROLLBACK IMMEDIATE
ALTER DATABASE yourdb Set READ_WRITE WITH ROLLBACK IMMEDIATE
if you want to have a criteria : sp_lock
create table #tmp_splock (
spid int...
November 17, 2004 at 2:43 am
That works fine if you don't use any sql2k features or new datatypes (e.g. tinyint, UDF,...)
November 17, 2004 at 2:20 am
Can you still script the job ?
if so, do you notice anything weird in the script ?
November 16, 2004 at 1:48 pm
check out "linked servers" in books online.
If this is only a one-shot event, it is best to use DTS for this kind of stuff.
You may want to read some more...
November 16, 2004 at 7:14 am
In addition to Max and Frank's clarifications :
One of the downsides of hints is that you'll have to check if they are needed with every hotfix/servicepack/upgrade you perform.
November 16, 2004 at 12:35 am
That's the concept of triggers, fire always when from the designed action. ![]()
If you have full control regarding the invocation of the designed...
November 16, 2004 at 12:20 am
It might even be from a _new_ mainframe db ![]()
November 16, 2004 at 12:07 am
If for any reason your database collation is changed, your existing tables will not be affected. If they used the "old" db-collation, they will still use the "old" db-collation, even...
November 15, 2004 at 11:48 pm
how about : ![]()
alter table mytable
alter column mycol type_and_length COLLATE mynewcollation
Ofcourse backup before!! ![]()
Maybe even script the full db, create...
November 15, 2004 at 8:36 am
Viewing 15 posts - 6,856 through 6,870 (of 7,498 total)