Viewing 15 posts - 376 through 390 (of 526 total)
I am a little confused. I'm making a lot of assumptions.
I'm guessing here, he linked in the tables and all the tables now are named something like "dbo_table1", "dbo_table2", etc....
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 10, 2005 at 8:23 am
That will work.
Thanks. Just didn't spot it in the BOL the first and second time through (smacking forehead
) Ouch! that hurt. 
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 8, 2005 at 4:57 pm
There shouldn't be a difference either way you do it.
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 8, 2005 at 12:42 pm
We are running a physical dual 1.8 and a dual 2.8 with hyperthreading. SQL2K standard edition. It looks like 4 processors to the server. We haven't had any problems.
On the...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 8, 2005 at 9:18 am
I found my own error.
In the second fetch, I missed the "INTO @StrSQL". ![]()
It messed with my mind ![]()
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 4, 2005 at 9:13 am
Our policy is that a non-technical person should be able to do the restores based on our policies and instructions. You never know how many of your I.T. people may be...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
February 25, 2005 at 10:21 am
The one that I found in upgrading is that the Yes/No has to translate to the smallint (not bit) if you are front-ending with Access 97. It may have changed...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
February 22, 2005 at 7:10 am
Going to ask the dumb question
....
What's GMAIL?
Second dumb question.....
Do you really want to leave your e-mail addresses hanging out on a public board...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
February 18, 2005 at 3:49 pm
If you are trying to FTP that is a whole different animal.
But it is conquerable.
This will need to be a several step...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
February 18, 2005 at 3:44 pm
You would need either use an ID that has implicit rights to the directory.
The other possibility is run a "net use" command first.
Such as
USE masterEXEC xp_cmdshell 'NET USE \\server2\backups\sqldumps...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
February 18, 2005 at 1:09 pm
You're welcome. ![]()
Have a great day! ![]()
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
February 18, 2005 at 10:38 am
It looks like that backup is corrupt. I would suggest manually doing another one, and seeing if that one will work.
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
February 18, 2005 at 9:15 am
Try
select *
from sysobjects
where uid 1
Hopefully that will show you where the problem is.
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
February 18, 2005 at 8:55 am
If you still have it as a dump device you'll need to drop it first before you can do the headeronly command.
When the sp_addumpdevice runs it locks onto the file...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
February 18, 2005 at 8:49 am
Issue number 2 is easier to answer first: sp_changeobjectowner
SELECT 'EXEC sp_changeobjectowner @objname = ' + CHAR(39) + TABLE_NAME + CHAR(39) + ...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
February 18, 2005 at 8:26 am
Viewing 15 posts - 376 through 390 (of 526 total)