SQL server newbie

Question

SQL server newbie

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply

Luis Cazares SSC Guru Points: 183706 More actions · Answer 1

JJR333 (10/31/2014)
... shrink the database...

Be careful, you shouldn't be shrinking the database.

http://blog.sqlauthority.com/2011/01/19/sql-server-shrinking-database-is-bad-increases-fragmentation-reduces-performance/

I can't remember if express version comes with SQL Server Agent. If it does, you should use it to schedule the jobs instead of windows task scheduler.

It's great that you're learning SQL Server, come back to the site if you need help. 😉

Luis C.
General Disclaimer:
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

How to post data/code on a forum to get the best help: Option 1 / Option 2

daniel.freedman 80164 Mr or Mrs. 500 Points: 535 More actions · Answer 2

JJR333 (10/31/2014)
... shrink the database...

Just be aware that if you do this you'll fragment all your indexes. Also it's generally frowned upon because the server will only have to grow the database again later as and when needed.

JJR333 Default port Points: 1469 More actions · Answer 3

Thank you for pointing this out to me.

Express version does not have the Agent.

Cheers,

Julian

Mile Higher Than Sea Level SSCarpal Tunnel Points: 4828 More actions · Answer 4

http://www.access-programmers.co.uk/forums/

Over 1 million posts. There is a SQL Server forum for advanced Access programmers that have helped many make the transaction successfully. Many of us have been using SQL Server for over a decade.

This site is wonderful as it helps us part-timers to do more on the SQL Server side.

I have almost 2,000 post there. Plus there are many really excellent contributors beyond my skills.

Many of us share tips on how to use SQL Server Migration Wizard for Access to make the transition.

There are code samples for a coding solution for the ODBC SQL Server Native Client 11.0 as a DSN-Less connection.

Also some great tips on the difference in Access and SQL query language.

If the SQL used in Access totally avoids the Access functions, the ODBC is extremely efficient in the execution plan.

For example: Making the View in SQL then using that view as a linked table to run Select queries against with filters will fully execute on the SQL side and return only the records requested.

Access is a very fast prototype front-end that plays well with SQL Server.

If good programming rules are followed, it is easy to connect 250 concurrent Access clients to a SQL Server back end.

That is 'if' good programming rules are followed.

My Access client is served on via Citrix on a national basis. Have been doing this in one way or another since 1997.

Access plays with Citrix very well. The ICA client is very secure, very low bandwidth and plays on platforms besides Windows.

While I prefer the paid version of SQL Server, other members at the site above use the Express version.

Some use AZURE. For the cost there is something to be said about AZURE.

Good luck to you. You are not alone. Many business applications that server under 100 end users are still done with Access.

There are many great tools out there to connect to SQL Server. It is easy to find poor Access applications because it is as available as Microsoft Excel. In fact, I program Excel Object Model to connect to SQL Server for some specific requirements.

To be successful in Access, it is worth learning how to do it correctly.

One of the post before this asked for your objectives. That would be important to know.