I've got both SQL 2000 and SQL Excess, er, Express on my PC doing C# Pro development.
If I try to Add Connection to get a data source, I can select an Express database MDF file, and operate on the data OK, but cannot select the Express server - it does NOT appear in the server list.
I added the server SQLSERVER.EXE to the Windows firewall 'Exceptions' list, along with Vis Studio - no change.
I CAN select the SQL 2000 server OK.
I can get into and use the Express Management tool OK. Properties for the Express server are Network connection (versus Local Service and Local System, both of which don't work), network connections allowed, TCPIP and the rest enabled, same user as for the 2000 server, same color, smell and taste.
How do I get the server to show up in a list of available servers I've been wrestling with this forever - no change.
Thanks
G.
PS So far have had more trouble with Express than ever with MSDE or 2000 - anyone agree
...and still cannot see the server from Visual Studio
ansarali
Unfortunately, the generator causes the same problem in the full version. It's a known bug and will be addressed in the first Service Pack
PerryTsai
Express Manager.
The issues are the first bugs encountered - things like files that couldn't be found, unhandled exceptions, etc.., and the connectivity problems, and the darn thing is real slow to both connect and deliver data, although the latter is intermittent.
Monitoring the SQL Express forum- looks like many others are finding glitches and it appears that Microsoft is not monitoring/replying to many of the posts.
I'm spooked because my (already shady) reputation may be further tarnished if things go south!
Regards,
G.
Scott Burkland
Are you using the full SQL Management Studio or the Express CTP Studio I was using SQL 2005 Express to develop a client's app (around 32 tables, with upwards of 250,000 rows on everything except for the lookup tables). Express 2005 handled it like a pro.
I'm now developing on SQL Standard 2005. Part of the application is an ETL from the old database into the new database (schema changes and the like). I get a throughput of 3000 entries per minute (each individual entry involves multiple selects from related tables in the old database, massaging the data into the new schema, and inserting the results into the new DB to the tune of about 30 inserts per item). Did I mention that I'm developing against a local installation of SQL 2005 running on a laptop with 768 MB of RAM
I know I could have used DTS or SSIS but the client isn't ready to make the transition to 2005/.net 2.0 just yet; and I don't have a 2000 Server installed anymore so I can't really test DTS out.
Basically from my experience, SQL 2005 Standard is definitely ready for prime time.
Marcus Adkison
Unfortunately ( ) I don't have SQL Server 2005, thus the Manager, to try.
...just tried dumping a database script out of Express to SQL Language = Server 2000 version.
Gee, seems there are syntax problems in trying to recreate the DB using the SQL Express script generator..... Chokes on the 'WITH (IGNORE_DUP_KEY = OFF)' part of:
"CONSTRAINT [PK_EquipmentType] PRIMARY KEY CLUSTERED
(
[EquipmentType] ASC
)WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]"
Luckily, it has a data export feature that...Oooops!...I guess not!
If I weren't already crazy I might go there : ;>
Methinks I'll keep my hands in plain sight and back away from Express quietly - it could get nasty.
Thanks, appreciate the advice.
G.
Thomas Lau
Did you turn on the Server Browser Open up the SQL Server Surface Area Configuration tool (in your SQL Server 2005 program group on the start menu).
Click the surface area configuration for services and connections link, select SQL Server Browser on the left and make sure it's running. Then VS should be able to discover it.
With less restrictions on db file size (4GB instead of 2) and the absence of the throughput throttling, I have to say that 2005 Express is better (and that's just the tip of the iceberg in terms of new features that I like about it :).
Brian R
CzarOfKatmandu
Browser has been running all along.
I just found that if I type the server name into the blank Add Connection box I can get the servername.master.dbo to connect (that's new by the way)- but no databases showing. Then I still have to select the MDF file name from the drop down list, and it has the complete folder path attached - ugh!
Gotta be some magic switch somewhere...
The problems I referred to are technical - the first install was way buggy and I did a reinstall. It also does not behave well when I have both the Manager and my Vis Studio open looking at the same database - I can guarantee that I can make all of the tables disappear from the database in Manager by doing a refresh on the Manager listed database. Then the fix is to close both Manager and Visual, stop and start the server, and go back in... I can imagine a client having to do that.
I'm testing Express as a preview to 2005 because I have a client who needs a SQL server backend - and if Express ( a crippled version of 2005) has glitches, then 2005 is probably not an option either. Will stay with 2000.
Thanks for the effort though - and if you have any more ideas...
Regards
G.
infology
...as an example - just did a reinstall and got "System.ArgumentOutOfRangeException: InvalidArgument=Value of '5' is not valid for 'index'.
Parameter name: index"
when I tried to look at the server properties in Manager.....
Sigh.
G.
Erick Ellis
The express manager is still pre-release. If you have access to it, I'd recommend installing the SSMS that comes with a full version of SQL 2005. It works (quite well I might add) with express and a lot of the quirks that come with express manager (like disappearing tables, and index out of bound exceptions in the summary page) are eliminated.