Viewing 15 posts - 346 through 360 (of 526 total)
You need either a local or domain user that has local adminsitrative rights on the server the service is going to run on.
In addition, if using mixed mode authentication, and...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 3:54 pm
Note that none of the system databases (master, msdb, or tempdb) can do transaction log backups because they are in simple recovery mode (i.e. trunc. log on chkpt.) So you...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 2:26 pm
You are right about xp_fixeddrives. It's an undocumented xp. I thought it would show the drive. Dagnabit! ![]()
From a query analyzer window can...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 1:22 pm
Ok, the mapped drive does not show up using EXEC master.dbo.xp_fixeddrives
This means that the the SQL server service/agent isn't recognizing the the drives existence.
From a command prompt type NET USE....
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 12:18 pm
What user id is the backup job running under?
What user id is the the SQL Server Agent running under?
My thinking/things to check:
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 11:21 am
That would be more of a DTS (Data Transformation Service) than T-SQL.
I suggest you try playing with that - it can read from a text file, do edits (transact sql...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 11:09 am
I'm against the idea. Relying on an error to decide on an insert vs update just doesn't seem like the way to do it.
The cost to do a query and...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 11:02 am
You have two possible methods.
If you are trying to track on a table you can set triggers on the table and write it to a narc table
SET QUOTED_IDENTIFIER ON GO SET...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 10:05 am
I agree wholeheartedly.
We have a servicer/vendor supplied database (comes off a mainframe) that has an address table the is separate adress data addr_ln_1, addr_ln_2, city, state, zip with possible multiple...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 8:40 am
Are they always double-spaced?
You could try
UPDATE TEST_CUST
SET COMBO_COL = REPLACE(COMBO_COL, ' ', ', ')
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 8:13 am
Welcome to the asylum.
You found this place sooner than I did.
The big one I see in unsnarling your databases is knowing the...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 24, 2005 at 7:39 am
Try puttin quotes around it such as
/EXCLUDE:"\Thumbnails"
Another coudl be
/EXCLUDE:\Thumbnails\*.*
And try to making it the last in the string so that the /S /L is before it.
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 22, 2005 at 12:56 pm
Are you trying to exclude a directory(ies) named "\Thumbnails\" or the "Thumbs.db" files.
I would try it as just "/S /L /EXCLUDE:\Thumbnails"
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 22, 2005 at 10:58 am
Another possibility is to shut down the SQL Server Service, take a physical copy of the .mdf and .ldf and rename them.
Bring up the SQL service and try attaching the...
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 22, 2005 at 7:46 am
I'd also look if you are using the same tables.
Could someone have coded as "Char" fields instead of "VarChar"
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
March 22, 2005 at 7:14 am
Viewing 15 posts - 346 through 360 (of 526 total)