Viewing 15 posts - 3,151 through 3,165 (of 3,232 total)
If you don't know what a format file is, you are probably not using one. That's OK. It can be done many ways. Don't worry about the format file. Follow...
November 30, 2005 at 1:06 pm
Brian's suggestion of using profiler to trace SQL statements would be the optimal solution if you are looking for a short term solution to figure out who's deleting your data. ...
November 30, 2005 at 12:50 pm
What I was getting at when asking if you are using the wizard again is that the package that the wizard is creating for your manual import must be different...
November 30, 2005 at 12:21 pm
Check the account permissions for the SQL Server account you are using. It must have sysadmin priviledges assigned to it.
If you need to reset your sa password, any sysadmin account...
November 30, 2005 at 11:53 am
There is not a logging feature in SQL Server 2000 that will accomplish what you are looking for. It sounds like you want to audit certain deletes? You may want...
November 30, 2005 at 11:47 am
When you are manually doing your import, are you using the wizard again, or running the actual scheduled job?
Can you post your table DDL, a copy of your format file...
November 30, 2005 at 11:41 am
Who is the job owner? Is it 'sa' or a Windows account?
November 30, 2005 at 11:34 am
When you are running your manual import, are you using the same package as your job or are you using the wizard? Is this a bulk imort job? Does it...
November 30, 2005 at 11:31 am
It can when they are sharing the same physical resources. You say this server only has 40 GB of disk space. I would assume that this is all on a single...
November 28, 2005 at 1:08 pm
I don't see that you've run sp_who2 while your DB is hung. I would recommend that you do this the next time your DB is hung prior to bouncing SQL...
November 28, 2005 at 12:54 pm
The SQL Server agent does not have to be running for SQL Server to be up and functioning. Think of the agent service as a scheduler as it handles running...
November 28, 2005 at 12:03 pm
What you are seeing is the directory from which the command shell is opening up. By default, this should be C:\windows\system32. I don't think anything is wrong with your SQL...
November 23, 2005 at 2:02 pm
No, I just wanted to make sure that the account that QA is using has rights to the file, but it sounds like it does since you are using Windows...
November 23, 2005 at 1:34 pm
Are you using SQL Server or Windows authentication when logging into Query Analyzer?
November 23, 2005 at 1:25 pm
ACCESS DENIED is usually a permissions error. Can you open up \\wwcd\test\filename.xls outside of Query Analyzer?
November 23, 2005 at 12:49 pm
Viewing 15 posts - 3,151 through 3,165 (of 3,232 total)