Viewing 15 posts - 3,331 through 3,345 (of 49,571 total)
Then you need to figure out what uses TempDB and whether it's correct usage or not, and whether there are transactions left open that keep the log from being reused.
April 5, 2016 at 8:07 am
Sounds like the backup was taken too early (and hence isn't quite in-sync with the replication).
You need to take the backup after creating the publication.
Create the publication. Set the options...
April 5, 2016 at 8:02 am
The script you posted, that you said you use to identify the foreign keys, will do exactly that, identify the foreign key constraints. It gives the table name and the...
April 5, 2016 at 7:47 am
ALTER TABLE <table name> DROP CONSTRAINT <constraint name>, instead of ALTER TABLE <table name> NOCHECK CONSTRAINT ALL. Make sure that you can put them back afterwards, and that they...
April 5, 2016 at 7:39 am
You cannot truncate a table that is referenced by a foreign key. It doesn't matter whether the constraint is enabled or not. If a table is referenced by a foreign...
April 5, 2016 at 7:26 am
The smallest one that supports the query.
While you can create a nonclustered and a clustered index on the same column, there's usually not much point in doing so. Unless the...
April 5, 2016 at 6:37 am
Your error was "log file is full". Full, meaning that the entire space in the file had been used up and there wasn't space available. That means the file is...
April 5, 2016 at 5:17 am
Green Armchair (4/5/2016)
It's a shame there is no "nolog" option for index rebuilds in FULL recovery mode.
There's no 'nolog' anywhere in SQL. All data modifications are logged. Some (like...
April 5, 2016 at 5:15 am
Siten0308 (4/4/2016)
April 5, 2016 at 3:07 am
coolchaitu (4/4/2016)
Dear Experts,Also, is there a way to find what caused tempdb to become full last night?
What kind of monitoring do you have on this server?
April 5, 2016 at 3:07 am
coolchaitu (4/4/2016)
Dear Experts,Can we shrink tempdb log file?
You can, but I don't know what you expect that to achieve.
The error said that the log was full, that is, the log...
April 5, 2016 at 3:03 am
We're missing the most critical information needed for a DR design.
What's your RPO and RTO?
What kind of disasters are you protecting against (for example, clustering won't protect against a SAN...
April 5, 2016 at 2:59 am
EXISTS (or NOT EXISTS in this case) can be cleaner and more intuitive as to what it's doing over a join/is null check.
Using John's tables
SELECTb.id
, b.name
FROM@records r
join@books b...
April 5, 2016 at 2:56 am
jacksonandrew321 (4/5/2016)
Try to run this:ALTER DATABASE Databasename
SET SINGLE_USER WITH ROLLBACK IMMEDIATE
GO
It won't work.
ALTER DATABASE requires that the session running it can connect to the DB. If the DB is...
April 5, 2016 at 2:47 am
Ok, so write the query. You had it almost right and you've had enough hints as to how to correct it.
April 4, 2016 at 9:57 am
Viewing 15 posts - 3,331 through 3,345 (of 49,571 total)