We have Small Business Server 2003 Premium including SQL 2000 at work.
At the recent launch event I got VS 2005 and SQL 2005.
I want to overhaul an Access database with poorly designed tables into a properly normalized SQL Server database.
Would I be best off using SQL 2000 that came with SBS 2003 Premium or SQL 2005 express or buy some CAL's and use the SQL 2005 that I got at the launch event.
I want to design with the thought that ultimately this data will be accessed by people outside our network and exposed via a web service and to/through a sharepoint site hosted locally or remotely by Microsoft.
I'd like to use the new VS 2005 Visual Basic from the launch event to code the front end and make an occasionally connected smart client front end for my boss to have on his laptop.
There will be 3 to 10 users initially. (We have 10 CAL's for our SBS)
Thanks for your advice and input!
JED_
VB 2005 & Small Business Server & SQL Server
Hot Topic
- Function Reference
- Cross Package Configuration Files
- To find all pairs in table that fits to given criteria.
- Parameter Change Rebuild Report?
- Query Issues Pt.3
- SQL 2005 - sp_rename doesn't work on user defined data types
- OLEDB versus ADO.NET for UPDATE statement using parms
- Retrieving multiple Result Sets from within a stored procedure
- Excel 2003 Query Performance
- Can MS Sharepoint Services work with Reporting Services 2000??
SQL Server
- sp_send_dbmail generate ansi file attachment format
- Please help me with my Top N query
- SQL 2000 -> SQL 2005 Merge Replication compatible?
- Connecting to SQL Server database via windows form app
- deadlock issue
- Hidden vs. Internal Parameters -- Got to be a better way...
- Basic Connection
- Autoscale
- Problems migrating DTS package
- Unable to connect to Analysis Services as a client
VB 2005 & Small Business Server & SQL Server