Viewing 15 posts - 8,461 through 8,475 (of 9,707 total)
Try switching the Model DB back to FULL recovery for a moment, backing up the transaction log, then switching Model back to SIMPLE. Then see if you can add the...
February 16, 2009 at 7:41 am
Granting references to DBO schema will indeed grant the ability to see the definitions to all DBO objects in that specific database. And remember, DBO doesn't own all schemas unless...
February 16, 2009 at 6:38 am
Your supplier's response still doesn't make sense to me. I can see granting reference to the defined user datatypes in the specific supplier's database, but not in TempDB.
I take...
February 16, 2009 at 6:26 am
BTW, as TempDB is essentially recreated every time you restart the services, what user defined datatypes are going to exist in it?
Does your supplier actually have code modifying TempDB?
That...
February 16, 2009 at 6:09 am
Have you checked the drive the transaction logs are on to make sure it isn't full?
Are you backing up your transaction logs (and checkpointing / truncating them) on a regular...
February 16, 2009 at 6:02 am
Question, what drive(s) are your system DBs on?
Also, does your Model db have a max file size?
Is your TempDB maxed out when you try this?
EDIT: I should clarify why I'm...
February 16, 2009 at 5:37 am
Sounds like you need to run Profiler when you run this job so you can track down exactly where the problem occurs. I'm betting your job gets suspended in the...
February 16, 2009 at 5:35 am
You can accomplish this output in two ways. The first way, as earlier suggested, is to write a stored procedure and put everything in a temp table, then select from...
February 16, 2009 at 5:32 am
Google running DTS in SQL Server 2005. Also, check this link for backward compatibility components:
I believe you have to have the backward compatibility installed prior to running DTS. I'm sure...
February 16, 2009 at 5:28 am
Chandu,
SQL Server does not take passwords for domain accounts. So don't write your code that way.
If you're automating the install of SQL Server itself, then what you're trying won't work....
February 13, 2009 at 11:20 am
Which means, what I originally thought is true.
Data Quality is not (or should not be) an issue.
February 13, 2009 at 11:08 am
Your biggest worry will be when two people try to change the same record & same field to two different things.
Say I have an auto insurance policy set as...
February 13, 2009 at 8:07 am
Glad I could help.
Let us know if you have any more questions after you're through gathering. @=)
February 13, 2009 at 7:45 am
Just because the server name is correct in the C# code, doesn't mean it's correct in the T-SQL Code. That's why you were asked to check it.
As far as everything...
February 13, 2009 at 7:44 am
Viewing 15 posts - 8,461 through 8,475 (of 9,707 total)