Viewing 15 posts - 46 through 60 (of 84 total)
This is a stumper... You've used 2 different kinds of connection methods, both have SQL Server telling you that you are connecting via windows authentication and failing... I...
October 2, 2007 at 4:20 pm
I think I've got it... Well, you are using the OLEDB driver for ODBC, right? Well, try straight OLEDB with the following connection string:
"Provider=sqloledb;Data Source=192.168.8.93;Initial Catalog=ead;User Id=ead;Password=webead;"
This way,...
October 2, 2007 at 3:20 pm
Hi Fabio,
I am 99% sure that the following error is caused by a failed connection using Windows authentication:
"Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed...
October 2, 2007 at 3:09 pm
Greg has a couple good points. First off, there is a difference between granting database access and granting login access. In theory, though, a user that can add...
October 2, 2007 at 10:07 am
Hi Ricardo,
You can certainly do this using T-SQL. Just for a point of reference, under Enterprise admin, go to security -> Server Roles -> security admin. Right-click and...
October 2, 2007 at 9:37 am
Hi Fabio,
Do you have the ability to try other accounts? For example, do you have privileges to use the sa account? If so, try to see if you...
October 2, 2007 at 9:24 am
Hi deucellion,
If you still have xp_cmdshell on your SQL Server, try running the following:
exec master..xp_cmdshell 'dir h:\' --If this works, try the next line:
exec master..xp_cmdshell 'echo "test" > h:\test.txt' --look...
August 1, 2007 at 9:29 am
Hello Julio,
I will have to concur with Colin despite his rather blunt answer. Using 1.7 GB of memory in SQL Server is normal behavior out of the box. If you...
August 1, 2007 at 9:19 am
Hi Christopher,
THis isn't an official Microsoft answer, but this is my gut instinct. If I were to see something like this, I would interpret it as follows. Essentially, we are...
July 23, 2007 at 9:59 am
I don't know the difference between mainstream support (ends 04/08/2008) and extended support (ends 04/08/2013), but here is the link to the info...
http://support.microsoft.com/lifecycle/?p1=2852
Thanks,
Eric
July 12, 2007 at 9:04 am
Whew, the flood and drought of on-call! There isn't too much to set up in SQL '05 64-bit. As long as you can lock pages inmemory, only max and min...
July 12, 2007 at 8:49 am
I took a quick glance at the query at looks like it should work. Can you parse the command and give us the error, or don't you have a SQL...
July 12, 2007 at 8:42 am
Here is some fun code I use for this kind of thing. It uses the undocumented command "dbcc showfilestats", which works in 2000 and 2005. Here is the script with...
July 12, 2007 at 8:37 am
I would try a couple troubleshooting steps just to narrow down the problem.
1) Look at the SQL Serrver error log to find what TCP/IP port the 2000 instance is listening...
July 12, 2007 at 8:27 am
I have a couple interesting observations.
1) When I looked at Steve's article, I saw it right next to an article about upgrading to SQL '05. (did anyone else see the humor...
July 12, 2007 at 12:32 am
Viewing 15 posts - 46 through 60 (of 84 total)