Viewing 15 posts - 391 through 405 (of 692 total)
Even after executing DBCC UPDATEUSAGE, the number reported in sysindexes is an estimate, so it may never show an exact count.
Steve
September 10, 2004 at 2:29 pm
I vote for your option. You could write a set based update, and a cursor based update against Pubs or Northwind and show the guy the difference in the estimated...
September 10, 2004 at 2:26 pm
Yes. SQL 2000 svc pack 3a, Windows XP Professional, svc pack 1, MMC 2.0. But I'm pretty sure that it has worked this way on other (earlier builds) machines as...
September 10, 2004 at 8:09 am
Karl made a very good point. One of the major things that will cause your msdb database to grow is backup history, especially in a log shipping scenario. I have...
September 9, 2004 at 4:43 pm
Its possible for you to block yourself from restoring a database. If you're doing the restore from query analyzer, first check that you are not connected to the database from...
September 9, 2004 at 3:49 pm
You can check the recovery model of your databases by right clicking on the database name, and select "Properties". From there, go to the "Options" tab. Recovery model is shown...
September 9, 2004 at 3:44 pm
DBCC SHRINKFILE will shrink the physical file, but if you're in a heavy transactional environment, that may not be desirable. First, you probably need to increase the frequency of your transaction...
September 9, 2004 at 3:38 pm
Hmm. I haven't used enterprise manager for my restores in a very long time, but, without actually restoring anything, I selected a transaction log backup to restore, and Enterprise manager...
September 9, 2004 at 2:39 pm
Not good.
Is your disk out of space?
If so, do you have another disk that you can use or can you free up space on that disk?
According to books online, this...
September 8, 2004 at 11:58 am
Assuming that the accountnumber in table 1 is a char or varchar column, and in table 2 it is an int column,
Select *
From Table1 as a
join Table2 as b...
September 8, 2004 at 11:47 am
Paul,
You MUST select
"Leave database nonoperational but able to restore additional transaction logs." on EVERY restore except the last one.
This means that you have to do that on the original...
September 8, 2004 at 11:39 am
Your MSDB database file is full. Right click on MSDB, select "Properties", click on "Data Files", and increase the size given in "Space Allocated (MB)" .
Steve
September 8, 2004 at 11:26 am
Double them up. ie. the percent sign '%' is a wildcard to sql. To look for a percent sign specifically you would place it in the literal twice - patindex('%%')
Steve
September 8, 2004 at 10:15 am
Paul,
While in the Restore database dialog, click on the options tab, and select
"Leave database nonoperational but able to restore additional transaction logs."
for all but your last restore. When you restore...
September 8, 2004 at 8:38 am
Here's an example. You'll need to use sp_executesql, and be sure to define the @ncommand (in your case, @sql) and the @nparmlist as nvarchar, not varchar.
declare
@ncommand nvarchar(1000),
@nparmlist nvarchar(100),
@fname varchar(20),
@lname...
September 7, 2004 at 4:25 pm
Viewing 15 posts - 391 through 405 (of 692 total)