From tuxedo_man at hotmail.com Mon Nov 1 01:00:09 2004 From: tuxedo_man at hotmail.com (Billy Pang) Date: Mon, 01 Nov 2004 07:00:09 +0000 Subject: [dba-SQLServer] sorting problem Message-ID: Hi Arthur: >Fine! Fine! Fine! In future, I suggest that you provide your third-world >developers with an adequeate data set. LOL. I shall go back to the salt >mines and toil endlessly until I have a solution. But you still haven't >made the rules quite clear, if I may say so, Sir. Perhaps my original approach to the sorting problem could be improved. I can't really define all the rules because they are not set yet and if they are set, the rules tend to get changed on me. Looking at my original post, I posted sample data but did not provide enough explanation on what I was really looking for (how to sort letters before numbers where the "no character" takes precendence over "existence of a character"). (like eating dessert before the main course). Sometimes, to communicate more effectively, we should explain the issue first with more words and provide example afterwards. The other way around, though allowed, is not that effective. Anyways, I was looking for an "all covering" "all knowing" solution to "sorting values where letters take precendence over numbers and where the "no character" takes precendence over the "existence of a character""; something simple that did not require hardcoding the solution. I didn't know if such exists but you never know unless you ask and I wanted to make sure that I wasn't overlooking anything obvious (can't see the forest because of all these trees). >Given strings x##x#x and xx###xx#xx, please define the desired sort order. x##x#x would come first, then xx###xx#xx. :P (running towards the forest) >I think I can do this by sequential calls to the func I wrote, but I could >be wrong. I need more evidence to determine how to revise my inadequate >contribution thus far. > I cannot provide more evidence so that you can revise your code because sting values could be anything. x or x# or x###x or x##x or x#x#x#x# etc... Please don't call your contribution inadequate. I believe that all contributions contribute in some way to some degree to the solution one way or another. I am reading this book called "Thinking for a change" by John Maxwell. He claims that "one idea + one idea = three ideas". Even though the statement is mathematically incorrect, it is very true because the words people say/write usually get other people thinking in some part to generate a new idea. There are many people I respect when it comes to databases; some are on this list and some who were but no longer on the list. Sincerely, Billy From rl_stewart at highstream.net Mon Nov 1 13:08:21 2004 From: rl_stewart at highstream.net (Robert L. Stewart) Date: Mon, 01 Nov 2004 13:08:21 -0600 Subject: [dba-SQLServer] Re: sorting problem In-Reply-To: <200411011803.iA1I3WL13089@databaseadvisors.com> Message-ID: <5.1.0.14.2.20041101130529.013d6aa8@pop3.highstream.net> Billy, With the rules changing and such, one of the ways of doing this might be to break out the unique values, if there are not too many of them, into their own table and define the sort order there. Give the end user a form to maintain the sort order and then they can apply all the rules they want to at the table level as they change the sort order themselves. :-) Robert At 12:03 PM 11/1/2004 -0600, you wrote: > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf > > Of Billy Pang > > Sent: Friday, October 29, 2004 8:35 PM > > To: dba-SQLServer at databaseadvisors.com > > Subject: [dba-SQLServer] sorting problem > > > > > > Hello: > > > > I have a table that contains one column with the following six values: > > > > a1 > > a2 > > a21 > > a10x > > a2a > > a10 > > > > Currently if that column is sorted, it is sorted this way: > > > > a1 > > a10 > > a10x > > a2 > > a21 > > a2a > > > > But I want it to be sorted this way: > > > > a1 > > a2 > > a2a > > a10 > > a10x > > a21 > > > > (note: a2a comes before a10, a21 goes after a10x, etc...ergo, > > letters come > > before numbers, contrary to their ascii values) > > > > Is it possible or is it a pipe dream? Below is copy of code. > > > > Thanks in advance, > > Billy > > From jwcolby at colbyconsulting.com Mon Nov 1 22:06:35 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Mon, 01 Nov 2004 23:06:35 -0500 Subject: [dba-SQLServer] Transactions and transaction logs In-Reply-To: Message-ID: <000001c4c091$5c2b29a0$e8dafea9@ColbyM6805> Are all db changes recorded in transaction logs (if they are enabled) or only statements between the begin and the commit / rollback? John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ From fhtapia at gmail.com Mon Nov 1 23:15:34 2004 From: fhtapia at gmail.com (Francisco Tapia) Date: Mon, 1 Nov 2004 21:15:34 -0800 Subject: [dba-SQLServer] Transactions and transaction logs In-Reply-To: <000001c4c091$5c2b29a0$e8dafea9@ColbyM6805> References: <000001c4c091$5c2b29a0$e8dafea9@ColbyM6805> Message-ID: if you set your transaction log to FULL logging, then ALL transactions are logged, the ones between the BEGIN and COMMIT / ROLLBACK are for being able to controll error handling but everything is LOGGED (when FULL logging is enabled). On Mon, 01 Nov 2004 23:06:35 -0500, John W. Colby wrote: > Are all db changes recorded in transaction logs (if they are enabled) or > only statements between the begin and the commit / rollback? > > John W. Colby > www.ColbyConsulting.com > > Contribute your unused CPU cycles to a good cause: > http://folding.stanford.edu/ > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco Pc This! pc news with out the jargon From andrew.haslett at ilc.gov.au Mon Nov 1 23:17:46 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Tue, 2 Nov 2004 15:47:46 +1030 Subject: [dba-SQLServer] Transactions and transaction logs Message-ID: <0A870603A2A816459078203FC07F4CD204C5EC@adl01s055.ilcorp.gov.au> And the don't have to be surrounded by Commit / Rollback.. It also depends on the recovery model you are using, as to which types of transactions are logged. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Tuesday, 2 November 2004 2:37 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Transactions and transaction logs Are all db changes recorded in transaction logs (if they are enabled) or only statements between the begin and the commit / rollback? John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From jwcolby at colbyconsulting.com Tue Nov 2 00:26:07 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Tue, 02 Nov 2004 01:26:07 -0500 Subject: [dba-SQLServer] Undoing transaction issues Message-ID: <000101c4c0a4$d97a58a0$e8dafea9@ColbyM6805> I am writing statements that sets up isolation levels on SQL statements. It appears that I have done something that prevents even seeing specific records in the database. AFAICT I have done commits etc. Is there any way to "undo" whatever the issue is? Is there any way to SEE what the issue is? John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ From jwcolby at colbyconsulting.com Tue Nov 2 00:54:04 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Tue, 02 Nov 2004 01:54:04 -0500 Subject: [dba-SQLServer] Undoing transaction issues In-Reply-To: <000101c4c0a4$d97a58a0$e8dafea9@ColbyM6805> Message-ID: <000201c4c0a8$c1e05600$e8dafea9@ColbyM6805> Never mind. When I tried to close QA it told me I had unfinished transactions. When I said yes, execute them it released the records. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John W. Colby Sent: Tuesday, November 02, 2004 1:26 AM To: SQLServer Subject: [dba-SQLServer] Undoing transaction issues I am writing statements that sets up isolation levels on SQL statements. It appears that I have done something that prevents even seeing specific records in the database. AFAICT I have done commits etc. Is there any way to "undo" whatever the issue is? Is there any way to SEE what the issue is? John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From andrew.haslett at ilc.gov.au Tue Nov 2 05:03:19 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Tue, 2 Nov 2004 21:33:19 +1030 Subject: [dba-SQLServer] Undoing transaction issues Message-ID: <0A870603A2A816459078203FC07F4CD20139D6@adl01s055.ilcorp.gov.au> One of the main things I remember from the course is that you *very rarely* need to manually handle locking and isolation. SS is excellent at handling this itself and avoid the type of issues you are bound to come up across. Before you know it, you'll have all types of locks blocking other transactions that you hadn't planned on. I'm not saying it can be a powerful tool, but just a word of warning... A _____ From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Tue 2/11/2004 5:24 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Undoing transaction issues Never mind. When I tried to close QA it told me I had unfinished transactions. When I said yes, execute them it released the records. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com ] On Behalf Of John W. Colby Sent: Tuesday, November 02, 2004 1:26 AM To: SQLServer Subject: [dba-SQLServer] Undoing transaction issues I am writing statements that sets up isolation levels on SQL statements. It appears that I have done something that prevents even seeing specific records in the database. AFAICT I have done commits etc. Is there any way to "undo" whatever the issue is? Is there any way to SEE what the issue is? John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From jwcolby at colbyconsulting.com Tue Nov 2 22:43:09 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Tue, 02 Nov 2004 23:43:09 -0500 Subject: [dba-SQLServer] Login names vs users In-Reply-To: <0A870603A2A816459078203FC07F4CD20139D6@adl01s055.ilcorp.gov.au> Message-ID: <001801c4c15f$a280cb20$e8dafea9@ColbyM6805> What is the relationship between login names and users, groups and roles? SP_AddLogin SP_AddUser Sp_AddGroup Sp_AddRole John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ From andrew.haslett at ilc.gov.au Tue Nov 2 23:13:06 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Wed, 3 Nov 2004 15:43:06 +1030 Subject: [dba-SQLServer] Login names vs users Message-ID: <0A870603A2A816459078203FC07F4CD204C5FF@adl01s055.ilcorp.gov.au> Sp_AddLogin - creates a SQL Login (User) - You can then connect to an instance via SQL Authentication using this login. Sp_AddUser (or sp_grantdbaccess in SQL 2K) - allows an existing SQL User access to the current database. Sp_AddGroup (of sp_AddRole in SQL 2K) - creates a new role in the current database. Workflow wise, you would first create the login (sp_addlogin), and then grant access for that login to a specific database (sp_grantdbaccess). If you wish, you can create a specific role in that database (sp_AddRole), add your user (or many users) to this role (sp_addrolemember), and give the required privileges to that role, instead of individual users. Similar to creating groups in active directory and adding users to those groups. Mind you, you can do all this through the GUI in Enterprise Manager.. Cheers, A -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Wednesday, 3 November 2004 3:13 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Login names vs users What is the relationship between login names and users, groups and roles? SP_AddLogin SP_AddUser Sp_AddGroup Sp_AddRole John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From kens.programming at verizon.net Tue Nov 2 23:26:20 2004 From: kens.programming at verizon.net (Ken Stoker) Date: Tue, 2 Nov 2004 21:26:20 -0800 Subject: [dba-SQLServer] Login names vs users In-Reply-To: <001801c4c15f$a280cb20$e8dafea9@ColbyM6805> Message-ID: <20041103052457.IVCI23519.out001.verizon.net@enterprise> Sp_addlogin - creates an account (SQL Server Authentication) at the server level. Sp_adduser - is primarily for backwards compatibility with SQL 7.0. In SS2K, use sp_grantdbaccess. This grants access to a specific database for the supplied account. The account has to be set up at the server level before one can use this. Sp_addgroup - this is also included for backwards compatibility with SQL 7.0. It adds groups (called roles in SS2K) within SQL Server. Sp_addrole - SS2K implementation to create a new SQL Server role/group. Using roles, you can implement permissions to the role instead of to each individual account. This makes managing permissions easier in the respect that there are fewer entities' permissions to maintain. However, users can be in more than one role, and the permissions will be implemented with the conglomeration of all roles' permissions a user is a member of. This part can get quite sticky if not managed correctly. The hierarchy for permissions is Deny --> Grant --> NULL. Let's say a user account is in two roles, role1 and role2, with the following permissions on the same table or view: ROLE1 ROLE2 SELECT GRANT NULL UPDATE DENY GRANT INSERT NULL GRANT DELETE DENY GRANT In this case, as I understand it, the account can SELECT because Role1 Grants it, superceding Role2 which implements nothing here. UPDATE, which is Granted in Role2, is actually Denied because of the implementation in Role1. INSERT would be Granted because Role2's Grant overrides Role1's non-implementation. And DELETE is Denied because Role1's Deny rights overrides Role2's Grant rights. Sp_grantlogin is used to create Windows Authentication accounts within SQL Server at the server level. Then you would use sp_grantdbaccess to give that account access to a specific database within the SQL Server instance. There is a lot of information on these in BOL under System Stored Procedures. If you scroll down, you will find a section for Security Procedures. Again, this is the way I have come to understand it. If I am wrong, I know someone here will correct me. Ken -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John W. Colby Sent: Tuesday, November 02, 2004 8:43 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Login names vs users What is the relationship between login names and users, groups and roles? SP_AddLogin SP_AddUser Sp_AddGroup Sp_AddRole John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From fhtapia at gmail.com Fri Nov 5 11:40:27 2004 From: fhtapia at gmail.com (Francisco Tapia) Date: Fri, 5 Nov 2004 09:40:27 -0800 Subject: [dba-SQLServer] Last Login? Message-ID: I'd like to use this for my FE app, that is return the "last login" information. However I'm not having any luck w/ my keywords in BOL any hints are appreciated :D -- -Francisco Pc This! pc news with out the jargon From HARVEYF1 at WESTAT.com Fri Nov 5 12:19:12 2004 From: HARVEYF1 at WESTAT.com (Francis Harvey) Date: Fri, 5 Nov 2004 13:19:12 -0500 Subject: [dba-SQLServer] Last Login? Message-ID: <446DDE75CFC7E1438061462F85557B0F0481EB32@remail2.westat.com> Francisco, Maybe something like: select top 1 loginame, login_time from master.dbo.sysprocesses order by login_time desc Francis R Harvey III WB 303, (301)294-3952 harveyf1 at westat.com > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf > Of Francisco Tapia > Sent: Friday, November 05, 2004 12:40 PM > To: dba-sqlserver at databaseadvisors.com > Subject: [dba-SQLServer] Last Login? > > > I'd like to use this for my FE app, that is return the "last login" > information. However I'm not having any luck w/ my keywords in BOL > > any hints are appreciated :D > -- > -Francisco > Pc This! pc news with > out the jargon > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > From fhtapia at gmail.com Fri Nov 5 12:31:21 2004 From: fhtapia at gmail.com (Francisco Tapia) Date: Fri, 5 Nov 2004 10:31:21 -0800 Subject: [dba-SQLServer] Last Login? In-Reply-To: <446DDE75CFC7E1438061462F85557B0F0481EB32@remail2.westat.com> References: <446DDE75CFC7E1438061462F85557B0F0481EB32@remail2.westat.com> Message-ID: That was IT! Thanks!!! On Fri, 5 Nov 2004 13:19:12 -0500, Francis Harvey wrote: > Francisco, > > Maybe something like: > > select top 1 loginame, login_time > from master.dbo.sysprocesses > order by login_time desc > > Francis R Harvey III > WB 303, (301)294-3952 > harveyf1 at westat.com > > > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf > > Of Francisco Tapia > > Sent: Friday, November 05, 2004 12:40 PM > > To: dba-sqlserver at databaseadvisors.com > > Subject: [dba-SQLServer] Last Login? > > > > > > I'd like to use this for my FE app, that is return the "last login" > > information. However I'm not having any luck w/ my keywords in BOL > > > > any hints are appreciated :D > > -- > > -Francisco > > Pc This! pc news with > > out the jargon > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco Pc This! pc news with out the jargon From jwcolby at colbyconsulting.com Sun Nov 7 21:50:06 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Sun, 07 Nov 2004 22:50:06 -0500 Subject: [dba-SQLServer] Dynamic from Access In-Reply-To: <20041103052457.IVCI23519.out001.verizon.net@enterprise> Message-ID: <000401c4c546$092bbb20$e8dafea9@ColbyM6805> I think I have figured out a strategy for the nVLDB - 64 million records, ~640 fields. The deal is that the table consists of sets of fields, typically 10-20 fields, where the "subject" of the field is the same, perhaps age, income, people in household, ethnicity, drugs taken, types of music listened to, types of books read etc. I have started breaking out these sets of fields into individual tables, with a PK field that is the PK of the main table. In other words I will now have a table with perhaps 12 fields that are yes / no / null listens to music type x, y, z. Another table with perhaps 20 fields with yes / no / null takes zocor, etc. etc. I will end up breaking the 640 fields down into perhaps 30 tables where each table holds a set of fields from the original table. This allows me to index each field which was not possible with the big table simply because any given table can only contain 240 indexes. The idea now is to be able to select a handful of these subtables, perhaps income, age, music, reading and autos, join them back using the PK, then do a where income >20k and <40K, age > 20 and <30, music = blues or rock, etc... Then do a count(pk) to get a count of people having those characteristics. Additionally I can now get a count on the values in each field, 2 million no, 250k yes, 60 million null "listens to rap" etc. Sound feasible? The issue now is that I need to do this stuff programmatically from Access or perhaps a web environment (eventually). IOW, I need to build up a query joining the income, age, music, reading and autos tables on PK, throw in the where(s), and get a count of PK. I need to do this dynamically from VB (or access), where I can let the user select tables to join (sets of related fields), hand back lists of fields to select where values from, and lists of values that are actually in those fields. I can do all of that stuff, where I need assistance is how to hand the finished SQL statement off to SQL Server and have it run the query, handing back the count. I can't have Access (Jet) brute force it simply because the tables each have 64 million records in them. Just getting the PKs back to JET would take days. So, how do I hand SQL Server a dynamically built SQL statement, ask it to evaluate the SQL statement and return a single count value? Eventually I also need to have SQL take that same where clause and hand me back a set of fields / records from the main name / address subtable for sending to the bulk mail client. I am considering doing this in an ADP environment, where I build and save the SQL as a UDF or something like that- not that I've ever done anything like that before. Or get out of Access entirely (though the data environment sure is nice) and use .NET or something. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ From stuart at lexacorp.com.pg Sun Nov 7 23:03:21 2004 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Mon, 08 Nov 2004 15:03:21 +1000 Subject: [dba-SQLServer] Dynamic from Access In-Reply-To: <000401c4c546$092bbb20$e8dafea9@ColbyM6805> References: <20041103052457.IVCI23519.out001.verizon.net@enterprise> Message-ID: <418F8AB9.23250.4F44994@lexacorp.com.pg> On 7 Nov 2004 at 22:50, John W. Colby wrote: > So, how do I hand SQL Server a dynamically built SQL statement, ask it to > evaluate the SQL statement and return a single count value? > Use an ADO connection. > Eventually I also need to have SQL take that same where clause and hand me > back a set of fields / records from the main name / address subtable for > sending to the bulk mail client. > Same thing, you just get a Recordset back -- Stuart From accessd at shaw.ca Mon Nov 8 00:15:36 2004 From: accessd at shaw.ca (Jim Lawrence (AccessD)) Date: Sun, 07 Nov 2004 22:15:36 -0800 Subject: [dba-SQLServer] Dynamic from Access In-Reply-To: <000401c4c546$092bbb20$e8dafea9@ColbyM6805> Message-ID: Hi John: You can either hand the request off to a (1) stored procedure or send it off direct through a (2) 'execute' request. The processes assume ADO-OLE referenced and Access unbound connection. Given; assuming Windows authentication: gstrConnection = "Provider=SQLOLEDB;Initial Catalog=MyDatabaseName;Data Source=MyServerName;Integrated Security=SSPI" 1. Something Like; where results are required: Dim objCmd As ADODB.Command Dim rsMyResultRecordset As ADODB.Recordset Set objCmd = New ADODB.Command With objCmd .ActiveConnection = gstrConnection .CommandText = "MyStoredProcedure" .CommandType = adCmdStoredProc ' If Parameters are required .Parameters.Append .CreateParameter("@intPKNumber", adInteger, adParamInput, , MyPKNumberField) .Parameters.Append .CreateParameter("@chvWholeNameField", adVarChar, adParamInput, 250, MyWholeNameField) End With Set rsMyResultRecordset = New ADODB.Recordset With rsMyResultRecordset .CursorLocation = adUseClient .Open objCmd, , adOpenDynamic, adLockOptimistic If .BOF = False Or .EOF = False Then .MoveLast End With Set objCmd = Nothing ...or... 2. Something like; where no return is necessary: Dim objConn As ADODB.Connection Dim strSQL As String strSQL = "UPDATE MyTable " & _ "SET MyFirstField = " & intActive & " " & _ "WHERE MySecondField = True" Set objConn = New ADODB.Connection objConn.Open gstrConnection objConn.Execute strSQL This is just the bare bones layout. There is no error controls like 'BeginTrans' or 'RollBackTrans' or how the receiving Stored procedure should be set up or how a variable is returned etc. but I hope this is enough to get you started. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Sunday, November 07, 2004 7:50 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Dynamic from Access I think I have figured out a strategy for the nVLDB - 64 million records, ~640 fields. The deal is that the table consists of sets of fields, typically 10-20 fields, where the "subject" of the field is the same, perhaps age, income, people in household, ethnicity, drugs taken, types of music listened to, types of books read etc. I have started breaking out these sets of fields into individual tables, with a PK field that is the PK of the main table. In other words I will now have a table with perhaps 12 fields that are yes / no / null listens to music type x, y, z. Another table with perhaps 20 fields with yes / no / null takes zocor, etc. etc. I will end up breaking the 640 fields down into perhaps 30 tables where each table holds a set of fields from the original table. This allows me to index each field which was not possible with the big table simply because any given table can only contain 240 indexes. The idea now is to be able to select a handful of these subtables, perhaps income, age, music, reading and autos, join them back using the PK, then do a where income >20k and <40K, age > 20 and <30, music = blues or rock, etc... Then do a count(pk) to get a count of people having those characteristics. Additionally I can now get a count on the values in each field, 2 million no, 250k yes, 60 million null "listens to rap" etc. Sound feasible? The issue now is that I need to do this stuff programmatically from Access or perhaps a web environment (eventually). IOW, I need to build up a query joining the income, age, music, reading and autos tables on PK, throw in the where(s), and get a count of PK. I need to do this dynamically from VB (or access), where I can let the user select tables to join (sets of related fields), hand back lists of fields to select where values from, and lists of values that are actually in those fields. I can do all of that stuff, where I need assistance is how to hand the finished SQL statement off to SQL Server and have it run the query, handing back the count. I can't have Access (Jet) brute force it simply because the tables each have 64 million records in them. Just getting the PKs back to JET would take days. So, how do I hand SQL Server a dynamically built SQL statement, ask it to evaluate the SQL statement and return a single count value? Eventually I also need to have SQL take that same where clause and hand me back a set of fields / records from the main name / address subtable for sending to the bulk mail client. I am considering doing this in an ADP environment, where I build and save the SQL as a UDF or something like that- not that I've ever done anything like that before. Or get out of Access entirely (though the data environment sure is nice) and use .NET or something. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jwcolby at colbyconsulting.com Mon Nov 8 06:27:23 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Mon, 08 Nov 2004 07:27:23 -0500 Subject: [dba-SQLServer] Dynamic from Access In-Reply-To: Message-ID: <000701c4c58e$4cf418f0$e8dafea9@ColbyM6805> Thanks Jim, I'll look at that. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence (AccessD) Sent: Monday, November 08, 2004 1:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Dynamic from Access Hi John: You can either hand the request off to a (1) stored procedure or send it off direct through a (2) 'execute' request. The processes assume ADO-OLE referenced and Access unbound connection. Given; assuming Windows authentication: gstrConnection = "Provider=SQLOLEDB;Initial Catalog=MyDatabaseName;Data Source=MyServerName;Integrated Security=SSPI" 1. Something Like; where results are required: Dim objCmd As ADODB.Command Dim rsMyResultRecordset As ADODB.Recordset Set objCmd = New ADODB.Command With objCmd .ActiveConnection = gstrConnection .CommandText = "MyStoredProcedure" .CommandType = adCmdStoredProc ' If Parameters are required .Parameters.Append .CreateParameter("@intPKNumber", adInteger, adParamInput, , MyPKNumberField) .Parameters.Append .CreateParameter("@chvWholeNameField", adVarChar, adParamInput, 250, MyWholeNameField) End With Set rsMyResultRecordset = New ADODB.Recordset With rsMyResultRecordset .CursorLocation = adUseClient .Open objCmd, , adOpenDynamic, adLockOptimistic If .BOF = False Or .EOF = False Then .MoveLast End With Set objCmd = Nothing ...or... 2. Something like; where no return is necessary: Dim objConn As ADODB.Connection Dim strSQL As String strSQL = "UPDATE MyTable " & _ "SET MyFirstField = " & intActive & " " & _ "WHERE MySecondField = True" Set objConn = New ADODB.Connection objConn.Open gstrConnection objConn.Execute strSQL This is just the bare bones layout. There is no error controls like 'BeginTrans' or 'RollBackTrans' or how the receiving Stored procedure should be set up or how a variable is returned etc. but I hope this is enough to get you started. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Sunday, November 07, 2004 7:50 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Dynamic from Access I think I have figured out a strategy for the nVLDB - 64 million records, ~640 fields. The deal is that the table consists of sets of fields, typically 10-20 fields, where the "subject" of the field is the same, perhaps age, income, people in household, ethnicity, drugs taken, types of music listened to, types of books read etc. I have started breaking out these sets of fields into individual tables, with a PK field that is the PK of the main table. In other words I will now have a table with perhaps 12 fields that are yes / no / null listens to music type x, y, z. Another table with perhaps 20 fields with yes / no / null takes zocor, etc. etc. I will end up breaking the 640 fields down into perhaps 30 tables where each table holds a set of fields from the original table. This allows me to index each field which was not possible with the big table simply because any given table can only contain 240 indexes. The idea now is to be able to select a handful of these subtables, perhaps income, age, music, reading and autos, join them back using the PK, then do a where income >20k and <40K, age > 20 and <30, music = blues or rock, etc... Then do a count(pk) to get a count of people having those characteristics. Additionally I can now get a count on the values in each field, 2 million no, 250k yes, 60 million null "listens to rap" etc. Sound feasible? The issue now is that I need to do this stuff programmatically from Access or perhaps a web environment (eventually). IOW, I need to build up a query joining the income, age, music, reading and autos tables on PK, throw in the where(s), and get a count of PK. I need to do this dynamically from VB (or access), where I can let the user select tables to join (sets of related fields), hand back lists of fields to select where values from, and lists of values that are actually in those fields. I can do all of that stuff, where I need assistance is how to hand the finished SQL statement off to SQL Server and have it run the query, handing back the count. I can't have Access (Jet) brute force it simply because the tables each have 64 million records in them. Just getting the PKs back to JET would take days. So, how do I hand SQL Server a dynamically built SQL statement, ask it to evaluate the SQL statement and return a single count value? Eventually I also need to have SQL take that same where clause and hand me back a set of fields / records from the main name / address subtable for sending to the bulk mail client. I am considering doing this in an ADP environment, where I build and save the SQL as a UDF or something like that- not that I've ever done anything like that before. Or get out of Access entirely (though the data environment sure is nice) and use .NET or something. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jwcolby at colbyconsulting.com Mon Nov 8 22:26:01 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Mon, 08 Nov 2004 23:26:01 -0500 Subject: [dba-SQLServer] Moving tables back and forth between databases In-Reply-To: <000701c4c58e$4cf418f0$e8dafea9@ColbyM6805> Message-ID: <000501c4c614$38047bc0$e8dafea9@ColbyM6805> Can SQL Server EM copy tables from a database in one SQL Server (Neo2) to another SQL Server (Neo1)? I am trying to tear down the big 64 million record 640 field table into sub-tables. The process consists of creating the tables, building an append query to copy the data from the big table to the new sub-table, then creating indexes on every field in the sub-table. The process of creating the new tables is relatively easy and quick, manually copying the field defs into the paste buffer, then pasting them back in to a new table. The process of creating and executing the append query is relatively painless and fairly quick though it does take a couple of hours (I think, never actually timed it) to copy the data. However the process of creating the indexes is time consuming both in the doing (manually in table design view) and particularly in the execution (saving the table with the new indexes - which can take overnight. The process of creating the indexes pretty much locks up the machine (80-100% CPU utilization) for many many hours. I would like to create the sub-tables all at once, then farm out the index creation to my other machines, but in order to do that I have to copy the data filled tables to another machine, switch to that machine, create the indexes in design view, then save the table in design view which starts the index creation process happening. I have no idea whether it is even possible to do this "table copy", but all indexes need to copy as well at least when I copy them back to the main SQL Server. On another note, how do I split the database into more files? I built it originally in 4 files, and then as I finished the import I shrank them down into two files (on two physical 250g disks). I am now pushing the size up such that I need to split them back out to at least one more 250g disk (one more file), and perhaps even two. I haven't discovered how to split the database into more physical files. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ From ebarro at afsweb.com Mon Nov 8 22:44:33 2004 From: ebarro at afsweb.com (Eric Barro) Date: Mon, 8 Nov 2004 20:44:33 -0800 Subject: [dba-SQLServer] leveraging the power of the database versus code In-Reply-To: <000701c4c58e$4cf418f0$e8dafea9@ColbyM6805> Message-ID: Ok I need to generate a crosstab query (aka pivot table) using SQL server. The problem with SQL server is that it can't handle dynamically generated columns. In other words you would need to hard code the names of the columns which assumes that you know them beforehand. However, in most cases, the column values could not be determined ahead of time. Access of course handles this with great aplomb. But SQL server? Well...that's another story. :) So...I found a way to do this utilizing a stored procedure that dynamically generates the SELECT statements and uses a temporary table to store the values. You'd think that would be the end of the story...BUT the dba balked at the proposed method since according to him SQL server was not designed to handle this sort of stuff and that the dynamically generated SELECT statements would be highly inefficient. My question then to the group is this... Is it not better to let SQL server handle the load and the processing on the server side rather than let the client side handle all that processing? To take an example: State Product1 Product2 Product3 CA 1000 500 200 MA 900 200 450 NV 600 600 600 where Products are dynamically generated The method I discovered to produce the desired results using a stored procedure worked. The suggestion I got was to handle all of that processing in code (outside of SQL server). Which means that in order to produce the desired results above, the code would need to grab the recordset from SQL server, and for each column generate the appropriate SELECT statement to return the values to either populate an in-memory array or post the results to a table from which it can read the final results. Now...given that scenario isn't it more efficient to let SQL server handle all of that processing given that it handles all of the processing on the server side instead of client side basically resulting in less round trips from the web server to the SQL server? I would appreciate feedback from you guys. The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy. The company will not accept any liability in respect of such communication. From michael at ddisolutions.com.au Mon Nov 8 23:53:55 2004 From: michael at ddisolutions.com.au (Michael Maddison) Date: Tue, 9 Nov 2004 16:53:55 +1100 Subject: [dba-SQLServer] Moving tables back and forth between databases Message-ID: <59A61174B1F5B54B97FD4ADDE71E7D0107C57F@ddi-01.DDI.local> John, I'm not sure EM or DTS will do a transfer with indexes. I'm pretty sure it wont actually. I think you will have to script the create indexes manually. What I'd do is create a script for each server, (QA will do most of the work for you) create table go append data go alter table (constraints) go create index go Then run it from the target server, that way it wont affect your main server too much. I hope your getting paid the big bucks because If you think you've had troubles before I think the fun is just about to begin ;-))) I read your other posts as well and I'm not sure if my comments will be all that helpful as I suspect you'll need a fair amount of trial and error anyway to see what works best for the environment you have to work with... However, I'm nervous about you normalising the big table. I predict you will only end up hampering performance. Joins on large table or many joins take a considerable amount of time. If you need to create separate files for space reasons have a look at Partitioned Views in BOL. This will allow you to split the table over multiple drives and multple servers. I'd also seriously try and coerce the client into taking an OLAP approach, though this also has its drawbacks as there are so many damn columns. A cube with 600 dimensions would never finish processing so maybe not :-))) Just how dynamic do the queries have to be? cheers Michael M Can SQL Server EM copy tables from a database in one SQL Server (Neo2) to another SQL Server (Neo1)? I am trying to tear down the big 64 million record 640 field table into sub-tables. The process consists of creating the tables, building an append query to copy the data from the big table to the new sub-table, then creating indexes on every field in the sub-table. The process of creating the new tables is relatively easy and quick, manually copying the field defs into the paste buffer, then pasting them back in to a new table. The process of creating and executing the append query is relatively painless and fairly quick though it does take a couple of hours (I think, never actually timed it) to copy the data. However the process of creating the indexes is time consuming both in the doing (manually in table design view) and particularly in the execution (saving the table with the new indexes - which can take overnight. The process of creating the indexes pretty much locks up the machine (80-100% CPU utilization) for many many hours. I would like to create the sub-tables all at once, then farm out the index creation to my other machines, but in order to do that I have to copy the data filled tables to another machine, switch to that machine, create the indexes in design view, then save the table in design view which starts the index creation process happening. I have no idea whether it is even possible to do this "table copy", but all indexes need to copy as well at least when I copy them back to the main SQL Server. On another note, how do I split the database into more files? I built it originally in 4 files, and then as I finished the import I shrank them down into two files (on two physical 250g disks). I am now pushing the size up such that I need to split them back out to at least one more 250g disk (one more file), and perhaps even two. I haven't discovered how to split the database into more physical files. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From fhtapia at gmail.com Tue Nov 9 00:26:38 2004 From: fhtapia at gmail.com (Francisco Tapia) Date: Mon, 8 Nov 2004 22:26:38 -0800 Subject: [dba-SQLServer] Moving tables back and forth between databases In-Reply-To: <59A61174B1F5B54B97FD4ADDE71E7D0107C57F@ddi-01.DDI.local> References: <59A61174B1F5B54B97FD4ADDE71E7D0107C57F@ddi-01.DDI.local> Message-ID: agreed, I'd first try to use a linked server to house the extended tables. This would help offload processing time, but perhaps increase network traffic, however IIRC you're on a gigabit backbone between the servers. On Tue, 9 Nov 2004 16:53:55 +1100, Michael Maddison wrote: > John, > > I'm not sure EM or DTS will do a transfer with indexes. I'm pretty sure > it wont actually. > I think you will have to script the create indexes manually. What I'd > do is create a script > for each server, (QA will do most of the work for you) > create table > go > append data > go > alter table (constraints) > go > create index > go > > Then run it from the target server, that way it wont affect your main > server too much. > > I hope your getting paid the big bucks because If you think you've had > troubles before I > think the fun is just about to begin ;-))) > > I read your other posts as well and I'm not sure if my comments will be > all that helpful as > I suspect you'll need a fair amount of trial and error anyway to see > what works best for > the environment you have to work with... > > However, I'm nervous about you normalising the big table. I predict you > will only end up > hampering performance. Joins on large table or many joins take a > considerable amount of time. > If you need to create separate files for space reasons have a look at > Partitioned Views in BOL. > This will allow you to split the table over multiple drives and multple > servers. > > I'd also seriously try and coerce the client into taking an OLAP > approach, though this also has its > drawbacks as there are so many damn columns. A cube with 600 dimensions > would never > finish processing so maybe not :-))) Just how dynamic do the queries > have to be? > > cheers > > Michael M > > > > > Can SQL Server EM copy tables from a database in one SQL Server (Neo2) > to another SQL Server (Neo1)? I am trying to tear down the big 64 > million record 640 field table into sub-tables. The process consists of > creating the tables, building an append query to copy the data from the > big table to the new sub-table, then creating indexes on every field in > the sub-table. > The process of creating the new tables is relatively easy and quick, > manually copying the field defs into the paste buffer, then pasting them > back in to a new table. The process of creating and executing the > append query is relatively painless and fairly quick though it does take > a couple of hours (I think, never actually timed it) to copy the data. > However the process of creating the indexes is time consuming both in > the doing (manually in table design view) and particularly in the > execution (saving the table with the new indexes - which can take > overnight. The process of creating the indexes pretty much locks up the > machine (80-100% CPU > utilization) for many many hours. > > I would like to create the sub-tables all at once, then farm out the > index creation to my other machines, but in order to do that I have to > copy the data filled tables to another machine, switch to that machine, > create the indexes in design view, then save the table in design view > which starts the index creation process happening. > > I have no idea whether it is even possible to do this "table copy", but > all indexes need to copy as well at least when I copy them back to the > main SQL Server. > > On another note, how do I split the database into more files? I built > it originally in 4 files, and then as I finished the import I shrank > them down into two files (on two physical 250g disks). I am now pushing > the size up such that I need to split them back out to at least one more > 250g disk (one more file), and perhaps even two. I haven't discovered > how to split the database into more physical files. > > John W. Colby > www.ColbyConsulting.com > > Contribute your unused CPU cycles to a good cause: > http://folding.stanford.edu/ > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco Pc This! pc news with out the jargon From jwcolby at colbyconsulting.com Tue Nov 9 00:51:25 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Tue, 09 Nov 2004 01:51:25 -0500 Subject: [dba-SQLServer] Moving tables back and forth between databases In-Reply-To: <59A61174B1F5B54B97FD4ADDE71E7D0107C57F@ddi-01.DDI.local> Message-ID: <000601c4c628$87e156e0$e8dafea9@ColbyM6805> I am not normalizing so much as breaking the table down into groups of related fields, which I suppose is normalization but not in the classical sense. The objective is to: 1) Get rid of having to process 640 fields at once. 2) Enable indexing ALL fields so that counts and so forth can be done in near-real time What typically happens (AFAICT) is that the person wanting to buy data asks for counts. How many records in these zip codes, where the income is in this range, age in this range and reads books (for example). That is only asking for where clauses in a handful of fields in perhaps 4 or 5 sub-tables. How do you do this at ALL on a table of 640 fields / 65 million records when SQL server only allows 240 indexes on a table? You don't. By breaking it down into address / then other related field tables, I end up having to join 4 or 5 sub-tables back on the PK of course, but I can now have every single field indexed. It appears that there are about 30 sets of related data. Again, this is never a 1 to many, just a set of 1-1 where the related data sets are pulled out into separate tables. And again, it's not like the client will ask questions about all 30 sub tables. Without an index a table scan on any one field would take a lifetime - well, actually about 24 hours. A simple count of a single field grouped to show all values and their count returns in about 30 seconds. So yea, I have to live with the join on the indexes putting 4 or 5 tables back together, but the count (per field?) drops from 24 hours to 30 seconds. I won't pretend that I have actually tried this yet (counts of joined tables), but I will be soon, and I'll report back with results. Bottom line, there is simply no other way to handle this at least on the full table. Furthermore, eventually I am looking to use the system to return actual data sets on the same where clause, i.e. a half million actual address records given a set of zip codes, income range, age range, reads books etc. This is more than simple data mining I think, it is asking COUNT questions on N fields selected more or less at random. ALWAYS a count. Then hopefully someday "ok give me 250k of those records" (actual address data). The big question... Will the query processor perform the where on each sub table, then join the results? Or join the 65 million record sub tables, then perform the wheres? Could I force the previous scenario somehow? Pull the N records (PK of) that fall in the given zip codes, then the M PKs of the records that fall in the selected income bracket, then the O PKs that fall in the selected age bracket, then the P PKs that... And then at the end join the result sets on the PKs returned in each of the subs? That should be relatively fast you would think, assuming an index on each and every field. Remember too that this is a static db, i.e.no records are added on a daily basis, so the large number of indexes don't kill you in adding / deleting / modifying records since you don't do that. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Michael Maddison Sent: Tuesday, November 09, 2004 12:54 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Moving tables back and forth between databases John, I'm not sure EM or DTS will do a transfer with indexes. I'm pretty sure it wont actually. I think you will have to script the create indexes manually. What I'd do is create a script for each server, (QA will do most of the work for you) create table go append data go alter table (constraints) go create index go Then run it from the target server, that way it wont affect your main server too much. I hope your getting paid the big bucks because If you think you've had troubles before I think the fun is just about to begin ;-))) I read your other posts as well and I'm not sure if my comments will be all that helpful as I suspect you'll need a fair amount of trial and error anyway to see what works best for the environment you have to work with... However, I'm nervous about you normalising the big table. I predict you will only end up hampering performance. Joins on large table or many joins take a considerable amount of time. If you need to create separate files for space reasons have a look at Partitioned Views in BOL. This will allow you to split the table over multiple drives and multple servers. I'd also seriously try and coerce the client into taking an OLAP approach, though this also has its drawbacks as there are so many damn columns. A cube with 600 dimensions would never finish processing so maybe not :-))) Just how dynamic do the queries have to be? cheers Michael M Can SQL Server EM copy tables from a database in one SQL Server (Neo2) to another SQL Server (Neo1)? I am trying to tear down the big 64 million record 640 field table into sub-tables. The process consists of creating the tables, building an append query to copy the data from the big table to the new sub-table, then creating indexes on every field in the sub-table. The process of creating the new tables is relatively easy and quick, manually copying the field defs into the paste buffer, then pasting them back in to a new table. The process of creating and executing the append query is relatively painless and fairly quick though it does take a couple of hours (I think, never actually timed it) to copy the data. However the process of creating the indexes is time consuming both in the doing (manually in table design view) and particularly in the execution (saving the table with the new indexes - which can take overnight. The process of creating the indexes pretty much locks up the machine (80-100% CPU utilization) for many many hours. I would like to create the sub-tables all at once, then farm out the index creation to my other machines, but in order to do that I have to copy the data filled tables to another machine, switch to that machine, create the indexes in design view, then save the table in design view which starts the index creation process happening. I have no idea whether it is even possible to do this "table copy", but all indexes need to copy as well at least when I copy them back to the main SQL Server. On another note, how do I split the database into more files? I built it originally in 4 files, and then as I finished the import I shrank them down into two files (on two physical 250g disks). I am now pushing the size up such that I need to split them back out to at least one more 250g disk (one more file), and perhaps even two. I haven't discovered how to split the database into more physical files. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From mark.breen at gmail.com Tue Nov 9 04:53:41 2004 From: mark.breen at gmail.com (Mark Breen) Date: Tue, 9 Nov 2004 10:53:41 +0000 Subject: [dba-SQLServer] leveraging the power of the database versus code In-Reply-To: References: <000701c4c58e$4cf418f0$e8dafea9@ColbyM6805> Message-ID: <26a96cce04110902536ed024d6@mail.gmail.com> Hello Eric, I am interested in this topic also. I recently had to create a SQL statement that selected the top n number of records. It was a reasonably complex sql statement filtering on a table with 12 million records. In SQL you can say Select top 10 .... but you cannot say Select top @MyValue .... So, the only way I could think of doing this was by concatenating a sql string together and then executing it. Of course this is similar to what you are doing and the downside is that SQL can never precompile the sql because it is effectively dynamic. Performance did drop, and in the end, I had to drop ,my order by clause which gained me a little increase in speed, however, I would have preferred not to drop it. I have no suggestions for myself, and I am interested in whether you get any insights for your very similar problem. Thanks Eric, Mark Breen Ireland On Mon, 8 Nov 2004 20:44:33 -0800, Eric Barro wrote: > Ok I need to generate a crosstab query (aka pivot table) using SQL server. The problem with SQL server is that it can't handle dynamically generated columns. In other words you would need to hard code the names of the columns which assumes that you know them beforehand. However, in most cases, the column values could not be determined ahead of time. Access of course handles this with great aplomb. But SQL server? Well...that's another story. :) > > So...I found a way to do this utilizing a stored procedure that dynamically generates the SELECT statements and uses a temporary table to store the values. You'd think that would be the end of the story...BUT the dba balked at the proposed method since according to him SQL server was not designed to handle this sort of stuff and that the dynamically generated SELECT statements would be highly inefficient. > > My question then to the group is this... > > Is it not better to let SQL server handle the load and the processing on the server side rather than let the client side handle all that processing? > > To take an example: > > State Product1 Product2 Product3 > CA 1000 500 200 > MA 900 200 450 > NV 600 600 600 > > where Products are dynamically generated > > The method I discovered to produce the desired results using a stored procedure worked. The suggestion I got was to handle all of that processing in code (outside of SQL server). Which means that in order to produce the desired results above, the code would need to grab the recordset from SQL server, and for each column generate the appropriate SELECT statement to return the values to either populate an in-memory array or post the results to a table from which it can read the final results. > > Now...given that scenario isn't it more efficient to let SQL server handle all of that processing given that it handles all of the processing on the server side instead of client side basically resulting in less round trips from the web server to the SQL server? > > I would appreciate feedback from you guys. > > The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. > The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy. The company will not accept any liability in respect of such communication. > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > From mmaddison at optusnet.com.au Tue Nov 9 08:09:14 2004 From: mmaddison at optusnet.com.au (Michael Maddison) Date: Wed, 10 Nov 2004 01:09:14 +1100 Subject: [dba-SQLServer] leveraging the power of the database versus code In-Reply-To: <26a96cce04110902536ed024d6@mail.gmail.com> Message-ID: Hi guys, I don't think there are any really good ways of pivoting in SQL 2K... I have a db that requires some reports based on pivot tables, but I'm lucky in that the data is only updated each month so I schedule a sproc that updates a scratch table with the pivoted data, it takes quite a while but once its done the reports run like a dream. We use cursors and a loop. Another option is to use OLAP. You state that using dynamic sql means that the sproc is not precompiled... I think this is wrong! Its probably using the 1st sql statement run since last startups plan. Which may explain your performance problems.. or not :-) Try adding WITH RECOMPILE to the sproc. This will force SQL to create a new plan each execution. Also check out parameter sniffing which may be hurting you as well. I presume your indexes are ok and the plan in QA shows only seeks not scans? cheers Michael M Hello Eric, I am interested in this topic also. I recently had to create a SQL statement that selected the top n number of records. It was a reasonably complex sql statement filtering on a table with 12 million records. In SQL you can say Select top 10 .... but you cannot say Select top @MyValue .... So, the only way I could think of doing this was by concatenating a sql string together and then executing it. Of course this is similar to what you are doing and the downside is that SQL can never precompile the sql because it is effectively dynamic. Performance did drop, and in the end, I had to drop ,my order by clause which gained me a little increase in speed, however, I would have preferred not to drop it. I have no suggestions for myself, and I am interested in whether you get any insights for your very similar problem. Thanks Eric, Mark Breen Ireland On Mon, 8 Nov 2004 20:44:33 -0800, Eric Barro wrote: > Ok I need to generate a crosstab query (aka pivot table) using SQL server. The problem with SQL server is that it can't handle dynamically generated columns. In other words you would need to hard code the names of the columns which assumes that you know them beforehand. However, in most cases, the column values could not be determined ahead of time. Access of course handles this with great aplomb. But SQL server? Well...that's another story. :) > > So...I found a way to do this utilizing a stored procedure that dynamically generates the SELECT statements and uses a temporary table to store the values. You'd think that would be the end of the story...BUT the dba balked at the proposed method since according to him SQL server was not designed to handle this sort of stuff and that the dynamically generated SELECT statements would be highly inefficient. > > My question then to the group is this... > > Is it not better to let SQL server handle the load and the processing on the server side rather than let the client side handle all that processing? > > To take an example: > > State Product1 Product2 Product3 > CA 1000 500 200 > MA 900 200 450 > NV 600 600 600 > > where Products are dynamically generated > > The method I discovered to produce the desired results using a stored procedure worked. The suggestion I got was to handle all of that processing in code (outside of SQL server). Which means that in order to produce the desired results above, the code would need to grab the recordset from SQL server, and for each column generate the appropriate SELECT statement to return the values to either populate an in-memory array or post the results to a table from which it can read the final results. > > Now...given that scenario isn't it more efficient to let SQL server handle all of that processing given that it handles all of the processing on the server side instead of client side basically resulting in less round trips from the web server to the SQL server? > > I would appreciate feedback from you guys. > > The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. > The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy. The company will not accept any liability in respect of such communication. > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.718 / Virus Database: 474 - Release Date: 9/07/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.718 / Virus Database: 474 - Release Date: 9/07/2004 From JColby at dispec.com Tue Nov 9 08:45:56 2004 From: JColby at dispec.com (Colby, John) Date: Tue, 9 Nov 2004 09:45:56 -0500 Subject: [dba-SQLServer] Moving tables back and forth between database s Message-ID: <05C61C52D7CAD211A7830008C7DF6F10CBF95F@DISABILITYINS01> Francisco, I do have a gigabit switch connecting all the machines. Even there, if each machine does all processing of its piece and just returned a data set to a control server, the total data over the wire would be fairly small. I would love to distribute the processing to different machines. I have potentially 4 3ghz machines with up to 3gb of ram on each machine. Assume that there are 30 sub-tables. If each machine could take a set of these sub-tables (8 each) and then each machine were to do the processing of the portion of the sql statement that was defined by the sub-tables each machine held, I could effectively multiply my processing power by a factor of 4 or so. Further, if this worked, I could add additional machines if required. Has anyone on this list ever done something of this nature? John W. Colby The DIS Database Guy -----Original Message----- From: Francisco Tapia [mailto:fhtapia at gmail.com] Sent: Tuesday, November 09, 2004 1:27 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Moving tables back and forth between databases agreed, I'd first try to use a linked server to house the extended tables. This would help offload processing time, but perhaps increase network traffic, however IIRC you're on a gigabit backbone between the servers. On Tue, 9 Nov 2004 16:53:55 +1100, Michael Maddison wrote: > John, > > I'm not sure EM or DTS will do a transfer with indexes. I'm pretty sure > it wont actually. > I think you will have to script the create indexes manually. What I'd > do is create a script > for each server, (QA will do most of the work for you) > create table > go > append data > go > alter table (constraints) > go > create index > go > > Then run it from the target server, that way it wont affect your main > server too much. > > I hope your getting paid the big bucks because If you think you've had > troubles before I > think the fun is just about to begin ;-))) > > I read your other posts as well and I'm not sure if my comments will be > all that helpful as > I suspect you'll need a fair amount of trial and error anyway to see > what works best for > the environment you have to work with... > > However, I'm nervous about you normalising the big table. I predict you > will only end up > hampering performance. Joins on large table or many joins take a > considerable amount of time. > If you need to create separate files for space reasons have a look at > Partitioned Views in BOL. > This will allow you to split the table over multiple drives and multple > servers. > > I'd also seriously try and coerce the client into taking an OLAP > approach, though this also has its > drawbacks as there are so many damn columns. A cube with 600 dimensions > would never > finish processing so maybe not :-))) Just how dynamic do the queries > have to be? > > cheers > > Michael M > > > > > Can SQL Server EM copy tables from a database in one SQL Server (Neo2) > to another SQL Server (Neo1)? I am trying to tear down the big 64 > million record 640 field table into sub-tables. The process consists of > creating the tables, building an append query to copy the data from the > big table to the new sub-table, then creating indexes on every field in > the sub-table. > The process of creating the new tables is relatively easy and quick, > manually copying the field defs into the paste buffer, then pasting them > back in to a new table. The process of creating and executing the > append query is relatively painless and fairly quick though it does take > a couple of hours (I think, never actually timed it) to copy the data. > However the process of creating the indexes is time consuming both in > the doing (manually in table design view) and particularly in the > execution (saving the table with the new indexes - which can take > overnight. The process of creating the indexes pretty much locks up the > machine (80-100% CPU > utilization) for many many hours. > > I would like to create the sub-tables all at once, then farm out the > index creation to my other machines, but in order to do that I have to > copy the data filled tables to another machine, switch to that machine, > create the indexes in design view, then save the table in design view > which starts the index creation process happening. > > I have no idea whether it is even possible to do this "table copy", but > all indexes need to copy as well at least when I copy them back to the > main SQL Server. > > On another note, how do I split the database into more files? I built > it originally in 4 files, and then as I finished the import I shrank > them down into two files (on two physical 250g disks). I am now pushing > the size up such that I need to split them back out to at least one more > 250g disk (one more file), and perhaps even two. I haven't discovered > how to split the database into more physical files. > > John W. Colby > www.ColbyConsulting.com > > Contribute your unused CPU cycles to a good cause: > http://folding.stanford.edu/ > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco Pc This! pc news with out the jargon _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From ebarro at afsweb.com Tue Nov 9 08:51:18 2004 From: ebarro at afsweb.com (Eric Barro) Date: Tue, 9 Nov 2004 06:51:18 -0800 Subject: [dba-SQLServer] leveraging the power of the database versus code In-Reply-To: Message-ID: Michael, I really didn't see any performance problems when I ran the stored procedure so I was baffled why our dba was not very keen on having me implement the solution I found. I also read somewhere that SQL server (at least from ver 7.0 and above) uses a stored procedure called sp_executesql that uses the same execution plan for similar queries and since each SELECT statement for each dynamic column would be about the same (the only change would be the column name), I believe that SQL server was in fact doing exactly just that. Eric -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Michael Maddison Sent: Tuesday, November 09, 2004 6:09 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] leveraging the power of the database versus code Hi guys, I don't think there are any really good ways of pivoting in SQL 2K... I have a db that requires some reports based on pivot tables, but I'm lucky in that the data is only updated each month so I schedule a sproc that updates a scratch table with the pivoted data, it takes quite a while but once its done the reports run like a dream. We use cursors and a loop. Another option is to use OLAP. You state that using dynamic sql means that the sproc is not precompiled... I think this is wrong! Its probably using the 1st sql statement run since last startups plan. Which may explain your performance problems.. or not :-) Try adding WITH RECOMPILE to the sproc. This will force SQL to create a new plan each execution. Also check out parameter sniffing which may be hurting you as well. I presume your indexes are ok and the plan in QA shows only seeks not scans? cheers Michael M Hello Eric, I am interested in this topic also. I recently had to create a SQL statement that selected the top n number of records. It was a reasonably complex sql statement filtering on a table with 12 million records. In SQL you can say Select top 10 .... but you cannot say Select top @MyValue .... So, the only way I could think of doing this was by concatenating a sql string together and then executing it. Of course this is similar to what you are doing and the downside is that SQL can never precompile the sql because it is effectively dynamic. Performance did drop, and in the end, I had to drop ,my order by clause which gained me a little increase in speed, however, I would have preferred not to drop it. I have no suggestions for myself, and I am interested in whether you get any insights for your very similar problem. Thanks Eric, Mark Breen Ireland On Mon, 8 Nov 2004 20:44:33 -0800, Eric Barro wrote: > Ok I need to generate a crosstab query (aka pivot table) using SQL server. The problem with SQL server is that it can't handle dynamically generated columns. In other words you would need to hard code the names of the columns which assumes that you know them beforehand. However, in most cases, the column values could not be determined ahead of time. Access of course handles this with great aplomb. But SQL server? Well...that's another story. :) > > So...I found a way to do this utilizing a stored procedure that dynamically generates the SELECT statements and uses a temporary table to store the values. You'd think that would be the end of the story...BUT the dba balked at the proposed method since according to him SQL server was not designed to handle this sort of stuff and that the dynamically generated SELECT statements would be highly inefficient. > > My question then to the group is this... > > Is it not better to let SQL server handle the load and the processing on the server side rather than let the client side handle all that processing? > > To take an example: > > State Product1 Product2 Product3 > CA 1000 500 200 > MA 900 200 450 > NV 600 600 600 > > where Products are dynamically generated > > The method I discovered to produce the desired results using a stored procedure worked. The suggestion I got was to handle all of that processing in code (outside of SQL server). Which means that in order to produce the desired results above, the code would need to grab the recordset from SQL server, and for each column generate the appropriate SELECT statement to return the values to either populate an in-memory array or post the results to a table from which it can read the final results. > > Now...given that scenario isn't it more efficient to let SQL server handle all of that processing given that it handles all of the processing on the server side instead of client side basically resulting in less round trips from the web server to the SQL server? > > I would appreciate feedback from you guys. The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy. The company will not accept any liability in respect of such communication. From artful at rogers.com Tue Nov 9 10:49:43 2004 From: artful at rogers.com (Arthur Fuller) Date: Tue, 09 Nov 2004 11:49:43 -0500 Subject: [dba-SQLServer] leveraging the power of the database versus code In-Reply-To: <26a96cce04110902536ed024d6@mail.gmail.com> References: <000701c4c58e$4cf418f0$e8dafea9@ColbyM6805> <26a96cce04110902536ed024d6@mail.gmail.com> Message-ID: <4190F527.6040009@rogers.com> Mark Breen wrote: >Hello Eric, > >I am interested in this topic also. > >I recently had to create a SQL statement that selected the top n >number of records. It was a reasonably complex sql statement >filtering on a table with 12 million records. > >In SQL you can say Select top 10 .... but you cannot say Select top >@MyValue .... > > > > One little footnore. In SQL 2005 you can say SELECT TOP @n. From mark.breen at gmail.com Tue Nov 9 12:37:56 2004 From: mark.breen at gmail.com (Mark Breen) Date: Tue, 9 Nov 2004 18:37:56 +0000 Subject: [dba-SQLServer] leveraging the power of the database versus code In-Reply-To: <4190F527.6040009@rogers.com> References: <000701c4c58e$4cf418f0$e8dafea9@ColbyM6805> <26a96cce04110902536ed024d6@mail.gmail.com> <4190F527.6040009@rogers.com> Message-ID: <26a96cce04110910375d4c202b@mail.gmail.com> Hello Arthur, Ahhh, it seems like it was a crazy feature to exclude, I have wondered why they did not allow us to do it. Thanks for that, I have the beta installed on a machine so I will have to have a more detailed play with it. Have you used SQL2005 much? What do you think of it? Thanks Mark On Tue, 09 Nov 2004 11:49:43 -0500, Arthur Fuller wrote: > Mark Breen wrote: > > >Hello Eric, > > > >I am interested in this topic also. > > > >I recently had to create a SQL statement that selected the top n > >number of records. It was a reasonably complex sql statement > >filtering on a table with 12 million records. > > > >In SQL you can say Select top 10 .... but you cannot say Select top > >@MyValue .... > > > > > > > > > One little footnore. In SQL 2005 you can say SELECT TOP @n. > _______________________________________________ > > > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > From fhtapia at gmail.com Tue Nov 9 17:03:55 2004 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 9 Nov 2004 15:03:55 -0800 Subject: [dba-SQLServer] Moving tables back and forth between database s In-Reply-To: <05C61C52D7CAD211A7830008C7DF6F10CBF95F@DISABILITYINS01> References: <05C61C52D7CAD211A7830008C7DF6F10CBF95F@DISABILITYINS01> Message-ID: John, Here are some tips for you to distrbute your processing around other servers ;o) http://www.sql-server-performance.com/linked_server.asp By default, when you run a distributed query using a linked server, the query is processed locally. This may or may not be efficient, depending on how much data must be sent from the remote server to the local server for processing. Sometimes it is more efficient to pass through the query so that it is run on the remote server. This way, if the query must process many rows, it can process them on the remote server, and only return to the local server the results of the query. The OPENQUERY function is used to specify that a distributed query be processed on the remote server instead of the local server. [7.0, 2000] Updated 2-16-2004 you can read more on the link I provided above... and of course any part of the openquery returned is processed locally, so you can define how many fields or which data to get back... :) On Tue, 9 Nov 2004 09:45:56 -0500, Colby, John wrote: > Francisco, > > I do have a gigabit switch connecting all the machines. Even there, if each > machine does all processing of its piece and just returned a data set to a > control server, the total data over the wire would be fairly small. > > I would love to distribute the processing to different machines. I have > potentially 4 3ghz machines with up to 3gb of ram on each machine. Assume > that there are 30 sub-tables. If each machine could take a set of these > sub-tables (8 each) and then each machine were to do the processing of the > portion of the sql statement that was defined by the sub-tables each machine > held, I could effectively multiply my processing power by a factor of 4 or > so. Further, if this worked, I could add additional machines if required. > > Has anyone on this list ever done something of this nature? > > John W. Colby > The DIS Database Guy > > -----Original Message----- > From: Francisco Tapia [mailto:fhtapia at gmail.com] > Sent: Tuesday, November 09, 2004 1:27 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Moving tables back and forth between > databases > > agreed, I'd first try to use a linked server to house the extended > tables. This would help offload processing time, but perhaps increase > network traffic, however IIRC you're on a gigabit backbone between the > servers. > > On Tue, 9 Nov 2004 16:53:55 +1100, Michael Maddison > wrote: > > John, > > > > I'm not sure EM or DTS will do a transfer with indexes. I'm pretty sure > > it wont actually. > > I think you will have to script the create indexes manually. What I'd > > do is create a script > > for each server, (QA will do most of the work for you) > > create table > > go > > append data > > go > > alter table (constraints) > > go > > create index > > go > > > > Then run it from the target server, that way it wont affect your main > > server too much. > > > > I hope your getting paid the big bucks because If you think you've had > > troubles before I > > think the fun is just about to begin ;-))) > > > > I read your other posts as well and I'm not sure if my comments will be > > all that helpful as > > I suspect you'll need a fair amount of trial and error anyway to see > > what works best for > > the environment you have to work with... > > > > However, I'm nervous about you normalising the big table. I predict you > > will only end up > > hampering performance. Joins on large table or many joins take a > > considerable amount of time. > > If you need to create separate files for space reasons have a look at > > Partitioned Views in BOL. > > This will allow you to split the table over multiple drives and multple > > servers. > > > > I'd also seriously try and coerce the client into taking an OLAP > > approach, though this also has its > > drawbacks as there are so many damn columns. A cube with 600 dimensions > > would never > > finish processing so maybe not :-))) Just how dynamic do the queries > > have to be? > > > > cheers > > > > Michael M > > > > > > > > > > Can SQL Server EM copy tables from a database in one SQL Server (Neo2) > > to another SQL Server (Neo1)? I am trying to tear down the big 64 > > million record 640 field table into sub-tables. The process consists of > > creating the tables, building an append query to copy the data from the > > big table to the new sub-table, then creating indexes on every field in > > the sub-table. > > The process of creating the new tables is relatively easy and quick, > > manually copying the field defs into the paste buffer, then pasting them > > back in to a new table. The process of creating and executing the > > append query is relatively painless and fairly quick though it does take > > a couple of hours (I think, never actually timed it) to copy the data. > > However the process of creating the indexes is time consuming both in > > the doing (manually in table design view) and particularly in the > > execution (saving the table with the new indexes - which can take > > overnight. The process of creating the indexes pretty much locks up the > > machine (80-100% CPU > > utilization) for many many hours. > > > > I would like to create the sub-tables all at once, then farm out the > > index creation to my other machines, but in order to do that I have to > > copy the data filled tables to another machine, switch to that machine, > > create the indexes in design view, then save the table in design view > > which starts the index creation process happening. > > > > I have no idea whether it is even possible to do this "table copy", but > > all indexes need to copy as well at least when I copy them back to the > > main SQL Server. > > > > On another note, how do I split the database into more files? I built > > it originally in 4 files, and then as I finished the import I shrank > > them down into two files (on two physical 250g disks). I am now pushing > > the size up such that I need to split them back out to at least one more > > 250g disk (one more file), and perhaps even two. I haven't discovered > > how to split the database into more physical files. > > > > John W. Colby > > www.ColbyConsulting.com > > > > Contribute your unused CPU cycles to a good cause: > > http://folding.stanford.edu/ > > > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > > > -- > -Francisco > Pc This! pc news with out the > jargon > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco Pc This! pc news with out the jargon From jwcolby at colbyconsulting.com Tue Nov 9 18:38:06 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Tue, 09 Nov 2004 19:38:06 -0500 Subject: [dba-SQLServer] Moving tables back and forth between database s In-Reply-To: Message-ID: <002601c4c6bd$8fad62c0$e8dafea9@ColbyM6805> Thanks Francisco. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, November 09, 2004 6:04 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Moving tables back and forth between database s John, Here are some tips for you to distrbute your processing around other servers ;o) http://www.sql-server-performance.com/linked_server.asp By default, when you run a distributed query using a linked server, the query is processed locally. This may or may not be efficient, depending on how much data must be sent from the remote server to the local server for processing. Sometimes it is more efficient to pass through the query so that it is run on the remote server. This way, if the query must process many rows, it can process them on the remote server, and only return to the local server the results of the query. The OPENQUERY function is used to specify that a distributed query be processed on the remote server instead of the local server. [7.0, 2000] Updated 2-16-2004 you can read more on the link I provided above... and of course any part of the openquery returned is processed locally, so you can define how many fields or which data to get back... :) On Tue, 9 Nov 2004 09:45:56 -0500, Colby, John wrote: > Francisco, > > I do have a gigabit switch connecting all the machines. Even there, > if each machine does all processing of its piece and just returned a > data set to a control server, the total data over the wire would be > fairly small. > > I would love to distribute the processing to different machines. I > have potentially 4 3ghz machines with up to 3gb of ram on each > machine. Assume that there are 30 sub-tables. If each machine could > take a set of these sub-tables (8 each) and then each machine were to > do the processing of the portion of the sql statement that was defined > by the sub-tables each machine held, I could effectively multiply my > processing power by a factor of 4 or so. Further, if this worked, I > could add additional machines if required. > > Has anyone on this list ever done something of this nature? > > John W. Colby > The DIS Database Guy > > -----Original Message----- > From: Francisco Tapia [mailto:fhtapia at gmail.com] > Sent: Tuesday, November 09, 2004 1:27 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Moving tables back and forth between > databases > > agreed, I'd first try to use a linked server to house the extended > tables. This would help offload processing time, but perhaps increase > network traffic, however IIRC you're on a gigabit backbone between the > servers. > > On Tue, 9 Nov 2004 16:53:55 +1100, Michael Maddison > wrote: > > John, > > > > I'm not sure EM or DTS will do a transfer with indexes. I'm pretty > > sure it wont actually. I think you will have to script the create > > indexes manually. What I'd do is create a script > > for each server, (QA will do most of the work for you) > > create table > > go > > append data > > go > > alter table (constraints) > > go > > create index > > go > > > > Then run it from the target server, that way it wont affect your > > main server too much. > > > > I hope your getting paid the big bucks because If you think you've > > had troubles before I think the fun is just about to begin ;-))) > > > > I read your other posts as well and I'm not sure if my comments will > > be all that helpful as I suspect you'll need a fair amount of trial > > and error anyway to see what works best for > > the environment you have to work with... > > > > However, I'm nervous about you normalising the big table. I predict > > you will only end up hampering performance. Joins on large table or > > many joins take a considerable amount of time. > > If you need to create separate files for space reasons have a look at > > Partitioned Views in BOL. > > This will allow you to split the table over multiple drives and multple > > servers. > > > > I'd also seriously try and coerce the client into taking an OLAP > > approach, though this also has its drawbacks as there are so many > > damn columns. A cube with 600 dimensions would never > > finish processing so maybe not :-))) Just how dynamic do the queries > > have to be? > > > > cheers > > > > Michael M > > > > > > > > > > Can SQL Server EM copy tables from a database in one SQL Server > > (Neo2) to another SQL Server (Neo1)? I am trying to tear down the > > big 64 million record 640 field table into sub-tables. The process > > consists of creating the tables, building an append query to copy > > the data from the big table to the new sub-table, then creating > > indexes on every field in the sub-table. The process of creating the > > new tables is relatively easy and quick, manually copying the field > > defs into the paste buffer, then pasting them back in to a new > > table. The process of creating and executing the append query is > > relatively painless and fairly quick though it does take a couple of > > hours (I think, never actually timed it) to copy the data. However > > the process of creating the indexes is time consuming both in the > > doing (manually in table design view) and particularly in the > > execution (saving the table with the new indexes - which can take > > overnight. The process of creating the indexes pretty much locks up > > the machine (80-100% CPU > > utilization) for many many hours. > > > > I would like to create the sub-tables all at once, then farm out the > > index creation to my other machines, but in order to do that I have > > to copy the data filled tables to another machine, switch to that > > machine, create the indexes in design view, then save the table in > > design view which starts the index creation process happening. > > > > I have no idea whether it is even possible to do this "table copy", > > but all indexes need to copy as well at least when I copy them back > > to the main SQL Server. > > > > On another note, how do I split the database into more files? I > > built it originally in 4 files, and then as I finished the import I > > shrank them down into two files (on two physical 250g disks). I am > > now pushing the size up such that I need to split them back out to > > at least one more 250g disk (one more file), and perhaps even two. > > I haven't discovered how to split the database into more physical > > files. > > > > John W. Colby > > www.ColbyConsulting.com > > > > Contribute your unused CPU cycles to a good cause: > > http://folding.stanford.edu/ > > > > _______________________________________________ > > dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > _______________________________________________ > > dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > > > -- > -Francisco > Pc This! pc news with out the > jargon > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco Pc This! pc news with out the jargon _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From tuxedo_man at hotmail.com Wed Nov 10 17:09:24 2004 From: tuxedo_man at hotmail.com (Billy Pang) Date: Wed, 10 Nov 2004 23:09:24 +0000 Subject: [dba-SQLServer] OT: global search and replace Message-ID: just curious, does anyone have a tool they recommend for performing global "search and replace" on text files? preferrably can handle text files saved in unicode text format. and free :) thanks Billy From stuart at lexacorp.com.pg Wed Nov 10 18:26:29 2004 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Thu, 11 Nov 2004 10:26:29 +1000 Subject: [dba-SQLServer] OT: global search and replace In-Reply-To: Message-ID: <41933E55.11400.2AD0B95@lexacorp.com.pg> On 10 Nov 2004 at 23:09, Billy Pang wrote: > just curious, does anyone have a tool they recommend for performing global > "search and replace" on text files? preferrably can handle text files saved > in unicode text format. and free :) > Take a look at: http://www.pricelessware.org/thelist/fil.htm#Search%20And%20Replace I've also got a couple of free utilities on my website (for single files and not unicode though). LineStrp: A utility to strip or modify lines from a text document (or text copied to the clipboard) if the lines contain a certain string ( or alternatively, if they don't contain the string) You can replace various parts of a matching line or remove it completely. Handy for extracting just the info you need from modem log files etc, stripping comments out of source code, changing multiple occurrences of a string throughout a file or stripping leading ">"s from an email. Also lets you easily view the original and stripped files so that you can change your stripping options. Ver 1.5 also lets you remove empty lines. Version 2.0 adds a command line interface so that you can run Linestrip from a batch file CharRepl: A variation on LineStrip, this utility lets you remove or replace characters in any file, not just line delimited files. It can globally replace any byte values. You could for instance use it to replace every CR in a Unix text file and replace them with CR/LF pairs for use in DOS/WIndows. Also lets you easily view the original and stripped files, (text files only - view binary files at your own risk!) -- Stuart From roz.clarke at donnslaw.co.uk Tue Nov 16 05:25:14 2004 From: roz.clarke at donnslaw.co.uk (Roz Clarke) Date: Tue, 16 Nov 2004 11:25:14 -0000 Subject: [dba-SQLServer] cross-posted - sql dba services Message-ID: <61F915314798D311A2F800A0C9C8318805CED7A8@dibble.observatory.donnslaw.co.uk> Hi all A couple of years ago I was recruiting for someone with SQL Server DBA skills, and someone from accessd put his company forward to provide those skills on a consultancy basis if I had trouble recruiting. At that time I found someone who was very good, but as good people do, he has now moved onwards & upwards to greater things. We are struggling to replace him; is anyone on the list currently providing SQL DBA consultancy in the North West of England? We have some potential projects coming up which are beyond our in-house skill set, and it would be nice to know if there is an alternative to hiring someone permanent. Many thanks Roz -------------- next part -------------- The contents of this message and any attachments are the property of Donns Solicitors and are intended for the confidential use of the named recipient only. They may be legally privileged and should not be communicated to, or relied upon, by any other party without our written consent. If you are not the addressee, please notify us immediately so that we can make arrangements for its return. You should not show this e-mail to any person or take copies as you may be committing a criminal or civil offence for which you may be liable. The statement and opinions expressed in this e-mail message are those of the writer, and do not necessarily represent that of Donns Solicitors. Although any files attached to this e-mail will have been checked with virus protection software prior to transmission, you should carry out your own virus check before opening any attachment. Donns Solicitors does not accept any liability for any damage or loss which may be caused by software viruses... From fhtapia at gmail.com Wed Nov 17 00:01:07 2004 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 16 Nov 2004 22:01:07 -0800 Subject: [dba-SQLServer] cross-posted - sql dba services In-Reply-To: <61F915314798D311A2F800A0C9C8318805CED7A8@dibble.observatory.donnslaw.co.uk> References: <61F915314798D311A2F800A0C9C8318805CED7A8@dibble.observatory.donnslaw.co.uk> Message-ID: no, but I think that if you need help with basic (and sometimes more complex problems) you can post them here, unless it's more confidential. On Tue, 16 Nov 2004 11:25:14 -0000, Roz Clarke wrote: > Hi all > > A couple of years ago I was recruiting for someone with SQL Server DBA > skills, and someone from accessd put his company forward to provide those > skills on a consultancy basis if I had trouble recruiting. > > At that time I found someone who was very good, but as good people do, he > has now moved onwards & upwards to greater things. We are struggling to > replace him; is anyone on the list currently providing SQL DBA consultancy > in the North West of England? We have some potential projects coming up > which are beyond our in-house skill set, and it would be nice to know if > there is an alternative to hiring someone permanent. > > Many thanks > > Roz > > > > The contents of this message and any attachments are the property of Donns Solicitors > and are intended for the confidential use of the named recipient only. They may be legally > privileged and should not be communicated to, or relied upon, by any other party without > our written consent. If you are not the addressee, please notify us immediately so that we > can make arrangements for its return. You should not show this e-mail to any person or > take copies as you may be committing a criminal or civil offence for which you may be > liable. The statement and opinions expressed in this e-mail message are those of the > writer, and do not necessarily represent that of Donns Solicitors. Although any files attached > to this e-mail will have been checked with virus protection software prior to transmission, > you should carry out your own virus check before opening any attachment. > Donns Solicitors does not accept any liability for any damage or loss which may be caused > by software viruses... > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > > -- -Francisco http://pcthis.blogspot.com | PC news with out the jargon! From mark.breen at gmail.com Wed Nov 17 16:11:00 2004 From: mark.breen at gmail.com (Mark Breen) Date: Wed, 17 Nov 2004 22:11:00 +0000 Subject: [dba-SQLServer] cross-posted - sql dba services In-Reply-To: <61F915314798D311A2F800A0C9C8318805CED7A8@dibble.observatory.donnslaw.co.uk> References: <61F915314798D311A2F800A0C9C8318805CED7A8@dibble.observatory.donnslaw.co.uk> Message-ID: <26a96cce041117141167d80954@mail.gmail.com> Hello Roz, I have sent a reply to you personal email, but both bounced, do you have an alternative? Cheers, Mark Breen Ireland On Tue, 16 Nov 2004 11:25:14 -0000, Roz Clarke wrote: > Hi all > > A couple of years ago I was recruiting for someone with SQL Server DBA > skills, and someone from accessd put his company forward to provide those > skills on a consultancy basis if I had trouble recruiting. > > At that time I found someone who was very good, but as good people do, he > has now moved onwards & upwards to greater things. We are struggling to > replace him; is anyone on the list currently providing SQL DBA consultancy > in the North West of England? We have some potential projects coming up > which are beyond our in-house skill set, and it would be nice to know if > there is an alternative to hiring someone permanent. > > Many thanks > > Roz > > > > The contents of this message and any attachments are the property of Donns Solicitors > and are intended for the confidential use of the named recipient only. They may be legally > privileged and should not be communicated to, or relied upon, by any other party without > our written consent. If you are not the addressee, please notify us immediately so that we > can make arrangements for its return. You should not show this e-mail to any person or > take copies as you may be committing a criminal or civil offence for which you may be > liable. The statement and opinions expressed in this e-mail message are those of the > writer, and do not necessarily represent that of Donns Solicitors. Although any files attached > to this e-mail will have been checked with virus protection software prior to transmission, > you should carry out your own virus check before opening any attachment. > Donns Solicitors does not accept any liability for any damage or loss which may be caused > by software viruses... > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > > From jwcolby at colbyconsulting.com Wed Nov 17 20:34:14 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Wed, 17 Nov 2004 21:34:14 -0500 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <002601c4c6bd$8fad62c0$e8dafea9@ColbyM6805> Message-ID: <007201c4cd17$19969f60$e8dafea9@ColbyM6805> I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ From michael at ddisolutions.com.au Wed Nov 17 21:14:22 2004 From: michael at ddisolutions.com.au (Michael Maddison) Date: Thu, 18 Nov 2004 14:14:22 +1100 Subject: [dba-SQLServer] Back to the login thing Message-ID: <59A61174B1F5B54B97FD4ADDE71E7D0107C5DC@ddi-01.DDI.local> How are you connecting with QA? What is different to how you connect EM? What happens in QA when you go File --> Connect? cheers Michael M I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jwcolby at colbyconsulting.com Wed Nov 17 21:46:53 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Wed, 17 Nov 2004 22:46:53 -0500 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <59A61174B1F5B54B97FD4ADDE71E7D0107C5DC@ddi-01.DDI.local> Message-ID: <000201c4cd21$3f72a7b0$e8dafea9@ColbyM6805> I get the "login failed for user 'Neo2\Guest'" message. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Michael Maddison Sent: Wednesday, November 17, 2004 10:14 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing How are you connecting with QA? What is different to how you connect EM? What happens in QA when you go File --> Connect? cheers Michael M I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From andrew.haslett at ilc.gov.au Wed Nov 17 22:11:04 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Thu, 18 Nov 2004 14:41:04 +1030 Subject: [dba-SQLServer] Back to the login thing Message-ID: <0A870603A2A816459078203FC07F4CD204C71A@adl01s055.ilcorp.gov.au> As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From michael at ddisolutions.com.au Wed Nov 17 22:29:50 2004 From: michael at ddisolutions.com.au (Michael Maddison) Date: Thu, 18 Nov 2004 15:29:50 +1100 Subject: [dba-SQLServer] Back to the login thing Message-ID: <59A61174B1F5B54B97FD4ADDE71E7D0107C5DE@ddi-01.DDI.local> I agree. I don't have access to a p2p network but if it insists you are logging on as Neo2\Guest I doubt you have many options. It seems to me that as it can't validate the user (DHCP?) it defaults to the guest account. Maybe this will do it... >From BOL The guest user account allows a login without a user account to access a database. A login assumes the identity of the guest user when both of the following conditions are met: The login has access to an instance of Microsoft(r) SQL Server(tm) but does not have access to the database through his or her own user account. The database contains a guest user account. Permissions can be applied to the guest user as if it were any other user account. The guest user can be deleted and added to all databases except master and tempdb, where it must always exist. By default, a guest user account does not exist in newly created databases. For example, to add a guest user account to a database named Accounts, run the following code in SQL Query Analyzer: USE Accounts GO EXECUTE sp_grantdbaccess guest cheers Michael M As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From andrew.haslett at ilc.gov.au Wed Nov 17 22:41:57 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Thu, 18 Nov 2004 15:11:57 +1030 Subject: [dba-SQLServer] Back to the login thing Message-ID: <0A870603A2A816459078203FC07F4CD204C71D@adl01s055.ilcorp.gov.au> Spot on.. John, for some more info, check out the thread 'Problems registering database' about a month ago. I went into detail as to why this is happening -> figured you'd sorted it out after that, as we didn't hear anything... -----Original Message----- From: Michael Maddison [mailto:michael at ddisolutions.com.au] Sent: Thursday, 18 November 2004 3:00 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing I agree. I don't have access to a p2p network but if it insists you are logging on as Neo2\Guest I doubt you have many options. It seems to me that as it can't validate the user (DHCP?) it defaults to the guest account. Maybe this will do it... >From BOL The guest user account allows a login without a user account to access a database. A login assumes the identity of the guest user when both of the following conditions are met: The login has access to an instance of Microsoft(r) SQL Server(tm) but does not have access to the database through his or her own user account. The database contains a guest user account. Permissions can be applied to the guest user as if it were any other user account. The guest user can be deleted and added to all databases except master and tempdb, where it must always exist. By default, a guest user account does not exist in newly created databases. For example, to add a guest user account to a database named Accounts, run the following code in SQL Query Analyzer: USE Accounts GO EXECUTE sp_grantdbaccess guest cheers Michael M As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. --- IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From martyconnelly at shaw.ca Thu Nov 18 01:09:43 2004 From: martyconnelly at shaw.ca (MartyConnelly) Date: Wed, 17 Nov 2004 23:09:43 -0800 Subject: [dba-SQLServer] OT: global search and replace References: Message-ID: <419C4AB7.8010509@shaw.ca> If you are doing multi language unicode with multiple keyboards, I would go with UniPad. It handles all the weird glyphs, 300 languages. It is free to use for 10 minutes of use then degrades; editing only allowed on 1000 character documents. http://www.unipad.org/main/ Billy Pang wrote: > just curious, does anyone have a tool they recommend for performing > global "search and replace" on text files? preferrably can handle > text files saved in unicode text format. and free :) > > thanks > > Billy > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- Marty Connelly Victoria, B.C. Canada From accessd at shaw.ca Thu Nov 18 01:16:22 2004 From: accessd at shaw.ca (Jim Lawrence (AccessD)) Date: Wed, 17 Nov 2004 23:16:22 -0800 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <0A870603A2A816459078203FC07F4CD204C71D@adl01s055.ilcorp.gov.au> Message-ID: Hi All: XP is a 'bastard' of an OS when it comes to security. Unlike all previous systems, it has a new method of handling security access, to a station. The default mode is the 'guest' mode and it has screwed up more uninformed users and technical support the possibly imagined. There is a way to fix this and that is by changing the security method to 'classic' mode but it is carefully hidden. Below are steps to resolve this: (You have to be logged on as administrator and have access to the WINNT directories and below.): 1. Go to and enter 'mmc' in the field. 2. When the MMC menu pops up select File/Add/Remove Snapin... 3. Select Add on the Add/Remove menu. 4. Select 'Security Configuration and Analysis' from the list menu. Highlight, Add, Close and OK. 5. At the 'Consul Root' menu, right-mouse click and select 'Open database'. 6. Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . (Usually 'update.sdb') 7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies' and 'Security Options'. 8. From the right list double click 'Network Access: Security Model for Local Accounts'. 9. Tag 'Define this Policy in the database', choose 'Classic - Local users authentication as themselves', Apply and Exit. Now you should not have any issues connecting to your SQL now. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 8:42 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Spot on.. John, for some more info, check out the thread 'Problems registering database' about a month ago. I went into detail as to why this is happening -> figured you'd sorted it out after that, as we didn't hear anything... -----Original Message----- From: Michael Maddison [mailto:michael at ddisolutions.com.au] Sent: Thursday, 18 November 2004 3:00 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing I agree. I don't have access to a p2p network but if it insists you are logging on as Neo2\Guest I doubt you have many options. It seems to me that as it can't validate the user (DHCP?) it defaults to the guest account. Maybe this will do it... >From BOL The guest user account allows a login without a user account to access a database. A login assumes the identity of the guest user when both of the following conditions are met: The login has access to an instance of Microsoft(r) SQL Server(tm) but does not have access to the database through his or her own user account. The database contains a guest user account. Permissions can be applied to the guest user as if it were any other user account. The guest user can be deleted and added to all databases except master and tempdb, where it must always exist. By default, a guest user account does not exist in newly created databases. For example, to add a guest user account to a database named Accounts, run the following code in SQL Query Analyzer: USE Accounts GO EXECUTE sp_grantdbaccess guest cheers Michael M As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. --- IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From roz.clarke at donnslaw.co.uk Thu Nov 18 05:22:06 2004 From: roz.clarke at donnslaw.co.uk (Roz Clarke) Date: Thu, 18 Nov 2004 11:22:06 -0000 Subject: [dba-SQLServer] cross-posted - sql dba services Message-ID: <61F915314798D311A2F800A0C9C8318805CED7C4@dibble.observatory.donnslaw.co.uk> Thanks Francisco It's not confidential, but it does involve things like setting up a replication server, writing dts packages and troubleshooting performance; this being a developers list more than a dba list (despite the name!!) I didn't think anyone would want to get too in depth, and whilst we are a team member down there really OUGHT to be budget to pay someone to help out!! So three cheers for the list but I will try and get the company to fork out... Roz -----Original Message----- From: Francisco Tapia [mailto:fhtapia at gmail.com] Sent: 17 November 2004 06:01 To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] cross-posted - sql dba services no, but I think that if you need help with basic (and sometimes more complex problems) you can post them here, unless it's more confidential. On Tue, 16 Nov 2004 11:25:14 -0000, Roz Clarke wrote: > Hi all > > A couple of years ago I was recruiting for someone with SQL Server DBA > skills, and someone from accessd put his company forward to provide > those skills on a consultancy basis if I had trouble recruiting. > > At that time I found someone who was very good, but as good people do, > he has now moved onwards & upwards to greater things. We are > struggling to replace him; is anyone on the list currently providing > SQL DBA consultancy in the North West of England? We have some > potential projects coming up which are beyond our in-house skill set, > and it would be nice to know if there is an alternative to hiring > someone permanent. > > Many thanks > > Roz > > > > The contents of this message and any attachments are the property of > Donns Solicitors and are intended for the confidential use of the > named recipient only. They may be legally privileged and should not > be communicated to, or relied upon, by any other party without our > written consent. If you are not the addressee, please notify us > immediately so that we can make arrangements for its return. You > should not show this e-mail to any person or take copies as you may > be committing a criminal or civil offence for which you may be > liable. The statement and opinions expressed in this e-mail message > are those of the writer, and do not necessarily represent that of > Donns Solicitors. Although any files attached to this e-mail will > have been checked with virus protection software prior to > transmission, you should carry out your own virus check before opening > any attachment. Donns Solicitors does not accept any liability for any > damage or loss which may be caused by software viruses... > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > > -- -Francisco http://pcthis.blogspot.com | PC news with out the jargon! _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com -------------- next part -------------- The contents of this message and any attachments are the property of Donns Solicitors and are intended for the confidential use of the named recipient only. They may be legally privileged and should not be communicated to, or relied upon, by any other party without our written consent. If you are not the addressee, please notify us immediately so that we can make arrangements for its return. You should not show this e-mail to any person or take copies as you may be committing a criminal or civil offence for which you may be liable. The statement and opinions expressed in this e-mail message are those of the writer, and do not necessarily represent that of Donns Solicitors. Although any files attached to this e-mail will have been checked with virus protection software prior to transmission, you should carry out your own virus check before opening any attachment. Donns Solicitors does not accept any liability for any damage or loss which may be caused by software viruses... From jwcolby at colbyconsulting.com Thu Nov 18 08:16:09 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Thu, 18 Nov 2004 09:16:09 -0500 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: Message-ID: <002101c4cd79$269125c0$e8dafea9@ColbyM6805> Jim, I followed you (I think) until I got to >Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . I assume that is the windows directory. I went there and found two databases. Secedit.sdb denies my attempt to open it. Udated.sdb allows me to open it but it cannot be expanded per your next instruction. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence (AccessD) Sent: Thursday, November 18, 2004 2:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi All: XP is a 'bastard' of an OS when it comes to security. Unlike all previous systems, it has a new method of handling security access, to a station. The default mode is the 'guest' mode and it has screwed up more uninformed users and technical support the possibly imagined. There is a way to fix this and that is by changing the security method to 'classic' mode but it is carefully hidden. Below are steps to resolve this: (You have to be logged on as administrator and have access to the WINNT directories and below.): 1. Go to and enter 'mmc' in the field. 2. When the MMC menu pops up select File/Add/Remove Snapin... 3. Select Add on the Add/Remove menu. 4. Select 'Security Configuration and Analysis' from the list menu. Highlight, Add, Close and OK. 5. At the 'Consul Root' menu, right-mouse click and select 'Open database'. 6. Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . (Usually 'update.sdb') 7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies' and 'Security Options'. 8. From the right list double click 'Network Access: Security Model for Local Accounts'. 9. Tag 'Define this Policy in the database', choose 'Classic - Local users authentication as themselves', Apply and Exit. Now you should not have any issues connecting to your SQL now. HTH Jim From jwcolby at colbyconsulting.com Thu Nov 18 08:25:59 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Thu, 18 Nov 2004 09:25:59 -0500 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <0A870603A2A816459078203FC07F4CD204C71A@adl01s055.ilcorp.gov.au> Message-ID: <002301c4cd7a$875538f0$e8dafea9@ColbyM6805> Andrew, While I am the only user of this db ATM, in the near future the owners of the database expect to be able to use it in some undetermined manner. I do not know yet the "how" of the access - it will probably be a mix of web server, remote access and / or vb.net application. In any event I have read (and as you are well aware I am totally ignorant on this stuff) that using windows authentication is more secure. I am therefore making every effort to get this set up from the gitgo to do that so I don't have a "gaping security hole" hanging out there forgotten. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 11:11 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From ebarro at afsweb.com Thu Nov 18 10:07:27 2004 From: ebarro at afsweb.com (Eric Barro) Date: Thu, 18 Nov 2004 08:07:27 -0800 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <002301c4cd7a$875538f0$e8dafea9@ColbyM6805> Message-ID: John, If you're using Windows authentication you just need to make sure that you have the same account on each machine and then add that user under the Security section (Login) of SQL server. Create the login that will be the basis for the user for the database. Basically you mirror the Windows account into the SQL server Login account and create users off of that Login. To make things simple just make it a one-to-one relationship. But in order for any machine to have access to other machine's resources you will need to set up the same account on each machine with the same user/pwd combo and same rights/privileges especially if you are not operating in a Windows domain environment with one server as the primary domain controller managing the Active Directory. Eric -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Thursday, November 18, 2004 6:26 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew, While I am the only user of this db ATM, in the near future the owners of the database expect to be able to use it in some undetermined manner. I do not know yet the "how" of the access - it will probably be a mix of web server, remote access and / or vb.net application. In any event I have read (and as you are well aware I am totally ignorant on this stuff) that using windows authentication is more secure. I am therefore making every effort to get this set up from the gitgo to do that so I don't have a "gaping security hole" hanging out there forgotten. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 11:11 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com ---------------------------------------------------------------- The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy. The company will not accept any liability in respect of such communication. From jwcolby at colbyconsulting.com Thu Nov 18 10:29:36 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Thu, 18 Nov 2004 11:29:36 -0500 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: Message-ID: <003301c4cd8b$cb343100$e8dafea9@ColbyM6805> Eric, Well that is the confusing thing here. Every one of these three machines has an administrator account (user name Administrator) all with the same password. I log in as that user on all the machines. Each of these Administrator accounts is indeed an administrator on that machine - these are the default admin accounts created by Windows as Windows is installed on the machine. So AFAICT I have done exactly what you are discussing. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Eric Barro Sent: Thursday, November 18, 2004 11:07 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing John, If you're using Windows authentication you just need to make sure that you have the same account on each machine and then add that user under the Security section (Login) of SQL server. Create the login that will be the basis for the user for the database. Basically you mirror the Windows account into the SQL server Login account and create users off of that Login. To make things simple just make it a one-to-one relationship. But in order for any machine to have access to other machine's resources you will need to set up the same account on each machine with the same user/pwd combo and same rights/privileges especially if you are not operating in a Windows domain environment with one server as the primary domain controller managing the Active Directory. Eric -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Thursday, November 18, 2004 6:26 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew, While I am the only user of this db ATM, in the near future the owners of the database expect to be able to use it in some undetermined manner. I do not know yet the "how" of the access - it will probably be a mix of web server, remote access and / or vb.net application. In any event I have read (and as you are well aware I am totally ignorant on this stuff) that using windows authentication is more secure. I am therefore making every effort to get this set up from the gitgo to do that so I don't have a "gaping security hole" hanging out there forgotten. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 11:11 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com ---------------------------------------------------------------- The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner.. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy. The company will not accept any liability in respect of such communication. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From rl_stewart at highstream.net Thu Nov 18 10:39:31 2004 From: rl_stewart at highstream.net (Robert L. Stewart) Date: Thu, 18 Nov 2004 10:39:31 -0600 Subject: [dba-SQLServer] Re: Back to the login thing In-Reply-To: <200411181629.iAIGTsL20860@databaseadvisors.com> Message-ID: <5.1.0.14.2.20041118103810.047d30c8@pop3.highstream.net> John, Create and use a User account other than Administrator, and I think the instructions given to you will work. Administrator is a "different" kind of user account and I have seen problems like yours when using it between machines. Robert At 10:29 AM 11/18/2004 -0600, you wrote: >Date: Thu, 18 Nov 2004 11:29:36 -0500 >From: "John W. Colby" >Subject: RE: [dba-SQLServer] Back to the login thing >To: dba-sqlserver at databaseadvisors.com >Message-ID: <003301c4cd8b$cb343100$e8dafea9 at ColbyM6805> >Content-Type: text/plain; charset=us-ascii > >Eric, > >Well that is the confusing thing here. Every one of these three machines >has an administrator account (user name Administrator) all with the same >password. I log in as that user on all the machines. Each of these >Administrator accounts is indeed an administrator on that machine - these >are the default admin accounts created by Windows as Windows is installed on >the machine. > >So AFAICT I have done exactly what you are discussing. > >John W. Colby From accessd at shaw.ca Thu Nov 18 11:41:14 2004 From: accessd at shaw.ca (Jim Lawrence (AccessD)) Date: Thu, 18 Nov 2004 09:41:14 -0800 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <002101c4cd79$269125c0$e8dafea9@ColbyM6805> Message-ID: Hi John: You should be able to set the security or these directories, when you are logged in as the administrator by right-mouse clicking on the directory (The Windows root.), select properties, select the security tab, select the full access control and allowing the security changes to cascade to all the subdirectories. (I have assumed that you have setup an administrator login with unlimited rights, first.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Thursday, November 18, 2004 6:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Jim, I followed you (I think) until I got to >Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . I assume that is the windows directory. I went there and found two databases. Secedit.sdb denies my attempt to open it. Udated.sdb allows me to open it but it cannot be expanded per your next instruction. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence (AccessD) Sent: Thursday, November 18, 2004 2:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi All: XP is a 'bastard' of an OS when it comes to security. Unlike all previous systems, it has a new method of handling security access, to a station. The default mode is the 'guest' mode and it has screwed up more uninformed users and technical support the possibly imagined. There is a way to fix this and that is by changing the security method to 'classic' mode but it is carefully hidden. Below are steps to resolve this: (You have to be logged on as administrator and have access to the WINNT directories and below.): 1. Go to and enter 'mmc' in the field. 2. When the MMC menu pops up select File/Add/Remove Snapin... 3. Select Add on the Add/Remove menu. 4. Select 'Security Configuration and Analysis' from the list menu. Highlight, Add, Close and OK. 5. At the 'Consul Root' menu, right-mouse click and select 'Open database'. 6. Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . (Usually 'update.sdb') 7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies' and 'Security Options'. 8. From the right list double click 'Network Access: Security Model for Local Accounts'. 9. Tag 'Define this Policy in the database', choose 'Classic - Local users authentication as themselves', Apply and Exit. Now you should not have any issues connecting to your SQL now. HTH Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From fhtapia at gmail.com Fri Nov 19 01:29:36 2004 From: fhtapia at gmail.com (Francisco Tapia) Date: Thu, 18 Nov 2004 23:29:36 -0800 Subject: [dba-SQLServer] cross-posted - sql dba services In-Reply-To: <61F915314798D311A2F800A0C9C8318805CED7C4@dibble.observatory.donnslaw.co.uk> References: <61F915314798D311A2F800A0C9C8318805CED7C4@dibble.observatory.donnslaw.co.uk> Message-ID: fair enough, I'd love it if the list supported a healthy combination of both dba and dbdev topics :) On Thu, 18 Nov 2004 11:22:06 -0000, Roz Clarke wrote: > Thanks Francisco > > It's not confidential, but it does involve things like setting up a > replication server, writing dts packages and troubleshooting performance; > this being a developers list more than a dba list (despite the name!!) I > didn't think anyone would want to get too in depth, and whilst we are a team > member down there really OUGHT to be budget to pay someone to help out!! > > So three cheers for the list but I will try and get the company to fork > out... > > Roz > > > > -----Original Message----- > From: Francisco Tapia [mailto:fhtapia at gmail.com] > Sent: 17 November 2004 06:01 > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] cross-posted - sql dba services > > no, but I think that if you need help with basic (and sometimes more complex > problems) you can post them here, unless it's more confidential. > > On Tue, 16 Nov 2004 11:25:14 -0000, Roz Clarke > wrote: > > Hi all > > > > A couple of years ago I was recruiting for someone with SQL Server DBA > > skills, and someone from accessd put his company forward to provide > > those skills on a consultancy basis if I had trouble recruiting. > > > > At that time I found someone who was very good, but as good people do, > > he has now moved onwards & upwards to greater things. We are > > struggling to replace him; is anyone on the list currently providing > > SQL DBA consultancy in the North West of England? We have some > > potential projects coming up which are beyond our in-house skill set, > > and it would be nice to know if there is an alternative to hiring > > someone permanent. > > > > Many thanks > > > > Roz > > > > > > > > The contents of this message and any attachments are the property of > > Donns Solicitors and are intended for the confidential use of the > > named recipient only. They may be legally privileged and should not > > be communicated to, or relied upon, by any other party without our > > written consent. If you are not the addressee, please notify us > > immediately so that we can make arrangements for its return. You > > should not show this e-mail to any person or take copies as you may > > be committing a criminal or civil offence for which you may be > > liable. The statement and opinions expressed in this e-mail message > > are those of the writer, and do not necessarily represent that of > > Donns Solicitors. Although any files attached to this e-mail will > > have been checked with virus protection software prior to > > transmission, you should carry out your own virus check before opening > > any attachment. Donns Solicitors does not accept any liability for any > > damage or loss which may be caused by software viruses... > > > > > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > > > > > -- > -Francisco > http://pcthis.blogspot.com | PC news with out the jargon! > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > > The contents of this message and any attachments are the property of Donns Solicitors > and are intended for the confidential use of the named recipient only. They may be legally > privileged and should not be communicated to, or relied upon, by any other party without > our written consent. If you are not the addressee, please notify us immediately so that we > can make arrangements for its return. You should not show this e-mail to any person or > take copies as you may be committing a criminal or civil offence for which you may be > liable. The statement and opinions expressed in this e-mail message are those of the > writer, and do not necessarily represent that of Donns Solicitors. Although any files attached > to this e-mail will have been checked with virus protection software prior to transmission, > you should carry out your own virus check before opening any attachment. > Donns Solicitors does not accept any liability for any damage or loss which may be caused > by software viruses... > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > > -- -Francisco http://pcthis.blogspot.com | PC news with out the jargon! From rmoore at comtechpst.com Fri Nov 19 09:16:40 2004 From: rmoore at comtechpst.com (Ron Moore) Date: Fri, 19 Nov 2004 10:16:40 -0500 Subject: [dba-SQLServer] Update using 'Select (TOP or COUNT) SQL String': Message-ID: I'm trying to stuff a flag when changes exist in metadata and have been unsuccessful using a SELECT TOP 1 fieldname, as well as SELECT COUNT(fieldname). Currently trying the count approach as that would give me the magnitudes of changes, and the SQL string looks like: UPDATE PLAN_STAGE.dbo.S2B_MD_DT_CHANGES SET MD_CHANGES = (SELECT COUNT(CHILD) FROM PLAN_STAGE.dbo.DATA_SOURCE_ACCOUNT_TMP WHERE CHILD IS NOT NULL) FROM PLAN_STAGE.dbo.S2B_MD_DT_CHANGES, PLAN_STAGE.dbo.DATA_SOURCE_ACCOUNT_TMP I have also tried substituting the following WHERE EXISTS in place of the last FROM line in above SQL string: WHERE EXISTS (SELECT COUNT(CHILD) FROM PLAN_STAGE.dbo.DATA_SOURCE_ACCOUNT_TMP WHERE CHILD IS NOT NULL) The select portion by itself works, but the update returns '(0 row(s) affected)'. What am I missing here? Thanks in Advance, Ron Moore From JColby at dispec.com Fri Nov 19 10:21:43 2004 From: JColby at dispec.com (Colby, John) Date: Fri, 19 Nov 2004 11:21:43 -0500 Subject: [dba-SQLServer] Back to the login thing Message-ID: <05C61C52D7CAD211A7830008C7DF6F10CBF99A@DISABILITYINS01> I am an administrator with full rights to everything. Is the method you described originally aimed at setting security back to classic? If so is this change global to all security? Or is it aimed at changing the security itself on a selected directory, to allow different users etc.? If the latter, why am I setting the security on this specific directory to handle a SQL login issue? John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Thursday, November 18, 2004 12:41 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: You should be able to set the security or these directories, when you are logged in as the administrator by right-mouse clicking on the directory (The Windows root.), select properties, select the security tab, select the full access control and allowing the security changes to cascade to all the subdirectories. (I have assumed that you have setup an administrator login with unlimited rights, first.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Thursday, November 18, 2004 6:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Jim, I followed you (I think) until I got to >Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . I assume that is the windows directory. I went there and found two databases. Secedit.sdb denies my attempt to open it. Udated.sdb allows me to open it but it cannot be expanded per your next instruction. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence (AccessD) Sent: Thursday, November 18, 2004 2:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi All: XP is a 'bastard' of an OS when it comes to security. Unlike all previous systems, it has a new method of handling security access, to a station. The default mode is the 'guest' mode and it has screwed up more uninformed users and technical support the possibly imagined. There is a way to fix this and that is by changing the security method to 'classic' mode but it is carefully hidden. Below are steps to resolve this: (You have to be logged on as administrator and have access to the WINNT directories and below.): 1. Go to and enter 'mmc' in the field. 2. When the MMC menu pops up select File/Add/Remove Snapin... 3. Select Add on the Add/Remove menu. 4. Select 'Security Configuration and Analysis' from the list menu. Highlight, Add, Close and OK. 5. At the 'Consul Root' menu, right-mouse click and select 'Open database'. 6. Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . (Usually 'update.sdb') 7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies' and 'Security Options'. 8. From the right list double click 'Network Access: Security Model for Local Accounts'. 9. Tag 'Define this Policy in the database', choose 'Classic - Local users authentication as themselves', Apply and Exit. Now you should not have any issues connecting to your SQL now. HTH Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From accessd at shaw.ca Fri Nov 19 11:19:53 2004 From: accessd at shaw.ca (Jim Lawrence (AccessD)) Date: Fri, 19 Nov 2004 09:19:53 -0800 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <05C61C52D7CAD211A7830008C7DF6F10CBF99A@DISABILITYINS01> Message-ID: Hi John: It sets the security of each XP station. If these XP stations are also being used as SQL servers then your NT authentication will not work as the login will not be properly recognized. Windows2000/XP Servers have issues handling XP stations default logins (P2P), you will have to setup a domain, if you can not or do not want to change the login style to 'classic'. If you need any more information I will send you all I have...(Did this all the hard way a few months ago and now my two servers, each with a SQL 2000 version and all the stations seem very happy...along with a number of clients.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, John Sent: Friday, November 19, 2004 8:22 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing I am an administrator with full rights to everything. Is the method you described originally aimed at setting security back to classic? If so is this change global to all security? Or is it aimed at changing the security itself on a selected directory, to allow different users etc.? If the latter, why am I setting the security on this specific directory to handle a SQL login issue? John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Thursday, November 18, 2004 12:41 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: You should be able to set the security or these directories, when you are logged in as the administrator by right-mouse clicking on the directory (The Windows root.), select properties, select the security tab, select the full access control and allowing the security changes to cascade to all the subdirectories. (I have assumed that you have setup an administrator login with unlimited rights, first.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Thursday, November 18, 2004 6:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Jim, I followed you (I think) until I got to >Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . I assume that is the windows directory. I went there and found two databases. Secedit.sdb denies my attempt to open it. Udated.sdb allows me to open it but it cannot be expanded per your next instruction. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence (AccessD) Sent: Thursday, November 18, 2004 2:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi All: XP is a 'bastard' of an OS when it comes to security. Unlike all previous systems, it has a new method of handling security access, to a station. The default mode is the 'guest' mode and it has screwed up more uninformed users and technical support the possibly imagined. There is a way to fix this and that is by changing the security method to 'classic' mode but it is carefully hidden. Below are steps to resolve this: (You have to be logged on as administrator and have access to the WINNT directories and below.): 1. Go to and enter 'mmc' in the field. 2. When the MMC menu pops up select File/Add/Remove Snapin... 3. Select Add on the Add/Remove menu. 4. Select 'Security Configuration and Analysis' from the list menu. Highlight, Add, Close and OK. 5. At the 'Consul Root' menu, right-mouse click and select 'Open database'. 6. Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . (Usually 'update.sdb') 7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies' and 'Security Options'. 8. From the right list double click 'Network Access: Security Model for Local Accounts'. 9. Tag 'Define this Policy in the database', choose 'Classic - Local users authentication as themselves', Apply and Exit. Now you should not have any issues connecting to your SQL now. HTH Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From JColby at dispec.com Fri Nov 19 11:35:21 2004 From: JColby at dispec.com (Colby, John) Date: Fri, 19 Nov 2004 12:35:21 -0500 Subject: [dba-SQLServer] Back to the login thing Message-ID: <05C61C52D7CAD211A7830008C7DF6F10CBF99E@DISABILITYINS01> Jim, I am running Windows XP Pro on all the boxes. I have SQL Server 2000 installed on all the boxes, a full install. I am not actually using the SQL Server piece on anything except Neo2, although the server does start as a service and is running. I could unload it if necessary since I really do not have any use for it on the other boxes ATM. I would prefer to keep it installed if possible, just not starting the service. Notice that SQL Server 2000 is not supposed to run on Windows XP Pro, i.e. if I just try an install from the disks I get a "won't run on this OS" error message and refuses to install. I have no idea why. I have a copy of SQL Server that has been modified to allow it to install without asking for a key or any such and it installs just fine on XP Pro so I have to believe that it really does run and is just an attempt by MS to force users of SQL Server to upgrade the server OS software. At any rate, I do not have a domain controller, just a workgroup. I am not savvy enough to get a domain server installed and fear opening a whole slew of issues by attempting to do so. What do you mean by setting the login style to classic? On WinXP? I have already done so, each machine presents the Windows 2000 style username / password dialog at boot. I would appreciate any info you can send to help me get this thing happening. John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Friday, November 19, 2004 12:20 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: It sets the security of each XP station. If these XP stations are also being used as SQL servers then your NT authentication will not work as the login will not be properly recognized. Windows2000/XP Servers have issues handling XP stations default logins (P2P), you will have to setup a domain, if you can not or do not want to change the login style to 'classic'. If you need any more information I will send you all I have...(Did this all the hard way a few months ago and now my two servers, each with a SQL 2000 version and all the stations seem very happy...along with a number of clients.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, John Sent: Friday, November 19, 2004 8:22 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing I am an administrator with full rights to everything. Is the method you described originally aimed at setting security back to classic? If so is this change global to all security? Or is it aimed at changing the security itself on a selected directory, to allow different users etc.? If the latter, why am I setting the security on this specific directory to handle a SQL login issue? John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Thursday, November 18, 2004 12:41 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: You should be able to set the security or these directories, when you are logged in as the administrator by right-mouse clicking on the directory (The Windows root.), select properties, select the security tab, select the full access control and allowing the security changes to cascade to all the subdirectories. (I have assumed that you have setup an administrator login with unlimited rights, first.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Thursday, November 18, 2004 6:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Jim, I followed you (I think) until I got to >Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . I assume that is the windows directory. I went there and found two databases. Secedit.sdb denies my attempt to open it. Udated.sdb allows me to open it but it cannot be expanded per your next instruction. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence (AccessD) Sent: Thursday, November 18, 2004 2:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi All: XP is a 'bastard' of an OS when it comes to security. Unlike all previous systems, it has a new method of handling security access, to a station. The default mode is the 'guest' mode and it has screwed up more uninformed users and technical support the possibly imagined. There is a way to fix this and that is by changing the security method to 'classic' mode but it is carefully hidden. Below are steps to resolve this: (You have to be logged on as administrator and have access to the WINNT directories and below.): 1. Go to and enter 'mmc' in the field. 2. When the MMC menu pops up select File/Add/Remove Snapin... 3. Select Add on the Add/Remove menu. 4. Select 'Security Configuration and Analysis' from the list menu. Highlight, Add, Close and OK. 5. At the 'Consul Root' menu, right-mouse click and select 'Open database'. 6. Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . (Usually 'update.sdb') 7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies' and 'Security Options'. 8. From the right list double click 'Network Access: Security Model for Local Accounts'. 9. Tag 'Define this Policy in the database', choose 'Classic - Local users authentication as themselves', Apply and Exit. Now you should not have any issues connecting to your SQL now. HTH Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From rmoore at comtechpst.com Fri Nov 19 12:55:06 2004 From: rmoore at comtechpst.com (Ron Moore) Date: Fri, 19 Nov 2004 13:55:06 -0500 Subject: FW: [dba-SQLServer] Update using 'Select (TOP or COUNT) SQL String': Message-ID: Sorry for the double spacing. I'm using the standard approach below (1 or 0 for the flag) for now, but I'm still curious whether I can use a select within the SET portion of an UPDATE statement? UPDATE PLAN_STAGE.dbo.S2B_MD_DT_CHANGES SET MD_CHANGES = 1 WHERE (SELECT COUNT(1) FROM PLAN_STAGE.dbo.DATA_SOURCE_ACCOUNT_TMP) > 0 Regards, Ron Moore -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Ron Moore Sent: Friday, November 19, 2004 10:17 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Update using 'Select (TOP or COUNT) SQL String': I'm trying to stuff a flag when changes exist in metadata and have been unsuccessful using a SELECT TOP 1 fieldname, as well as SELECT COUNT(fieldname). Currently trying the count approach as that would give me the magnitudes of changes, and the SQL string looks like: UPDATE PLAN_STAGE.dbo.S2B_MD_DT_CHANGES SET MD_CHANGES = (SELECT COUNT(CHILD) FROM PLAN_STAGE.dbo.DATA_SOURCE_ACCOUNT_TMP WHERE CHILD IS NOT NULL) FROM PLAN_STAGE.dbo.S2B_MD_DT_CHANGES, PLAN_STAGE.dbo.DATA_SOURCE_ACCOUNT_TMP I have also tried substituting the following WHERE EXISTS in place of the last FROM line in above SQL string: WHERE EXISTS (SELECT COUNT(CHILD) FROM PLAN_STAGE.dbo.DATA_SOURCE_ACCOUNT_TMP WHERE CHILD IS NOT NULL) The select portion by itself works, but the update returns '(0 row(s) affected)'. What am I missing here? Thanks in Advance, Ron Moore _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From accessd at shaw.ca Fri Nov 19 13:25:04 2004 From: accessd at shaw.ca (Jim Lawrence (AccessD)) Date: Fri, 19 Nov 2004 11:25:04 -0800 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <05C61C52D7CAD211A7830008C7DF6F10CBF99E@DISABILITYINS01> Message-ID: Hi John: I do have a couple of versions of SQL server running on my LAN but both are running on Servers. I had tried to implement a test SQL on a station (2000, I believe) and it produced less than stellar results...(It only partially installed, would not fire-up correctly and everything else on the system started to run screwy.) I believe you will have to get a server as there is a robust multi-user messaging service that is not fully implemented on a station OS. Last year I bought the MS Action Pac and received a large bunch of software packages. It came with 4 full server OSs, along with 6 XP Pro, 6 Office 2003, Exchange mail server, ISA Servers, Biz server etc, etc and it only cost $399US, upgrades this year are about half price. I would not implement a domain, if you do not have to. (In my case it started to get confused between the local domain and the remote domain which is my ISP cable provider but it may not be an issue in you case.) If you do so after the initial installation there are all sorts of problems to resolve....(Another lesson learned the hard way.) I would suggest you seriously look into getting yourself a Server OS. I would recommend XP server 2003 standard edition as it will have all the features you need, it is dead simple to install, installs SQL without a quibble and it is not expensive. ($500US ?) ...or... Your client must have a Server based LAN system and I would suggest you set you system up to emulate theirs if the SQL DB is going to be ultimately running there; Offsite server backup? > What do you mean by setting the login style to classic? On WinXP? I have > already done so, each machine presents the Windows 2000 style username / > password dialog at boot. Do you mean that the stations have been set to the 'classic' style or that they login in classically. What I am asking is did you finally get the XP setting adjusted to 'classic' as per my previous posts? If you have any other questions just send them along. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, John Sent: Friday, November 19, 2004 9:35 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Jim, I am running Windows XP Pro on all the boxes. I have SQL Server 2000 installed on all the boxes, a full install. I am not actually using the SQL Server piece on anything except Neo2, although the server does start as a service and is running. I could unload it if necessary since I really do not have any use for it on the other boxes ATM. I would prefer to keep it installed if possible, just not starting the service. Notice that SQL Server 2000 is not supposed to run on Windows XP Pro, i.e. if I just try an install from the disks I get a "won't run on this OS" error message and refuses to install. I have no idea why. I have a copy of SQL Server that has been modified to allow it to install without asking for a key or any such and it installs just fine on XP Pro so I have to believe that it really does run and is just an attempt by MS to force users of SQL Server to upgrade the server OS software. At any rate, I do not have a domain controller, just a workgroup. I am not savvy enough to get a domain server installed and fear opening a whole slew of issues by attempting to do so. What do you mean by setting the login style to classic? On WinXP? I have already done so, each machine presents the Windows 2000 style username / password dialog at boot. I would appreciate any info you can send to help me get this thing happening. John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Friday, November 19, 2004 12:20 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: It sets the security of each XP station. If these XP stations are also being used as SQL servers then your NT authentication will not work as the login will not be properly recognized. Windows2000/XP Servers have issues handling XP stations default logins (P2P), you will have to setup a domain, if you can not or do not want to change the login style to 'classic'. If you need any more information I will send you all I have...(Did this all the hard way a few months ago and now my two servers, each with a SQL 2000 version and all the stations seem very happy...along with a number of clients.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, John Sent: Friday, November 19, 2004 8:22 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing I am an administrator with full rights to everything. Is the method you described originally aimed at setting security back to classic? If so is this change global to all security? Or is it aimed at changing the security itself on a selected directory, to allow different users etc.? If the latter, why am I setting the security on this specific directory to handle a SQL login issue? John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Thursday, November 18, 2004 12:41 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: You should be able to set the security or these directories, when you are logged in as the administrator by right-mouse clicking on the directory (The Windows root.), select properties, select the security tab, select the full access control and allowing the security changes to cascade to all the subdirectories. (I have assumed that you have setup an administrator login with unlimited rights, first.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Thursday, November 18, 2004 6:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Jim, I followed you (I think) until I got to >Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . I assume that is the windows directory. I went there and found two databases. Secedit.sdb denies my attempt to open it. Udated.sdb allows me to open it but it cannot be expanded per your next instruction. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence (AccessD) Sent: Thursday, November 18, 2004 2:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi All: XP is a 'bastard' of an OS when it comes to security. Unlike all previous systems, it has a new method of handling security access, to a station. The default mode is the 'guest' mode and it has screwed up more uninformed users and technical support the possibly imagined. There is a way to fix this and that is by changing the security method to 'classic' mode but it is carefully hidden. Below are steps to resolve this: (You have to be logged on as administrator and have access to the WINNT directories and below.): 1. Go to and enter 'mmc' in the field. 2. When the MMC menu pops up select File/Add/Remove Snapin... 3. Select Add on the Add/Remove menu. 4. Select 'Security Configuration and Analysis' from the list menu. Highlight, Add, Close and OK. 5. At the 'Consul Root' menu, right-mouse click and select 'Open database'. 6. Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . (Usually 'update.sdb') 7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies' and 'Security Options'. 8. From the right list double click 'Network Access: Security Model for Local Accounts'. 9. Tag 'Define this Policy in the database', choose 'Classic - Local users authentication as themselves', Apply and Exit. Now you should not have any issues connecting to your SQL now. HTH Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From JColby at dispec.com Fri Nov 19 13:45:32 2004 From: JColby at dispec.com (Colby, John) Date: Fri, 19 Nov 2004 14:45:32 -0500 Subject: [dba-SQLServer] Back to the login thing Message-ID: <05C61C52D7CAD211A7830008C7DF6F10CBF9A3@DISABILITYINS01> Jim, I bought the action pack so I have the server OSs. The issue here is that I built a couple of high powered systems but the driver disks do an OS check on install and don't recognize the 2003 stuff. 2003 won't install on top of XP. I would love to get a real 2003 server up but it isn't going to happen by buying a server from a vendor, it's just too much money. I did not get the setup adjusted to classic. See the second to the bottom message in this email. John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Friday, November 19, 2004 2:25 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: I do have a couple of versions of SQL server running on my LAN but both are running on Servers. I had tried to implement a test SQL on a station (2000, I believe) and it produced less than stellar results...(It only partially installed, would not fire-up correctly and everything else on the system started to run screwy.) I believe you will have to get a server as there is a robust multi-user messaging service that is not fully implemented on a station OS. Last year I bought the MS Action Pac and received a large bunch of software packages. It came with 4 full server OSs, along with 6 XP Pro, 6 Office 2003, Exchange mail server, ISA Servers, Biz server etc, etc and it only cost $399US, upgrades this year are about half price. I would not implement a domain, if you do not have to. (In my case it started to get confused between the local domain and the remote domain which is my ISP cable provider but it may not be an issue in you case.) If you do so after the initial installation there are all sorts of problems to resolve....(Another lesson learned the hard way.) I would suggest you seriously look into getting yourself a Server OS. I would recommend XP server 2003 standard edition as it will have all the features you need, it is dead simple to install, installs SQL without a quibble and it is not expensive. ($500US ?) ...or... Your client must have a Server based LAN system and I would suggest you set you system up to emulate theirs if the SQL DB is going to be ultimately running there; Offsite server backup? > What do you mean by setting the login style to classic? On WinXP? I have > already done so, each machine presents the Windows 2000 style username / > password dialog at boot. Do you mean that the stations have been set to the 'classic' style or that they login in classically. What I am asking is did you finally get the XP setting adjusted to 'classic' as per my previous posts? If you have any other questions just send them along. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, John Sent: Friday, November 19, 2004 9:35 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Jim, I am running Windows XP Pro on all the boxes. I have SQL Server 2000 installed on all the boxes, a full install. I am not actually using the SQL Server piece on anything except Neo2, although the server does start as a service and is running. I could unload it if necessary since I really do not have any use for it on the other boxes ATM. I would prefer to keep it installed if possible, just not starting the service. Notice that SQL Server 2000 is not supposed to run on Windows XP Pro, i.e. if I just try an install from the disks I get a "won't run on this OS" error message and refuses to install. I have no idea why. I have a copy of SQL Server that has been modified to allow it to install without asking for a key or any such and it installs just fine on XP Pro so I have to believe that it really does run and is just an attempt by MS to force users of SQL Server to upgrade the server OS software. At any rate, I do not have a domain controller, just a workgroup. I am not savvy enough to get a domain server installed and fear opening a whole slew of issues by attempting to do so. What do you mean by setting the login style to classic? On WinXP? I have already done so, each machine presents the Windows 2000 style username / password dialog at boot. I would appreciate any info you can send to help me get this thing happening. John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Friday, November 19, 2004 12:20 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: It sets the security of each XP station. If these XP stations are also being used as SQL servers then your NT authentication will not work as the login will not be properly recognized. Windows2000/XP Servers have issues handling XP stations default logins (P2P), you will have to setup a domain, if you can not or do not want to change the login style to 'classic'. If you need any more information I will send you all I have...(Did this all the hard way a few months ago and now my two servers, each with a SQL 2000 version and all the stations seem very happy...along with a number of clients.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, John Sent: Friday, November 19, 2004 8:22 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing I am an administrator with full rights to everything. Is the method you described originally aimed at setting security back to classic? If so is this change global to all security? Or is it aimed at changing the security itself on a selected directory, to allow different users etc.? If the latter, why am I setting the security on this specific directory to handle a SQL login issue? John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Thursday, November 18, 2004 12:41 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: You should be able to set the security or these directories, when you are logged in as the administrator by right-mouse clicking on the directory (The Windows root.), select properties, select the security tab, select the full access control and allowing the security changes to cascade to all the subdirectories. (I have assumed that you have setup an administrator login with unlimited rights, first.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Thursday, November 18, 2004 6:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Jim, I followed you (I think) until I got to >Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . I assume that is the windows directory. I went there and found two databases. Secedit.sdb denies my attempt to open it. Udated.sdb allows me to open it but it cannot be expanded per your next instruction. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence (AccessD) Sent: Thursday, November 18, 2004 2:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi All: XP is a 'bastard' of an OS when it comes to security. Unlike all previous systems, it has a new method of handling security access, to a station. The default mode is the 'guest' mode and it has screwed up more uninformed users and technical support the possibly imagined. There is a way to fix this and that is by changing the security method to 'classic' mode but it is carefully hidden. Below are steps to resolve this: (You have to be logged on as administrator and have access to the WINNT directories and below.): 1. Go to and enter 'mmc' in the field. 2. When the MMC menu pops up select File/Add/Remove Snapin... 3. Select Add on the Add/Remove menu. 4. Select 'Security Configuration and Analysis' from the list menu. Highlight, Add, Close and OK. 5. At the 'Consul Root' menu, right-mouse click and select 'Open database'. 6. Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . (Usually 'update.sdb') 7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies' and 'Security Options'. 8. From the right list double click 'Network Access: Security Model for Local Accounts'. 9. Tag 'Define this Policy in the database', choose 'Classic - Local users authentication as themselves', Apply and Exit. Now you should not have any issues connecting to your SQL now. HTH Jim From mwp.reid at qub.ac.uk Fri Nov 19 13:59:17 2004 From: mwp.reid at qub.ac.uk (Martin Reid) Date: Fri, 19 Nov 2004 19:59:17 -0000 Subject: [dba-SQLServer] Back to the login thing References: <05C61C52D7CAD211A7830008C7DF6F10CBF9A3@DISABILITYINS01> Message-ID: <000a01c4ce72$40b824e0$0100a8c0@Martin> John The evual copy of SQL Server (Downloaded from MS) runs on XP Pro not the full version - i.e the one you pay for. I believe this to be the case - anyone else know?? Martin ----- Original Message ----- From: "Colby, John" To: Sent: Friday, November 19, 2004 7:45 PM Subject: RE: [dba-SQLServer] Back to the login thing > Jim, > > I bought the action pack so I have the server OSs. The issue here is that > I > built a couple of high powered systems but the driver disks do an OS check > on install and don't recognize the 2003 stuff. 2003 won't install on top > of > XP. > > I would love to get a real 2003 server up but it isn't going to happen by > buying a server from a vendor, it's just too much money. > > I did not get the setup adjusted to classic. See the second to the bottom > message in this email. > > John W. Colby > The DIS Database Guy > > > -----Original Message----- > From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] > Sent: Friday, November 19, 2004 2:25 PM > To: dba-sqlserver at databaseadvisors.com > Subject: RE: [dba-SQLServer] Back to the login thing > > > Hi John: > > I do have a couple of versions of SQL server running on my LAN but both > are > running on Servers. I had tried to implement a test SQL on a station > (2000, > I believe) and it produced less than stellar results...(It only partially > installed, would not fire-up correctly and everything else on the system > started to run screwy.) > > I believe you will have to get a server as there is a robust multi-user > messaging service that is not fully implemented on a station OS. Last year > I > bought the MS Action Pac and received a large bunch of software packages. > It > came with 4 full server OSs, along with 6 XP Pro, 6 Office 2003, Exchange > mail server, ISA Servers, Biz server etc, etc and it only cost $399US, > upgrades this year are about half price. > > I would not implement a domain, if you do not have to. (In my case it > started to get confused between the local domain and the remote domain > which > is my ISP cable provider but it may not be an issue in you case.) If you > do > so after the initial installation there are all sorts of problems to > resolve....(Another lesson learned the hard way.) > > I would suggest you seriously look into getting yourself a Server OS. I > would recommend XP server 2003 standard edition as it will have all the > features you need, it is dead simple to install, installs SQL without a > quibble and it is not expensive. ($500US ?) > ...or... > Your client must have a Server based LAN system and I would suggest you > set > you system up to emulate theirs if the SQL DB is going to be ultimately > running there; Offsite server backup? > >> What do you mean by setting the login style to classic? On WinXP? I >> have >> already done so, each machine presents the Windows 2000 style username / >> password dialog at boot. > > Do you mean that the stations have been set to the 'classic' style or that > they login in classically. What I am asking is did you finally get the XP > setting adjusted to 'classic' as per my previous posts? > > If you have any other questions just send them along. > > HTH > Jim > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, > John > Sent: Friday, November 19, 2004 9:35 AM > To: 'dba-sqlserver at databaseadvisors.com' > Subject: RE: [dba-SQLServer] Back to the login thing > > > Jim, > > I am running Windows XP Pro on all the boxes. I have SQL Server 2000 > installed on all the boxes, a full install. I am not actually using the > SQL > Server piece on anything except Neo2, although the server does start as a > service and is running. I could unload it if necessary since I really do > not have any use for it on the other boxes ATM. I would prefer to keep it > installed if possible, just not starting the service. > > Notice that SQL Server 2000 is not supposed to run on Windows XP Pro, i.e. > if I just try an install from the disks I get a "won't run on this OS" > error > message and refuses to install. I have no idea why. I have a copy of SQL > Server that has been modified to allow it to install without asking for a > key or any such and it installs just fine on XP Pro so I have to believe > that it really does run and is just an attempt by MS to force users of SQL > Server to upgrade the server OS software. > > At any rate, I do not have a domain controller, just a workgroup. I am > not > savvy enough to get a domain server installed and fear opening a whole > slew > of issues by attempting to do so. > > What do you mean by setting the login style to classic? On WinXP? I have > already done so, each machine presents the Windows 2000 style username / > password dialog at boot. > > I would appreciate any info you can send to help me get this thing > happening. > > John W. Colby > The DIS Database Guy > > > -----Original Message----- > From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] > Sent: Friday, November 19, 2004 12:20 PM > To: dba-sqlserver at databaseadvisors.com > Subject: RE: [dba-SQLServer] Back to the login thing > > > Hi John: > > It sets the security of each XP station. If these XP stations are also > being > used as SQL servers then your NT authentication will not work as the login > will not be properly recognized. Windows2000/XP Servers have issues > handling > XP stations default logins (P2P), you will have to setup a domain, if you > can not or do not want to change the login style to 'classic'. > > If you need any more information I will send you all I have...(Did this > all > the hard way a few months ago and now my two servers, each with a SQL 2000 > version and all the stations seem very happy...along with a number of > clients.) > > HTH > Jim > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, > John > Sent: Friday, November 19, 2004 8:22 AM > To: 'dba-sqlserver at databaseadvisors.com' > Subject: RE: [dba-SQLServer] Back to the login thing > > > I am an administrator with full rights to everything. > > Is the method you described originally aimed at setting security back to > classic? If so is this change global to all security? Or is it aimed at > changing the security itself on a selected directory, to allow different > users etc.? If the latter, why am I setting the security on this specific > directory to handle a SQL login issue? > > John W. Colby > The DIS Database Guy > > > -----Original Message----- > From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] > Sent: Thursday, November 18, 2004 12:41 PM > To: dba-sqlserver at databaseadvisors.com > Subject: RE: [dba-SQLServer] Back to the login thing > > > Hi John: > > You should be able to set the security or these directories, when you are > logged in as the administrator by right-mouse clicking on the directory > (The > Windows root.), select properties, select the security tab, select the > full > access control and allowing the security changes to cascade to all the > subdirectories. (I have assumed that you have setup an administrator login > with unlimited rights, first.) > > HTH > Jim > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. > Colby > Sent: Thursday, November 18, 2004 6:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: RE: [dba-SQLServer] Back to the login thing > > > Jim, > > I followed you (I think) until I got to > >>Navigate to the X:\windows\security\database\ directory and select the > latest *.sdb . > > I assume that is the windows directory. I went there and found two > databases. Secedit.sdb denies my attempt to open it. Udated.sdb allows > me > to open it but it cannot be expanded per your next instruction. > > John W. Colby > www.ColbyConsulting.com > > Contribute your unused CPU cycles to a good cause: > http://folding.stanford.edu/ > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim > Lawrence (AccessD) > Sent: Thursday, November 18, 2004 2:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: RE: [dba-SQLServer] Back to the login thing > > > Hi All: > > XP is a 'bastard' of an OS when it comes to security. Unlike all previous > systems, it has a new method of handling security access, to a station. > The > default mode is the 'guest' mode and it has screwed up more uninformed > users > and technical support the possibly imagined. There is a way to fix this > and > that is by changing the security method to 'classic' mode but it is > carefully hidden. Below are steps to resolve this: (You have to be logged > on > as administrator and have access to the WINNT directories and below.): > > 1. Go to and enter 'mmc' in the field. > 2. When the MMC menu pops up select File/Add/Remove Snapin... > 3. Select Add on the Add/Remove menu. > 4. Select 'Security Configuration and Analysis' from the list menu. > Highlight, Add, Close and OK. > 5. At the 'Consul Root' menu, right-mouse click and select 'Open > database'. > 6. Navigate to the X:\windows\security\database\ directory and select the > latest *.sdb . (Usually 'update.sdb') > 7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies' > and 'Security Options'. > 8. From the right list double click 'Network Access: Security Model for > Local Accounts'. > 9. Tag 'Define this Policy in the database', choose 'Classic - Local users > authentication as themselves', Apply and Exit. > > Now you should not have any issues connecting to your SQL now. > > HTH > Jim > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > From accessd at shaw.ca Fri Nov 19 14:35:12 2004 From: accessd at shaw.ca (Jim Lawrence (AccessD)) Date: Fri, 19 Nov 2004 12:35:12 -0800 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <05C61C52D7CAD211A7830008C7DF6F10CBF9A3@DISABILITYINS01> Message-ID: Hi John: You do have an issue if you can build an Server OS on which to launch your SQL server. If you do have the Action Pac then there should be no problem but you will have to start from scratch on what box you decide. When you log into your XP station as administrator, then you are god and should be able gain access to any of the files on the station by set and unsetting their security. That will allow you to view and edit the sdb files. I have do the same to a number of home office and client stations. I can not remember the exact method I employed but it did not seem to be a difficult issue. You just have to set up your god accounts from the control panel. I could also help you remotely if you like? HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, John Sent: Friday, November 19, 2004 11:46 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Jim, I bought the action pack so I have the server OSs. The issue here is that I built a couple of high powered systems but the driver disks do an OS check on install and don't recognize the 2003 stuff. 2003 won't install on top of XP. I would love to get a real 2003 server up but it isn't going to happen by buying a server from a vendor, it's just too much money. I did not get the setup adjusted to classic. See the second to the bottom message in this email. John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Friday, November 19, 2004 2:25 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: I do have a couple of versions of SQL server running on my LAN but both are running on Servers. I had tried to implement a test SQL on a station (2000, I believe) and it produced less than stellar results...(It only partially installed, would not fire-up correctly and everything else on the system started to run screwy.) I believe you will have to get a server as there is a robust multi-user messaging service that is not fully implemented on a station OS. Last year I bought the MS Action Pac and received a large bunch of software packages. It came with 4 full server OSs, along with 6 XP Pro, 6 Office 2003, Exchange mail server, ISA Servers, Biz server etc, etc and it only cost $399US, upgrades this year are about half price. I would not implement a domain, if you do not have to. (In my case it started to get confused between the local domain and the remote domain which is my ISP cable provider but it may not be an issue in you case.) If you do so after the initial installation there are all sorts of problems to resolve....(Another lesson learned the hard way.) I would suggest you seriously look into getting yourself a Server OS. I would recommend XP server 2003 standard edition as it will have all the features you need, it is dead simple to install, installs SQL without a quibble and it is not expensive. ($500US ?) ...or... Your client must have a Server based LAN system and I would suggest you set you system up to emulate theirs if the SQL DB is going to be ultimately running there; Offsite server backup? > What do you mean by setting the login style to classic? On WinXP? I have > already done so, each machine presents the Windows 2000 style username / > password dialog at boot. Do you mean that the stations have been set to the 'classic' style or that they login in classically. What I am asking is did you finally get the XP setting adjusted to 'classic' as per my previous posts? If you have any other questions just send them along. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, John Sent: Friday, November 19, 2004 9:35 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Jim, I am running Windows XP Pro on all the boxes. I have SQL Server 2000 installed on all the boxes, a full install. I am not actually using the SQL Server piece on anything except Neo2, although the server does start as a service and is running. I could unload it if necessary since I really do not have any use for it on the other boxes ATM. I would prefer to keep it installed if possible, just not starting the service. Notice that SQL Server 2000 is not supposed to run on Windows XP Pro, i.e. if I just try an install from the disks I get a "won't run on this OS" error message and refuses to install. I have no idea why. I have a copy of SQL Server that has been modified to allow it to install without asking for a key or any such and it installs just fine on XP Pro so I have to believe that it really does run and is just an attempt by MS to force users of SQL Server to upgrade the server OS software. At any rate, I do not have a domain controller, just a workgroup. I am not savvy enough to get a domain server installed and fear opening a whole slew of issues by attempting to do so. What do you mean by setting the login style to classic? On WinXP? I have already done so, each machine presents the Windows 2000 style username / password dialog at boot. I would appreciate any info you can send to help me get this thing happening. John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Friday, November 19, 2004 12:20 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: It sets the security of each XP station. If these XP stations are also being used as SQL servers then your NT authentication will not work as the login will not be properly recognized. Windows2000/XP Servers have issues handling XP stations default logins (P2P), you will have to setup a domain, if you can not or do not want to change the login style to 'classic'. If you need any more information I will send you all I have...(Did this all the hard way a few months ago and now my two servers, each with a SQL 2000 version and all the stations seem very happy...along with a number of clients.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Colby, John Sent: Friday, November 19, 2004 8:22 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing I am an administrator with full rights to everything. Is the method you described originally aimed at setting security back to classic? If so is this change global to all security? Or is it aimed at changing the security itself on a selected directory, to allow different users etc.? If the latter, why am I setting the security on this specific directory to handle a SQL login issue? John W. Colby The DIS Database Guy -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Thursday, November 18, 2004 12:41 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi John: You should be able to set the security or these directories, when you are logged in as the administrator by right-mouse clicking on the directory (The Windows root.), select properties, select the security tab, select the full access control and allowing the security changes to cascade to all the subdirectories. (I have assumed that you have setup an administrator login with unlimited rights, first.) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Thursday, November 18, 2004 6:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Jim, I followed you (I think) until I got to >Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . I assume that is the windows directory. I went there and found two databases. Secedit.sdb denies my attempt to open it. Udated.sdb allows me to open it but it cannot be expanded per your next instruction. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence (AccessD) Sent: Thursday, November 18, 2004 2:16 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Hi All: XP is a 'bastard' of an OS when it comes to security. Unlike all previous systems, it has a new method of handling security access, to a station. The default mode is the 'guest' mode and it has screwed up more uninformed users and technical support the possibly imagined. There is a way to fix this and that is by changing the security method to 'classic' mode but it is carefully hidden. Below are steps to resolve this: (You have to be logged on as administrator and have access to the WINNT directories and below.): 1. Go to and enter 'mmc' in the field. 2. When the MMC menu pops up select File/Add/Remove Snapin... 3. Select Add on the Add/Remove menu. 4. Select 'Security Configuration and Analysis' from the list menu. Highlight, Add, Close and OK. 5. At the 'Consul Root' menu, right-mouse click and select 'Open database'. 6. Navigate to the X:\windows\security\database\ directory and select the latest *.sdb . (Usually 'update.sdb') 7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies' and 'Security Options'. 8. From the right list double click 'Network Access: Security Model for Local Accounts'. 9. Tag 'Define this Policy in the database', choose 'Classic - Local users authentication as themselves', Apply and Exit. Now you should not have any issues connecting to your SQL now. HTH Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From andrew.haslett at ilc.gov.au Mon Nov 22 23:07:27 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Tue, 23 Nov 2004 15:37:27 +1030 Subject: [dba-SQLServer] Back to the login thing Message-ID: <0A870603A2A816459078203FC07F4CD204C74D@adl01s055.ilcorp.gov.au> Fair enough. However, despite what you've read, I wouldn't say SQL Authentication is *insecure* - well, its definitely no worse than entering a username / password on a website which I'm sure you do from time to time.. You still neet to get access *through firewall and NAT* to the network that the server is on (which is currently your LAN) and *then* guess a username and password for an account on SQL, which *then* must have the necessary privileges to do any harm to the server. And to be honest, if your LAN is compromised, odds are the administrator account will be hacked anyway, giving the user access to the SQL server whether you're using Windows or SQL authentication. Anyway, I'm assuming that whatever the final product, its not going to remain on your home LAN is it? What I'm getting at, is that once its finished, an entirely new security model will need to be implemeted on the server that it will reside on, so its pretty much irrelevant as to how you're accessing the database from EM at the moment. Even if it is to remain on your LAN it takes only the click of a button to switch off SQL Authentication.. Considering the trouble its caused you and the time lost trying to set up Windows Auth, seems pretty pointless not to use SQL Authentication to get the job done in the meantime... -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Friday, 19 November 2004 12:56 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew, While I am the only user of this db ATM, in the near future the owners of the database expect to be able to use it in some undetermined manner. I do not know yet the "how" of the access - it will probably be a mix of web server, remote access and / or vb.net application. In any event I have read (and as you are well aware I am totally ignorant on this stuff) that using windows authentication is more secure. I am therefore making every effort to get this set up from the gitgo to do that so I don't have a "gaping security hole" hanging out there forgotten. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 11:11 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From jwcolby at colbyconsulting.com Tue Nov 23 06:17:29 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Tue, 23 Nov 2004 07:17:29 -0500 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <0A870603A2A816459078203FC07F4CD204C74D@adl01s055.ilcorp.gov.au> Message-ID: <004801c4d156$66a6b310$e8dafea9@ColbyM6805> Andrew, You are right, sql server authentication "in the meantime" is becoming the obvious answer. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Tuesday, November 23, 2004 12:07 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Fair enough. However, despite what you've read, I wouldn't say SQL Authentication is *insecure* - well, its definitely no worse than entering a username / password on a website which I'm sure you do from time to time.. You still neet to get access *through firewall and NAT* to the network that the server is on (which is currently your LAN) and *then* guess a username and password for an account on SQL, which *then* must have the necessary privileges to do any harm to the server. And to be honest, if your LAN is compromised, odds are the administrator account will be hacked anyway, giving the user access to the SQL server whether you're using Windows or SQL authentication. Anyway, I'm assuming that whatever the final product, its not going to remain on your home LAN is it? What I'm getting at, is that once its finished, an entirely new security model will need to be implemeted on the server that it will reside on, so its pretty much irrelevant as to how you're accessing the database from EM at the moment. Even if it is to remain on your LAN it takes only the click of a button to switch off SQL Authentication.. Considering the trouble its caused you and the time lost trying to set up Windows Auth, seems pretty pointless not to use SQL Authentication to get the job done in the meantime... -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Friday, 19 November 2004 12:56 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew, While I am the only user of this db ATM, in the near future the owners of the database expect to be able to use it in some undetermined manner. I do not know yet the "how" of the access - it will probably be a mix of web server, remote access and / or vb.net application. In any event I have read (and as you are well aware I am totally ignorant on this stuff) that using windows authentication is more secure. I am therefore making every effort to get this set up from the gitgo to do that so I don't have a "gaping security hole" hanging out there forgotten. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 11:11 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From accessd at shaw.ca Tue Nov 23 11:42:10 2004 From: accessd at shaw.ca (Jim Lawrence (AccessD)) Date: Tue, 23 Nov 2004 09:42:10 -0800 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <0A870603A2A816459078203FC07F4CD204C74D@adl01s055.ilcorp.gov.au> Message-ID: I concur. When setting up authentication on a LAN it is very easy to create a group on the LAN or on the SQL's server and then apply that group to your SQL security. From then on security is a matter for the local system admin and they can just adds or subtracts users from the group(s) as required and it is straight forward to assign various sets of access rights; viewer/user/data-entry/backup/admin. But I do recommend that you create a back-door or two. Maybe add your user name directly to the SQL security and leave SQL authentication available with a very complex password. You hopefully will never have to use them but there is time when they will be required. Like when some admin person inadvertently turns off 'log-ins' or the domain server goes down etc.. There is other way to add to the security. I understand, though I have never done it that you can change the default port (1433) to something else. Francisco Tapia is a proponent of this method and you should check with him on the deployment. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Monday, November 22, 2004 9:07 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Fair enough. However, despite what you've read, I wouldn't say SQL Authentication is *insecure* - well, its definitely no worse than entering a username / password on a website which I'm sure you do from time to time.. You still neet to get access *through firewall and NAT* to the network that the server is on (which is currently your LAN) and *then* guess a username and password for an account on SQL, which *then* must have the necessary privileges to do any harm to the server. And to be honest, if your LAN is compromised, odds are the administrator account will be hacked anyway, giving the user access to the SQL server whether you're using Windows or SQL authentication. Anyway, I'm assuming that whatever the final product, its not going to remain on your home LAN is it? What I'm getting at, is that once its finished, an entirely new security model will need to be implemeted on the server that it will reside on, so its pretty much irrelevant as to how you're accessing the database from EM at the moment. Even if it is to remain on your LAN it takes only the click of a button to switch off SQL Authentication.. Considering the trouble its caused you and the time lost trying to set up Windows Auth, seems pretty pointless not to use SQL Authentication to get the job done in the meantime... -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Friday, 19 November 2004 12:56 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew, While I am the only user of this db ATM, in the near future the owners of the database expect to be able to use it in some undetermined manner. I do not know yet the "how" of the access - it will probably be a mix of web server, remote access and / or vb.net application. In any event I have read (and as you are well aware I am totally ignorant on this stuff) that using windows authentication is more secure. I am therefore making every effort to get this set up from the gitgo to do that so I don't have a "gaping security hole" hanging out there forgotten. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 11:11 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From andrew.haslett at ilc.gov.au Tue Nov 23 16:28:51 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Wed, 24 Nov 2004 08:58:51 +1030 Subject: [dba-SQLServer] Back to the login thing Message-ID: <0A870603A2A816459078203FC07F4CD204C753@adl01s055.ilcorp.gov.au> "Server Network Utility" - changes the port SQL listens on. There's also a KB article on it. -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Wednesday, 24 November 2004 4:12 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing I concur. When setting up authentication on a LAN it is very easy to create a group on the LAN or on the SQL's server and then apply that group to your SQL security. From then on security is a matter for the local system admin and they can just adds or subtracts users from the group(s) as required and it is straight forward to assign various sets of access rights; viewer/user/data-entry/backup/admin. But I do recommend that you create a back-door or two. Maybe add your user name directly to the SQL security and leave SQL authentication available with a very complex password. You hopefully will never have to use them but there is time when they will be required. Like when some admin person inadvertently turns off 'log-ins' or the domain server goes down etc.. There is other way to add to the security. I understand, though I have never done it that you can change the default port (1433) to something else. Francisco Tapia is a proponent of this method and you should check with him on the deployment. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Monday, November 22, 2004 9:07 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Fair enough. However, despite what you've read, I wouldn't say SQL Authentication is *insecure* - well, its definitely no worse than entering a username / password on a website which I'm sure you do from time to time.. You still neet to get access *through firewall and NAT* to the network that the server is on (which is currently your LAN) and *then* guess a username and password for an account on SQL, which *then* must have the necessary privileges to do any harm to the server. And to be honest, if your LAN is compromised, odds are the administrator account will be hacked anyway, giving the user access to the SQL server whether you're using Windows or SQL authentication. Anyway, I'm assuming that whatever the final product, its not going to remain on your home LAN is it? What I'm getting at, is that once its finished, an entirely new security model will need to be implemeted on the server that it will reside on, so its pretty much irrelevant as to how you're accessing the database from EM at the moment. Even if it is to remain on your LAN it takes only the click of a button to switch off SQL Authentication.. Considering the trouble its caused you and the time lost trying to set up Windows Auth, seems pretty pointless not to use SQL Authentication to get the job done in the meantime... -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Friday, 19 November 2004 12:56 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew, While I am the only user of this db ATM, in the near future the owners of the database expect to be able to use it in some undetermined manner. I do not know yet the "how" of the access - it will probably be a mix of web server, remote access and / or vb.net application. In any event I have read (and as you are well aware I am totally ignorant on this stuff) that using windows authentication is more secure. I am therefore making every effort to get this set up from the gitgo to do that so I don't have a "gaping security hole" hanging out there forgotten. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 11:11 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From accessd at shaw.ca Tue Nov 23 19:14:39 2004 From: accessd at shaw.ca (Jim Lawrence (AccessD)) Date: Tue, 23 Nov 2004 17:14:39 -0800 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <0A870603A2A816459078203FC07F4CD204C753@adl01s055.ilcorp.gov.au> Message-ID: Andrew: ...and how do you can the logging in to accommodate the new port designation? Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Tuesday, November 23, 2004 2:29 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing "Server Network Utility" - changes the port SQL listens on. There's also a KB article on it. -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Wednesday, 24 November 2004 4:12 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing I concur. When setting up authentication on a LAN it is very easy to create a group on the LAN or on the SQL's server and then apply that group to your SQL security. From then on security is a matter for the local system admin and they can just adds or subtracts users from the group(s) as required and it is straight forward to assign various sets of access rights; viewer/user/data-entry/backup/admin. But I do recommend that you create a back-door or two. Maybe add your user name directly to the SQL security and leave SQL authentication available with a very complex password. You hopefully will never have to use them but there is time when they will be required. Like when some admin person inadvertently turns off 'log-ins' or the domain server goes down etc.. There is other way to add to the security. I understand, though I have never done it that you can change the default port (1433) to something else. Francisco Tapia is a proponent of this method and you should check with him on the deployment. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Monday, November 22, 2004 9:07 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Fair enough. However, despite what you've read, I wouldn't say SQL Authentication is *insecure* - well, its definitely no worse than entering a username / password on a website which I'm sure you do from time to time.. You still neet to get access *through firewall and NAT* to the network that the server is on (which is currently your LAN) and *then* guess a username and password for an account on SQL, which *then* must have the necessary privileges to do any harm to the server. And to be honest, if your LAN is compromised, odds are the administrator account will be hacked anyway, giving the user access to the SQL server whether you're using Windows or SQL authentication. Anyway, I'm assuming that whatever the final product, its not going to remain on your home LAN is it? What I'm getting at, is that once its finished, an entirely new security model will need to be implemeted on the server that it will reside on, so its pretty much irrelevant as to how you're accessing the database from EM at the moment. Even if it is to remain on your LAN it takes only the click of a button to switch off SQL Authentication.. Considering the trouble its caused you and the time lost trying to set up Windows Auth, seems pretty pointless not to use SQL Authentication to get the job done in the meantime... -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Friday, 19 November 2004 12:56 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew, While I am the only user of this db ATM, in the near future the owners of the database expect to be able to use it in some undetermined manner. I do not know yet the "how" of the access - it will probably be a mix of web server, remote access and / or vb.net application. In any event I have read (and as you are well aware I am totally ignorant on this stuff) that using windows authentication is more secure. I am therefore making every effort to get this set up from the gitgo to do that so I don't have a "gaping security hole" hanging out there forgotten. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 11:11 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From andrew.haslett at ilc.gov.au Tue Nov 23 19:52:24 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Wed, 24 Nov 2004 12:22:24 +1030 Subject: [dba-SQLServer] Back to the login thing Message-ID: <0A870603A2A816459078203FC07F4CD204C758@adl01s055.ilcorp.gov.au> >From remote sites, you access just using that port, which obviously requires that port to be forwarded in your router. For internal access, there's also a 'Client Network Utility' you can use to set up an ALIAS to use a different port. I think there are also issues with port 1434(UDP) from memory, but I can't remember exactly what is involved. Anyway I think that's what youre asking? If not, keep firing away! PS - The KB article is here if that helps: http://support.microsoft.com/default.aspx?scid=kb;EN-US;815146 Also, Top 10 tips to secure SQL http://www.microsoft.com/sql/techinfo/administration/2000/security/securings qlserver.asp -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Wednesday, 24 November 2004 11:45 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew: ...and how do you can the logging in to accommodate the new port designation? Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Tuesday, November 23, 2004 2:29 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing "Server Network Utility" - changes the port SQL listens on. There's also a KB article on it. -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Wednesday, 24 November 2004 4:12 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing I concur. When setting up authentication on a LAN it is very easy to create a group on the LAN or on the SQL's server and then apply that group to your SQL security. From then on security is a matter for the local system admin and they can just adds or subtracts users from the group(s) as required and it is straight forward to assign various sets of access rights; viewer/user/data-entry/backup/admin. But I do recommend that you create a back-door or two. Maybe add your user name directly to the SQL security and leave SQL authentication available with a very complex password. You hopefully will never have to use them but there is time when they will be required. Like when some admin person inadvertently turns off 'log-ins' or the domain server goes down etc.. There is other way to add to the security. I understand, though I have never done it that you can change the default port (1433) to something else. Francisco Tapia is a proponent of this method and you should check with him on the deployment. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Monday, November 22, 2004 9:07 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Fair enough. However, despite what you've read, I wouldn't say SQL Authentication is *insecure* - well, its definitely no worse than entering a username / password on a website which I'm sure you do from time to time.. You still neet to get access *through firewall and NAT* to the network that the server is on (which is currently your LAN) and *then* guess a username and password for an account on SQL, which *then* must have the necessary privileges to do any harm to the server. And to be honest, if your LAN is compromised, odds are the administrator account will be hacked anyway, giving the user access to the SQL server whether you're using Windows or SQL authentication. Anyway, I'm assuming that whatever the final product, its not going to remain on your home LAN is it? What I'm getting at, is that once its finished, an entirely new security model will need to be implemeted on the server that it will reside on, so its pretty much irrelevant as to how you're accessing the database from EM at the moment. Even if it is to remain on your LAN it takes only the click of a button to switch off SQL Authentication.. Considering the trouble its caused you and the time lost trying to set up Windows Auth, seems pretty pointless not to use SQL Authentication to get the job done in the meantime... -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Friday, 19 November 2004 12:56 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew, While I am the only user of this db ATM, in the near future the owners of the database expect to be able to use it in some undetermined manner. I do not know yet the "how" of the access - it will probably be a mix of web server, remote access and / or vb.net application. In any event I have read (and as you are well aware I am totally ignorant on this stuff) that using windows authentication is more secure. I am therefore making every effort to get this set up from the gitgo to do that so I don't have a "gaping security hole" hanging out there forgotten. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 11:11 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From accessd at shaw.ca Wed Nov 24 00:16:02 2004 From: accessd at shaw.ca (Jim Lawrence (AccessD)) Date: Tue, 23 Nov 2004 22:16:02 -0800 Subject: [dba-SQLServer] Back to the login thing In-Reply-To: <0A870603A2A816459078203FC07F4CD204C758@adl01s055.ilcorp.gov.au> Message-ID: Andrew: Thanks a lot for those links. I have not read all detail but it looks like the right addresses. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Tuesday, November 23, 2004 5:52 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing >From remote sites, you access just using that port, which obviously requires that port to be forwarded in your router. For internal access, there's also a 'Client Network Utility' you can use to set up an ALIAS to use a different port. I think there are also issues with port 1434(UDP) from memory, but I can't remember exactly what is involved. Anyway I think that's what youre asking? If not, keep firing away! PS - The KB article is here if that helps: http://support.microsoft.com/default.aspx?scid=kb;EN-US;815146 Also, Top 10 tips to secure SQL http://www.microsoft.com/sql/techinfo/administration/2000/security/securings qlserver.asp -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Wednesday, 24 November 2004 11:45 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew: ...and how do you can the logging in to accommodate the new port designation? Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Tuesday, November 23, 2004 2:29 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing "Server Network Utility" - changes the port SQL listens on. There's also a KB article on it. -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Wednesday, 24 November 2004 4:12 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing I concur. When setting up authentication on a LAN it is very easy to create a group on the LAN or on the SQL's server and then apply that group to your SQL security. From then on security is a matter for the local system admin and they can just adds or subtracts users from the group(s) as required and it is straight forward to assign various sets of access rights; viewer/user/data-entry/backup/admin. But I do recommend that you create a back-door or two. Maybe add your user name directly to the SQL security and leave SQL authentication available with a very complex password. You hopefully will never have to use them but there is time when they will be required. Like when some admin person inadvertently turns off 'log-ins' or the domain server goes down etc.. There is other way to add to the security. I understand, though I have never done it that you can change the default port (1433) to something else. Francisco Tapia is a proponent of this method and you should check with him on the deployment. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Monday, November 22, 2004 9:07 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing Fair enough. However, despite what you've read, I wouldn't say SQL Authentication is *insecure* - well, its definitely no worse than entering a username / password on a website which I'm sure you do from time to time.. You still neet to get access *through firewall and NAT* to the network that the server is on (which is currently your LAN) and *then* guess a username and password for an account on SQL, which *then* must have the necessary privileges to do any harm to the server. And to be honest, if your LAN is compromised, odds are the administrator account will be hacked anyway, giving the user access to the SQL server whether you're using Windows or SQL authentication. Anyway, I'm assuming that whatever the final product, its not going to remain on your home LAN is it? What I'm getting at, is that once its finished, an entirely new security model will need to be implemeted on the server that it will reside on, so its pretty much irrelevant as to how you're accessing the database from EM at the moment. Even if it is to remain on your LAN it takes only the click of a button to switch off SQL Authentication.. Considering the trouble its caused you and the time lost trying to set up Windows Auth, seems pretty pointless not to use SQL Authentication to get the job done in the meantime... -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Friday, 19 November 2004 12:56 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Back to the login thing Andrew, While I am the only user of this db ATM, in the near future the owners of the database expect to be able to use it in some undetermined manner. I do not know yet the "how" of the access - it will probably be a mix of web server, remote access and / or vb.net application. In any event I have read (and as you are well aware I am totally ignorant on this stuff) that using windows authentication is more secure. I am therefore making every effort to get this set up from the gitgo to do that so I don't have a "gaping security hole" hanging out there forgotten. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 17, 2004 11:11 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Back to the login thing As we've suggested multiple times, why are you using Windows Only Authentication? If this is just an internal system, then there's no need. Just set up some accounts using SQL Authentication on the other boxes and connect to it using this username and password. Presto. You're done. -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, 18 November 2004 1:04 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Back to the login thing I really need to get query analyzer able to run on Neo2 SQL Server from all of my workstations. I have gone through the systems setting security on the servers to Windows only / System Account. EM is now able to see Neo2 Server from all the workstations, and can in fact browse the tables, open the main table and return records etc. QA however fails at the login with a consistent "Login failed for user 'Neo2\Guest'". Msg 18456, level 16, state1. On Neo1, Neo2 and Soltek1 I am logging in to Windows as Administrator with an identical password on each of those three machines. I can use QA on Neo2 but I cannot use QA on Neo1 or Soltek1 against Neo2. Can anyone help me figure this thing out? I REALLY need to get all my workstations banging queries against SQL Server on Neo2. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From mark.breen at gmail.com Wed Nov 24 08:30:32 2004 From: mark.breen at gmail.com (Mark Breen) Date: Wed, 24 Nov 2004 14:30:32 +0000 Subject: [dba-SQLServer] DTS Guru's Message-ID: <26a96cce04112406306835a636@mail.gmail.com> Hello Susan and other DTS-er's out there. I have been using DTS for the last six or seven years now, but today for the very first time, I wrote some VB script within in one. Cool, I was able to use the powerful TRIM function instead of SQL's rather less powerful ltrim and rtrim functions. However, I have one problem yo guys may know how to handle. I have an if statement with my VB script that filters certain fields and does not copy the column if we fail the criteria check, but the DTS package still inserts a record, so I have to allow nulls and finally delete the records where the column values are Null. What I had hoped the If would do was skip the insertion completely if we fail to meet its condition. Can this be done? Would be create a performance hit because if really has to do a record by record check? Thanks in advance for any suggestions Mark Breen Ireland PS . here is the DTS package '********************************************************************** ' Visual Basic Transformation Script '************************************************************************ ' Copy each source column to the destination column Function Main() If DTSSource("Col008") = "PPID" Then strPartRev = trim(DTSSource("Col003")) strRev = right( strPartRev ,3) ' First we get the location of the Hyphen intHypyen = (InStr( strPartRev, "-" )) ' We move back one character from the actual hyphen, because we do not want it intHypyen =intHypyen -1 strPart = left(strPartRev, intHypyen) ' we do not know how many characters, so we pad it with the whole six zeros strPart = "000000" & strPart ' And now we remove any characters more than six DTSDestination("DI_Part") = right(strPart , 6 ) ' And here are the other columns DTSDestination("DI_Rev") = strRev DTSDestination("DI_JobNum") = trim(DTSSource("Col006")) DTSDestination("DI_JobQty") = trim(DTSSource("Col007")) DTSDestination("DI_DueDate") = trim(DTSSource("Col009")) DTSDestination("DI_Material") = trim(DTSSource("Col011")) End If Main = DTSTransformStat_OK End Function From artful at rogers.com Wed Nov 24 11:53:28 2004 From: artful at rogers.com (Arthur Fuller) Date: Wed, 24 Nov 2004 12:53:28 -0500 Subject: [dba-SQLServer] Copy database question In-Reply-To: <26a96cce04112406306835a636@mail.gmail.com> References: <26a96cce04112406306835a636@mail.gmail.com> Message-ID: <41A4CA98.8050108@rogers.com> I want to copy a database containing 100+ tables, about 500 sprocs and about 200 views and about 20 UDFs to a new database, but with the proviso that no data goes, only the structures. I'm not sure how to do this. Suggestions? TIA, A. > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004 From CMackin at quiznos.com Wed Nov 24 12:05:35 2004 From: CMackin at quiznos.com (Mackin, Christopher) Date: Wed, 24 Nov 2004 11:05:35 -0700 Subject: [dba-SQLServer] Copy database question Message-ID: Backup the source database and restore it as the new one. Chris Mackin -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Arthur Fuller Sent: Wednesday, November 24, 2004 10:53 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Copy database question I want to copy a database containing 100+ tables, about 500 sprocs and about 200 views and about 20 UDFs to a new database, but with the proviso that no data goes, only the structures. I'm not sure how to do this. Suggestions? TIA, A. > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From Developer at UltraDNT.com Wed Nov 24 12:24:10 2004 From: Developer at UltraDNT.com (Steve Conklin (Developer@UltraDNT)) Date: Wed, 24 Nov 2004 13:24:10 -0500 Subject: [dba-SQLServer] Copy database question In-Reply-To: <41A4CA98.8050108@rogers.com> Message-ID: <000501c4d252$cb400c20$0200a8c0@COA3> In Ent. Mgr. 2000, right click the source database, then "All Tasks" then "Generate SQL Script." Run the resulting script in QA in the target database. Hth Steve -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Wednesday, November 24, 2004 12:53 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Copy database question I want to copy a database containing 100+ tables, about 500 sprocs and about 200 views and about 20 UDFs to a new database, but with the proviso that no data goes, only the structures. I'm not sure how to do this. Suggestions? TIA, A. > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From Developer at UltraDNT.com Wed Nov 24 12:29:09 2004 From: Developer at UltraDNT.com (Steve Conklin (Developer@UltraDNT)) Date: Wed, 24 Nov 2004 13:29:09 -0500 Subject: [dba-SQLServer] Copy database question In-Reply-To: Message-ID: <000801c4d253$7d26cd70$0200a8c0@COA3> Backup/Restore WILL bring bring along the data, scripting will not. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mackin, Christopher Sent: Wednesday, November 24, 2004 1:06 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Copy database question Backup the source database and restore it as the new one. Chris Mackin -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Arthur Fuller Sent: Wednesday, November 24, 2004 10:53 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Copy database question I want to copy a database containing 100+ tables, about 500 sprocs and about 200 views and about 20 UDFs to a new database, but with the proviso that no data goes, only the structures. I'm not sure how to do this. Suggestions? TIA, A. > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From andrew.haslett at ilc.gov.au Wed Nov 24 19:08:08 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Thu, 25 Nov 2004 11:38:08 +1030 Subject: [dba-SQLServer] Copy database question Message-ID: <0A870603A2A816459078203FC07F4CD204C765@adl01s055.ilcorp.gov.au> DTS is also an option, and gives you more control over what you want to copy: Right-Click Database -> All Tasks -> Export Data Choose the Source and Destination Database Choose 'Copy Objects And Data..' Uncheck 'Copy Data' .. continue select options and objects that you want to copy as required. Cheers, Andrew -----Original Message----- From: Arthur Fuller [mailto:artful at rogers.com] Sent: Thursday, 25 November 2004 4:23 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Copy database question I want to copy a database containing 100+ tables, about 500 sprocs and about 200 views and about 20 UDFs to a new database, but with the proviso that no data goes, only the structures. I'm not sure how to do this. Suggestions? TIA, A. > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From andrew.haslett at ilc.gov.au Wed Nov 24 19:24:09 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Thu, 25 Nov 2004 11:54:09 +1030 Subject: [dba-SQLServer] Copy database question Message-ID: <0A870603A2A816459078203FC07F4CD204C767@adl01s055.ilcorp.gov.au> Sorry, formatting got stuffed up as it came through: * Right-Click Database -> All Tasks -> Export Data * Choose the Source and Destination Database * Choose 'Copy Objects And Data..' * Uncheck 'Copy Data' * .. continue select options and objects that you want to copy as required. -----Original Message----- From: Haslett, Andrew [mailto:andrew.haslett at ilc.gov.au] Sent: Thursday, 25 November 2004 11:38 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Copy database question DTS is also an option, and gives you more control over what you want to copy: Right-Click Database -> All Tasks -> Export Data Choose the Source and Destination Database Choose 'Copy Objects And Data..' Uncheck 'Copy Data' .. continue select options and objects that you want to copy as required. Cheers, Andrew -----Original Message----- From: Arthur Fuller [mailto:artful at rogers.com] Sent: Thursday, 25 November 2004 4:23 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Copy database question I want to copy a database containing 100+ tables, about 500 sprocs and about 200 views and about 20 UDFs to a new database, but with the proviso that no data goes, only the structures. I'm not sure how to do this. Suggestions? TIA, A. > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From jwcolby at colbyconsulting.com Fri Nov 26 21:06:53 2004 From: jwcolby at colbyconsulting.com (John W. Colby) Date: Fri, 26 Nov 2004 22:06:53 -0500 Subject: [dba-SQLServer] Copy database question In-Reply-To: <0A870603A2A816459078203FC07F4CD204C765@adl01s055.ilcorp.gov.au> Message-ID: <000001c4d42e$28844e00$e8dafea9@ColbyM6805> Can dts work between sql servers? John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 24, 2004 8:08 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Copy database question DTS is also an option, and gives you more control over what you want to copy: Right-Click Database -> All Tasks -> Export Data Choose the Source and Destination Database Choose 'Copy Objects And Data..' Uncheck 'Copy Data' .. continue select options and objects that you want to copy as required. Cheers, Andrew -----Original Message----- From: Arthur Fuller [mailto:artful at rogers.com] Sent: Thursday, 25 November 2004 4:23 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Copy database question I want to copy a database containing 100+ tables, about 500 sprocs and about 200 views and about 20 UDFs to a new database, but with the proviso that no data goes, only the structures. I'm not sure how to do this. Suggestions? TIA, A. > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From ebarro at afsweb.com Fri Nov 26 21:21:55 2004 From: ebarro at afsweb.com (Eric Barro) Date: Fri, 26 Nov 2004 19:21:55 -0800 Subject: [dba-SQLServer] Copy database question In-Reply-To: <000001c4d42e$28844e00$e8dafea9@ColbyM6805> Message-ID: Yes you just need to create a connection to the sql server (source and destination). The best way to do this is via DTS packages. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Friday, November 26, 2004 7:07 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Copy database question Can dts work between sql servers? John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Wednesday, November 24, 2004 8:08 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Copy database question DTS is also an option, and gives you more control over what you want to copy: Right-Click Database -> All Tasks -> Export Data Choose the Source and Destination Database Choose 'Copy Objects And Data..' Uncheck 'Copy Data' .. continue select options and objects that you want to copy as required. Cheers, Andrew -----Original Message----- From: Arthur Fuller [mailto:artful at rogers.com] Sent: Thursday, 25 November 2004 4:23 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Copy database question I want to copy a database containing 100+ tables, about 500 sprocs and about 200 views and about 20 UDFs to a new database, but with the proviso that no data goes, only the structures. I'm not sure how to do this. Suggestions? TIA, A. > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com ---------------------------------------------------------------- The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy. The company will not accept any liability in respect of such communication. From andrew.haslett at ilc.gov.au Mon Nov 29 01:55:01 2004 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Mon, 29 Nov 2004 18:25:01 +1030 Subject: [dba-SQLServer] Copy database question Message-ID: <0A870603A2A816459078203FC07F4CD20139FF@adl01s055.ilcorp.gov.au> yup. You just specify the same connection credentials as you would when connecting through EM _____ From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Sat 27/11/2004 1:36 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Copy database question Can dts work between sql servers? John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com ] On Behalf Of Haslett, Andrew Sent: Wednesday, November 24, 2004 8:08 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Copy database question DTS is also an option, and gives you more control over what you want to copy: Right-Click Database -> All Tasks -> Export Data Choose the Source and Destination Database Choose 'Copy Objects And Data..' Uncheck 'Copy Data' .. continue select options and objects that you want to copy as required. Cheers, Andrew -----Original Message----- From: Arthur Fuller [mailto:artful at rogers.com ] Sent: Thursday, 25 November 2004 4:23 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Copy database question I want to copy a database containing 100+ tables, about 500 sprocs and about 200 views and about 20 UDFs to a new database, but with the proviso that no data goes, only the structures. I'm not sure how to do this. Suggestions? TIA, A. > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. From kens.programming at verizon.net Mon Nov 29 14:12:27 2004 From: kens.programming at verizon.net (Ken Stoker) Date: Mon, 29 Nov 2004 12:12:27 -0800 Subject: [dba-SQLServer] Import data from Excel into SS2K Message-ID: <20041129201119.ETBO1432.out012.verizon.net@enterprise> Using a DTS package, how would I import data from an Excel file into SS2K? I can create a connection object for the destination database and the location of the Excel files, but am not seeing how I would then move the data. Any help is greatly appreciated. Thanks. Ken -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.3 - Release Date: 11/26/2004 From fhtapia at gmail.com Mon Nov 29 16:04:54 2004 From: fhtapia at gmail.com (Francisco Tapia) Date: Mon, 29 Nov 2004 14:04:54 -0800 Subject: [dba-SQLServer] Import data from Excel into SS2K In-Reply-To: <20041129201119.ETBO1432.out012.verizon.net@enterprise> References: <20041129201119.ETBO1432.out012.verizon.net@enterprise> Message-ID: look in BOL for the transformation object in DTS. On Mon, 29 Nov 2004 12:12:27 -0800, Ken Stoker wrote: > Using a DTS package, how would I import data from an Excel file into SS2K? > I can create a connection object for the destination database and the > location of the Excel files, but am not seeing how I would then move the > data. Any help is greatly appreciated. > > Thanks. > > Ken > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.289 / Virus Database: 265.4.3 - Release Date: 11/26/2004 > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://pcthis.blogspot.com | PC news with out the jargon! From mwp.reid at qub.ac.uk Mon Nov 29 16:15:24 2004 From: mwp.reid at qub.ac.uk (Martin Reid) Date: Mon, 29 Nov 2004 22:15:24 -0000 Subject: [dba-SQLServer] Cant connect References: <20041129201119.ETBO1432.out012.verizon.net@enterprise> Message-ID: <000801c4d660$ed6043d0$0100a8c0@Martin> Was working on SQL Server this evening. All was well. Installed Tight VNC and connected up to server in USA, All worked fine. On my own Machine now I cant start SQL Server. Using the service manager nothing happens. When I try it from EM I get the following message A connection could not be established REason: Client unable to establish connection Shared Memory Provider: File not found Any ideas?? Martin From kens.programming at verizon.net Mon Nov 29 16:29:45 2004 From: kens.programming at verizon.net (Ken Stoker) Date: Mon, 29 Nov 2004 14:29:45 -0800 Subject: [dba-SQLServer] Import data from Excel into SS2K In-Reply-To: Message-ID: <20041129222836.XRTI1390.out001.verizon.net@enterprise> Thank you. I wasn't using the right keywords in BOL. Really helps when you have a clue what you are looking for. Ken -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Monday, November 29, 2004 2:05 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Import data from Excel into SS2K look in BOL for the transformation object in DTS. On Mon, 29 Nov 2004 12:12:27 -0800, Ken Stoker wrote: > Using a DTS package, how would I import data from an Excel file into SS2K? > I can create a connection object for the destination database and the > location of the Excel files, but am not seeing how I would then move the > data. Any help is greatly appreciated. > > Thanks. > > Ken > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.289 / Virus Database: 265.4.3 - Release Date: 11/26/2004 > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://pcthis.blogspot.com | PC news with out the jargon! _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.3 - Release Date: 11/26/2004 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.3 - Release Date: 11/26/2004 From fhtapia at gmail.com Mon Nov 29 16:50:05 2004 From: fhtapia at gmail.com (Francisco Tapia) Date: Mon, 29 Nov 2004 14:50:05 -0800 Subject: [dba-SQLServer] Cant connect In-Reply-To: <000801c4d660$ed6043d0$0100a8c0@Martin> References: <20041129201119.ETBO1432.out012.verizon.net@enterprise> <000801c4d660$ed6043d0$0100a8c0@Martin> Message-ID: not sure.. I use Ultr at VNC on my boxes w/ SQL Server and have not had a problem... also I'm assuming you've rebooted since? (btw, Ultr@) also has all the underlying tech from tightVNC along w/ their developer :) On Mon, 29 Nov 2004 22:15:24 -0000, Martin Reid wrote: > Was working on SQL Server this evening. All was well. > > Installed Tight VNC and connected up to server in USA, All worked fine. > > On my own Machine now I cant start SQL Server. Using the service manager > nothing happens. When I try it from EM I get the following message > > A connection could not be established > REason: Client unable to establish connection > Shared Memory Provider: File not found > > Any ideas?? > > Martin > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://pcthis.blogspot.com | PC news with out the jargon! From serbach at new.rr.com Tue Nov 30 13:05:04 2004 From: serbach at new.rr.com (Steven W. Erbach) Date: Tue, 30 Nov 2004 13:05:04 -0600 Subject: [dba-SQLServer] Graphics in SQL Server table Message-ID: <20041130130504.1719938970.serbach@new.rr.com> Dear Group, Even though the standard advice for storing graphics on a web server is to store them in the file system, I've decided to store graphics in tables. I've used the ADO Stream object to read GIFs from disk and write them into an Image field. I found that the original images (over 4,000 GIFs) averaged 53.6KB each. When they've been written into the SQL Server tables the amount of table "space" allocated for each image stored averages 63.2KB. So there's about 10K of "overhead" (about 18%) for each image. Not bad. Getting the images out of the original Access database was a bit of a chore, though. Fortunately IrfanView allows command line options to paste an image into the window and convert the image to a GIF. I was able to cycle through all the images in relatively short order by copying to the Windows clipboard and pasting and saving with IrfanView. Steve Erbach Neenah, WI sweblog1.blogspot.com From mark.breen at gmail.com Tue Nov 30 17:15:57 2004 From: mark.breen at gmail.com (Mark Breen) Date: Tue, 30 Nov 2004 23:15:57 +0000 Subject: [dba-SQLServer] Graphics in SQL Server table In-Reply-To: <20041130130504.1719938970.serbach@new.rr.com> References: <20041130130504.1719938970.serbach@new.rr.com> Message-ID: <26a96cce041130151525bf1646@mail.gmail.com> Hello Steve, Now that is interesting, but what I would really be interested in for a potential future project is (and I know this is a solution trying to find a problem), what do you think of storing a whole lots of PDF's in SQL? Of course I can store them in the file system, but I am going to have to build a system that will track and print PDF's, your email has made me wonder whether there is any benefit in attempting to keep them in the db. One thing that I will have to do in have a sort of in-form PDF viewer. Again, there is no need to store them in the db, but I just thought it might be an idea. Any thoughts? Are you glad that you stored your gig's in the db, did you reap any benefit? Thanks Mark On Tue, 30 Nov 2004 13:05:04 -0600, Steven W. Erbach wrote: > Dear Group, > > Even though the standard advice for storing graphics on a web server is to store them in the file system, I've decided to store graphics in tables. I've used the ADO Stream object to read GIFs from disk and write them into an Image field. > > I found that the original images (over 4,000 GIFs) averaged 53.6KB each. When they've been written into the SQL Server tables the amount of table "space" allocated for each image stored averages 63.2KB. So there's about 10K of "overhead" (about 18%) for each image. Not bad. > > Getting the images out of the original Access database was a bit of a chore, though. Fortunately IrfanView allows command line options to paste an image into the window and convert the image to a GIF. I was able to cycle through all the images in relatively short order by copying to the Windows clipboard and pasting and saving with IrfanView. > > Steve Erbach > Neenah, WI > > sweblog1.blogspot.com > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > From accessd at shaw.ca Tue Nov 30 17:32:34 2004 From: accessd at shaw.ca (Jim Lawrence (AccessD)) Date: Tue, 30 Nov 2004 15:32:34 -0800 Subject: [dba-SQLServer] Graphics in SQL Server table In-Reply-To: <20041130130504.1719938970.serbach@new.rr.com> Message-ID: Hi Steve: Have you had a chance to test the performanace rates, comparing the standard storing method (outside the SQL) and new ADO.Stream method. I would be interested to hear the results from a large 'imbedded' implementation. Just one question: Why were the files all convereted to GIF format instead of maybe JPG? Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Steven W. Erbach Sent: Tuesday, November 30, 2004 11:05 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: [dba-SQLServer] Graphics in SQL Server table Dear Group, Even though the standard advice for storing graphics on a web server is to store them in the file system, I've decided to store graphics in tables. I've used the ADO Stream object to read GIFs from disk and write them into an Image field. I found that the original images (over 4,000 GIFs) averaged 53.6KB each. When they've been written into the SQL Server tables the amount of table "space" allocated for each image stored averages 63.2KB. So there's about 10K of "overhead" (about 18%) for each image. Not bad. Getting the images out of the original Access database was a bit of a chore, though. Fortunately IrfanView allows command line options to paste an image into the window and convert the image to a GIF. I was able to cycle through all the images in relatively short order by copying to the Windows clipboard and pasting and saving with IrfanView. Steve Erbach Neenah, WI sweblog1.blogspot.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com