My SQL Server Authentication is set to SQL Server and Windows Authentication mode.
Do you know what is the default for this? Assuming I did not set up a user at all? Daniel On Wed, Jul 20, 2011 at 1:55 AM, Jason King <[email protected]> wrote: > Are you using SQL Authentication or Windows Authentication? > > With SQL Authentication, you have a user setup within SQL Server. With > WIndows Authentication, you are using your Windows OS/Active Directory > user base. > > Either way, you have to have a user setup as a user of the database. > If you are just using the system administrator account, then that > would be your login. But if you go into SQL and create a specific > user, such as "SQL_USER_XYZ", you assign it a role, and then use that > login as your login for the datasource. > > > > On Tue, Jul 19, 2011 at 12:53 PM, Daniel Eng <[email protected]> wrote: > > Ok, I have tried changing the port for the SQL Server. And I think I have > > made some progress. Another thing is this... the username and password - > is > > this the place to set it or is it to specify the username and password > that > > was set earlier? Cos I did not set any username and password for my SQL. > Is > > it attached to my DB user? > > > > Daniel > > > > On Wed, Jul 20, 2011 at 1:36 AM, Carl Von Stetten < > [email protected]> > > wrote: > >> > >> When you install SQL Server Express (2005 or 2008), you have the option > of > >> creating a default instance (which will be named MSSQLSERVER and will be > on > >> the default port), or a named instance (which will be named SQLEXPRESS > and > >> will be on a non-standard port). The screen where you pick either > default > >> instance or named instance is set to named instance by default (umm.... > the > >> default setting is not the default instance, how confusing is that? :-P > ). > >> > >> Of course you can then go into the SQL Server Configuration Manager and > >> change the port assignment to the "standard" port of 1433, as long as > you > >> don't have another instance of SQL Server already running on port 1433. > >> > >> Carl > >> > >> On 7/19/2011 9:59 AM, Matthew Woodward wrote: > >> > >> On Tue, Jul 19, 2011 at 9:47 AM, Carl Von Stetten > >> <[email protected]> wrote: > >>> > >>> If your SQL Server is SERVERNAME\SQLEXPRESS, it's a named instance and > is > >>> running on a non-standard port. > >> > >> Well, this instance isn't necessarily running on a non-standard port. > >> Someone pointed out in another thread recently that may be the default > >> instance name that's running on port 1433. > >> But yes, if it's running on a non-standard port, you'd have to know what > >> that is. Technically speaking both the MS and jTDS drivers support named > >> instances but I've never had good luck with them, and when you use the > named > >> instance you're making another round trip to the server to negotiate the > >> port number anyway. > >> -- > >> Matthew Woodward > >> [email protected] > >> http://blog.mattwoodward.com > >> identi.ca / Twitter: @mpwoodward > >> > >> Please do not send me proprietary file formats such as Word, PowerPoint, > >> etc. as attachments. > >> http://www.gnu.org/philosophy/no-word-attachments.html > >> -- > >> official tag/function reference: http://openbd.org/manual/ > >> mailing list - http://groups.google.com/group/openbd?hl=en > >> > >> -- > >> official tag/function reference: http://openbd.org/manual/ > >> mailing list - http://groups.google.com/group/openbd?hl=en > > > > -- > > official tag/function reference: http://openbd.org/manual/ > > mailing list - http://groups.google.com/group/openbd?hl=en > > > > -- > official tag/function reference: http://openbd.org/manual/ > mailing list - http://groups.google.com/group/openbd?hl=en > -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
