Rabu, 30 Maret 2016

[MS_AccessPros] Re: system resource exceeded on ddl

 

Forgive me if this is a duplicate post. I thought I posted this about 30 minutes ago but it didn't show up.

When you start using SQL Server databases check out ApexSQL tools. They have some free ones that I find very useful. http://www.apexsql.com/Download.aspx

Regards,

Bill Mosca, Founder - MS_Access_Professionals

http://www.thatlldoit.com

Microsoft Office Access MVP

https://mvp.microsoft.com/en-us/PublicProfile/35852?fullName=Bill%20%20Mosca

My nothing-to-do-with-Access blog

http://wrmosca.wordpress.com


 




---In MS_Access_Professionals@yahoogroups.com, <liz_ravenwood@beaerospace.com> wrote :

Thanks Andrew. Good stuff.

 

From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Tuesday, March 29, 2016 4:08 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Re: system resource exceeded on ddl

 



Good news Liz,

 

if you are going to start getting into SQL Server one day then you might want to work on the naming conventions early ;-)

 

Out of old habit, if my SQL Databases are going to be linked to anything like Access, I use "aaaaa" as prefix for the Primary Key index because older versions took the alphabetically first unique Key as the primary key. I'm not keen on prefixes otherwise, I'm more of a postfix type and Indexes tend to get called [Tablename_Fieldname_idx] which is usually unique.

 

As for caSe-senSitive, SQL Server can be either, depending on how it is installed and configured. T-SQL might not correct the capiTalisaTion of your coding as VBA does so you can end up with a piece of code working on a SQL Server with CI (Case Insensitve) sorting but not working when transfered to a production CS (Case Sensitive) Server.

 

Oh, be careful transferring code l! inking on Access DATE fields to SQL Server DATETIME Fields. Depending on how the fields are filled you can end up with values which won't JOIN because of value differences in the thousandths of a second on SQL Server.

 

Yours,

Andrew






This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

__._,_.___

Posted by: wrmosca@comcast.net
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (10)

.

__,_._,___

Tidak ada komentar:

Poskan Komentar