Got Started But Not Really: SQL Server does not allow remote connections

I downloaded VS studio express, and created a personal website using the wizard to test drive the thing. When I hit ctr + f5 to run the sample provided, then I get this message:

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) "

I tried disabling the firewall (Norton's firewall because Windows is disable always). Any suggestions? This is a brand-new machine, running XP sp2, just downloaded the VS studio express.

I really appreciate your inputs.

Regards,

Carlos

info@.paesano.com

Have a look at the following KB Article.

How to configure SQL Server 2005 to allow remote conections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

|||

Hi Glenn,

Thanks a lot for the answer. I followed the instructions provided in the article. Everything fine until I tried to start the SQL Express, which at the end gave me an error message: An error ocurred while performing this operation.

It seems like something is preventing SQL to start. I disabled my firewall thinking that the firewall was the cause of it, but it did not work either. If you have any suggestions, please help. As I mentioned, this is a brand-new machine running on Win SP2.

Thanks in advance.

Carlos

|||

As this looks more like a sql server express problem I will move the thread to the sql express group/

But in the mean time I would have a look at the event log for the machine to see if there are any errors being returned. With out any more details on the actuall error it is going to be hard to help.

Got an expensive server, SQL is very slow on writes

Hi,

i am experiencing SQl write performance problems on a very shiny server. Got data files on a Raid 1+0, log files on a separate drive, all SCSI, Win2003 server, 6G RAM, 2 Xeon processors. I've created a small benchmarking program and run it on my desktop pc and this 'big' server. Here are the results:

Desktop: SQL server inserts: 78 Seconds, Direct writes to the harddisk(Just write a string to the file 10000 times): 13 seconds

SQLServer: SQL server inserts: 422 Seconds, Direct writes to the harddisk: 16 seconds

So, for some reason, my 'shiny' machine is 6 times slower on writes than my desktop. When i tried comparing the select performance, my shiny server is 10 times faster than my desktop.

Initially i had Raid5 on my server and it had poorer direct write performance but now, direct writes seem to be ok, so, i recon this is a problem related to SQL server.

What can i do to improve the insert performance?

Thanks in advanceYour performance should double by placing the database file and transaction log file on different drives.

HTH|||As i mentioned previously, i already have my data and log files in different physical drives but it it does not make a difference.
Playing around with Raid configurations i managed to significally improve the speed of direct writes to hardisk (not within SQL) but sql write speed still stayed the same. I have a feeling that this is either Win2003 server or sql server matter. Cannot find any info about it.

Had someone come accross the same problem?|||Maybe check if your RAID-controller has its writecache disabled. How did you test? Within Queryanalyzer or custom Tool.?|||I wrote a small c# utility to do the test. Tool does 2 types of test:

1. It runs 10,000 insert quieries against a simple table

2. It writes a string into the flat file using direct file access 10,000 times.

I thought that writecache might be an issue but my direct writes (test 2) perform very well (equal to my desktop pc, whereas test 1 is 6 times slower than on my desktop) so i think that bottleneck is not in disk/raid configuration but somewhere else.

Not sure where though:( Same thing happens with SQL7.

Currently trying to install Win2k server op.|||For anyone having the same kind of a problem, issue was resolved by by installing a battery backed write cache on the SCSI controller. Achieved 24 times speed boost at once.|||... though enabling write cache is not a good idea anyways since it can lead to data corruption, even during normal operation.|||I've paid £250 for this write cache chip, it's backup onboard battery will last for 72 hours. I am pretty confident that my cached data will be save. Besides that, apparently write caching with battery backup is microsoft's recommendation. (Q230785)|||It's not a matter of how long your battery lasts. I read that the datapages can get out of sync with write caching enabled which leads to corrupt data files. But not 100% sure could be an issue of SQL 7 only.

... maybe one of our friendly MVP-SQL-Gurus here can confirm or disproof that hardware write caching can be a problem? :)

- Moon

Good Tape software for SQL backups

We would like to backup some databases natively and move the bak files to a
tape server that has a tape drive DLT1 Dell 120T.What are some of the 3rd
party tape software options thats reasonably priced that i can use for the
tape autoloader and that can send me some reports daily about the success or
failure of the SQL backup files copy onto tape.Veritas.
Yovan
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OsBU8LOfDHA.616@.TK2MSFTNGP11.phx.gbl...
> We would like to backup some databases natively and move the bak files to
a
> tape server that has a tape drive DLT1 Dell 120T.What are some of the 3rd
> party tape software options thats reasonably priced that i can use for the
> tape autoloader and that can send me some reports daily about the success
or
> failure of the SQL backup files copy onto tape.
>
>