From artful at rogers.com Sat Aug 5 11:51:05 2006 From: artful at rogers.com (artful at rogers.com) Date: Sat, 5 Aug 2006 09:51:05 -0700 (PDT) Subject: [dba-SQLServer] SSN Question Message-ID: <20060805165105.7952.qmail@web88212.mail.re2.yahoo.com> In Canada, it is illegal to use SINs (our equivalent of SSNs) for any purpose save Revenue Canada reporting. IOW, it is illegal to use a SIN as the PK of some table. Does the same hold true in the USA? TIA, Arthur From jwcolby at colbyconsulting.com Sat Aug 5 12:39:21 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Sat, 5 Aug 2006 13:39:21 -0400 Subject: [dba-SQLServer] SSN Question In-Reply-To: <20060805165105.7952.qmail@web88212.mail.re2.yahoo.com> Message-ID: <002901c6b8b6$16a81270$647aa8c0@m6805> It is supposed to, but the law is simply never enforced. EVERYBODY DEMANDS it - opening a business account at the bank, getting a drivers license etc. Quite illegal, but the law is simply ignored. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Saturday, August 05, 2006 12:51 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] SSN Question In Canada, it is illegal to use SINs (our equivalent of SSNs) for any purpose save Revenue Canada reporting. IOW, it is illegal to use a SIN as the PK of some table. Does the same hold true in the USA? TIA, Arthur _______________________________________________ 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 Sat Aug 5 14:01:10 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Sat, 05 Aug 2006 12:01:10 -0700 Subject: [dba-SQLServer] SSN Question In-Reply-To: <20060805165105.7952.qmail@web88212.mail.re2.yahoo.com> Message-ID: <0J3J00GB7GTKO710@l-daemon> Hi Arthur: It is legal to use it in a database situation but a client by law is not required to give it unless the information is directly related to his/her employment... so appropriate deductions can be made to revenue Canada. Convoluted? It seems an employer can request your SIN number or a bank when you are requesting an account or credit but a store where you purchase from can not. A lot of sites on the web, when purchasing from them leave a place for your SIN but do not make it mandatory. A subtle difference. SIN numbers are great for research tools. The number can suggest when the person legally started working in Canada, whether they are a landed immigrant or have a working visa or whether the number is fake or whether a SIN is being copied.... (Designed a database for H&R Block a few years back.) I do not know about the states but I have worked under the same assumptions and have never heard anything to the contrary. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Saturday, August 05, 2006 9:51 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] SSN Question In Canada, it is illegal to use SINs (our equivalent of SSNs) for any purpose save Revenue Canada reporting. IOW, it is illegal to use a SIN as the PK of some table. Does the same hold true in the USA? TIA, Arthur _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From artful at rogers.com Sat Aug 5 16:49:33 2006 From: artful at rogers.com (artful at rogers.com) Date: Sat, 5 Aug 2006 14:49:33 -0700 (PDT) Subject: [dba-SQLServer] SSN Question In-Reply-To: <002901c6b8b6$16a81270$647aa8c0@m6805> Message-ID: <20060805214933.61581.qmail@web88206.mail.re2.yahoo.com> Thanks for that input, JC. for the record, what would be the punishment should said law be enforced? ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Saturday, August 5, 2006 1:39:21 PM Subject: Re: [dba-SQLServer] SSN Question It is supposed to, but the law is simply never enforced. EVERYBODY DEMANDS it - opening a business account at the bank, getting a drivers license etc. Quite illegal, but the law is simply ignored. John W. Colby Colby Consulting www.ColbyConsulting.com From askolits at ot.com Tue Aug 8 16:52:08 2006 From: askolits at ot.com (askolits at ot.com) Date: Tue, 8 Aug 2006 17:52:08 -0400 Subject: [dba-SQLServer] UTC Date Time Fields and Baan with SqlServer Message-ID: <005501c6bb34$e8814fc0$6e01a8c0@LaptopXP> I'm working for a customer who has an MRP system called BAAN. All data tables are on SqlServer. For some reason, when we look at the data through SqlServer. All the times are 4 hours off. When we use their app, the time is correct. The question is, is it their app or a setting we need to set in SqlServer. The claim it's not there issue and they don't support direct access to the data through SQL Server. We have written custom reports to get the many reports their system doesn't provide. Any way to change SQLServer's time so we can fix this issue. Setting the Server's Region codes won't help us since the server is used for other things. I'm thinking there some type of parameter setting we can use. Note: They used to use standard time fields but now using UTC (makes sense?) Thanks, John Skolits From stuart at lexacorp.com.pg Tue Aug 8 17:13:17 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Wed, 09 Aug 2006 08:13:17 +1000 Subject: [dba-SQLServer] UTC Date Time Fields and Baan with SqlServer In-Reply-To: <005501c6bb34$e8814fc0$6e01a8c0@LaptopXP> References: <005501c6bb34$e8814fc0$6e01a8c0@LaptopXP> Message-ID: <44D9991D.25947.377E072@stuart.lexacorp.com.pg> On 8 Aug 2006 at 17:52, askolits at ot.com wrote: > > For some reason, when we look at the data through SqlServer. All the times > are 4 hours off. When we use their app, the time is correct. > > The question is, is it their app or a setting we need to set in SqlServer. > The claim it's not there issue and they don't support direct access to the > data through SQL Server. ..... > > Note: They used to use standard time fields but now using UTC (makes sense?) And your time zone is -0400, so ISTM that it is working exactly as it should. If you want local times in your reports, you will have to add your time zone offset to the stored times. You can use sp_help_targetserver to return time_zone_adjustment for you server. -- Stuart From martyconnelly at shaw.ca Tue Aug 8 17:44:25 2006 From: martyconnelly at shaw.ca (MartyConnelly) Date: Tue, 08 Aug 2006 15:44:25 -0700 Subject: [dba-SQLServer] UTC Date Time Fields and Baan with SqlServer In-Reply-To: <005501c6bb34$e8814fc0$6e01a8c0@LaptopXP> References: <005501c6bb34$e8814fc0$6e01a8c0@LaptopXP> Message-ID: <44D913C9.4020703@shaw.ca> This line "They used to use standard time fields but now using UTC" makes me think that they are accepting data from multiple time zones and have standardized the time of their SQL Server on UTC Greenwich time. This way all their data input times are the same, no matter what time zone it is coming from. This quite common in large organizations. The 4 hour time difference is correct as UTC is one hour a head of British Standard time and I'll bet you are running in American EST timezone. What you want to do is query your client machine for its local time and subtract or add the difference from UTC. So you will need code below. The date of a time zone DST change is in an odd format in the registrty. Have a look at the code in this basClock module Access97 mdb It gets local machine time and UTC. It handles a lot of the little glitches like daylight saving time switches for example Europe switches DST a week before the US. UTC time doesn't use DST and some US states don't either. Windows local time handles most of these but not in weird cases like Sydney Australia changing their time zone for their Olympics for a month. http://www.mvps.org/access/forms/frm0051.htm askolits at ot.com wrote: >I'm working for a customer who has an MRP system called BAAN. All data >tables are on SqlServer. > > > >For some reason, when we look at the data through SqlServer. All the times >are 4 hours off. When we use their app, the time is correct. > >The question is, is it their app or a setting we need to set in SqlServer. >The claim it's not there issue and they don't support direct access to the >data through SQL Server. > > > >We have written custom reports to get the many reports their system doesn't >provide. > > > >Any way to change SQLServer's time so we can fix this issue. > >Setting the Server's Region codes won't help us since the server is used for >other things. > >I'm thinking there some type of parameter setting we can use. > > > >Note: They used to use standard time fields but now using UTC (makes sense?) > > > >Thanks, > > > >John Skolits > > > > > >_______________________________________________ >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 askolits at ot.com Wed Aug 9 10:36:10 2006 From: askolits at ot.com (John Skolits) Date: Wed, 9 Aug 2006 11:36:10 -0400 Subject: [dba-SQLServer] UTC Date Time Fields and Baan with SqlServer In-Reply-To: <44D9991D.25947.377E072@stuart.lexacorp.com.pg> Message-ID: <002201c6bbc9$8d561f50$6e01a8c0@LaptopXP> Stuart, I wanted to try your method to at least retrieve the settings. I ran the Query analyzer and ran Exec sp_help_targetserver And the return message was that it "could not find stored procedure sp_help_targetserver". I was it running against the specific database. I then ran it against all the databases and it only found it in msbd. I copied the SP from msbd to the database I'm working with and it now returned some column headings but no data. Am I missing something? -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Tuesday, August 08, 2006 6:13 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] UTC Date Time Fields and Baan with SqlServer On 8 Aug 2006 at 17:52, askolits at ot.com wrote: > > For some reason, when we look at the data through SqlServer. All the times > are 4 hours off. When we use their app, the time is correct. > > The question is, is it their app or a setting we need to set in SqlServer. > The claim it's not there issue and they don't support direct access to the > data through SQL Server. ..... > > Note: They used to use standard time fields but now using UTC (makes sense?) And your time zone is -0400, so ISTM that it is working exactly as it should. If you want local times in your reports, you will have to add your time zone offset to the stored times. You can use sp_help_targetserver to return time_zone_adjustment for you server. -- Stuart _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From askolits at ot.com Wed Aug 9 10:47:55 2006 From: askolits at ot.com (John Skolits) Date: Wed, 9 Aug 2006 11:47:55 -0400 Subject: [dba-SQLServer] UTC Date Time Fields and Baan with SqlServer In-Reply-To: <44D913C9.4020703@shaw.ca> Message-ID: <002701c6bbcb$3197e070$6e01a8c0@LaptopXP> Marty, We are in the EST and I believe the company is in Sweden. Thanks for the possible solution below. I can certainly use it for my static reports. But my other issues is many people reference these tables through Access. Therefore if they do any custom queries on their own, they will always be 4 hours off. One solution is to make SQLServer views of each table that they use. I can place the date/time conversions in the views. But I'm thinking that will cause query performance issues. Usually, I have found views to work well with criteria specified on a date/time field without a heavy performance hit. But I wonder if I have a date/time formula conversions in the view, if the indexes won't work well. Any thoughts? John -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of MartyConnelly Sent: Tuesday, August 08, 2006 6:44 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] UTC Date Time Fields and Baan with SqlServer This line "They used to use standard time fields but now using UTC" makes me think that they are accepting data from multiple time zones and have standardized the time of their SQL Server on UTC Greenwich time. This way all their data input times are the same, no matter what time zone it is coming from. This quite common in large organizations. The 4 hour time difference is correct as UTC is one hour a head of British Standard time and I'll bet you are running in American EST timezone. What you want to do is query your client machine for its local time and subtract or add the difference from UTC. So you will need code below. The date of a time zone DST change is in an odd format in the registrty. Have a look at the code in this basClock module Access97 mdb It gets local machine time and UTC. It handles a lot of the little glitches like daylight saving time switches for example Europe switches DST a week before the US. UTC time doesn't use DST and some US states don't either. Windows local time handles most of these but not in weird cases like Sydney Australia changing their time zone for their Olympics for a month. http://www.mvps.org/access/forms/frm0051.htm askolits at ot.com wrote: >I'm working for a customer who has an MRP system called BAAN. All data >tables are on SqlServer. > > > >For some reason, when we look at the data through SqlServer. All the times >are 4 hours off. When we use their app, the time is correct. > >The question is, is it their app or a setting we need to set in SqlServer. >The claim it's not there issue and they don't support direct access to the >data through SQL Server. > > > >We have written custom reports to get the many reports their system doesn't >provide. > > > >Any way to change SQLServer's time so we can fix this issue. > >Setting the Server's Region codes won't help us since the server is used for >other things. > >I'm thinking there some type of parameter setting we can use. > > > >Note: They used to use standard time fields but now using UTC (makes sense?) > > > >Thanks, > > > >John Skolits > > > > > >_______________________________________________ >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 _______________________________________________ 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 Aug 9 14:51:52 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Wed, 9 Aug 2006 15:51:52 -0400 Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: <20060805214933.61581.qmail@web88206.mail.re2.yahoo.com> Message-ID: <003c01c6bbed$4509c7f0$657aa8c0@m6805> Is there any way to tell what is going on with SQL Server when it hangs? I am trying to import these tens of millions of records into SQL Server. They are flat file comma delimited text files, 3 million recs / file. Everything is working fine, I have ~12 files imported (36 million records) and I am humming along. I have about 6 import processes running (import and export data manager) at once and of course things slow down but suddenly none of the imports is progressing at all. I try to connect with EM and when I try to expand the "databases" tree it gives an error connecting, "unable to obtain a lock" or some such. I let the import functions continue to run but 20 minutes later still not a single more record imported. So I use task manager to shut down all of the import processes, shut down EM, shut down the SQL Server manager normally, unload it, shut off the computer, restart it. Try to connect with enterprise manager and no go. In fact it APPEARS to be locked up. When I go in with task manager and look at the process, it is slowly gaining "memory used" until it basically runs out then starts increasing the page file size, until that hits about 1.7g and then that too stops incrementing but EM is still hung. CPU usage is now down about 2%, no "more" memory being grabbed by EM, the page file is static, but EM is hung. I need to find out what is going on here. I have about 12 of these 3 million record text files imported and don't want to have to clean it out and start over, but worse, I have no clue why it stopped working. Is there any (free) tool that will tell me what SQL Server thinks it is up to? If I can't get EM to see the databases I am basically hosed here. John W. Colby Colby Consulting www.ColbyConsulting.com From mwp.reid at qub.ac.uk Wed Aug 9 15:04:10 2006 From: mwp.reid at qub.ac.uk (Martin Reid) Date: Wed, 9 Aug 2006 21:04:10 +0100 Subject: [dba-SQLServer] SQL Server hanging References: <003c01c6bbed$4509c7f0$657aa8c0@m6805> Message-ID: John Try and run a trace on the server and database your importing to. Open SQL Proflier -> File -> New->Trace See what that shows you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 From martyconnelly at shaw.ca Wed Aug 9 15:28:10 2006 From: martyconnelly at shaw.ca (MartyConnelly) Date: Wed, 09 Aug 2006 13:28:10 -0700 Subject: [dba-SQLServer] UTC Date Time Fields and Baan with SqlServer In-Reply-To: <002701c6bbcb$3197e070$6e01a8c0@LaptopXP> References: <002701c6bbcb$3197e070$6e01a8c0@LaptopXP> Message-ID: <44DA455A.8040702@shaw.ca> Well if your server is running on UTC, it never undergoes a Daylight Savings or Standard time change. There is a difference between GMT and UTC Now you get to make an executive decision do you base all your reports on local time or UTCDateTime. If local then on queries add the time difference from parameters and on reports subtract time difference to dates on returned views or tables etc. Using DateAdd or DateDiff in your SQL. Not all time zones are 1 hour interval differences, Newfoundland has a half hour offset. You can get both times from SQL Server 2000 via this Function GetServerUTCDate() Dim dteServerDateUTC As Date Dim dteServerDateLocal As Date 'assumes connection to server 'GETUTCDATE works on SQL 2000 + dteServerDateUTC = CurrentProject.Connection.Execute("SELECT GETUTCDATE()").Collect(0) dteServerDateLocal = CurrentProject.Connection.Execute("SELECT GETDATE()").Collect(0) Debug.Print "Local Time " & dteServerDateLocal Debug.Print "UTC Time " & dteServerDateUTC 'delta hour server difference Debug.Print "Difference in hours " & DateDiff("h", dteServerDateUTC, dteServerDateLocal) 'or local machine time Debug.Print "Difference in hours " & DateDiff("h", dteServerDateUTC, Now) 'This delta time difference will change locally twice a year at 2AM October, April US End Function John Skolits wrote: >Marty, > >We are in the EST and I believe the company is in Sweden. > >Thanks for the possible solution below. I can certainly use it for my static >reports. > >But my other issues is many people reference these tables through Access. >Therefore if they do any custom queries on their own, they will always be 4 >hours off. > >One solution is to make SQLServer views of each table that they use. I can >place the date/time conversions in the views. But I'm thinking that will >cause query performance issues. Usually, I have found views to work well >with criteria specified on a date/time field without a heavy performance >hit. But I wonder if I have a date/time formula conversions in the view, if >the indexes won't work well. > >Any thoughts? > >John > > >-----Original Message----- >From: dba-sqlserver-bounces at databaseadvisors.com >[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of >MartyConnelly >Sent: Tuesday, August 08, 2006 6:44 PM >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] UTC Date Time Fields and Baan with SqlServer > >This line "They used to use standard time fields but now using UTC" >makes me think >that they are accepting data from multiple time zones and have >standardized the time of their SQL >Server on UTC Greenwich time. This way all their data input times are >the same, no matter >what time zone it is coming from. This quite common in large organizations. > >The 4 hour time difference is correct as UTC is one hour >a head of British Standard time and I'll bet you are running in >American EST timezone. >What you want to do is query your client machine for its local time and >subtract or add the difference >from UTC. So you will need code below. The date of a time zone DST >change is in an odd format in the registrty. > >Have a look at the code in this basClock module Access97 mdb >It gets local machine time and UTC. >It handles a lot of the little glitches like daylight saving time switches >for example Europe switches DST a week before the US. >UTC time doesn't use DST and some US states don't either. >Windows local time handles most of these but not in weird >cases like Sydney Australia changing their time zone for >their Olympics for a month. > >http://www.mvps.org/access/forms/frm0051.htm > > > >askolits at ot.com wrote: > > > >>I'm working for a customer who has an MRP system called BAAN. All data >>tables are on SqlServer. >> >> >> >>For some reason, when we look at the data through SqlServer. All the times >>are 4 hours off. When we use their app, the time is correct. >> >>The question is, is it their app or a setting we need to set in SqlServer. >>The claim it's not there issue and they don't support direct access to the >>data through SQL Server. >> >> >> >>We have written custom reports to get the many reports their system doesn't >>provide. >> >> >> >>Any way to change SQLServer's time so we can fix this issue. >> >>Setting the Server's Region codes won't help us since the server is used >> >> >for > > >>other things. >> >>I'm thinking there some type of parameter setting we can use. >> >> >> >>Note: They used to use standard time fields but now using UTC (makes >> >> >sense?) > > >> >>Thanks, >> >> >> >>John Skolits >> >> >> >> >> >>_______________________________________________ >>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 artful at rogers.com Wed Aug 9 16:19:17 2006 From: artful at rogers.com (artful at rogers.com) Date: Wed, 9 Aug 2006 14:19:17 -0700 (PDT) Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: Message-ID: <20060809211917.64577.qmail@web88203.mail.re2.yahoo.com> Assuming that you are importing the data using DTS, you can adjust the "commit after # rows" level. Cut it back to say 100 or 1000 rows and then see what is happening. ----- Original Message ---- From: Martin Reid To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, August 9, 2006 4:04:10 PM Subject: Re: [dba-SQLServer] SQL Server hanging John Try and run a trace on the server and database your importing to. Open SQL Proflier -> File -> New->Trace See what that shows you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 _______________________________________________ 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 Wed Aug 9 17:13:36 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Wed, 09 Aug 2006 15:13:36 -0700 Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: <003c01c6bbed$4509c7f0$657aa8c0@m6805> Message-ID: <0J3R00ED84EBPZ80@l-daemon> Hi John: I had some issues when importing a large batch of comma delimitated records. The problem was because one of the records had an imbedded comma. I found the offending record by importing a block into MSAccess... You could always try to import the data in blocks. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Wednesday, August 09, 2006 12:52 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] SQL Server hanging Is there any way to tell what is going on with SQL Server when it hangs? I am trying to import these tens of millions of records into SQL Server. They are flat file comma delimited text files, 3 million recs / file. Everything is working fine, I have ~12 files imported (36 million records) and I am humming along. I have about 6 import processes running (import and export data manager) at once and of course things slow down but suddenly none of the imports is progressing at all. I try to connect with EM and when I try to expand the "databases" tree it gives an error connecting, "unable to obtain a lock" or some such. I let the import functions continue to run but 20 minutes later still not a single more record imported. So I use task manager to shut down all of the import processes, shut down EM, shut down the SQL Server manager normally, unload it, shut off the computer, restart it. Try to connect with enterprise manager and no go. In fact it APPEARS to be locked up. When I go in with task manager and look at the process, it is slowly gaining "memory used" until it basically runs out then starts increasing the page file size, until that hits about 1.7g and then that too stops incrementing but EM is still hung. CPU usage is now down about 2%, no "more" memory being grabbed by EM, the page file is static, but EM is hung. I need to find out what is going on here. I have about 12 of these 3 million record text files imported and don't want to have to clean it out and start over, but worse, I have no clue why it stopped working. Is there any (free) tool that will tell me what SQL Server thinks it is up to? If I can't get EM to see the databases I am basically hosed here. John W. Colby Colby Consulting www.ColbyConsulting.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 Wed Aug 9 19:39:51 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Wed, 9 Aug 2006 20:39:51 -0400 Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: <003c01c6bbed$4509c7f0$657aa8c0@m6805> Message-ID: <004901c6bc15$7ea27930$657aa8c0@m6805> It turns out it was just thinking. Unfortunately I am now totally confused on which files succeeded and which failed. Arthur, I do think that adjusting the number of records that are imported before a commit is a grand idea. I also need info on how to shrink the log file. As you might guess I am still muddling through this SQL Server thing. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Wednesday, August 09, 2006 3:52 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] SQL Server hanging Is there any way to tell what is going on with SQL Server when it hangs? I am trying to import these tens of millions of records into SQL Server. They are flat file comma delimited text files, 3 million recs / file. Everything is working fine, I have ~12 files imported (36 million records) and I am humming along. I have about 6 import processes running (import and export data manager) at once and of course things slow down but suddenly none of the imports is progressing at all. I try to connect with EM and when I try to expand the "databases" tree it gives an error connecting, "unable to obtain a lock" or some such. I let the import functions continue to run but 20 minutes later still not a single more record imported. So I use task manager to shut down all of the import processes, shut down EM, shut down the SQL Server manager normally, unload it, shut off the computer, restart it. Try to connect with enterprise manager and no go. In fact it APPEARS to be locked up. When I go in with task manager and look at the process, it is slowly gaining "memory used" until it basically runs out then starts increasing the page file size, until that hits about 1.7g and then that too stops incrementing but EM is still hung. CPU usage is now down about 2%, no "more" memory being grabbed by EM, the page file is static, but EM is hung. I need to find out what is going on here. I have about 12 of these 3 million record text files imported and don't want to have to clean it out and start over, but worse, I have no clue why it stopped working. Is there any (free) tool that will tell me what SQL Server thinks it is up to? If I can't get EM to see the databases I am basically hosed here. John W. Colby Colby Consulting www.ColbyConsulting.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From michael at ddisolutions.com.au Wed Aug 9 20:32:35 2006 From: michael at ddisolutions.com.au (Michael Maddison) Date: Thu, 10 Aug 2006 11:32:35 +1000 Subject: [dba-SQLServer] SQL Server hanging Message-ID: <59A61174B1F5B54B97FD4ADDE71E7D0116A8DA@ddi-01.DDI.local> John, Yes SQL will stop and 'think' in situations like yours :-) Stopping SQL when it is busy is almost always a bad idea. It will attempt to recover, roll back etc when you restart it again as you discovered. IIRC you can configure DTS to log any errors. You can also specify that each package operates within a transaction. 1 fails all fails and rolls back, which is probably what was happening when SQL stopped responding. It takes a while to roll back a large number of transaction. I have learnt to give it the benefit of the doubt and 99/100 it will eventually roll back and then display whatever the problem was with the package. Making the data chunks smaller is also a good idea. You could also look at bcp to import your files, it should be faster. cheers Michael M -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Thursday, 10 August 2006 10:40 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging It turns out it was just thinking. Unfortunately I am now totally confused on which files succeeded and which failed. Arthur, I do think that adjusting the number of records that are imported before a commit is a grand idea. I also need info on how to shrink the log file. As you might guess I am still muddling through this SQL Server thing. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Wednesday, August 09, 2006 3:52 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] SQL Server hanging Is there any way to tell what is going on with SQL Server when it hangs? I am trying to import these tens of millions of records into SQL Server. They are flat file comma delimited text files, 3 million recs / file. Everything is working fine, I have ~12 files imported (36 million records) and I am humming along. I have about 6 import processes running (import and export data manager) at once and of course things slow down but suddenly none of the imports is progressing at all. I try to connect with EM and when I try to expand the "databases" tree it gives an error connecting, "unable to obtain a lock" or some such. I let the import functions continue to run but 20 minutes later still not a single more record imported. So I use task manager to shut down all of the import processes, shut down EM, shut down the SQL Server manager normally, unload it, shut off the computer, restart it. Try to connect with enterprise manager and no go. In fact it APPEARS to be locked up. When I go in with task manager and look at the process, it is slowly gaining "memory used" until it basically runs out then starts increasing the page file size, until that hits about 1.7g and then that too stops incrementing but EM is still hung. CPU usage is now down about 2%, no "more" memory being grabbed by EM, the page file is static, but EM is hung. I need to find out what is going on here. I have about 12 of these 3 million record text files imported and don't want to have to clean it out and start over, but worse, I have no clue why it stopped working. Is there any (free) tool that will tell me what SQL Server thinks it is up to? If I can't get EM to see the databases I am basically hosed here. John W. Colby Colby Consulting www.ColbyConsulting.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 darrend at nimble.com.au Wed Aug 9 20:39:17 2006 From: darrend at nimble.com.au (Darren DICK) Date: Thu, 10 Aug 2006 11:39:17 +1000 Subject: [dba-SQLServer] OT: Reporting Services Guru Required Message-ID: <20060810013917.BBZB6880.omta04ps.mx.bigpond.com@DENZILLAP> Hi Team CROSS POSTED A bit OT I know - so please respond off-list - thanks Our firm needs to find a Sydney based Reporting Services Guru we can call on from time to time to assist with various things who from time to time may be required to come on-site with us to some of our clients If you or someone you know fits the bill - can you get them to contact me off list please at darrend @ nimble.com.au? Many thanks See y'all Darren From jwcolby at colbyconsulting.com Wed Aug 9 20:41:41 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Wed, 9 Aug 2006 21:41:41 -0400 Subject: [dba-SQLServer] BCP In-Reply-To: <59A61174B1F5B54B97FD4ADDE71E7D0116A8DA@ddi-01.DDI.local> Message-ID: <004d01c6bc1e$21dadc70$657aa8c0@m6805> >You could also look at bcp to import your files, it should be faster. These files come to me in a zip file (21 of them), unzipped they are each exactly 9,706,055 bytes (just under 10 gigabytes). Each contains exactly 3 million records. Each record contains some 400+ fields, fixed width but comma delimited. The FIRST file has the header containing the field names etc, but the remaining files do not. Because of the size of the files, they are a pain to do anything with programmatically (VBA etc). BCP is a command line process correct? I would love to do anything to speed this up but basically the import wizard, while cumbersome to use over and over, make it drop dead simple to get these imported. IIRC BCP (which I have never used) requires a format file? Can I get SQL Server (EM?) to create the format file for the table given the existing table (which I have). I sure don't want to John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Michael Maddison Sent: Wednesday, August 09, 2006 9:33 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging John, Yes SQL will stop and 'think' in situations like yours :-) Stopping SQL when it is busy is almost always a bad idea. It will attempt to recover, roll back etc when you restart it again as you discovered. IIRC you can configure DTS to log any errors. You can also specify that each package operates within a transaction. 1 fails all fails and rolls back, which is probably what was happening when SQL stopped responding. It takes a while to roll back a large number of transaction. I have learnt to give it the benefit of the doubt and 99/100 it will eventually roll back and then display whatever the problem was with the package. Making the data chunks smaller is also a good idea. You could also look at bcp to import your files, it should be faster. cheers Michael M From michael at ddisolutions.com.au Wed Aug 9 21:26:23 2006 From: michael at ddisolutions.com.au (Michael Maddison) Date: Thu, 10 Aug 2006 12:26:23 +1000 Subject: [dba-SQLServer] BCP Message-ID: <59A61174B1F5B54B97FD4ADDE71E7D0116A8DE@ddi-01.DDI.local> John, Havn't done it myself but BOL says... Using Format Files When bulk copying data using interactive mode, the bcp utility prompts you to store information regarding the storage type, prefix length, field length, and field and row terminators. The file used to store the format information for each field in the data file is called the format file: Do you want to save this format information in a file? [Y/n] y Host filename: [bcp.fmt] Although the default name for the format file is Bcp.fmt, a different file name can be specified. This format file provides the default information used either to bulk copy the data in the data file back into an instance of Microsoft(r) SQL Server(tm) or to bulk copy data out from the table another time, without needing to respecify the format. When bulk copying data into or out of an instance of SQL Server with an existing format file, bcp does not prompt for the file storage type, prefix length, field length, or field terminator because it uses the values already recorded. To use a previously created format file when importing data into an instance of SQL Server, use the -f switch with the bcp utility or the FORMATFILE clause with the BULK INSERT statement. For example, the command to bulk copy the contents of New_auth.dat data file into the authors2 table in the pubs database using the previously created format file (Authors.fmt) is: bcp pubs..authors2 in c:\new_auth.dat -fc:\authors.fmt -Sservername -Usa -Ppassword So, create an out script based on your table, 400 fields (wow), save the format file it generates. Use that for the import... How hard could it be...lol cheers Michael M -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Thursday, 10 August 2006 11:42 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] BCP >You could also look at bcp to import your files, it should be faster. These files come to me in a zip file (21 of them), unzipped they are each exactly 9,706,055 bytes (just under 10 gigabytes). Each contains exactly 3 million records. Each record contains some 400+ fields, fixed width but comma delimited. The FIRST file has the header containing the field names etc, but the remaining files do not. Because of the size of the files, they are a pain to do anything with programmatically (VBA etc). BCP is a command line process correct? I would love to do anything to speed this up but basically the import wizard, while cumbersome to use over and over, make it drop dead simple to get these imported. IIRC BCP (which I have never used) requires a format file? Can I get SQL Server (EM?) to create the format file for the table given the existing table (which I have). I sure don't want to John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Michael Maddison Sent: Wednesday, August 09, 2006 9:33 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging John, Yes SQL will stop and 'think' in situations like yours :-) Stopping SQL when it is busy is almost always a bad idea. It will attempt to recover, roll back etc when you restart it again as you discovered. IIRC you can configure DTS to log any errors. You can also specify that each package operates within a transaction. 1 fails all fails and rolls back, which is probably what was happening when SQL stopped responding. It takes a while to roll back a large number of transaction. I have learnt to give it the benefit of the doubt and 99/100 it will eventually roll back and then display whatever the problem was with the package. Making the data chunks smaller is also a good idea. You could also look at bcp to import your files, it should be faster. cheers Michael M _______________________________________________ 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 Thu Aug 10 07:42:43 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Thu, 10 Aug 2006 08:42:43 -0400 Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: <20060809211917.64577.qmail@web88203.mail.re2.yahoo.com> Message-ID: <005801c6bc7a$7a1275e0$657aa8c0@m6805> >using DTS, you can adjust the "commit after # rows" level. Is this possible using the DTS wizard? I am not able to find this property anywhere and of course the help doesn't. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Wednesday, August 09, 2006 5:19 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging Assuming that you are importing the data using DTS, you can adjust the "commit after # rows" level. Cut it back to say 100 or 1000 rows and then see what is happening. ----- Original Message ---- From: Martin Reid To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, August 9, 2006 4:04:10 PM Subject: Re: [dba-SQLServer] SQL Server hanging John Try and run a trace on the server and database your importing to. Open SQL Proflier -> File -> New->Trace See what that shows you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 _______________________________________________ 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 mwp.reid at qub.ac.uk Thu Aug 10 08:12:19 2006 From: mwp.reid at qub.ac.uk (Martin Reid) Date: Thu, 10 Aug 2006 14:12:19 +0100 Subject: [dba-SQLServer] SQL Server hanging References: <005801c6bc7a$7a1275e0$657aa8c0@m6805> Message-ID: John Look up Insert Commit Size re DTS Soorry my server is down at the moment so cant check it for you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of JWColby Sent: Thu 10/08/2006 13:42 To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging >using DTS, you can adjust the "commit after # rows" level. Is this possible using the DTS wizard? I am not able to find this property anywhere and of course the help doesn't. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Wednesday, August 09, 2006 5:19 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging Assuming that you are importing the data using DTS, you can adjust the "commit after # rows" level. Cut it back to say 100 or 1000 rows and then see what is happening. ----- Original Message ---- From: Martin Reid To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, August 9, 2006 4:04:10 PM Subject: Re: [dba-SQLServer] SQL Server hanging John Try and run a trace on the server and database your importing to. Open SQL Proflier -> File -> New->Trace See what that shows you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 _______________________________________________ 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 jwcolby at colbyconsulting.com Thu Aug 10 08:15:47 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Thu, 10 Aug 2006 09:15:47 -0400 Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: <005801c6bc7a$7a1275e0$657aa8c0@m6805> Message-ID: <005901c6bc7f$18890820$657aa8c0@m6805> Never mind, I just found the DTS editor, which is exactly what I needed. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Thursday, August 10, 2006 8:43 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging >using DTS, you can adjust the "commit after # rows" level. Is this possible using the DTS wizard? I am not able to find this property anywhere and of course the help doesn't. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Wednesday, August 09, 2006 5:19 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging Assuming that you are importing the data using DTS, you can adjust the "commit after # rows" level. Cut it back to say 100 or 1000 rows and then see what is happening. ----- Original Message ---- From: Martin Reid To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, August 9, 2006 4:04:10 PM Subject: Re: [dba-SQLServer] SQL Server hanging John Try and run a trace on the server and database your importing to. Open SQL Proflier -> File -> New->Trace See what that shows you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 _______________________________________________ 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 jwcolby at colbyconsulting.com Thu Aug 10 09:05:57 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Thu, 10 Aug 2006 10:05:57 -0400 Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: Message-ID: <005f01c6bc86$1abcd3e0$657aa8c0@m6805> It doesn't appear that it is possible to do this via the wizard, or at least I can't see how. However under data transformation / local packages / right click / New package you can get at the designer which does allow all of this stuff. I have been doing more than one transform (several different files) from the simple wizard. Under normal circumstances, the second and subsequent transforms wait for the first to finish. However, and I have not determined how or why, sometimes the second or third or fourth transform that I define will start executing as well. Sometimes all of them at once!!! When that happens of course, things slow down a LOT. I could never tell if the slow down was linear or not. Unfortunately, I also started getting "unable to obtain lock" failures when this happens. Of course the error messages don't make clear whether the locks are database licks or file system locks. I suspect that it is db (row) locks. I thought perhaps the designer would give enough more control that it would significantly speed up the imports. I set the properties to use a table lock which it seems would speed things up. I also set it up to read 1000 records (lines, or at least so I think) into the source buffer from the source text file instead of one line at a time, thinking that this too might speed things up. I did however ask it to commit after each 1000 rows which is supposed to slow it down a bit. All in all I cannot see any visible speedup, though it doesn't appear to be any slower either. I must say that the process of switching from file to file using the same transform is a bit cumbersome. You have a source object and a destination object, and then a transform object. The transform defines all these properties such as buffer size, table / row locks, commit after N rows etc. What makes no sense to me however is that it ALSO defines the source, i.e. the NAME of the table is also embedded in the transform object. This just makes no sense to me since the transform operates on a source (thus already defined) and a destination. The upshot is that in order to move from one text file to the next using the same setup (transform) I have to open the source object and change the file name there, then open the transform object and change the source file there. No big deal except that doing the change in the transform object then prompts for something like "specify which transform to delete", very confusing. The upshot of all this is that I do now have more control than using the simple wizard, however it is more of a PITA. This may be mitigated by being able to simply edit the transform package in two places (the source object table and the transform object source property) instead of running through the entire wizard again. I may also be able to get around the locking issue by going back to the row level locking, but commit after every 1000 rows. This might allow me to queue up 4 or 5 of these and let them run so I am not baby sitting this thing all day. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Martin Reid Sent: Thursday, August 10, 2006 9:12 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging John Look up Insert Commit Size re DTS Soorry my server is down at the moment so cant check it for you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of JWColby Sent: Thu 10/08/2006 13:42 To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging >using DTS, you can adjust the "commit after # rows" level. Is this possible using the DTS wizard? I am not able to find this property anywhere and of course the help doesn't. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Wednesday, August 09, 2006 5:19 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging Assuming that you are importing the data using DTS, you can adjust the "commit after # rows" level. Cut it back to say 100 or 1000 rows and then see what is happening. ----- Original Message ---- From: Martin Reid To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, August 9, 2006 4:04:10 PM Subject: Re: [dba-SQLServer] SQL Server hanging John Try and run a trace on the server and database your importing to. Open SQL Proflier -> File -> New->Trace See what that shows you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 _______________________________________________ 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 artful at rogers.com Thu Aug 10 09:34:16 2006 From: artful at rogers.com (artful at rogers.com) Date: Thu, 10 Aug 2006 07:34:16 -0700 (PDT) Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: <005901c6bc7f$18890820$657aa8c0@m6805> Message-ID: <20060810143416.32758.qmail@web88202.mail.re2.yahoo.com> For future reference, it's in the wizard on the last page, Options. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Thursday, August 10, 2006 9:15:47 AM Subject: Re: [dba-SQLServer] SQL Server hanging Never mind, I just found the DTS editor, which is exactly what I needed. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Thursday, August 10, 2006 8:43 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging >using DTS, you can adjust the "commit after # rows" level. Is this possible using the DTS wizard? I am not able to find this property anywhere and of course the help doesn't. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Wednesday, August 09, 2006 5:19 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging Assuming that you are importing the data using DTS, you can adjust the "commit after # rows" level. Cut it back to say 100 or 1000 rows and then see what is happening. ----- Original Message ---- From: Martin Reid To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, August 9, 2006 4:04:10 PM Subject: Re: [dba-SQLServer] SQL Server hanging John Try and run a trace on the server and database your importing to. Open SQL Proflier -> File -> New->Trace See what that shows you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 _______________________________________________ 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 James at fcidms.com Thu Aug 10 10:00:35 2006 From: James at fcidms.com (James Barash) Date: Thu, 10 Aug 2006 11:00:35 -0400 Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: <005f01c6bc86$1abcd3e0$657aa8c0@m6805> Message-ID: <005401c6bc8d$bc551120$800101df@fci.local> John, Here is an exaple of a dts package that loops through all the files in a directory and imports them by dynamically changing the source object. It's a bit hard to understand at first but I've used it as a starting point for doing something very similar to what you're doing now. http://www.sqldts.com/default.aspx?246 It's written for SQL Server 2000. If you are using 2005, it is much easier to create an SSIS package that does the same thing since looping is written into the dtsx object set. Hope this helps James Barash -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Thursday, August 10, 2006 10:06 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging It doesn't appear that it is possible to do this via the wizard, or at least I can't see how. However under data transformation / local packages / right click / New package you can get at the designer which does allow all of this stuff. I have been doing more than one transform (several different files) from the simple wizard. Under normal circumstances, the second and subsequent transforms wait for the first to finish. However, and I have not determined how or why, sometimes the second or third or fourth transform that I define will start executing as well. Sometimes all of them at once!!! When that happens of course, things slow down a LOT. I could never tell if the slow down was linear or not. Unfortunately, I also started getting "unable to obtain lock" failures when this happens. Of course the error messages don't make clear whether the locks are database licks or file system locks. I suspect that it is db (row) locks. I thought perhaps the designer would give enough more control that it would significantly speed up the imports. I set the properties to use a table lock which it seems would speed things up. I also set it up to read 1000 records (lines, or at least so I think) into the source buffer from the source text file instead of one line at a time, thinking that this too might speed things up. I did however ask it to commit after each 1000 rows which is supposed to slow it down a bit. All in all I cannot see any visible speedup, though it doesn't appear to be any slower either. I must say that the process of switching from file to file using the same transform is a bit cumbersome. You have a source object and a destination object, and then a transform object. The transform defines all these properties such as buffer size, table / row locks, commit after N rows etc. What makes no sense to me however is that it ALSO defines the source, i.e. the NAME of the table is also embedded in the transform object. This just makes no sense to me since the transform operates on a source (thus already defined) and a destination. The upshot is that in order to move from one text file to the next using the same setup (transform) I have to open the source object and change the file name there, then open the transform object and change the source file there. No big deal except that doing the change in the transform object then prompts for something like "specify which transform to delete", very confusing. The upshot of all this is that I do now have more control than using the simple wizard, however it is more of a PITA. This may be mitigated by being able to simply edit the transform package in two places (the source object table and the transform object source property) instead of running through the entire wizard again. I may also be able to get around the locking issue by going back to the row level locking, but commit after every 1000 rows. This might allow me to queue up 4 or 5 of these and let them run so I am not baby sitting this thing all day. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Martin Reid Sent: Thursday, August 10, 2006 9:12 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging John Look up Insert Commit Size re DTS Soorry my server is down at the moment so cant check it for you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of JWColby Sent: Thu 10/08/2006 13:42 To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging >using DTS, you can adjust the "commit after # rows" level. Is this possible using the DTS wizard? I am not able to find this property anywhere and of course the help doesn't. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Wednesday, August 09, 2006 5:19 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging Assuming that you are importing the data using DTS, you can adjust the "commit after # rows" level. Cut it back to say 100 or 1000 rows and then see what is happening. ----- Original Message ---- From: Martin Reid To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, August 9, 2006 4:04:10 PM Subject: Re: [dba-SQLServer] SQL Server hanging John Try and run a trace on the server and database your importing to. Open SQL Proflier -> File -> New->Trace See what that shows you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 _______________________________________________ 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 artful at rogers.com Thu Aug 10 10:03:23 2006 From: artful at rogers.com (artful at rogers.com) Date: Thu, 10 Aug 2006 08:03:23 -0700 (PDT) Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: <005f01c6bc86$1abcd3e0$657aa8c0@m6805> Message-ID: <20060810150323.5540.qmail@web88206.mail.re2.yahoo.com> DTS Global variables might help solve your problem, JC. Look it up in BOL. The gist is that you can use a DTS global variable in place of an actual filename or even a PK. As an example of the latter, a while back I had need to copy all the rows from variables tables that were in a hierarchy, specifying the PK of the topmost table in the tree. IOW: T1.PK = 123 T2.FK = 123 T3.PK = all the rows where the FK = the T2.PKs returned from the previous step. I used to save the package, then clone it for each new T1.PK whose relational tree I needed. Then I discovered global variables, and was able to use the same package over and over, just by redefining the global variable. HTH, Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Thursday, August 10, 2006 10:05:57 AM Subject: Re: [dba-SQLServer] SQL Server hanging It doesn't appear that it is possible to do this via the wizard, or at least I can't see how. However under data transformation / local packages / right click / New package you can get at the designer which does allow all of this stuff. I have been doing more than one transform (several different files) from the simple wizard. Under normal circumstances, the second and subsequent transforms wait for the first to finish. However, and I have not determined how or why, sometimes the second or third or fourth transform that I define will start executing as well. Sometimes all of them at once!!! When that happens of course, things slow down a LOT. I could never tell if the slow down was linear or not. Unfortunately, I also started getting "unable to obtain lock" failures when this happens. Of course the error messages don't make clear whether the locks are database licks or file system locks. I suspect that it is db (row) locks. I thought perhaps the designer would give enough more control that it would significantly speed up the imports. I set the properties to use a table lock which it seems would speed things up. I also set it up to read 1000 records (lines, or at least so I think) into the source buffer from the source text file instead of one line at a time, thinking that this too might speed things up. I did however ask it to commit after each 1000 rows which is supposed to slow it down a bit. All in all I cannot see any visible speedup, though it doesn't appear to be any slower either. I must say that the process of switching from file to file using the same transform is a bit cumbersome. You have a source object and a destination object, and then a transform object. The transform defines all these properties such as buffer size, table / row locks, commit after N rows etc. What makes no sense to me however is that it ALSO defines the source, i.e. the NAME of the table is also embedded in the transform object. This just makes no sense to me since the transform operates on a source (thus already defined) and a destination. The upshot is that in order to move from one text file to the next using the same setup (transform) I have to open the source object and change the file name there, then open the transform object and change the source file there. No big deal except that doing the change in the transform object then prompts for something like "specify which transform to delete", very confusing. The upshot of all this is that I do now have more control than using the simple wizard, however it is more of a PITA. This may be mitigated by being able to simply edit the transform package in two places (the source object table and the transform object source property) instead of running through the entire wizard again. I may also be able to get around the locking issue by going back to the row level locking, but commit after every 1000 rows. This might allow me to queue up 4 or 5 of these and let them run so I am not baby sitting this thing all day. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Martin Reid Sent: Thursday, August 10, 2006 9:12 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging John Look up Insert Commit Size re DTS Soorry my server is down at the moment so cant check it for you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of JWColby Sent: Thu 10/08/2006 13:42 To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging >using DTS, you can adjust the "commit after # rows" level. Is this possible using the DTS wizard? I am not able to find this property anywhere and of course the help doesn't. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Wednesday, August 09, 2006 5:19 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging Assuming that you are importing the data using DTS, you can adjust the "commit after # rows" level. Cut it back to say 100 or 1000 rows and then see what is happening. ----- Original Message ---- From: Martin Reid To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, August 9, 2006 4:04:10 PM Subject: Re: [dba-SQLServer] SQL Server hanging John Try and run a trace on the server and database your importing to. Open SQL Proflier -> File -> New->Trace See what that shows you. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 _______________________________________________ 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 artful at rogers.com Thu Aug 10 11:45:34 2006 From: artful at rogers.com (artful at rogers.com) Date: Thu, 10 Aug 2006 09:45:34 -0700 (PDT) Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: <004901c6bc15$7ea27930$657aa8c0@m6805> Message-ID: <20060810164534.40494.qmail@web88212.mail.re2.yahoo.com> Use DCC SHRINKFILE or DBCC SHRINKDATABASE. Note that shrinking the log doesn't always do what you might excpect, since it is based on the size of the virtual logs. There is a good explanation of this (and how to get around it) in BOL under the topic "Shrinking the Transaction Log". HTH,. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, August 9, 2006 8:39:51 PM Subject: Re: [dba-SQLServer] SQL Server hanging It turns out it was just thinking. Unfortunately I am now totally confused on which files succeeded and which failed. Arthur, I do think that adjusting the number of records that are imported before a commit is a grand idea. I also need info on how to shrink the log file. As you might guess I am still muddling through this SQL Server thing. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Wednesday, August 09, 2006 3:52 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] SQL Server hanging Is there any way to tell what is going on with SQL Server when it hangs? I am trying to import these tens of millions of records into SQL Server. They are flat file comma delimited text files, 3 million recs / file. Everything is working fine, I have ~12 files imported (36 million records) and I am humming along. I have about 6 import processes running (import and export data manager) at once and of course things slow down but suddenly none of the imports is progressing at all. I try to connect with EM and when I try to expand the "databases" tree it gives an error connecting, "unable to obtain a lock" or some such. I let the import functions continue to run but 20 minutes later still not a single more record imported. So I use task manager to shut down all of the import processes, shut down EM, shut down the SQL Server manager normally, unload it, shut off the computer, restart it. Try to connect with enterprise manager and no go. In fact it APPEARS to be locked up. When I go in with task manager and look at the process, it is slowly gaining "memory used" until it basically runs out then starts increasing the page file size, until that hits about 1.7g and then that too stops incrementing but EM is still hung. CPU usage is now down about 2%, no "more" memory being grabbed by EM, the page file is static, but EM is hung. I need to find out what is going on here. I have about 12 of these 3 million record text files imported and don't want to have to clean it out and start over, but worse, I have no clue why it stopped working. Is there any (free) tool that will tell me what SQL Server thinks it is up to? If I can't get EM to see the databases I am basically hosed here. John W. Colby Colby Consulting www.ColbyConsulting.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 fhtapia at gmail.com Thu Aug 10 13:40:04 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Thu, 10 Aug 2006 11:40:04 -0700 Subject: [dba-SQLServer] SQL Server hanging In-Reply-To: <20060810164534.40494.qmail@web88212.mail.re2.yahoo.com> References: <004901c6bc15$7ea27930$657aa8c0@m6805> <20060810164534.40494.qmail@web88212.mail.re2.yahoo.com> Message-ID: excellent, I also use the following to shrink the log files BACKUP LOG DB_NAME WITH TRUNCATE_ONLY DBCC SHRINKFILE ('DB_NAME_LOG', 10) if you are unsure of what the database log filename is, do a "Select * From sysfiles" in the database where you need to shrink the log file. On 8/10/06, artful at rogers.com wrote: > > Use DCC SHRINKFILE or DBCC SHRINKDATABASE. Note that shrinking the log > doesn't always do what you might excpect, since it is based on the size of > the virtual logs. There is a good explanation of this (and how to get around > it) in BOL under the topic "Shrinking the Transaction Log". > > HTH,. > Arthur > > ----- Original Message ---- > From: JWColby > To: dba-sqlserver at databaseadvisors.com > Sent: Wednesday, August 9, 2006 8:39:51 PM > Subject: Re: [dba-SQLServer] SQL Server hanging > > It turns out it was just thinking. Unfortunately I am now totally > confused > on which files succeeded and which failed. > > Arthur, I do think that adjusting the number of records that are imported > before a commit is a grand idea. I also need info on how to shrink the > log > file. As you might guess I am still muddling through this SQL Server > thing. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby > Sent: Wednesday, August 09, 2006 3:52 PM > To: dba-sqlserver at databaseadvisors.com > Subject: [dba-SQLServer] SQL Server hanging > > Is there any way to tell what is going on with SQL Server when it hangs? > > I am trying to import these tens of millions of records into SQL Server. > They are flat file comma delimited text files, 3 million recs / file. > Everything is working fine, I have ~12 files imported (36 million records) > and I am humming along. I have about 6 import processes running (import > and > export data manager) at once and of course things slow down but suddenly > none of the imports is progressing at all. I try to connect with EM and > when I try to expand the "databases" tree it gives an error connecting, > "unable to obtain a lock" or some such. I let the import functions > continue > to run but 20 minutes later still not a single more record imported. So I > use task manager to shut down all of the import processes, shut down EM, > shut down the SQL Server manager normally, unload it, shut off the > computer, > restart it. Try to connect with enterprise manager and no go. In fact it > APPEARS to be locked up. When I go in with task manager and look at the > process, it is slowly gaining "memory used" until it basically runs out > then > starts increasing the page file size, until that hits about 1.7g and then > that too stops incrementing but EM is still hung. > > CPU usage is now down about 2%, no "more" memory being grabbed by EM, the > page file is static, but EM is hung. > > I need to find out what is going on here. I have about 12 of these 3 > million record text files imported and don't want to have to clean it out > and start over, but worse, I have no clue why it stopped working. Is > there > any (free) tool that will tell me what SQL Server thinks it is up to? If > I > can't get EM to see the databases I am basically hosed here. > > John W. Colby > Colby Consulting > www.ColbyConsulting.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 > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Thu Aug 10 17:49:47 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Thu, 10 Aug 2006 15:49:47 -0700 Subject: [dba-SQLServer] Reporting Services 2000, 2nd Y Axis Chart Message-ID: (sorry for the cross-post) I've been googling for the answer all yesterday afternoon, and today morning, but to no avail, I have a report that looks a bit like the following: Month, Fail, Installed 1/1/2000, 3, 300 2/1/2000, 1.5, 256 3/1/2000, 2.5, 280 ... ... The purpose it to graph the report with one of the series on a second y axis, then on this 2nd axis I'm supposed to generate a trend line. Any advice on this in Sql Server Reporting services (2000) would be much appreciated. Thanks, -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From michael at ddisolutions.com.au Thu Aug 10 23:27:11 2006 From: michael at ddisolutions.com.au (Michael Maddison) Date: Fri, 11 Aug 2006 14:27:11 +1000 Subject: [dba-SQLServer] SQL Server hanging Message-ID: <59A61174B1F5B54B97FD4ADDE71E7D0116A8F5@ddi-01.DDI.local> Also set the db to 'Simple' recovery model, drop all indexes, make sire the db + log files are big enough not to need auto-growing, turn off auto grow? You can also set the number of parallel tasks (need to experiment with this one), Set priority to high, turn off logging, maybe fiddle with the Transaction isolation level, chaos sounds good...lol As others have suggested use a global for the path changes. cheers Michael M -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Friday, 11 August 2006 4:40 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] SQL Server hanging excellent, I also use the following to shrink the log files BACKUP LOG DB_NAME WITH TRUNCATE_ONLY DBCC SHRINKFILE ('DB_NAME_LOG', 10) if you are unsure of what the database log filename is, do a "Select * >From sysfiles" in the database where you need to shrink the log file. On 8/10/06, artful at rogers.com wrote: > > Use DCC SHRINKFILE or DBCC SHRINKDATABASE. Note that shrinking the log > doesn't always do what you might excpect, since it is based on the > size of the virtual logs. There is a good explanation of this (and how > to get around > it) in BOL under the topic "Shrinking the Transaction Log". > > HTH,. > Arthur > > ----- Original Message ---- > From: JWColby > To: dba-sqlserver at databaseadvisors.com > Sent: Wednesday, August 9, 2006 8:39:51 PM > Subject: Re: [dba-SQLServer] SQL Server hanging > > It turns out it was just thinking. Unfortunately I am now totally > confused on which files succeeded and which failed. > > Arthur, I do think that adjusting the number of records that are > imported before a commit is a grand idea. I also need info on how to > shrink the log file. As you might guess I am still muddling through > this SQL Server thing. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > JWColby > Sent: Wednesday, August 09, 2006 3:52 PM > To: dba-sqlserver at databaseadvisors.com > Subject: [dba-SQLServer] SQL Server hanging > > Is there any way to tell what is going on with SQL Server when it hangs? > > I am trying to import these tens of millions of records into SQL Server. > They are flat file comma delimited text files, 3 million recs / file. > Everything is working fine, I have ~12 files imported (36 million > records) and I am humming along. I have about 6 import processes > running (import and export data manager) at once and of course things > slow down but suddenly none of the imports is progressing at all. I > try to connect with EM and when I try to expand the "databases" tree > it gives an error connecting, "unable to obtain a lock" or some such. > I let the import functions continue to run but 20 minutes later still > not a single more record imported. So I use task manager to shut down > all of the import processes, shut down EM, shut down the SQL Server > manager normally, unload it, shut off the computer, restart it. Try > to connect with enterprise manager and no go. In fact it APPEARS to > be locked up. When I go in with task manager and look at the process, > it is slowly gaining "memory used" until it basically runs out then > starts increasing the page file size, until that hits about 1.7g and > then that too stops incrementing but EM is still hung. > > CPU usage is now down about 2%, no "more" memory being grabbed by EM, > the page file is static, but EM is hung. > > I need to find out what is going on here. I have about 12 of these 3 > million record text files imported and don't want to have to clean it > out and start over, but worse, I have no clue why it stopped working. > Is there any (free) tool that will tell me what SQL Server thinks it > is up to? If I can't get EM to see the databases I am basically hosed > here. > > John W. Colby > Colby Consulting > www.ColbyConsulting.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 > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From askolits at ot.com Fri Aug 11 08:09:51 2006 From: askolits at ot.com (John Skolits) Date: Fri, 11 Aug 2006 09:09:51 -0400 Subject: [dba-SQLServer] Pass Thru syntax In-Reply-To: <44DA455A.8040702@shaw.ca> Message-ID: <000501c6bd47$71bb8440$6e01a8c0@LaptopXP> Haven't done this in a while. I have a pass thru query and need to know the syntax for running a stored procedure on SQLServer. If the SP is called SP_LoadData. I have Tried : EXEC SP_loadData Exec [dbo].[SP_LoadData} EXEC [databasename].[dbo].[Sp_LoadData] ... and many others. Thanks, John From artful at rogers.com Fri Aug 11 08:18:45 2006 From: artful at rogers.com (artful at rogers.com) Date: Fri, 11 Aug 2006 06:18:45 -0700 (PDT) Subject: [dba-SQLServer] SQL Express and SQL 2005 side by side In-Reply-To: <20060810164534.40494.qmail@web88212.mail.re2.yahoo.com> Message-ID: <20060811131845.86939.qmail@web88208.mail.re2.yahoo.com> Are there any known issues with installing these side by side? I have SQL 2005 installed (with SQL 2000) already. Would I have to remove SQL 2005 before installing Express? TIA, Arthur From tuxedoman888 at gmail.com Fri Aug 11 11:17:23 2006 From: tuxedoman888 at gmail.com (Billy Pang) Date: Fri, 11 Aug 2006 09:17:23 -0700 Subject: [dba-SQLServer] Pass Thru syntax In-Reply-To: <000501c6bd47$71bb8440$6e01a8c0@LaptopXP> References: <44DA455A.8040702@shaw.ca> <000501c6bd47$71bb8440$6e01a8c0@LaptopXP> Message-ID: <7c8826480608110917k3852f3d8mfc8fd1eb411dc4d9@mail.gmail.com> exec usp_hello @test='my value' the above works for me. are you getting an error message? On 8/11/06, John Skolits wrote: > > Haven't done this in a while. > > I have a pass thru query and need to know the syntax for running a stored > procedure on SQLServer. > > > If the SP is called SP_LoadData. > > I have Tried : > > EXEC SP_loadData > Exec [dbo].[SP_LoadData} > EXEC [databasename].[dbo].[Sp_LoadData] > > ... > > and many others. > > Thanks, > > John > > > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- Billy Pang http://dbnotes.blogspot.com/ "Once the game is over, the King and the pawn go back in the same box." - Italian proverb From jim.moss at jlmoss.net Fri Aug 11 11:09:00 2006 From: jim.moss at jlmoss.net (Jim Moss) Date: Fri, 11 Aug 2006 11:09:00 -0500 (CDT) Subject: [dba-SQLServer] Pass Thru syntax In-Reply-To: <000501c6bd47$71bb8440$6e01a8c0@LaptopXP> References: <44DA455A.8040702@shaw.ca> <000501c6bd47$71bb8440$6e01a8c0@LaptopXP> Message-ID: <50648.65.196.182.34.1155312540.squirrel@65.196.182.34> John, I use the EXEC SP_loadData format and it works just fine. Just make sure that you are using a SQL Specific Pass-Through query and that you have your ODBC and other properties set. > Haven't done this in a while. > > I have a pass thru query and need to know the syntax for running a stored > procedure on SQLServer. > > > If the SP is called SP_LoadData. > > I have Tried : > > EXEC SP_loadData > Exec [dbo].[SP_LoadData} > EXEC [databasename].[dbo].[Sp_LoadData] > > ... > > and many others. > > Thanks, > > John > > > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > From askolits at ot.com Fri Aug 11 12:03:13 2006 From: askolits at ot.com (John Skolits) Date: Fri, 11 Aug 2006 13:03:13 -0400 Subject: [dba-SQLServer] Pass Thru syntax In-Reply-To: <50648.65.196.182.34.1155312540.squirrel@65.196.182.34> Message-ID: <003401c6bd68$0ae276e0$6e01a8c0@LaptopXP> I got it. Turned out to be the connect string was wrong. What a goof! Thanks Jim and Billy -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Moss Sent: Friday, August 11, 2006 12:09 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Pass Thru syntax John, I use the EXEC SP_loadData format and it works just fine. Just make sure that you are using a SQL Specific Pass-Through query and that you have your ODBC and other properties set. > Haven't done this in a while. > > I have a pass thru query and need to know the syntax for running a stored > procedure on SQLServer. > > > If the SP is called SP_LoadData. > > I have Tried : > > EXEC SP_loadData > Exec [dbo].[SP_LoadData} > EXEC [databasename].[dbo].[Sp_LoadData] > > ... > > and many others. > > Thanks, > > John > > > > > > _______________________________________________ > 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 Fri Aug 11 15:30:49 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Fri, 11 Aug 2006 16:30:49 -0400 Subject: [dba-SQLServer] Specifying index file In-Reply-To: <59A61174B1F5B54B97FD4ADDE71E7D0116A8F5@ddi-01.DDI.local> Message-ID: <00ad01c6bd85$0a9ed800$657aa8c0@m6805> Is it possible to specify the file that indexes go into to spread out the processing load on the disk drives? IOW I have 4 drives of 250gb each. 3 of them have data files that are approaching 100gb. The fourth is only used for the log file which so far is smallish since I am mostly doing bulk inserts so far. I do now need to build some additional fields and add indexes on those fields. Can I specify that the indexes go into a given file on a given drive? Or does SQL Server just put the index right in the data files? John W. Colby Colby Consulting www.ColbyConsulting.com From jwcolby at colbyconsulting.com Fri Aug 11 15:38:28 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Fri, 11 Aug 2006 16:38:28 -0400 Subject: [dba-SQLServer] Update query leaves null In-Reply-To: <59A61174B1F5B54B97FD4ADDE71E7D0116A8F5@ddi-01.DDI.local> Message-ID: <00ae01c6bd86$1b7aae50$657aa8c0@m6805> I need to build a new field on a table, and insert the first N characters of Y other fields into that new field. This will be known as a match code and it is an accepted and known method in the client's industry of weeding out duplicates. For example I need to create a new string with the first 5 characters of the first name, last name, address1, address2, zip and the plus4. I will write this new string back into a new field. What I want to do is to build a unique index on the field. Then as the update occurs, I need a silent failure if the match code already exists. Thus if the same exact match code is already in the table, just leave a null of empty string in that match field for the duplicate record. Doing this would allow me to then go back and delete the records where the match code is null and "de-dupe" the table. If I do an update query in SQL, will it do this silent failure or will it stop and announce the failure? Do I need to do something specific to get a "silent failure"? John W. Colby Colby Consulting www.ColbyConsulting.com From fhtapia at gmail.com Fri Aug 11 18:01:53 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Fri, 11 Aug 2006 16:01:53 -0700 Subject: [dba-SQLServer] Creating a Manual TrendLine Message-ID: After much re-search I found that I could "NOT" easily just create a trend line in Sql Server Reporting Services (2000). Therefore I need to manually create the data for a TrendLine. Question is, Does anyone know how? My Data looks like this: (object is to trend the Failure rate) Month, Installs, Fails, Trend 01/00, 200, 1.5, ? 01/00, 278, 1.0, ? 01/00, 325, .9, ? ... ...etc Thanks, -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From martyconnelly at shaw.ca Sat Aug 12 14:10:14 2006 From: martyconnelly at shaw.ca (MartyConnelly) Date: Sat, 12 Aug 2006 12:10:14 -0700 Subject: [dba-SQLServer] Creating a Manual TrendLine In-Reply-To: References: Message-ID: <44DE2796.8000509@shaw.ca> There are a lot of equations you can use to curve fit a trendline But sticking with say something simple, say a moving average. Here are two examples from Joe Celko's book SQL for Smarties You can find other examples here. Usually a moving average is calculated over a fixed period of time (i.e. last five days, last two batches, etc.) SELECT B2.mydate, AVG(B1.lData) AS moving_avg_wgt FROM Table1 AS B1, Table1 AS B2 WHERE B1.mydate BETWEEN B2.mydate AND (B2.mydate - 5) GROUP BY B2.mydate; or if you do not like the scalar subquery expression: SELECT mydate, (SELECT AVG(ldata) FROM Table1 AS B1 WHERE B1.mydate BETWEEN B2.mydate AND B2.mydate - 1) AS moving_avg_wgt FROM Table1 AS B2; ID lData mydate 1 10 01/01/2006 2 20 02/01/2006 3 40 03/01/2006 4 390 04/01/2006 5 50 05/01/2006 6 30 02/01/2006 Table1 ID lData mydate 1 10 01/01/2006 2 20 02/01/2006 3 40 03/01/2006 4 390 04/01/2006 5 50 05/01/2006 6 30 02/01/2006 Francisco Tapia wrote: >After much re-search I found that I could "NOT" easily just create a >trend line in Sql Server Reporting Services (2000). Therefore I need >to manually create the data for a TrendLine. Question is, Does anyone >know how? > >My Data looks like this: (object is to trend the Failure rate) > >Month, Installs, Fails, Trend >01/00, 200, 1.5, ? >01/00, 278, 1.0, ? >01/00, 325, .9, ? >... >...etc > >Thanks, > > > > > -- Marty Connelly Victoria, B.C. Canada From rl_stewart at highstream.net Sat Aug 12 21:53:27 2006 From: rl_stewart at highstream.net (Robert L. Stewart) Date: Sat, 12 Aug 2006 22:53:27 -0400 Subject: [dba-SQLServer] Specifying index file In-Reply-To: References: Message-ID: <6.2.3.4.2.20060812225233.0216d840@pop3.highstream.net> John, Check out file groups. You can specify one for indexes. Robert At 01:00 PM 8/12/2006, you wrote: >Date: Fri, 11 Aug 2006 16:30:49 -0400 >From: "JWColby" >Subject: [dba-SQLServer] Specifying index file >To: >Message-ID: <00ad01c6bd85$0a9ed800$657aa8c0 at m6805> >Content-Type: text/plain; charset="us-ascii" > >Is it possible to specify the file that indexes go into to spread out the >processing load on the disk drives? IOW I have 4 drives of 250gb each. 3 >of them have data files that are approaching 100gb. The fourth is only used >for the log file which so far is smallish since I am mostly doing bulk >inserts so far. I do now need to build some additional fields and add >indexes on those fields. Can I specify that the indexes go into a given >file on a given drive? Or does SQL Server just put the index right in the >data files? > > >John W. Colby >Colby Consulting >www.ColbyConsulting.com From andrew.haslett at ilc.gov.au Mon Aug 14 04:32:19 2006 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Mon, 14 Aug 2006 19:02:19 +0930 Subject: [dba-SQLServer] Update query leaves null Message-ID: <0A870603A2A816459078203FC07F4CD2BE3FB3@adl01s055.ilcorp.gov.au> Why not just build a unique index / constraint on the existing 4 fields? This will prevent duplicates from being created at all... -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Saturday, 12 August 2006 6:08 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Update query leaves null I need to build a new field on a table, and insert the first N characters of Y other fields into that new field. This will be known as a match code and it is an accepted and known method in the client's industry of weeding out duplicates. For example I need to create a new string with the first 5 characters of the first name, last name, address1, address2, zip and the plus4. I will write this new string back into a new field. What I want to do is to build a unique index on the field. Then as the update occurs, I need a silent failure if the match code already exists. Thus if the same exact match code is already in the table, just leave a null of empty string in that match field for the duplicate record. Doing this would allow me to then go back and delete the records where the match code is null and "de-dupe" the table. If I do an update query in SQL, will it do this silent failure or will it stop and announce the failure? Do I need to do something specific to get a "silent failure"? John W. Colby Colby Consulting www.ColbyConsulting.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 artful at rogers.com Mon Aug 14 07:50:13 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 14 Aug 2006 05:50:13 -0700 (PDT) Subject: [dba-SQLServer] Update query leaves null In-Reply-To: <0A870603A2A816459078203FC07F4CD2BE3FB3@adl01s055.ilcorp.gov.au> Message-ID: <20060814125013.21605.qmail@web88209.mail.re2.yahoo.com> To this I would add, why use a physical column at all? Why not define a calculated column and then index it? That would be a much more efficient way of doing what you want, I think. Arthur ----- Original Message ---- From: "Haslett, Andrew" To: dba-sqlserver at databaseadvisors.com Sent: Monday, August 14, 2006 5:32:19 AM Subject: Re: [dba-SQLServer] Update query leaves null Why not just build a unique index / constraint on the existing 4 fields? This will prevent duplicates from being created at all... -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Saturday, 12 August 2006 6:08 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Update query leaves null I need to build a new field on a table, and insert the first N characters of Y other fields into that new field. This will be known as a match code and it is an accepted and known method in the client's industry of weeding out duplicates. For example I need to create a new string with the first 5 characters of the first name, last name, address1, address2, zip and the plus4. I will write this new string back into a new field. What I want to do is to build a unique index on the field. Then as the update occurs, I need a silent failure if the match code already exists. Thus if the same exact match code is already in the table, just leave a null of empty string in that match field for the duplicate record. Doing this would allow me to then go back and delete the records where the match code is null and "de-dupe" the table. If I do an update query in SQL, will it do this silent failure or will it stop and announce the failure? Do I need to do something specific to get a "silent failure"? John W. Colby Colby Consulting www.ColbyConsulting.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 jwcolby at colbyconsulting.com Mon Aug 14 08:37:26 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 14 Aug 2006 09:37:26 -0400 Subject: [dba-SQLServer] Update query leaves null In-Reply-To: <0A870603A2A816459078203FC07F4CD2BE3FB3@adl01s055.ilcorp.gov.au> Message-ID: <001b01c6bfa6$c950a620$657aa8c0@m6805> Unfortunately this is one of those conventions that the client understands and wants. It all has to do with the fact that data is pulled in from dozens of surveys. The person taking the survey may (for example) write his address as 1723 Twin Pines Drive on one survey, 1723 Twin Pines Dr on the next, 1723 Twin Pines Dr. on the next. All three are different and a unique index does not help. OTOH, if you take the first 5 characters of all of those you end up with 1723^ where ^ is a space character. ALL of the various means of spelling the address would end up with the same first N characters (unless misspelled). All addresses will be run through a CASS process that ensures that the address is deliverable. Approximately 11% of all my records drop out there for address error issues. The client WANTS a single field that they can compare to the same field in any other table of addresses - the first 5 characters of each of the address fields, then that with the first 5 characters of the last name (to get down to a "family") and then the first 5 characters of the first name added to that to get down to the individual. There are just times when a client (and their industry) does something in a specific way and it is useless to try to get them to change. It isn't the CLIENT that needs to change, it is the INDUSTRY and I don't have the time to fight THAT battle! John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 14, 2006 5:32 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null Why not just build a unique index / constraint on the existing 4 fields? This will prevent duplicates from being created at all... -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Saturday, 12 August 2006 6:08 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Update query leaves null I need to build a new field on a table, and insert the first N characters of Y other fields into that new field. This will be known as a match code and it is an accepted and known method in the client's industry of weeding out duplicates. For example I need to create a new string with the first 5 characters of the first name, last name, address1, address2, zip and the plus4. I will write this new string back into a new field. What I want to do is to build a unique index on the field. Then as the update occurs, I need a silent failure if the match code already exists. Thus if the same exact match code is already in the table, just leave a null of empty string in that match field for the duplicate record. Doing this would allow me to then go back and delete the records where the match code is null and "de-dupe" the table. If I do an update query in SQL, will it do this silent failure or will it stop and announce the failure? Do I need to do something specific to get a "silent failure"? John W. Colby Colby Consulting www.ColbyConsulting.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 artful at rogers.com Mon Aug 14 10:47:49 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 14 Aug 2006 08:47:49 -0700 (PDT) Subject: [dba-SQLServer] Installing SQL 2000 on a server that already has SQL 2003 In-Reply-To: <0J2B00MXRBBFYLE0@l-daemon> Message-ID: <20060814154749.24582.qmail@web88203.mail.re2.yahoo.com> What is SQL 2003? I've been in this game for a while and never heard of this product. ----- Original Message ---- From: Jim Lawrence To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, July 12, 2006 6:51:07 PM Subject: [dba-SQLServer] Installing SQL 2000 on a server that already has SQL 2003 Hi All: Installing MSSQL 2003 on a server already hosting MSSQL 2000 is a simple task. The installation routines asks how you wish to name the new SQL 2003 install so it does not conflict with the present MSSQL. I have not tried to install MSSQL 2000 on a box already hosting MSSQL 2003 and was wondering if anyone has done this process and if there are any issues to manage. MTIA Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From artful at rogers.com Mon Aug 14 10:59:53 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 14 Aug 2006 08:59:53 -0700 (PDT) Subject: [dba-SQLServer] Addresses in Europe and elsewhere In-Reply-To: <1152813145.44b688590a2c9@webmail.highstream.net> Message-ID: <20060814155953.46846.qmail@web88211.mail.re2.yahoo.com> I'm looking for some input from various regions around the world. I have the USA and Canada covered, but I need info from elsewhere. In North America, the usual form of a mailing address is: [StreetNumber] [StreetName] [Suffix] [City], [State/Province] [Postal Code] [Country] I know that in The Netherlands, the convention is to place the [StreetName] first, followed by the [StreetNumber]. By suffix, I meant such appendages as "Apt. #306". Then again, in various relatively rural parts of Spain, there are no street addresses. Here is an actual example of same: Brens-Cee <-- 5 towns on La Finisterra (NW corner of Spain) Fadibon <-- immediate town of interest La Corrunna <-- largest city in that part of Spain Spain <-- nation Arthur From accessd at shaw.ca Mon Aug 14 11:20:52 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Mon, 14 Aug 2006 09:20:52 -0700 Subject: [dba-SQLServer] Update query leaves null In-Reply-To: <001b01c6bfa6$c950a620$657aa8c0@m6805> Message-ID: <0J3Z005FLXE61C30@l-daemon> Hi John: Have you thought of using a soundex combination type index field solution? Padded from the right with zeros can group the data surprisingly accurate. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, August 14, 2006 6:37 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null Unfortunately this is one of those conventions that the client understands and wants. It all has to do with the fact that data is pulled in from dozens of surveys. The person taking the survey may (for example) write his address as 1723 Twin Pines Drive on one survey, 1723 Twin Pines Dr on the next, 1723 Twin Pines Dr. on the next. All three are different and a unique index does not help. OTOH, if you take the first 5 characters of all of those you end up with 1723^ where ^ is a space character. ALL of the various means of spelling the address would end up with the same first N characters (unless misspelled). All addresses will be run through a CASS process that ensures that the address is deliverable. Approximately 11% of all my records drop out there for address error issues. The client WANTS a single field that they can compare to the same field in any other table of addresses - the first 5 characters of each of the address fields, then that with the first 5 characters of the last name (to get down to a "family") and then the first 5 characters of the first name added to that to get down to the individual. There are just times when a client (and their industry) does something in a specific way and it is useless to try to get them to change. It isn't the CLIENT that needs to change, it is the INDUSTRY and I don't have the time to fight THAT battle! John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 14, 2006 5:32 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null Why not just build a unique index / constraint on the existing 4 fields? This will prevent duplicates from being created at all... -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Saturday, 12 August 2006 6:08 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Update query leaves null I need to build a new field on a table, and insert the first N characters of Y other fields into that new field. This will be known as a match code and it is an accepted and known method in the client's industry of weeding out duplicates. For example I need to create a new string with the first 5 characters of the first name, last name, address1, address2, zip and the plus4. I will write this new string back into a new field. What I want to do is to build a unique index on the field. Then as the update occurs, I need a silent failure if the match code already exists. Thus if the same exact match code is already in the table, just leave a null of empty string in that match field for the duplicate record. Doing this would allow me to then go back and delete the records where the match code is null and "de-dupe" the table. If I do an update query in SQL, will it do this silent failure or will it stop and announce the failure? Do I need to do something specific to get a "silent failure"? John W. Colby Colby Consulting www.ColbyConsulting.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 From accessd at shaw.ca Mon Aug 14 11:23:10 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Mon, 14 Aug 2006 09:23:10 -0700 Subject: [dba-SQLServer] Installing SQL 2000 on a server that already has SQL 2003 In-Reply-To: <20060814154749.24582.qmail@web88203.mail.re2.yahoo.com> Message-ID: <0J3Z005O9XI01C30@l-daemon> OK... late night, non-focused is my excuse and I am sticking to it. Jim PS The product is very similar to MSSQL 2005 -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Monday, August 14, 2006 8:48 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Installing SQL 2000 on a server that already has SQL 2003 What is SQL 2003? I've been in this game for a while and never heard of this product. ----- Original Message ---- From: Jim Lawrence To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, July 12, 2006 6:51:07 PM Subject: [dba-SQLServer] Installing SQL 2000 on a server that already has SQL 2003 Hi All: Installing MSSQL 2003 on a server already hosting MSSQL 2000 is a simple task. The installation routines asks how you wish to name the new SQL 2003 install so it does not conflict with the present MSSQL. I have not tried to install MSSQL 2000 on a box already hosting MSSQL 2003 and was wondering if anyone has done this process and if there are any issues to manage. MTIA 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 jwcolby at colbyconsulting.com Mon Aug 14 11:32:47 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 14 Aug 2006 12:32:47 -0400 Subject: [dba-SQLServer] Update query leaves null In-Reply-To: <20060814125013.21605.qmail@web88209.mail.re2.yahoo.com> Message-ID: <003101c6bfbf$49475c30$657aa8c0@m6805> What is a calculated column? If this is something "calculated" on the fly what would the speed be on a 50 million row table? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Monday, August 14, 2006 8:50 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null To this I would add, why use a physical column at all? Why not define a calculated column and then index it? That would be a much more efficient way of doing what you want, I think. Arthur ----- Original Message ---- From: "Haslett, Andrew" To: dba-sqlserver at databaseadvisors.com Sent: Monday, August 14, 2006 5:32:19 AM Subject: Re: [dba-SQLServer] Update query leaves null Why not just build a unique index / constraint on the existing 4 fields? This will prevent duplicates from being created at all... -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Saturday, 12 August 2006 6:08 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Update query leaves null I need to build a new field on a table, and insert the first N characters of Y other fields into that new field. This will be known as a match code and it is an accepted and known method in the client's industry of weeding out duplicates. For example I need to create a new string with the first 5 characters of the first name, last name, address1, address2, zip and the plus4. I will write this new string back into a new field. What I want to do is to build a unique index on the field. Then as the update occurs, I need a silent failure if the match code already exists. Thus if the same exact match code is already in the table, just leave a null of empty string in that match field for the duplicate record. Doing this would allow me to then go back and delete the records where the match code is null and "de-dupe" the table. If I do an update query in SQL, will it do this silent failure or will it stop and announce the failure? Do I need to do something specific to get a "silent failure"? John W. Colby Colby Consulting www.ColbyConsulting.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 From artful at rogers.com Mon Aug 14 11:45:45 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 14 Aug 2006 09:45:45 -0700 (PDT) Subject: [dba-SQLServer] Update query leaves null In-Reply-To: <003101c6bfbf$49475c30$657aa8c0@m6805> Message-ID: <20060814164545.37079.qmail@web88208.mail.re2.yahoo.com> A calculated column is a non-existent column, defined by a formula. For example, imagine a table with columns Qty, Price and Discount. A calculated column might have the formula Qty * Price * (1-Discount). This would of course require NOT NULL defintions for each column. The point is, said column virtually exists but does not physically exist. It is therefore indexable. There is no detectable speed hit (at least in my 50M sample tables). These columns are trivial to create. Inspect the property sheet for a column and you'll figure it out. A. ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Monday, August 14, 2006 12:32:47 PM Subject: Re: [dba-SQLServer] Update query leaves null What is a calculated column? If this is something "calculated" on the fly what would the speed be on a 50 million row table? John W. Colby Colby Consulting www.ColbyConsulting.com From jwcolby at colbyconsulting.com Mon Aug 14 11:57:48 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 14 Aug 2006 12:57:48 -0400 Subject: [dba-SQLServer] Update query leaves null In-Reply-To: <0J3Z005FLXE61C30@l-daemon> Message-ID: <003b01c6bfc2$c69a7610$657aa8c0@m6805> Tell me more. Just remember that this is a table with (ATM) 60 million records and will grow, so whatever it does can't be going out to lunch for the next week calculating something. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Monday, August 14, 2006 12:21 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null Hi John: Have you thought of using a soundex combination type index field solution? Padded from the right with zeros can group the data surprisingly accurate. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, August 14, 2006 6:37 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null Unfortunately this is one of those conventions that the client understands and wants. It all has to do with the fact that data is pulled in from dozens of surveys. The person taking the survey may (for example) write his address as 1723 Twin Pines Drive on one survey, 1723 Twin Pines Dr on the next, 1723 Twin Pines Dr. on the next. All three are different and a unique index does not help. OTOH, if you take the first 5 characters of all of those you end up with 1723^ where ^ is a space character. ALL of the various means of spelling the address would end up with the same first N characters (unless misspelled). All addresses will be run through a CASS process that ensures that the address is deliverable. Approximately 11% of all my records drop out there for address error issues. The client WANTS a single field that they can compare to the same field in any other table of addresses - the first 5 characters of each of the address fields, then that with the first 5 characters of the last name (to get down to a "family") and then the first 5 characters of the first name added to that to get down to the individual. There are just times when a client (and their industry) does something in a specific way and it is useless to try to get them to change. It isn't the CLIENT that needs to change, it is the INDUSTRY and I don't have the time to fight THAT battle! John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 14, 2006 5:32 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null Why not just build a unique index / constraint on the existing 4 fields? This will prevent duplicates from being created at all... -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Saturday, 12 August 2006 6:08 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Update query leaves null I need to build a new field on a table, and insert the first N characters of Y other fields into that new field. This will be known as a match code and it is an accepted and known method in the client's industry of weeding out duplicates. For example I need to create a new string with the first 5 characters of the first name, last name, address1, address2, zip and the plus4. I will write this new string back into a new field. What I want to do is to build a unique index on the field. Then as the update occurs, I need a silent failure if the match code already exists. Thus if the same exact match code is already in the table, just leave a null of empty string in that match field for the duplicate record. Doing this would allow me to then go back and delete the records where the match code is null and "de-dupe" the table. If I do an update query in SQL, will it do this silent failure or will it stop and announce the failure? Do I need to do something specific to get a "silent failure"? John W. Colby Colby Consulting www.ColbyConsulting.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 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From ggonzalez at cccis.com Mon Aug 14 12:04:34 2006 From: ggonzalez at cccis.com (ggonzalez at cccis.com) Date: Mon, 14 Aug 2006 12:04:34 -0500 Subject: [dba-SQLServer] Gumaro Gonzalez is out of the office. Message-ID: I will be out of the office starting 08/14/2006 and will not return until 08/21/2006. I will respond to your message when I return. From newsgrps at dalyn.co.nz Mon Aug 14 12:27:18 2006 From: newsgrps at dalyn.co.nz (David Emerson) Date: Tue, 15 Aug 2006 05:27:18 +1200 Subject: [dba-SQLServer] Addresses in Europe and elsewhere In-Reply-To: <20060814155953.46846.qmail@web88211.mail.re2.yahoo.com> References: <1152813145.44b688590a2c9@webmail.highstream.net> <20060814155953.46846.qmail@web88211.mail.re2.yahoo.com> Message-ID: <7.0.1.0.0.20060815052355.01acf340@dalyn.co.nz> Arthur, New Zealand is as follows [Suffix], [StreetNumber] [StreetName] [Suburb] [City] [Postal Code] [Country] Regards David At 15/08/2006, you wrote: >I'm looking for some input from various regions around the world. I >have the USA and Canada covered, but I need info from elsewhere. In >North America, the usual form of a mailing address is: > > > [StreetNumber] [StreetName] [Suffix] > [City], [State/Province] > [Postal Code] > [Country] > > >I know that in The Netherlands, the convention is to place the >[StreetName] first, followed by the [StreetNumber]. By suffix, I >meant such appendages as "Apt. #306". Then again, in various >relatively rural parts of Spain, there are no street addresses. Here >is an actual example of same: > >Brens-Cee <-- 5 towns on La Finisterra (NW corner of Spain) >Fadibon <-- immediate town of interest >La Corrunna <-- largest city in that part of Spain >Spain <-- nation > >Arthur > > >_______________________________________________ >dba-SQLServer mailing list >dba-SQLServer at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/dba-sqlserver >http://www.databaseadvisors.com From artful at rogers.com Mon Aug 14 12:31:37 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 14 Aug 2006 10:31:37 -0700 (PDT) Subject: [dba-SQLServer] Update query leaves null In-Reply-To: <003b01c6bfc2$c69a7610$657aa8c0@m6805> Message-ID: <20060814173137.64177.qmail@web88203.mail.re2.yahoo.com> A calculated column derives its value when the row is added. If the column is indexed, the index derives its value when the row is added or updated. A calculated column MUST derive its contents from the row of interest. A trivial example: CREATE TABLE dbo.CalcExample_tbl ( PK int identity(1,1) Column1 varchar(20) NOT NULL, Column2 varchar(20) NOT NULL, CalcColumn AS Left(Column1,5)+Left(Column2,5) ) Now you can index CalcColumn as if it physically existed. The further point is that the index holds the already-calculated values and only has to add new rows' values or update old rows' values, so there is no overhead other than what you might expect in a similar situation with a physical column. (That is, there is overhead, but not an extra and inordinate amount.) Net net, you store the formula once and the column once (in the index, not the table). Having created this table, add two rows: 1JohnColbyJohnColby2ArthurFullerArthuFulle Note that the calc column subtracted the sixth letter from my given name and surname, while yours survived intact. Hth, Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Monday, August 14, 2006 12:57:48 PM Subject: Re: [dba-SQLServer] Update query leaves null Tell me more. Just remember that this is a table with (ATM) 60 million records and will grow, so whatever it does can't be going out to lunch for the next week calculating something. John W. Colby Colby Consulting www.ColbyConsulting.com From accessd at shaw.ca Mon Aug 14 12:46:18 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Mon, 14 Aug 2006 10:46:18 -0700 Subject: [dba-SQLServer] Update query leaves null In-Reply-To: <003b01c6bfc2$c69a7610$657aa8c0@m6805> Message-ID: <0J4000J381CKN2I0@l-daemon> Hi John: With the latest fuzzy match Soundex algorithm (enhanced version...US census uses it.) it will translate a field of data into a simplified number. See http://en.wikipedia.org/wiki/Soundex and http://www.creativyst.com/Doc/Articles/SoundEx1/SoundEx1.htm for details and access to code samples. (I have one around here somewhere and will send a copy when found...) Example: Twin Pines Drive, Twin Pines Dr and Twin Pines Dr. would resolve to index T515 which I believe is what you are looking for. The Soundex field would have to be created and populated after the 60 million odd rows have been imported... post process. And the address number will have to be managed; maybe as a separate field. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, August 14, 2006 9:58 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null Tell me more. Just remember that this is a table with (ATM) 60 million records and will grow, so whatever it does can't be going out to lunch for the next week calculating something. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Monday, August 14, 2006 12:21 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null Hi John: Have you thought of using a soundex combination type index field solution? Padded from the right with zeros can group the data surprisingly accurate. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, August 14, 2006 6:37 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null Unfortunately this is one of those conventions that the client understands and wants. It all has to do with the fact that data is pulled in from dozens of surveys. The person taking the survey may (for example) write his address as 1723 Twin Pines Drive on one survey, 1723 Twin Pines Dr on the next, 1723 Twin Pines Dr. on the next. All three are different and a unique index does not help. OTOH, if you take the first 5 characters of all of those you end up with 1723^ where ^ is a space character. ALL of the various means of spelling the address would end up with the same first N characters (unless misspelled). All addresses will be run through a CASS process that ensures that the address is deliverable. Approximately 11% of all my records drop out there for address error issues. The client WANTS a single field that they can compare to the same field in any other table of addresses - the first 5 characters of each of the address fields, then that with the first 5 characters of the last name (to get down to a "family") and then the first 5 characters of the first name added to that to get down to the individual. There are just times when a client (and their industry) does something in a specific way and it is useless to try to get them to change. It isn't the CLIENT that needs to change, it is the INDUSTRY and I don't have the time to fight THAT battle! John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 14, 2006 5:32 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Update query leaves null Why not just build a unique index / constraint on the existing 4 fields? This will prevent duplicates from being created at all... -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Saturday, 12 August 2006 6:08 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Update query leaves null I need to build a new field on a table, and insert the first N characters of Y other fields into that new field. This will be known as a match code and it is an accepted and known method in the client's industry of weeding out duplicates. For example I need to create a new string with the first 5 characters of the first name, last name, address1, address2, zip and the plus4. I will write this new string back into a new field. What I want to do is to build a unique index on the field. Then as the update occurs, I need a silent failure if the match code already exists. Thus if the same exact match code is already in the table, just leave a null of empty string in that match field for the duplicate record. Doing this would allow me to then go back and delete the records where the match code is null and "de-dupe" the table. If I do an update query in SQL, will it do this silent failure or will it stop and announce the failure? Do I need to do something specific to get a "silent failure"? John W. Colby Colby Consulting www.ColbyConsulting.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 _______________________________________________ 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 artful at rogers.com Mon Aug 14 13:08:39 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 14 Aug 2006 11:08:39 -0700 (PDT) Subject: [dba-SQLServer] Addresses in Europe and elsewhere In-Reply-To: <7.0.1.0.0.20060815052355.01acf340@dalyn.co.nz> Message-ID: <20060814180839.82405.qmail@web88212.mail.re2.yahoo.com> That's interesting! Can you supply a concrete (if fictional) example? I'm guessing that you mean: Apt. 103, 34567 Minor Street MaoriTurf Awkland 34567 NZ Would that be about right? Due to my geographical ignorance, I'm surprised that the suburb is mentioned. Wouldn't one deduce that from the postal code? Thanks for the input, Arthur ----- Original Message ---- From: David Emerson To: dba-sqlserver at databaseadvisors.com Sent: Monday, August 14, 2006 1:27:18 PM Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere Arthur, New Zealand is as follows [Suffix], [StreetNumber] [StreetName] [Suburb] [City] [Postal Code] [Country] Regards David From martyconnelly at shaw.ca Mon Aug 14 13:08:33 2006 From: martyconnelly at shaw.ca (MartyConnelly) Date: Mon, 14 Aug 2006 11:08:33 -0700 Subject: [dba-SQLServer] Addresses in Europe and elsewhere In-Reply-To: <20060814155953.46846.qmail@web88211.mail.re2.yahoo.com> References: <20060814155953.46846.qmail@web88211.mail.re2.yahoo.com> Message-ID: <44E0BC21.5040808@shaw.ca> Two things to consider: the foriegn clients will probably know the correct formatting for their local address, and will this local format get you out of the USPS without a problem. So you may want to keep this format and your own broken down by elements of the address. There are commercial address cleaning firms if you have a large volume. First stop FRANK'S COMPULSIVE GUIDE TO POSTAL ADDRESSES Effective Addressing for International Mail http://www.columbia.edu/kermit/postal.html Postal Codes and IPU or UPU I can't remember why this was changed from International Postal Union to Universal http://www.upu.int/index.html http://www.embassyworld.com/data/Zip_Codes.html artful at rogers.com wrote: >I'm looking for some input from various regions around the world. I have the USA and Canada covered, but I need info from elsewhere. In North America, the usual form of a mailing address is: > > > [StreetNumber] [StreetName] [Suffix] > [City], [State/Province] > [Postal Code] > [Country] > > >I know that in The Netherlands, the convention is to place the [StreetName] first, followed by the [StreetNumber]. By suffix, I meant such appendages as "Apt. #306". Then again, in various relatively rural parts of Spain, there are no street addresses. Here is an actual example of same: > >Brens-Cee <-- 5 towns on La Finisterra (NW corner of Spain) >Fadibon <-- immediate town of interest >La Corrunna <-- largest city in that part of Spain >Spain <-- nation > >Arthur > > > > -- Marty Connelly Victoria, B.C. Canada From artful at rogers.com Mon Aug 14 13:10:53 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 14 Aug 2006 11:10:53 -0700 (PDT) Subject: [dba-SQLServer] Update query leaves null In-Reply-To: <0J4000J381CKN2I0@l-daemon> Message-ID: <20060814181053.32790.qmail@web88204.mail.re2.yahoo.com> Wow! I MUST check into this! Thanks for the heads up! But I think that this can still be done in SQL 2000+ using a calculated column. I shall begin my experiments and let y'all know wha 'appen. Arthur ----- Original Message ---- From: Jim Lawrence To: dba-sqlserver at databaseadvisors.com Sent: Monday, August 14, 2006 1:46:18 PM Subject: Re: [dba-SQLServer] Update query leaves null Hi John: With the latest fuzzy match Soundex algorithm (enhanced version...US census uses it.) it will translate a field of data into a simplified number. See http://en.wikipedia.org/wiki/Soundex and http://www.creativyst.com/Doc/Articles/SoundEx1/SoundEx1.htm for details and access to code samples. (I have one around here somewhere and will send a copy when found...) Example: Twin Pines Drive, Twin Pines Dr and Twin Pines Dr. would resolve to index T515 which I believe is what you are looking for. The Soundex field would have to be created and populated after the 60 million odd rows have been imported... post process. And the address number will have to be managed; maybe as a separate field. Jim From martyconnelly at shaw.ca Mon Aug 14 13:22:30 2006 From: martyconnelly at shaw.ca (MartyConnelly) Date: Mon, 14 Aug 2006 11:22:30 -0700 Subject: [dba-SQLServer] Installing SQL 2000 on a server that already has SQL 2003 In-Reply-To: <0J3Z005O9XI01C30@l-daemon> References: <0J3Z005O9XI01C30@l-daemon> Message-ID: <44E0BF66.2080502@shaw.ca> You might want to check if the SQL-SMO (2005) SQL-DMO (2000) contretemp has been resolved, at one time both could not exist on the same machine. It would then mess up EM. But this may only occur if you also install SQL Express. I haven't looked to see if it is all resolved and for what versions. There are re-registration fixes. http://blogs.msdn.com/sqlexpress/archive/2004/07/04/172956.aspx Jim Lawrence wrote: >OK... late night, non-focused is my excuse and I am sticking to it. > >Jim > >PS The product is very similar to MSSQL 2005 > >-----Original Message----- >From: dba-sqlserver-bounces at databaseadvisors.com >[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of >artful at rogers.com >Sent: Monday, August 14, 2006 8:48 AM >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] Installing SQL 2000 on a server that already >has SQL 2003 > >What is SQL 2003? I've been in this game for a while and never heard of this >product. > >----- Original Message ---- >From: Jim Lawrence >To: dba-sqlserver at databaseadvisors.com >Sent: Wednesday, July 12, 2006 6:51:07 PM >Subject: [dba-SQLServer] Installing SQL 2000 on a server that already has >SQL 2003 > >Hi All: > >Installing MSSQL 2003 on a server already hosting MSSQL 2000 is a simple >task. The installation routines asks how you wish to name the new SQL 2003 >install so it does not conflict with the present MSSQL. > >I have not tried to install MSSQL 2000 on a box already hosting MSSQL 2003 >and was wondering if anyone has done this process and if there are any >issues to manage. > >MTIA >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 > > > > > -- Marty Connelly Victoria, B.C. Canada From newsgrps at dalyn.co.nz Mon Aug 14 13:39:20 2006 From: newsgrps at dalyn.co.nz (David Emerson) Date: Tue, 15 Aug 2006 06:39:20 +1200 Subject: [dba-SQLServer] Addresses in Europe and elsewhere In-Reply-To: <20060814180839.82405.qmail@web88212.mail.re2.yahoo.com> References: <7.0.1.0.0.20060815052355.01acf340@dalyn.co.nz> <20060814180839.82405.qmail@web88212.mail.re2.yahoo.com> Message-ID: <7.0.1.0.0.20060815063507.01ad8898@dalyn.co.nz> Your example is correct. Post codes are not really used in NZ unless a business is doing a bulk mailout - in this case they get a discount for having their mail sorted by post code. Otherwise post codes are not even necessary. (NZ is so small (only 4 million people) that everyone knows where everyone lives anyway :-)) (By the way - just so that you don't upset the million or so people that live up north - the correct spelling is Auckland) David At 15/08/2006, you wrote: >That's interesting! Can you supply a concrete (if fictional) >example? I'm guessing that you mean: > >Apt. 103, 34567 Minor Street >MaoriTurf >Awkland 34567 >NZ > >Would that be about right? > >Due to my geographical ignorance, I'm surprised that the suburb is >mentioned. Wouldn't one deduce that from the postal code? > >Thanks for the input, >Arthur > > >----- Original Message ---- >From: David Emerson >To: dba-sqlserver at databaseadvisors.com >Sent: Monday, August 14, 2006 1:27:18 PM >Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere > >Arthur, > >New Zealand is as follows > >[Suffix], [StreetNumber] [StreetName] >[Suburb] >[City] [Postal Code] >[Country] > >Regards > >David > > > > >_______________________________________________ >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 Mon Aug 14 14:26:27 2006 From: rl_stewart at highstream.net (Robert L. Stewart) Date: Mon, 14 Aug 2006 15:26:27 -0400 Subject: [dba-SQLServer] dba-SQLServer Digest, Vol 42, Issue 12 In-Reply-To: References: Message-ID: <1155583587.44e0ce63971c7@webmail.highstream.net> Russia is... Country Postal Code Region/Republic, City Apartment/Building Street Last Name First Name Robert L. Stewart The Dyson Group International Software for the Non-profit Enterprise Expanding your Sphere of Knowledge Quoting dba-sqlserver-request at databaseadvisors.com: > At 15/08/2006, you wrote: > >I'm looking for some input from various regions around the world. I > >have the USA and Canada covered, but I need info from elsewhere. In > >North America, the usual form of a mailing address is: > > > > > > [StreetNumber] [StreetName] [Suffix] > > [City], [State/Province] > > [Postal Code] > > [Country] > > > > From fhtapia at gmail.com Mon Aug 14 14:51:09 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Mon, 14 Aug 2006 12:51:09 -0700 Subject: [dba-SQLServer] SQL Express and SQL 2005 side by side In-Reply-To: <20060811131845.86939.qmail@web88208.mail.re2.yahoo.com> References: <20060810164534.40494.qmail@web88212.mail.re2.yahoo.com> <20060811131845.86939.qmail@web88208.mail.re2.yahoo.com> Message-ID: Not sure, I have them in Virtual Machines so they don't really run on the same machine. Have you tried VMs? On 8/11/06, artful at rogers.com wrote: > Are there any known issues with installing these side by side? I have SQL 2005 installed (with SQL 2000) already. Would I have to remove SQL 2005 before installing Express? > > TIA, > Arthur > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From artful at rogers.com Mon Aug 14 15:37:12 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 14 Aug 2006 13:37:12 -0700 (PDT) Subject: [dba-SQLServer] Addresses in Europe and elsewhere In-Reply-To: <7.0.1.0.0.20060815063507.01ad8898@dalyn.co.nz> Message-ID: <20060814203712.97013.qmail@web88206.mail.re2.yahoo.com> Thank you for the info and the spelling correction. I guess I was thinking of awk as in *nix. That's my story and I'm sticking to it. Arthur P.S. I have no idea what NZ'ers think of Once Were Warrirors, but I liked that movie a lot. ----- Original Message ---- From: David Emerson To: dba-sqlserver at databaseadvisors.com Sent: Monday, August 14, 2006 2:39:20 PM Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere Your example is correct. Post codes are not really used in NZ unless a business is doing a bulk mailout - in this case they get a discount for having their mail sorted by post code. Otherwise post codes are not even necessary. (NZ is so small (only 4 million people) that everyone knows where everyone lives anyway :-)) (By the way - just so that you don't upset the million or so people that live up north - the correct spelling is Auckland) David At 15/08/2006, you wrote: >That's interesting! Can you supply a concrete (if fictional) >example? I'm guessing that you mean: > >Apt. 103, 34567 Minor Street >MaoriTurf >Awkland 34567 >NZ > >Would that be about right? > >Due to my geographical ignorance, I'm surprised that the suburb is >mentioned. Wouldn't one deduce that from the postal code? > >Thanks for the input, >Arthur > > >----- Original Message ---- >From: David Emerson >To: dba-sqlserver at databaseadvisors.com >Sent: Monday, August 14, 2006 1:27:18 PM >Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere > >Arthur, > >New Zealand is as follows > >[Suffix], [StreetNumber] [StreetName] >[Suburb] >[City] [Postal Code] >[Country] > >Regards > >David > > > > >_______________________________________________ >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 artful at rogers.com Mon Aug 14 15:46:20 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 14 Aug 2006 13:46:20 -0700 (PDT) Subject: [dba-SQLServer] dba-SQLServer Digest, Vol 42, Issue 12 In-Reply-To: <1155583587.44e0ce63971c7@webmail.highstream.net> Message-ID: <20060814204620.39873.qmail@web88203.mail.re2.yahoo.com> Now this is Intelligent! I am most pleased. I have tried to introduce this convention to various Canadian organizations and invariably met hostile responses... but it seems the way to go, IMO. It's a drill-down operation. I would like some input from people residing in those nether-worlds such as Singapore, Hong Kong and so on -- which seem not to have a CountryID or RegionID, but stand alone in the world as CityStates. Anyone here able to respond to this? In terms of Access (not my concern in this thread), the question often arises, "How do I synchronize comboA with comboB, so that the selection in comboA refills the options in comboB?" By drilling down into addresses such as you suggest, this is trivial. I just wish that your average user would comprehend this strategy. For example, I have a list of about 10,000 cities in North America, all defined by their State/Province and Country. Select a County, I show you the regions. Select a region, I show you the Cities/Towns. The actual db contains only the City/TownID, since all the rest can be inferred. The problem occurs with rural routes and so on (anything not directly connected to a city or town or village). Any ideas how to handle those? TIA, Arthur ----- Original Message ---- From: Robert L. Stewart To: dba-sqlserver at databaseadvisors.com Sent: Monday, August 14, 2006 3:26:27 PM Subject: Re: [dba-SQLServer] dba-SQLServer Digest, Vol 42, Issue 12 Russia is... Country Postal Code Region/Republic, City Apartment/Building Street Last Name First Name Robert L. Stewart The Dyson Group International Software for the Non-profit Enterprise Expanding your Sphere of Knowledge Quoting dba-sqlserver-request at databaseadvisors.com: > At 15/08/2006, you wrote: > >I'm looking for some input from various regions around the world. I > >have the USA and Canada covered, but I need info from elsewhere. In > >North America, the usual form of a mailing address is: > > > > > > [StreetNumber] [StreetName] [Suffix] > > [City], [State/Province] > > [Postal Code] > > [Country] > > > > _______________________________________________ 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 Aug 14 22:58:14 2006 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Tue, 15 Aug 2006 13:28:14 +0930 Subject: [dba-SQLServer] Addresses in Europe and elsewhere Message-ID: <0A870603A2A816459078203FC07F4CD2BE3FBF@adl01s055.ilcorp.gov.au> I think you'll find that postcodes are *the* primary method used in automated sorting of mail. At least, they are here in OZ, and from what I can remember we used the NZ and UK systems as examples before we implemented an equivalent system in the late 90's. The OCR readers will first look at the postcode before anything else (hence the squares provided on envelopes) and then on second and subsequent passes it will read street names (and suburbs if required -> very rare, since there is usually only one instance of a street name in a given postcode) and others. Of course, if the OCR can't deduce what is written on the envelope, then that's when its passed on to human eyes to hand sort, who may then use suburbs to help sort the mail, but again postcode always took precedence when I worked at the post. But this isn't restricted to just the 'presorted' business mail -> the automated readers will attempt to scan all mail. Cheers, A -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Tuesday, 15 August 2006 4:09 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere Your example is correct. Post codes are not really used in NZ unless a business is doing a bulk mailout - in this case they get a discount for having their mail sorted by post code. Otherwise post codes are not even necessary. (NZ is so small (only 4 million people) that everyone knows where everyone lives anyway :-)) (By the way - just so that you don't upset the million or so people that live up north - the correct spelling is Auckland) David At 15/08/2006, you wrote: >That's interesting! Can you supply a concrete (if fictional) example? >I'm guessing that you mean: > >Apt. 103, 34567 Minor Street >MaoriTurf >Awkland 34567 >NZ > >Would that be about right? > >Due to my geographical ignorance, I'm surprised that the suburb is >mentioned. Wouldn't one deduce that from the postal code? > >Thanks for the input, >Arthur > > >----- Original Message ---- >From: David Emerson >To: dba-sqlserver at databaseadvisors.com >Sent: Monday, August 14, 2006 1:27:18 PM >Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere > >Arthur, > >New Zealand is as follows > >[Suffix], [StreetNumber] [StreetName] >[Suburb] >[City] [Postal Code] >[Country] > >Regards > >David > > > > >_______________________________________________ >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 newsgrps at dalyn.co.nz Mon Aug 14 23:17:24 2006 From: newsgrps at dalyn.co.nz (David Emerson) Date: Tue, 15 Aug 2006 16:17:24 +1200 Subject: [dba-SQLServer] Addresses in Europe and elsewhere In-Reply-To: <0A870603A2A816459078203FC07F4CD2BE3FBF@adl01s055.ilcorp.go v.au> References: <0A870603A2A816459078203FC07F4CD2BE3FBF@adl01s055.ilcorp.gov.au> Message-ID: <7.0.1.0.0.20060815161419.01b08428@dalyn.co.nz> Ah - that's the difference between the writers and the (automated) readers. As far as I am aware, mail will take the same time to get from one place to another in NZ whether it has a postcode or not. For the senders there is little benefit (apart from the extra reassurance that a post code could make it more certain that the letter will arrive near the correct place. However, this is getting off topic. David At 15/08/2006, you wrote: >I think you'll find that postcodes are *the* primary method used in >automated sorting of mail. > >At least, they are here in OZ, and from what I can remember we used the >NZ and UK systems as examples before we implemented an equivalent system >in the late 90's. > >The OCR readers will first look at the postcode before anything else >(hence the squares provided on envelopes) and then on second and >subsequent passes it will read street names (and suburbs if required -> >very rare, since there is usually only one instance of a street name in >a given postcode) and others. > >Of course, if the OCR can't deduce what is written on the envelope, then >that's when its passed on to human eyes to hand sort, who may then use >suburbs to help sort the mail, but again postcode always took precedence >when I worked at the post. > >But this isn't restricted to just the 'presorted' business mail -> the >automated readers will attempt to scan all mail. > >Cheers, >A > > > > >-----Original Message----- >From: dba-sqlserver-bounces at databaseadvisors.com >[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of David >Emerson >Sent: Tuesday, 15 August 2006 4:09 AM >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere > >Your example is correct. Post codes are not really used in NZ unless a >business is doing a bulk mailout - in this case they get a discount for >having their mail sorted by post code. Otherwise post codes are not >even necessary. (NZ is so small (only 4 million people) that everyone >knows where everyone lives anyway :-)) > >(By the way - just so that you don't upset the million or so people that >live up north - the correct spelling is Auckland) > >David > >At 15/08/2006, you wrote: > >That's interesting! Can you supply a concrete (if fictional) example? > >I'm guessing that you mean: > > > >Apt. 103, 34567 Minor Street > >MaoriTurf > >Awkland 34567 > >NZ > > > >Would that be about right? > > > >Due to my geographical ignorance, I'm surprised that the suburb is > >mentioned. Wouldn't one deduce that from the postal code? > > > >Thanks for the input, > >Arthur > > > > > >----- Original Message ---- > >From: David Emerson > >To: dba-sqlserver at databaseadvisors.com > >Sent: Monday, August 14, 2006 1:27:18 PM > >Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere > > > >Arthur, > > > >New Zealand is as follows > > > >[Suffix], [StreetNumber] [StreetName] > >[Suburb] > >[City] [Postal Code] > >[Country] > > > >Regards > > > >David > > > > > > > > > >_______________________________________________ > >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 Aug 15 00:52:49 2006 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Tue, 15 Aug 2006 15:22:49 +0930 Subject: [dba-SQLServer] Addresses in Europe and elsewhere Message-ID: <0A870603A2A816459078203FC07F4CD2BE3FC2@adl01s055.ilcorp.gov.au> >> As far as I am aware, mail will take the same time to get from one place to another in NZ whether it has a postcode or not. That's because Postal services, like most other organisations, are performance driven. They have to report to some-one, be it government, private enterprise etc, and all aim for a certain KPI. In OZ, Australia Post sat somewhere in the 90% range for on-time (next-day) delivery when I was there. I can gurantee if no-one put postcodes on their mail, this KPI would drop signifigantly. The more mail without postcodes, the more than could not be read by the OCR machines, and the more that would have to be hand-sorted => slower delivery times. >> However, this is getting off topic. True. In database talk, think of postcodes as the PK -> they must have one! -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Tuesday, 15 August 2006 1:47 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere Ah - that's the difference between the writers and the (automated) readers. As far as I am aware, mail will take the same time to get from one place to another in NZ whether it has a postcode or not. For the senders there is little benefit (apart from the extra reassurance that a post code could make it more certain that the letter will arrive near the correct place. However, this is getting off topic. David At 15/08/2006, you wrote: >I think you'll find that postcodes are *the* primary method used in >automated sorting of mail. > >At least, they are here in OZ, and from what I can remember we used the >NZ and UK systems as examples before we implemented an equivalent >system in the late 90's. > >The OCR readers will first look at the postcode before anything else >(hence the squares provided on envelopes) and then on second and >subsequent passes it will read street names (and suburbs if required -> >very rare, since there is usually only one instance of a street name in >a given postcode) and others. > >Of course, if the OCR can't deduce what is written on the envelope, >then that's when its passed on to human eyes to hand sort, who may then >use suburbs to help sort the mail, but again postcode always took >precedence when I worked at the post. > >But this isn't restricted to just the 'presorted' business mail -> the >automated readers will attempt to scan all mail. > >Cheers, >A > > > > >-----Original Message----- >From: dba-sqlserver-bounces at databaseadvisors.com >[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of David >Emerson >Sent: Tuesday, 15 August 2006 4:09 AM >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere > >Your example is correct. Post codes are not really used in NZ unless a >business is doing a bulk mailout - in this case they get a discount for >having their mail sorted by post code. Otherwise post codes are not >even necessary. (NZ is so small (only 4 million people) that everyone >knows where everyone lives anyway :-)) > >(By the way - just so that you don't upset the million or so people >that live up north - the correct spelling is Auckland) > >David > >At 15/08/2006, you wrote: > >That's interesting! Can you supply a concrete (if fictional) example? > >I'm guessing that you mean: > > > >Apt. 103, 34567 Minor Street > >MaoriTurf > >Awkland 34567 > >NZ > > > >Would that be about right? > > > >Due to my geographical ignorance, I'm surprised that the suburb is > >mentioned. Wouldn't one deduce that from the postal code? > > > >Thanks for the input, > >Arthur > > > > > >----- Original Message ---- > >From: David Emerson > >To: dba-sqlserver at databaseadvisors.com > >Sent: Monday, August 14, 2006 1:27:18 PM > >Subject: Re: [dba-SQLServer] Addresses in Europe and elsewhere > > > >Arthur, > > > >New Zealand is as follows > > > >[Suffix], [StreetNumber] [StreetName] [Suburb] [City] [Postal Code] > >[Country] > > > >Regards > > > >David > > > > > > > > > >_______________________________________________ > >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 rl_stewart at highstream.net Tue Aug 15 08:06:53 2006 From: rl_stewart at highstream.net (Robert L. Stewart) Date: Tue, 15 Aug 2006 09:06:53 -0400 Subject: [dba-SQLServer] Addresses in Europe and elsewhere In-Reply-To: References: Message-ID: <1155647213.44e1c6ed8cf51@webmail.highstream.net> Yes, I have found out that there are a number of things that we could "learn" from the Russians. :-) I think that you will find that because of 911 services, rural routes are going away. About 4 years ago, the area I live in was renumbered because of it. After 3 years, the post office returnd mail that was addressed to the old address. But, that is Texas. I will let others speak for their area of the US. Robert L. Stewart The Dyson Group International Software for the Non-profit Enterprise Expanding your Sphere of Knowledge Quoting dba-sqlserver-request at databaseadvisors.com: > Date: Mon, 14 Aug 2006 13:46:20 -0700 (PDT) > From: > Subject: Re: [dba-SQLServer] dba-SQLServer Digest, Vol 42, Issue 12 > To: dba-sqlserver at databaseadvisors.com > Message-ID: <20060814204620.39873.qmail at web88203.mail.re2.yahoo.com> > Content-Type: text/plain; charset=us-ascii > > Now this is Intelligent! I am most pleased. I have tried to introduce this > convention to various Canadian organizations and invariably met hostile > responses... but it seems the way to go, IMO. It's a drill-down operation. > > I would like some input from people residing in those nether-worlds such as > Singapore, Hong Kong and so on -- which seem not to have a CountryID or > RegionID, but stand alone in the world as CityStates. Anyone here able to > respond to this? > > In terms of Access (not my concern in this thread), the question often > arises, "How do I synchronize comboA with comboB, so that the selection in > comboA refills the options in comboB?" By drilling down into addresses such > as you suggest, this is trivial. I just wish that your average user would > comprehend this strategy. For example, I have a list of about 10,000 cities > in North America, all defined by their State/Province and Country. Select a > County, I show you the regions. Select a region, I show you the Cities/Towns. > The actual db contains only the City/TownID, since all the rest can be > inferred. > > The problem occurs with rural routes and so on (anything not directly > connected to a city or town or village). Any ideas how to handle those? > > TIA, > Arthur From fhtapia at gmail.com Tue Aug 15 12:54:59 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 15 Aug 2006 10:54:59 -0700 Subject: [dba-SQLServer] Creating a Manual TrendLine In-Reply-To: <44DE2796.8000509@shaw.ca> References: <44DE2796.8000509@shaw.ca> Message-ID: Marty thanks for responding. The data that I have is: Jan-03 1.06 395 Feb-03 0.91 256 Mar-03 1.40 225 Apr-03 1.23 280 May-03 1.31 224 Jun-03 1.33 256 Jul-03 1.40 305 Aug-03 1.21 232 Sep-03 1.10 304 Oct-03 0.83 293 Nov-03 0.91 322 Dec-03 1.21 319 Jan-04 1.05 222 I want to trend the 2nd column, If i use the standard slope formula, I suppose X just represents rows 1, 2, 3, etc. On 8/12/06, MartyConnelly wrote: > There are a lot of equations you can use to curve fit a trendline > But sticking with say something simple, say a moving average. > > Here are two examples from Joe Celko's book SQL for Smarties > You can find other examples here. > > Usually a moving average is calculated over a fixed period of time > (i.e. last five days, last two batches, etc.) > > SELECT B2.mydate, AVG(B1.lData) AS moving_avg_wgt > FROM Table1 AS B1, Table1 AS B2 > WHERE B1.mydate > BETWEEN B2.mydate > AND (B2.mydate - 5) > GROUP BY B2.mydate; > > or if you do not like the scalar subquery expression: > > SELECT mydate, (SELECT AVG(ldata) > FROM Table1 AS B1 > WHERE B1.mydate > BETWEEN B2.mydate > AND B2.mydate - 1) AS moving_avg_wgt > FROM Table1 AS B2; > > ID lData mydate > 1 10 01/01/2006 > 2 20 02/01/2006 > 3 40 03/01/2006 > 4 390 04/01/2006 > 5 50 05/01/2006 > 6 30 02/01/2006 > > > Table1 ID lData mydate > 1 10 01/01/2006 > 2 20 02/01/2006 > 3 40 03/01/2006 > 4 390 04/01/2006 > 5 50 05/01/2006 > 6 30 02/01/2006 > > > > > Francisco Tapia wrote: > > >After much re-search I found that I could "NOT" easily just create a > >trend line in Sql Server Reporting Services (2000). Therefore I need > >to manually create the data for a TrendLine. Question is, Does anyone > >know how? > > > >My Data looks like this: (object is to trend the Failure rate) > > > >Month, Installs, Fails, Trend > >01/00, 200, 1.5, ? > >01/00, 278, 1.0, ? > >01/00, 325, .9, ? > >... > >...etc > > > >Thanks, > > > > > > > > > > > > -- > Marty Connelly > Victoria, B.C. > Canada > > _______________________________________________ > 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! http://sqlthis.blogspot.com | Tsql and More... From martyconnelly at shaw.ca Tue Aug 15 18:41:51 2006 From: martyconnelly at shaw.ca (MartyConnelly) Date: Tue, 15 Aug 2006 16:41:51 -0700 Subject: [dba-SQLServer] Creating a Manual TrendLine In-Reply-To: References: <44DE2796.8000509@shaw.ca> Message-ID: <44E25BBF.5010205@shaw.ca> Have a look at this first How to create a bar graph that has a trend line in a chart in Report Designer http://support.microsoft.com/kb/842422/en-us Or you could run something like this via UDF or straight SQL Essentially you would have you X (Date) and Y value in the table, run the SQL to create a third field in the Table YY containing interpolated Y value via least square fit method. Sub sInterpolation() Dim strSQL As String Dim m As Double Dim b As Double ' Best least square Fit Line: Y = mX + b Call sRegressionLineA(m, b) 'add new calc Y values to table strSQL = "UPDATE Table1 SET Table1.YY = " & _ "(" & m & ")" & " * [X] + (" & b & ");" Debug.Print strSQL CurrentDb.Execute strSQL Debug.Print "end" End Sub Function sRegressionLineA(m As Double, b As Double) Dim dbs As Database, rcs As Recordset Dim strSQL As String strSQL = "SELECT Sum(Table1.X) AS SumX, " & _ "Sum([X]*[X]) AS SumXX, Sum(Table1.Y) AS SumY, Sum([X]*[Y]) AS SumXY, " & _ "Count(Table1.X) AS N FROM Table1 WHERE (((Table1.X) Is Not Null) AND ((Table1.Y) Is Not Null));" Debug.Print strSQL Set dbs = CurrentDb() Set rcs = dbs.OpenRecordset(strSQL, dbOpenDynaset) m = (rcs!N * rcs!SumXY - rcs!SumX * rcs!SumY) / (rcs!N * rcs!SumXX - rcs!SumX ^ 2) b = (rcs!SumY * rcs!SumXX - rcs!SumX * rcs!SumXY) / (rcs!N * rcs!SumXX - rcs!SumX ^ 2) Debug.Print m; b End Function If you had the Excel Solver Pack installed on the server you could call it's curve fitting functions, easy to do in Access might be a pain in SQL, haven't tried. Francisco Tapia wrote: >Marty thanks for responding. The data that I have is: > >Jan-03 1.06 395 >Feb-03 0.91 256 >Mar-03 1.40 225 >Apr-03 1.23 280 >May-03 1.31 224 >Jun-03 1.33 256 >Jul-03 1.40 305 >Aug-03 1.21 232 >Sep-03 1.10 304 >Oct-03 0.83 293 >Nov-03 0.91 322 >Dec-03 1.21 319 >Jan-04 1.05 222 > >I want to trend the 2nd column, If i use the standard slope formula, I >suppose X just represents rows 1, 2, 3, etc. > > > >On 8/12/06, MartyConnelly wrote: > > >>There are a lot of equations you can use to curve fit a trendline >>But sticking with say something simple, say a moving average. >> >>Here are two examples from Joe Celko's book SQL for Smarties >>You can find other examples here. >> >>Usually a moving average is calculated over a fixed period of time >>(i.e. last five days, last two batches, etc.) >> >>SELECT B2.mydate, AVG(B1.lData) AS moving_avg_wgt >>FROM Table1 AS B1, Table1 AS B2 >>WHERE B1.mydate >> BETWEEN B2.mydate >> AND (B2.mydate - 5) >>GROUP BY B2.mydate; >> >>or if you do not like the scalar subquery expression: >> >>SELECT mydate, (SELECT AVG(ldata) >> FROM Table1 AS B1 >> WHERE B1.mydate >> BETWEEN B2.mydate >> AND B2.mydate - 1) AS moving_avg_wgt >>FROM Table1 AS B2; >> >>ID lData mydate >>1 10 01/01/2006 >>2 20 02/01/2006 >>3 40 03/01/2006 >>4 390 04/01/2006 >>5 50 05/01/2006 >>6 30 02/01/2006 >> >> >>Table1 ID lData mydate >>1 10 01/01/2006 >>2 20 02/01/2006 >>3 40 03/01/2006 >>4 390 04/01/2006 >>5 50 05/01/2006 >>6 30 02/01/2006 >> >> >> >> >>Francisco Tapia wrote: >> >> >> >>>After much re-search I found that I could "NOT" easily just create a >>>trend line in Sql Server Reporting Services (2000). Therefore I need >>>to manually create the data for a TrendLine. Question is, Does anyone >>>know how? >>> >>>My Data looks like this: (object is to trend the Failure rate) >>> >>>Month, Installs, Fails, Trend >>>01/00, 200, 1.5, ? >>>01/00, 278, 1.0, ? >>>01/00, 325, .9, ? >>>... >>>...etc >>> >>>Thanks, >>> >>> >>> >>> >>> >>> >>> >>-- >>Marty Connelly >>Victoria, B.C. >>Canada >> >>_______________________________________________ >>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 fhtapia at gmail.com Fri Aug 18 10:32:39 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Fri, 18 Aug 2006 08:32:39 -0700 Subject: [dba-SQLServer] My Agent was assasinated!! Message-ID: Helpdesk guy on an instruction from our sysadmin, was instructed to visit one of my sql servers and "UNINSTALL" BackupExec from the machine as we have moved to a central backup system. After the install the server came up but he did not know to check in EM that the sql server was running and that the agent was running... ON the server you cannot use EM to see the (local) sql server status, remotely I can use EM and verified that the server is running, and all my users can access the server just fine. What is not running is the Sql Server Agent. And I am not able to restart it for some reason. Any advise would be very helpful. -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Fri Aug 18 10:52:51 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Fri, 18 Aug 2006 08:52:51 -0700 Subject: [dba-SQLServer] My Agent was assasinated!! In-Reply-To: References: Message-ID: Followup, Server is Win2003 SP1, Sql Srv 2000 SP4. When I pull up EM on the Server I get this error: -------------------------------------------------------------------- A connection could not be established to (local) Reason: SQL Server does not exist or access denied. ConnectionOpen (Connect()) Please Verify SQL Server is running and check your SQL Server registration properties (by right-clicking on the (local) node) and try again. -------------------------------------------------------------------- The SQLAgent.out file reads as follows: --------------- 2006-08-18 08:39:49 - ! [298] SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE 08001] 2006-08-18 08:39:49 - ! [298] SQLServer Error: 1703, ConnectionOpen (Connect()). [SQLSTATE 01000] 2006-08-18 08:39:49 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start 2006-08-18 08:39:50 - ? [098] SQLServerAgent terminated (normally) ---------------- question is how do I restore the connectivity on the server (to itself?) On 8/18/06, Francisco Tapia wrote: > Helpdesk guy on an instruction from our sysadmin, was instructed to > visit one of my sql servers and "UNINSTALL" BackupExec from the > machine as we have moved to a central backup system. After the > install the server came up but he did not know to check in EM that the > sql server was running and that the agent was running... > > ON the server you cannot use EM to see the (local) sql server status, > remotely I can use EM and verified that the server is running, and all > my users can access the server just fine. What is not running is the > Sql Server Agent. And I am not able to restart it for some reason. > Any advise would be very helpful. -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Fri Aug 18 13:03:58 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Fri, 18 Aug 2006 11:03:58 -0700 Subject: [dba-SQLServer] [SQL2K] My Agent was assasinated!! - Revived Message-ID: Mohammed, And others, (follow-up) It turns out that the fix was a lot easier than that, I opened up the client network utility and found that the TCP/IP and Named Pipes protocols were removed on the uninstall of BackupExec. I re-added these protocols and the Agent was able to start up again! On 8/18/06, Mohammed Uddin wrote: > Please check SQL error log and SQL Agent Error log first for any > possible errors. And also check for any .dmp files too in the sql error > log folder. > > Mohammed. > > -----Original Message----- > From: listbounces at sswug.org [mailto:listbounces at sswug.org] On Behalf Of > Francisco Tapia > Sent: Friday, August 18, 2006 8:33 AM > To: SQL Server 2k List; dba-sqlserver at databaseadvisors.com > Subject: [SQL2K] My Agent was assasinated!! > > Helpdesk guy on an instruction from our sysadmin, was instructed to > visit one of my sql servers and "UNINSTALL" BackupExec from the > machine as we have moved to a central backup system. After the > install the server came up but he did not know to check in EM that the > sql server was running and that the agent was running... > > ON the server you cannot use EM to see the (local) sql server status, > remotely I can use EM and verified that the server is running, and all > my users can access the server just fine. What is not running is the > Sql Server Agent. And I am not able to restart it for some reason. > Any advise would be very helpful. > > -- > -Francisco > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > > > ------ > For archives, see http://www.sswug.org/archives > For list assistance, contact members at sswug.org > To unsubscribe, email lists at sswug.org with > UNSUBSCRIBE SQL2K in the body of the message. > > > > > ------ > For archives, see http://www.sswug.org/archives > For list assistance, contact members at sswug.org > To unsubscribe, email lists at sswug.org with > UNSUBSCRIBE SQL2K in the body of the message. > > > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From jlawrenc1 at shaw.ca Fri Aug 18 13:28:57 2006 From: jlawrenc1 at shaw.ca (Jim Lawrence) Date: Fri, 18 Aug 2006 11:28:57 -0700 Subject: [dba-SQLServer] [SQL2K] My Agent was assasinated!! - Revived In-Reply-To: Message-ID: <0J47009SCHZD0AE0@l-daemon> Hi Francisco: That was quick. I will stash that aside as one of our clients is on that move. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Friday, August 18, 2006 11:04 AM To: sql2k at ls.sswug.org; dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [SQL2K] My Agent was assasinated!! - Revived Mohammed, And others, (follow-up) It turns out that the fix was a lot easier than that, I opened up the client network utility and found that the TCP/IP and Named Pipes protocols were removed on the uninstall of BackupExec. I re-added these protocols and the Agent was able to start up again! On 8/18/06, Mohammed Uddin wrote: > Please check SQL error log and SQL Agent Error log first for any > possible errors. And also check for any .dmp files too in the sql error > log folder. > > Mohammed. > > -----Original Message----- > From: listbounces at sswug.org [mailto:listbounces at sswug.org] On Behalf Of > Francisco Tapia > Sent: Friday, August 18, 2006 8:33 AM > To: SQL Server 2k List; dba-sqlserver at databaseadvisors.com > Subject: [SQL2K] My Agent was assasinated!! > > Helpdesk guy on an instruction from our sysadmin, was instructed to > visit one of my sql servers and "UNINSTALL" BackupExec from the > machine as we have moved to a central backup system. After the > install the server came up but he did not know to check in EM that the > sql server was running and that the agent was running... > > ON the server you cannot use EM to see the (local) sql server status, > remotely I can use EM and verified that the server is running, and all > my users can access the server just fine. What is not running is the > Sql Server Agent. And I am not able to restart it for some reason. > Any advise would be very helpful. > > -- > -Francisco > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > > > ------ > For archives, see http://www.sswug.org/archives > For list assistance, contact members at sswug.org > To unsubscribe, email lists at sswug.org with > UNSUBSCRIBE SQL2K in the body of the message. > > > > > ------ > For archives, see http://www.sswug.org/archives > For list assistance, contact members at sswug.org > To unsubscribe, email lists at sswug.org with > UNSUBSCRIBE SQL2K in the body of the message. > > > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 Aug 18 15:16:48 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Fri, 18 Aug 2006 13:16:48 -0700 Subject: [dba-SQLServer] [SQL2K] My Agent was assasinated!! - Revived In-Reply-To: <1589370312_69903303@mail.sswug.org> References: <1589370312_69903303@mail.sswug.org> Message-ID: On a hunch I thought that maybe the DLL's were removed when BackupExec was removed (as you know Backupexec will install MSDE for it's purposes of tracking backups). I checked for the default DBNETLIB.DLL (TCP/IP) and then DBNMPNTW.DLL (Named Pipes) but found that they were still in the system, the next thing I thought was that possibly the client network utility didn't have them enabled, so I poped it open and sure enough they were "not" enabled. A quick enable and my agent was back online On 8/18/06, Mohammed Uddin wrote: > Thanks for sharing... > How did you find the protocols removed? > > Mohammed. > > -----Original Message----- > From: listbounces at sswug.org [mailto:listbounces at sswug.org] On Behalf Of > Francisco Tapia > Sent: Friday, August 18, 2006 11:04 AM > To: sql2k at ls.sswug.org; dba-sqlserver at databaseadvisors.com > Subject: Re: [SQL2K] My Agent was assasinated!! - Revived > > Mohammed, > And others, (follow-up) It turns out that the fix was a lot easier > than that, I opened up the client network utility and found that the > TCP/IP and Named Pipes protocols were removed on the uninstall of > BackupExec. I re-added these protocols and the Agent was able to > start up again! > > > > On 8/18/06, Mohammed Uddin wrote: > > Please check SQL error log and SQL Agent Error log first for any > > possible errors. And also check for any .dmp files too in the sql > error > > log folder. > > > > Mohammed. > > > > -----Original Message----- > > From: listbounces at sswug.org [mailto:listbounces at sswug.org] On Behalf > Of > > Francisco Tapia > > Sent: Friday, August 18, 2006 8:33 AM > > To: SQL Server 2k List; dba-sqlserver at databaseadvisors.com > > Subject: [SQL2K] My Agent was assasinated!! > > > > Helpdesk guy on an instruction from our sysadmin, was instructed to > > visit one of my sql servers and "UNINSTALL" BackupExec from the > > machine as we have moved to a central backup system. After the > > install the server came up but he did not know to check in EM that the > > sql server was running and that the agent was running... > > > > ON the server you cannot use EM to see the (local) sql server status, > > remotely I can use EM and verified that the server is running, and all > > my users can access the server just fine. What is not running is the > > Sql Server Agent. And I am not able to restart it for some reason. > > Any advise would be very helpful. > > > > -- > > -Francisco > > http://pcthis.blogspot.com |PC news with out the jargon! > > http://sqlthis.blogspot.com | Tsql and More... > > > > > > ------ > > For archives, see http://www.sswug.org/archives > > For list assistance, contact members at sswug.org > > To unsubscribe, email lists at sswug.org with > > UNSUBSCRIBE SQL2K in the body of the message. > > > > > > > > > > ------ > > For archives, see http://www.sswug.org/archives > > For list assistance, contact members at sswug.org > > To unsubscribe, email lists at sswug.org with > > UNSUBSCRIBE SQL2K in the body of the message. > > > > > > > > > > > -- > -Francisco > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > > > ------ > For archives, see http://www.sswug.org/archives > For list assistance, contact members at sswug.org > To unsubscribe, email lists at sswug.org with > UNSUBSCRIBE SQL2K in the body of the message. > > > > > ------ > For archives, see http://www.sswug.org/archives > For list assistance, contact members at sswug.org > To unsubscribe, email lists at sswug.org with > UNSUBSCRIBE SQL2K in the body of the message. > > > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From ssharkins at setel.com Sun Aug 20 14:22:37 2006 From: ssharkins at setel.com (Susan Harkins) Date: Sun, 20 Aug 2006 15:22:37 -0400 Subject: [dba-SQLServer] sp_configure question Message-ID: <002501c6c48d$ffbbac00$dabc2ad1@SUSANONE> I'm trying to read the cursor threshold value using sp_configure, but I get an error on the following: EXEC sp_configure 'cursor threshold' Although, it's listed in Help, I can't seem to get a read of the value. The error says it doesn't exist or that it's an advanced option. I'm using Express and Management Studio, so it's possible that I just can't do this with Express, but I can't find any documentation warning me of that. Susan H. From stuart at lexacorp.com.pg Sun Aug 20 16:43:09 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Mon, 21 Aug 2006 07:43:09 +1000 Subject: [dba-SQLServer] sp_configure question In-Reply-To: <002501c6c48d$ffbbac00$dabc2ad1@SUSANONE> References: <002501c6c48d$ffbbac00$dabc2ad1@SUSANONE> Message-ID: <44E9640D.7763.41284143@stuart.lexacorp.com.pg> On 20 Aug 2006 at 15:22, Susan Harkins wrote: > > > I'm trying to read the cursor threshold value using sp_configure, but I get > an error on the following: > > EXEC sp_configure 'cursor threshold' > > Although, it's listed in Help, I can't seem to get a read of the value. The > error says it doesn't exist or that it's an advanced option. >From the documentation: "Some options supported by sp_configure are designated as Advanced. By default, these options are not available for viewing and changing; setting the Show Advanced Options configuration option to 1 makes these options available." -- Stuart From ssharkins at setel.com Sun Aug 20 17:35:43 2006 From: ssharkins at setel.com (Susan Harkins) Date: Sun, 20 Aug 2006 18:35:43 -0400 Subject: [dba-SQLServer] sp_configure question In-Reply-To: <44E9640D.7763.41284143@stuart.lexacorp.com.pg> Message-ID: <000b01c6c4a8$fb936ad0$8732fad1@SUSANONE> That's Stuart -- that's probably it. I don't have BOL for SQL Server, just one of the CTP Express versions and it's not very helpful. I really dread downloading the full blown bol using dialup, but if I had it, I'd have not had to ask. :) Susan H. >From the documentation: "Some options supported by sp_configure are designated as Advanced. By default, these options are not available for viewing and changing; setting the Show Advanced Options configuration option to 1 makes these options available." From andrew.haslett at ilc.gov.au Sun Aug 20 20:20:23 2006 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Mon, 21 Aug 2006 10:50:23 +0930 Subject: [dba-SQLServer] sp_configure question Message-ID: <0A870603A2A816459078203FC07F4CD2BE3FF0@adl01s055.ilcorp.gov.au> You can always access it online at MSDN.. ;=) http://msdn2.microsoft.com/en-us/library/ms130214.aspx Cheers, A -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Monday, 21 August 2006 8:06 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] sp_configure question That's Stuart -- that's probably it. I don't have BOL for SQL Server, just one of the CTP Express versions and it's not very helpful. I really dread downloading the full blown bol using dialup, but if I had it, I'd have not had to ask. :) Susan H. >From the documentation: "Some options supported by sp_configure are designated as Advanced. By default, these options are not available for viewing and changing; setting the Show Advanced Options configuration option to 1 makes these options available." _______________________________________________ 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 ssharkins at setel.com Mon Aug 21 08:12:10 2006 From: ssharkins at setel.com (Susan Harkins) Date: Mon, 21 Aug 2006 09:12:10 -0400 Subject: [dba-SQLServer] sp_configure question In-Reply-To: <0A870603A2A816459078203FC07F4CD2BE3FF0@adl01s055.ilcorp.gov.au> Message-ID: <000301c6c523$6ccd5100$2732fad1@SUSANONE> Thank you - -- that'll be useful. Susan H. You can always access it online at MSDN.. ;=) http://msdn2.microsoft.com/en-us/library/ms130214.aspx From artful at rogers.com Mon Aug 21 09:21:18 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 21 Aug 2006 07:21:18 -0700 (PDT) Subject: [dba-SQLServer] Reporting Servers error (SQL 2005) Message-ID: <20060821142118.27671.qmail@web88210.mail.re2.yahoo.com> I'm baffled. I have successfully configured Reporting Services using the Configuration tool. It's running, etc. But when I switch to Mgmt Studio and attempt to connect, I get the following error: Cannot connect to .. Client found response content type of 'text/html', but expected 'text/xml'. The request failed with the error message: - Server Application Error

The server has encounted an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance. - (Microsoft.SqlServer.Management.UI.RSClient) --------------- Anyone got any idea what is going on? TIA, Arthur From ssharkins at setel.com Mon Aug 21 09:31:16 2006 From: ssharkins at setel.com (Susan Harkins) Date: Mon, 21 Aug 2006 10:31:16 -0400 Subject: [dba-SQLServer] Reporting Servers error (SQL 2005) In-Reply-To: <20060821142118.27671.qmail@web88210.mail.re2.yahoo.com> Message-ID: <000a01c6c52e$76f4ccc0$2732fad1@SUSANONE> Arthur, I used Express yesterday for the first time in a few months and I had a similar problem -- couldn't connect, but it had nothing to do with Reporting Services. It took me a while to find the problem, but it was as simple as enabling a protocol that had been disabled (don't know how or when that happened). Even though the service was running, it still wouldn't connect and enabling the protocol did the trick. I don't think my exact solution will help you, just suggesting that it might be a simple property that's not enabled. I'm not familiar enough with Reporting Services to even suggest what. Susan H. I'm baffled. I have successfully configured Reporting Services using the Configuration tool. It's running, etc. But when I switch to Mgmt Studio and attempt to connect, I get the following error: From artful at rogers.com Mon Aug 21 10:20:38 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 21 Aug 2006 08:20:38 -0700 (PDT) Subject: [dba-SQLServer] Reporting Servers error (SQL 2005) In-Reply-To: <000a01c6c52e$76f4ccc0$2732fad1@SUSANONE> Message-ID: <20060821152038.36395.qmail@web88209.mail.re2.yahoo.com> That's a useful clue, Susan. I'll check out which protocols are enabled, for starters. Thanks! Arthur ----- Original Message ---- From: Susan Harkins To: dba-sqlserver at databaseadvisors.com Sent: Monday, August 21, 2006 10:31:16 AM Subject: Re: [dba-SQLServer] Reporting Servers error (SQL 2005) Arthur, I used Express yesterday for the first time in a few months and I had a similar problem -- couldn't connect, but it had nothing to do with Reporting Services. It took me a while to find the problem, but it was as simple as enabling a protocol that had been disabled (don't know how or when that happened). Even though the service was running, it still wouldn't connect and enabling the protocol did the trick. I don't think my exact solution will help you, just suggesting that it might be a simple property that's not enabled. I'm not familiar enough with Reporting Services to even suggest what. Susan H. I'm baffled. I have successfully configured Reporting Services using the Configuration tool. It's running, etc. But when I switch to Mgmt Studio and attempt to connect, I get the following error: _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From newsgrps at dalyn.co.nz Mon Aug 21 23:44:29 2006 From: newsgrps at dalyn.co.nz (David Emerson) Date: Tue, 22 Aug 2006 16:44:29 +1200 Subject: [dba-SQLServer] SQL Equivalents of PV and NPer Message-ID: <7.0.1.0.0.20060822164325.01ab4e18@dalyn.co.nz> Does anyone know what the equivalent SQL functions are for the VB PV and NPer functions? Regards David Emerson Dalyn Software Ltd Wellington, New Zealand From stuart at lexacorp.com.pg Mon Aug 21 23:59:46 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Tue, 22 Aug 2006 14:59:46 +1000 Subject: [dba-SQLServer] SQL Equivalents of PV and NPer In-Reply-To: <7.0.1.0.0.20060822164325.01ab4e18@dalyn.co.nz> References: <7.0.1.0.0.20060822164325.01ab4e18@dalyn.co.nz> Message-ID: <44EB1BE2.8952.C2277D@stuart.lexacorp.com.pg> On 22 Aug 2006 at 16:44, David Emerson wrote: > Does anyone know what the equivalent SQL functions are for the VB PV > and NPer functions? > AFAIK, SQL doesn't have any such functions, you'd have to roll your own UDFs from first principles. PV = FV [ 1 / (1 + i)n ] Where: PV = Present Value FV = Future Value i = Interest Rate Per Period n = Number of Compounding Periods number of periods = natural log [(FV * i) / (PV * i)] / natural log (1 + i) where: PV = present value, the amount you invested FV = future value, the amount your investment will grow to i = interest per period You can find these and other financial formulae at: http://www.getobjects.com/Components/Finance/TVM/concepts.html -- Stuart McLachlan From michael at ddisolutions.com.au Tue Aug 22 00:05:34 2006 From: michael at ddisolutions.com.au (Michael Maddison) Date: Tue, 22 Aug 2006 15:05:34 +1000 Subject: [dba-SQLServer] SQL Equivalents of PV and NPer Message-ID: <59A61174B1F5B54B97FD4ADDE71E7D0116A98F@ddi-01.DDI.local> David, They don't seem to have a financial category for SQL 2K. Havn't got 2005 installed at the moment. But seeing as I didn't know VB had such a large range of financial functions, anything is possible... Seems you are not on your own... http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=643660&SiteID=1 cheers Michael M -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Tuesday, 22 August 2006 2:44 PM To: dba-SQLServer at databaseadvisors.com Subject: [dba-SQLServer] SQL Equivalents of PV and NPer Does anyone know what the equivalent SQL functions are for the VB PV and NPer functions? Regards David Emerson Dalyn Software Ltd Wellington, New Zealand _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From artful at rogers.com Tue Aug 22 12:30:47 2006 From: artful at rogers.com (artful at rogers.com) Date: Tue, 22 Aug 2006 10:30:47 -0700 (PDT) Subject: [dba-SQLServer] SQL Equivalents of PV and NPer In-Reply-To: <7.0.1.0.0.20060822164325.01ab4e18@dalyn.co.nz> Message-ID: <20060822173047.70584.qmail@web88203.mail.re2.yahoo.com> I have a pair of UDFs to do these calculations. Do you want them? Arthur ----- Original Message ---- From: David Emerson To: dba-SQLServer at databaseadvisors.com Sent: Tuesday, August 22, 2006 12:44:29 AM Subject: [dba-SQLServer] SQL Equivalents of PV and NPer Does anyone know what the equivalent SQL functions are for the VB PV and NPer functions? Regards David Emerson Dalyn Software Ltd Wellington, New Zealand _______________________________________________ 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 Sun Aug 27 08:38:15 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Sun, 27 Aug 2006 09:38:15 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: Message-ID: <000c01c6c9de$0d767eb0$657aa8c0@m6805> I have just finished rebuilding a machine (new motherboard) and need to transfer a large SQL Server database to that new server. The two servers can see each other (shared folders), but ... I cannot register the other SQL Servers, getting an error "Login failed for 'MachineName\Guest'. I get this error on either machine when trying to register the SQL Server on the other machine. My login user / password is the same on both machines. Both databases were installed using "Windows Authentication" rather than "SQL Server Authentication". Any ideas? John W. Colby Colby Consulting www.ColbyConsulting.com From ridermark at gmail.com Sun Aug 27 09:36:59 2006 From: ridermark at gmail.com (Mark Rider) Date: Sun, 27 Aug 2006 09:36:59 -0500 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <000c01c6c9de$0d767eb0$657aa8c0@m6805> References: <000c01c6c9de$0d767eb0$657aa8c0@m6805> Message-ID: I'm not sure about the login issue, but a good way to transfer the DB is to Detach it on the old server, copy the MDF and LDF files to the new server and then attach it. This will preserve all of the data, and has worked for me several times. On 8/27/06, JWColby wrote: > I have just finished rebuilding a machine (new motherboard) and need to > transfer a large SQL Server database to that new server. The two servers > can see each other (shared folders), but ... > > I cannot register the other SQL Servers, getting an error "Login failed for > 'MachineName\Guest'. I get this error on either machine when trying to > register the SQL Server on the other machine. My login user / password is > the same on both machines. Both databases were installed using "Windows > Authentication" rather than "SQL Server Authentication". > > Any ideas? > > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- Mark Rider http://commonsensesecurity.info There are 10 kinds of people in the world: Those who understand binary and those who don't. From ssharkins at setel.com Sun Aug 27 09:48:32 2006 From: ssharkins at setel.com (Susan Harkins) Date: Sun, 27 Aug 2006 10:48:32 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: Message-ID: <001e01c6c9e7$de624b90$9cb82ad1@SUSANONE> So, are you trying to make a remote connection ? Susan H. I'm not sure about the login issue, but a good way to transfer the DB is to Detach it on the old server, copy the MDF and LDF files to the new server and then attach it. This will preserve all of the data, and has worked for me several times. On 8/27/06, JWColby wrote: > I have just finished rebuilding a machine (new motherboard) and need > to transfer a large SQL Server database to that new server. The two > servers can see each other (shared folders), but ... > > I cannot register the other SQL Servers, getting an error "Login > failed for 'MachineName\Guest'. I get this error on either machine > when trying to register the SQL Server on the other machine. My login > user / password is the same on both machines. Both databases were > installed using "Windows Authentication" rather than "SQL Server Authentication". From ssharkins at setel.com Sun Aug 27 09:49:51 2006 From: ssharkins at setel.com (Susan Harkins) Date: Sun, 27 Aug 2006 10:49:51 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: Message-ID: <001f01c6c9e8$0df714d0$9cb82ad1@SUSANONE> John... Right-click the service, choose Properties and view the Edit Server Registration Properties -- might get a clue there. Susan H. I'm not sure about the login issue, but a good way to transfer the DB is to Detach it on the old server, copy the MDF and LDF files to the new server and then attach it. This will preserve all of the data, and has worked for me several times. On 8/27/06, JWColby wrote: > I have just finished rebuilding a machine (new motherboard) and need > to transfer a large SQL Server database to that new server. The two > servers can see each other (shared folders), but ... > > I cannot register the other SQL Servers, getting an error "Login > failed for 'MachineName\Guest'. I get this error on either machine > when trying to register the SQL Server on the other machine. My login > user / password is the same on both machines. Both databases were > installed using "Windows Authentication" rather than "SQL Server Authentication". From artful at rogers.com Sun Aug 27 11:23:06 2006 From: artful at rogers.com (artful at rogers.com) Date: Sun, 27 Aug 2006 09:23:06 -0700 (PDT) Subject: [dba-SQLServer] [AccessD] Transferring a database to another SQL Server In-Reply-To: <0J4N00ISMZG6WT40@l-daemon> Message-ID: <20060827162307.37721.qmail@web88206.mail.re2.yahoo.com> In addition, SQL 2005 has "remote access" turned off by default. Go into Configuration Manager and have a look there. My guess is that this is your problem. Arthur ----- Original Message ---- From: Jim Lawrence To: Access Developers discussion and problem solving Sent: Sunday, August 27, 2006 12:08:30 PM Subject: Re: [AccessD] Transferring a database to another SQL Server Hi John: 1. Would you have an IIS server running on both computers? 2. Are both MS SQLs using different ports (1433 default)? 3. The 'guest' account is turned off by default on new installs; would this be the case on the new computer? 4. Do you have a personal firewall setup on either/both computers that may be blocking the MS SQL ports? HTH Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Sunday, August 27, 2006 6:38 AM To: dba-sqlserver at databaseadvisors.com Cc: 'Access Developers discussion and problem solving' Subject: [AccessD] Transferring a database to another SQL Server I have just finished rebuilding a machine (new motherboard) and need to transfer a large SQL Server database to that new server. The two servers can see each other (shared folders), but ... I cannot register the other SQL Servers, getting an error "Login failed for 'MachineName\Guest'. I get this error on either machine when trying to register the SQL Server on the other machine. My login user / password is the same on both machines. Both databases were installed using "Windows Authentication" rather than "SQL Server Authentication". Any ideas? John W. Colby Colby Consulting www.ColbyConsulting.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com From jwcolby at colbyconsulting.com Sun Aug 27 12:26:31 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Sun, 27 Aug 2006 13:26:31 -0400 Subject: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server In-Reply-To: <20060827162307.37721.qmail@web88206.mail.re2.yahoo.com> Message-ID: <000e01c6c9fd$f0e583c0$657aa8c0@m6805> SQL Server 2K John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Sunday, August 27, 2006 12:23 PM To: Access Developers discussion and problem solving Cc: dba-SQLServer Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server In addition, SQL 2005 has "remote access" turned off by default. Go into Configuration Manager and have a look there. My guess is that this is your problem. Arthur ----- Original Message ---- From: Jim Lawrence To: Access Developers discussion and problem solving Sent: Sunday, August 27, 2006 12:08:30 PM Subject: Re: [AccessD] Transferring a database to another SQL Server Hi John: 1. Would you have an IIS server running on both computers? 2. Are both MS SQLs using different ports (1433 default)? 3. The 'guest' account is turned off by default on new installs; would this be the case on the new computer? 4. Do you have a personal firewall setup on either/both computers that may be blocking the MS SQL ports? HTH Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Sunday, August 27, 2006 6:38 AM To: dba-sqlserver at databaseadvisors.com Cc: 'Access Developers discussion and problem solving' Subject: [AccessD] Transferring a database to another SQL Server I have just finished rebuilding a machine (new motherboard) and need to transfer a large SQL Server database to that new server. The two servers can see each other (shared folders), but ... I cannot register the other SQL Servers, getting an error "Login failed for 'MachineName\Guest'. I get this error on either machine when trying to register the SQL Server on the other machine. My login user / password is the same on both machines. Both databases were installed using "Windows Authentication" rather than "SQL Server Authentication". Any ideas? John W. Colby Colby Consulting www.ColbyConsulting.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: 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 artful at rogers.com Sun Aug 27 15:44:47 2006 From: artful at rogers.com (artful at rogers.com) Date: Sun, 27 Aug 2006 13:44:47 -0700 (PDT) Subject: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server In-Reply-To: <000e01c6c9fd$f0e583c0$657aa8c0@m6805> Message-ID: <20060827204447.61541.qmail@web88201.mail.re2.yahoo.com> In that case, the simplest means is detach the db, copy it to a memory stick or something, then copy it to the data directory of the new machine, and finally attach it. This sidesteps the problem of why you cannot see each box from the other, but one thing at a time. Presumably the most important thing is to get the db there. Depending on the size of the MDF and LDF files, you may need to ZIP or RAR them first, then extract them upon arrival. If space on the stick or CD or DVD is really a problem, you could skip or truncate the Log file. hth. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Sunday, August 27, 2006 1:26:31 PM Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server SQL Server 2K John W. Colby Colby Consulting www.ColbyConsulting.com From andrew.haslett at ilc.gov.au Sun Aug 27 16:04:10 2006 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Mon, 28 Aug 2006 06:34:10 +0930 Subject: [dba-SQLServer] Transferring a database to another SQL Server Message-ID: <0A870603A2A816459078203FC07F4CD2BE4034@adl01s055.ilcorp.gov.au> Have you setup security on the new box? -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Sunday, 27 August 2006 11:08 PM To: dba-sqlserver at databaseadvisors.com Cc: 'Access Developers discussion and problem solving' Subject: [dba-SQLServer] Transferring a database to another SQL Server I have just finished rebuilding a machine (new motherboard) and need to transfer a large SQL Server database to that new server. The two servers can see each other (shared folders), but ... I cannot register the other SQL Servers, getting an error "Login failed for 'MachineName\Guest'. I get this error on either machine when trying to register the SQL Server on the other machine. My login user / password is the same on both machines. Both databases were installed using "Windows Authentication" rather than "SQL Server Authentication". Any ideas? John W. Colby Colby Consulting www.ColbyConsulting.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 andrew.haslett at ilc.gov.au Sun Aug 27 17:42:36 2006 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Mon, 28 Aug 2006 08:12:36 +0930 Subject: [dba-SQLServer] Transferring a database to another SQL Server Message-ID: <0A870603A2A816459078203FC07F4CD2BE4035@adl01s055.ilcorp.gov.au> Ie - I meant the Login rights of your account in SQL Server. You'll need to give your Windows account login permissions to the SQL Server and to your database. You won't be able to log into your box from another machine using Windows Auth unless you're using a domain. Much easier to just setup SQL Authentication and specify a username and password. Also, might pay to remove and re-add DB-Level permissions as even though they may be the same as the old box, they don't automatically map to the SQL login. Search Books-On-Line for a stored proc called sp_change_users_login, although from memory, this was for SQL logins, not Integrated Auth logins. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, 28 August 2006 6:34 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Have you setup security on the new box? -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Sunday, 27 August 2006 11:08 PM To: dba-sqlserver at databaseadvisors.com Cc: 'Access Developers discussion and problem solving' Subject: [dba-SQLServer] Transferring a database to another SQL Server I have just finished rebuilding a machine (new motherboard) and need to transfer a large SQL Server database to that new server. The two servers can see each other (shared folders), but ... I cannot register the other SQL Servers, getting an error "Login failed for 'MachineName\Guest'. I get this error on either machine when trying to register the SQL Server on the other machine. My login user / password is the same on both machines. Both databases were installed using "Windows Authentication" rather than "SQL Server Authentication". Any ideas? John W. Colby Colby Consulting www.ColbyConsulting.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 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 Sun Aug 27 20:36:59 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Sun, 27 Aug 2006 21:36:59 -0400 Subject: [dba-SQLServer] [AccessD] Transferring a database to anotherSQLServer In-Reply-To: <20060827204447.61541.qmail@web88201.mail.re2.yahoo.com> Message-ID: <001a01c6ca42$75932e30$657aa8c0@m6805> >If space on the stick or CD or DVD is really a problem, you could skip or truncate the Log file. LOL, I have three files. One is 150 GIG, the other two are 140 GIG but only 56 GIG actually used. Unlikely to fit on a memory stick, or a dvd - even zipped. But if I can detach them, then just move the entire disks and then reattach that would be fine. I really need to get these disks moved to the new machine anyway. Which leaves me with the issue of why EM is not able to attach to the database on the other machine. This was working in the past. These are simple Windows XP Pro boxes, identical username / password on all the boxes. Workgroup, no domains. Simple file sharing is working, I can see directories on the other boxes. Each machine has a SQL Server running. Each machine can see its own local database, and I can see the other machine (it comes up in a list of machines / databases to connect to) but the connect itself fails with a "can't use guest". All of them are set up to use Windows Server authentication. Why is it trying to use Guest as opposed to using the current logged in user on the current machine (jwcolby)? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Sunday, August 27, 2006 4:45 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQLServer In that case, the simplest means is detach the db, copy it to a memory stick or something, then copy it to the data directory of the new machine, and finally attach it. This sidesteps the problem of why you cannot see each box from the other, but one thing at a time. Presumably the most important thing is to get the db there. Depending on the size of the MDF and LDF files, you may need to ZIP or RAR them first, then extract them upon arrival. If space on the stick or CD or DVD is really a problem, you could skip or truncate the Log file. hth. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Sunday, August 27, 2006 1:26:31 PM Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server SQL Server 2K John W. Colby Colby Consulting www.ColbyConsulting.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From michael at ddisolutions.com.au Sun Aug 27 22:52:26 2006 From: michael at ddisolutions.com.au (Michael Maddison) Date: Mon, 28 Aug 2006 13:52:26 +1000 Subject: [dba-SQLServer] [AccessD] Transferring a database toanotherSQLServer Message-ID: <59A61174B1F5B54B97FD4ADDE71E7D0116A9B7@ddi-01.DDI.local> Why is it trying to use Guest as opposed to using the current logged in user on the current machine (jwcolby)? Because it is expecting a domain user and then defaulting to guest when there is no domain user??? I would try using SQL user logins (sa? or another sys admin acc) Set up a sa account on the target SQL server instance. Attach the target SQL instance to EM using sa (on the base (non target) instance) If that works you should be ok. cheers Michael M John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Sunday, August 27, 2006 4:45 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQLServer In that case, the simplest means is detach the db, copy it to a memory stick or something, then copy it to the data directory of the new machine, and finally attach it. This sidesteps the problem of why you cannot see each box from the other, but one thing at a time. Presumably the most important thing is to get the db there. Depending on the size of the MDF and LDF files, you may need to ZIP or RAR them first, then extract them upon arrival. If space on the stick or CD or DVD is really a problem, you could skip or truncate the Log file. hth. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Sunday, August 27, 2006 1:26:31 PM Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server SQL Server 2K John W. Colby Colby Consulting www.ColbyConsulting.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 andrew.haslett at ilc.gov.au Mon Aug 28 02:15:09 2006 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Mon, 28 Aug 2006 16:45:09 +0930 Subject: [dba-SQLServer] [AccessD] Transferring a database toanotherSQLServer Message-ID: <0A870603A2A816459078203FC07F4CD2BE4038@adl01s055.ilcorp.gov.au> Turn *off* simple file sharing. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, 28 August 2006 11:07 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database toanotherSQLServer >If space on the stick or CD or DVD is really a problem, you could skip >or truncate the Log file. LOL, I have three files. One is 150 GIG, the other two are 140 GIG but only 56 GIG actually used. Unlikely to fit on a memory stick, or a dvd - even zipped. But if I can detach them, then just move the entire disks and then reattach that would be fine. I really need to get these disks moved to the new machine anyway. Which leaves me with the issue of why EM is not able to attach to the database on the other machine. This was working in the past. These are simple Windows XP Pro boxes, identical username / password on all the boxes. Workgroup, no domains. Simple file sharing is working, I can see directories on the other boxes. Each machine has a SQL Server running. Each machine can see its own local database, and I can see the other machine (it comes up in a list of machines / databases to connect to) but the connect itself fails with a "can't use guest". All of them are set up to use Windows Server authentication. Why is it trying to use Guest as opposed to using the current logged in user on the current machine (jwcolby)? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Sunday, August 27, 2006 4:45 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQLServer In that case, the simplest means is detach the db, copy it to a memory stick or something, then copy it to the data directory of the new machine, and finally attach it. This sidesteps the problem of why you cannot see each box from the other, but one thing at a time. Presumably the most important thing is to get the db there. Depending on the size of the MDF and LDF files, you may need to ZIP or RAR them first, then extract them upon arrival. If space on the stick or CD or DVD is really a problem, you could skip or truncate the Log file. hth. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Sunday, August 27, 2006 1:26:31 PM Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server SQL Server 2K John W. Colby Colby Consulting www.ColbyConsulting.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 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 Mon Aug 28 07:16:23 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 28 Aug 2006 08:16:23 -0400 Subject: [dba-SQLServer] [AccessD] Transferring a databasetoanotherSQLServer In-Reply-To: <0A870603A2A816459078203FC07F4CD2BE4038@adl01s055.ilcorp.gov.au> Message-ID: <002b01c6ca9b$c83eac50$657aa8c0@m6805> This is a network in my home office. Why do I need to turn Simple File Sharing off, and if I need to do that, how do I replace it's functionality? With Simple File Sharing OFF my workstations can no longer see each other and I get "no permission to use" error messages when trying to browse for shares in Explorer. Furthermore, with SFS off, the other machines do not show up when browsing in EM for other servers. I seem to remember that I had to set up the databases to use "mixed mode" login, but that option is not readily available to me anywhere. The only two choices on these two machines are straight "windows login" or "SQL Server" login. How do I turn on Mixed Mode? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 28, 2006 3:15 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a databasetoanotherSQLServer Turn *off* simple file sharing. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, 28 August 2006 11:07 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database toanotherSQLServer >If space on the stick or CD or DVD is really a problem, you could skip >or truncate the Log file. LOL, I have three files. One is 150 GIG, the other two are 140 GIG but only 56 GIG actually used. Unlikely to fit on a memory stick, or a dvd - even zipped. But if I can detach them, then just move the entire disks and then reattach that would be fine. I really need to get these disks moved to the new machine anyway. Which leaves me with the issue of why EM is not able to attach to the database on the other machine. This was working in the past. These are simple Windows XP Pro boxes, identical username / password on all the boxes. Workgroup, no domains. Simple file sharing is working, I can see directories on the other boxes. Each machine has a SQL Server running. Each machine can see its own local database, and I can see the other machine (it comes up in a list of machines / databases to connect to) but the connect itself fails with a "can't use guest". All of them are set up to use Windows Server authentication. Why is it trying to use Guest as opposed to using the current logged in user on the current machine (jwcolby)? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Sunday, August 27, 2006 4:45 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQLServer In that case, the simplest means is detach the db, copy it to a memory stick or something, then copy it to the data directory of the new machine, and finally attach it. This sidesteps the problem of why you cannot see each box from the other, but one thing at a time. Presumably the most important thing is to get the db there. Depending on the size of the MDF and LDF files, you may need to ZIP or RAR them first, then extract them upon arrival. If space on the stick or CD or DVD is really a problem, you could skip or truncate the Log file. hth. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Sunday, August 27, 2006 1:26:31 PM Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server SQL Server 2K John W. Colby Colby Consulting www.ColbyConsulting.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 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 stuart at lexacorp.com.pg Mon Aug 28 07:33:45 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Mon, 28 Aug 2006 22:33:45 +1000 Subject: [dba-SQLServer] [AccessD] Transferring a databasetoanotherSQLServer In-Reply-To: <002b01c6ca9b$c83eac50$657aa8c0@m6805> References: <0A870603A2A816459078203FC07F4CD2BE4038@adl01s055.ilcorp.gov.au>, <002b01c6ca9b$c83eac50$657aa8c0@m6805> Message-ID: <44F36F49.24807.6863EBDA@stuart.lexacorp.com.pg> On 28 Aug 2006 at 8:16, JWColby wrote: > This is a network in my home office. Why do I need to turn Simple File > Sharing off, and if I need to do that, how do I replace it's functionality? > > With Simple File Sharing OFF my workstations can no longer see each other > and I get "no permission to use" error messages when trying to browse for > shares in Explorer. > > Furthermore, with SFS off, the other machines do not show up when browsing > in EM for other servers. > You need to turn "Simple File Sharing" off, not turn "File Sharing" off. In yet another attempt to cater to the masses, MS introduced a new simplified type of file sharing in XP as an alternative to the standard file sharing that we have always used. They call this new system "Simple File Sharing". XP Home always uses Simple File Sharing. XP Pro defaults to Simple File Sharing if you are using a peer to peer network (no domain controller). If you are configured to use Simple File Sharing, remote users always authenticate using the Guest account and you run into the sort or problem you are facing. To switch to classic file sharing, 1. Double-click My Computer on the desktop. 2. On the Tools menu, click Folder Options. 3. Click the View tab, and then de-select "Use Simple File Sharing" Now you can set proper permissions on your resources and authenticate using accounts with appropriate permissions. See http://support.microsoft.com/kb/304040/ for all the gory details -- Stuart From artful at rogers.com Mon Aug 28 07:40:59 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 28 Aug 2006 05:40:59 -0700 (PDT) Subject: [dba-SQLServer] [AccessD] Transferring a databasetoanotherSQLServer In-Reply-To: <002b01c6ca9b$c83eac50$657aa8c0@m6805> Message-ID: <20060828124059.8751.qmail@web88203.mail.re2.yahoo.com> SQL Server Login is mixed mode, IIRC. It simply means that a Windows login is not enough. In addition, you need a SQL user/password. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Monday, August 28, 2006 8:16:23 AM Subject: Re: [dba-SQLServer] [AccessD] Transferring a databasetoanotherSQLServer This is a network in my home office. Why do I need to turn Simple File Sharing off, and if I need to do that, how do I replace it's functionality? With Simple File Sharing OFF my workstations can no longer see each other and I get "no permission to use" error messages when trying to browse for shares in Explorer. Furthermore, with SFS off, the other machines do not show up when browsing in EM for other servers. I seem to remember that I had to set up the databases to use "mixed mode" login, but that option is not readily available to me anywhere. The only two choices on these two machines are straight "windows login" or "SQL Server" login. How do I turn on Mixed Mode? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 28, 2006 3:15 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a databasetoanotherSQLServer Turn *off* simple file sharing. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, 28 August 2006 11:07 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database toanotherSQLServer >If space on the stick or CD or DVD is really a problem, you could skip >or truncate the Log file. LOL, I have three files. One is 150 GIG, the other two are 140 GIG but only 56 GIG actually used. Unlikely to fit on a memory stick, or a dvd - even zipped. But if I can detach them, then just move the entire disks and then reattach that would be fine. I really need to get these disks moved to the new machine anyway. Which leaves me with the issue of why EM is not able to attach to the database on the other machine. This was working in the past. These are simple Windows XP Pro boxes, identical username / password on all the boxes. Workgroup, no domains. Simple file sharing is working, I can see directories on the other boxes. Each machine has a SQL Server running. Each machine can see its own local database, and I can see the other machine (it comes up in a list of machines / databases to connect to) but the connect itself fails with a "can't use guest". All of them are set up to use Windows Server authentication. Why is it trying to use Guest as opposed to using the current logged in user on the current machine (jwcolby)? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Sunday, August 27, 2006 4:45 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQLServer In that case, the simplest means is detach the db, copy it to a memory stick or something, then copy it to the data directory of the new machine, and finally attach it. This sidesteps the problem of why you cannot see each box from the other, but one thing at a time. Presumably the most important thing is to get the db there. Depending on the size of the MDF and LDF files, you may need to ZIP or RAR them first, then extract them upon arrival. If space on the stick or CD or DVD is really a problem, you could skip or truncate the Log file. hth. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Sunday, August 27, 2006 1:26:31 PM Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server SQL Server 2K John W. Colby Colby Consulting www.ColbyConsulting.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 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 From jwcolby at colbyconsulting.com Mon Aug 28 07:46:41 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 28 Aug 2006 08:46:41 -0400 Subject: [dba-SQLServer] [AccessD] Transferring a databasetoanotherSQLServer In-Reply-To: <0A870603A2A816459078203FC07F4CD2BE4038@adl01s055.ilcorp.gov.au> Message-ID: <002c01c6caa0$032d8210$657aa8c0@m6805> Having turned off simple file sharing, I now seem to be incapable of turning it back on!!! 8-( I turned it back on via the Explorer / tools / folder options, but all computers now give an error "ColbyConsulting not accessible. You might not have permissions... Etc blah blah". I have rebooted all machines after turning SFS back on but to no avail. Likewise, SQL Server can no longer see the other machines. What a PITA. How do I get my workgroup / SFS back? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 28, 2006 3:15 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a databasetoanotherSQLServer Turn *off* simple file sharing. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, 28 August 2006 11:07 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database toanotherSQLServer >If space on the stick or CD or DVD is really a problem, you could skip >or truncate the Log file. LOL, I have three files. One is 150 GIG, the other two are 140 GIG but only 56 GIG actually used. Unlikely to fit on a memory stick, or a dvd - even zipped. But if I can detach them, then just move the entire disks and then reattach that would be fine. I really need to get these disks moved to the new machine anyway. Which leaves me with the issue of why EM is not able to attach to the database on the other machine. This was working in the past. These are simple Windows XP Pro boxes, identical username / password on all the boxes. Workgroup, no domains. Simple file sharing is working, I can see directories on the other boxes. Each machine has a SQL Server running. Each machine can see its own local database, and I can see the other machine (it comes up in a list of machines / databases to connect to) but the connect itself fails with a "can't use guest". All of them are set up to use Windows Server authentication. Why is it trying to use Guest as opposed to using the current logged in user on the current machine (jwcolby)? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Sunday, August 27, 2006 4:45 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQLServer In that case, the simplest means is detach the db, copy it to a memory stick or something, then copy it to the data directory of the new machine, and finally attach it. This sidesteps the problem of why you cannot see each box from the other, but one thing at a time. Presumably the most important thing is to get the db there. Depending on the size of the MDF and LDF files, you may need to ZIP or RAR them first, then extract them upon arrival. If space on the stick or CD or DVD is really a problem, you could skip or truncate the Log file. hth. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Sunday, August 27, 2006 1:26:31 PM Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server SQL Server 2K John W. Colby Colby Consulting www.ColbyConsulting.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 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 darrend at nimble.com.au Mon Aug 28 07:50:34 2006 From: darrend at nimble.com.au (Darren DICK) Date: Mon, 28 Aug 2006 22:50:34 +1000 Subject: [dba-SQLServer] See who has logged on Message-ID: <20060828125042.UCEQ11832.omta05sl.mx.bigpond.com@DENZILLAP> Hi All Is it possible to find out who has logged on over a period of time into our SQL Server? I know I can use EntManager to look into Management|Current Activity|Process info And that will tell me 'who is on' at that given moment by logonname (User) or by machine name (Host) But is there a way I can interrogate some log or some table via say...Query Analyser or by some other method - Just so I can see the same information as "Process Info" gives me but in an archive kind of way? Many thanks Have a great day y'all Darren From jwcolby at colbyconsulting.com Mon Aug 28 07:59:31 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 28 Aug 2006 08:59:31 -0400 Subject: [dba-SQLServer] [AccessD] Transferring adatabasetoanotherSQLServer In-Reply-To: <44F36F49.24807.6863EBDA@stuart.lexacorp.com.pg> Message-ID: <002d01c6caa1$ce32d0e0$657aa8c0@m6805> >In yet another attempt to cater to the masses... I AM the masses. >You need to turn "Simple File Sharing" off, not turn "File Sharing" off. I have no idea how to turn "file sharing" on / off. I have turned "simple file sharing" off with the result that the poor huddled masses can no longer see the files on the poor huddled masses other machines, which makes the poor huddled masses most unhappy. Furthermore, in SQL Server EM with SFS turned off, the other machines no longer even show up as available to register a server on, which also makes the poor huddled masses most unhappy. It seems that by following the simple edict "turn off SFS" the poor huddled masses have royally screwed up the private little workgroup in the home office, and can not seem to get it back. Sigh. DETAILED INSTRUCTIONS on how to COMPLETELY implement something are so much appreciated. The poor huddled masses are called the poor huddled masses precisely because they have not spent the hundreds of hours required to become OS administrators. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Monday, August 28, 2006 8:34 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring adatabasetoanotherSQLServer On 28 Aug 2006 at 8:16, JWColby wrote: > This is a network in my home office. Why do I need to turn Simple > File Sharing off, and if I need to do that, how do I replace it's functionality? > > With Simple File Sharing OFF my workstations can no longer see each > other and I get "no permission to use" error messages when trying to > browse for shares in Explorer. > > Furthermore, with SFS off, the other machines do not show up when > browsing in EM for other servers. > You need to turn "Simple File Sharing" off, not turn "File Sharing" off. In yet another attempt to cater to the masses, MS introduced a new simplified type of file sharing in XP as an alternative to the standard file sharing that we have always used. They call this new system "Simple File Sharing". XP Home always uses Simple File Sharing. XP Pro defaults to Simple File Sharing if you are using a peer to peer network (no domain controller). If you are configured to use Simple File Sharing, remote users always authenticate using the Guest account and you run into the sort or problem you are facing. To switch to classic file sharing, 1. Double-click My Computer on the desktop. 2. On the Tools menu, click Folder Options. 3. Click the View tab, and then de-select "Use Simple File Sharing" Now you can set proper permissions on your resources and authenticate using accounts with appropriate permissions. See http://support.microsoft.com/kb/304040/ for all the gory details -- Stuart _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From michael at ddisolutions.com.au Mon Aug 28 08:08:20 2006 From: michael at ddisolutions.com.au (Michael Maddison) Date: Mon, 28 Aug 2006 23:08:20 +1000 Subject: [dba-SQLServer] See who has logged on Message-ID: <59A61174B1F5B54B97FD4ADDE71E7D0116A9BC@ddi-01.DDI.local> Hi Darren, Seems you need to set the audit level (none by default) in the server properties tab, under security. You then need to use profiler to keep track of the events you want to trace. ie logon, logout, logon failure etc... Never done it myself but BOL has the answers, look under audit. cheers Michael M -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK Sent: Monday, 28 August 2006 10:51 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] See who has logged on Hi All Is it possible to find out who has logged on over a period of time into our SQL Server? I know I can use EntManager to look into Management|Current Activity|Process info And that will tell me 'who is on' at that given moment by logonname (User) or by machine name (Host) But is there a way I can interrogate some log or some table via say...Query Analyser or by some other method - Just so I can see the same information as "Process Info" gives me but in an archive kind of way? Many thanks Have a great day y'all Darren _______________________________________________ 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 Aug 28 09:23:45 2006 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Mon, 28 Aug 2006 23:53:45 +0930 Subject: [dba-SQLServer] [AccessD] TransferringadatabasetoanotherSQLServer Message-ID: <0A870603A2A816459078203FC07F4CD2BE403A@adl01s055.ilcorp.gov.au> Perhaps the advice provided months (a year?) ago when I recall this same (or similar) problem arose, recommending that this type of thing should not be attempted without sufficient training / experience / professional assistance, was good advice? Simple file sharing is the reason you could not connect. Steps to disable it were posted in a previous post. Enabling it is as simple as checking the box instead of unchecking it.. A 1 minute search on google will further provide these details. Furthermore, the documentation for SQL Server - Books On Line, by far the best product documentation that MS has provided, will provide you with plenty of easy to find material on configuring security in SQL Server, which will detail the issues you are requesting on SQL / Windows Authentication. Sorry if this sounds harsh but there are reasons that this stuff is taught in detailed courses -> it's just not something you can pick up and try to do off the cuff without some experience or at least willingness to investigate the documentation provided. And when the (correct) help we provide is thrown back at us with "you screwed my network" then, with all respect -> good luck with it yourself.. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, 28 August 2006 10:30 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] TransferringadatabasetoanotherSQLServer >In yet another attempt to cater to the masses... I AM the masses. >You need to turn "Simple File Sharing" off, not turn "File Sharing" off. I have no idea how to turn "file sharing" on / off. I have turned "simple file sharing" off with the result that the poor huddled masses can no longer see the files on the poor huddled masses other machines, which makes the poor huddled masses most unhappy. Furthermore, in SQL Server EM with SFS turned off, the other machines no longer even show up as available to register a server on, which also makes the poor huddled masses most unhappy. It seems that by following the simple edict "turn off SFS" the poor huddled masses have royally screwed up the private little workgroup in the home office, and can not seem to get it back. Sigh. DETAILED INSTRUCTIONS on how to COMPLETELY implement something are so much appreciated. The poor huddled masses are called the poor huddled masses precisely because they have not spent the hundreds of hours required to become OS administrators. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Monday, August 28, 2006 8:34 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring adatabasetoanotherSQLServer On 28 Aug 2006 at 8:16, JWColby wrote: > This is a network in my home office. Why do I need to turn Simple > File Sharing off, and if I need to do that, how do I replace it's functionality? > > With Simple File Sharing OFF my workstations can no longer see each > other and I get "no permission to use" error messages when trying to > browse for shares in Explorer. > > Furthermore, with SFS off, the other machines do not show up when > browsing in EM for other servers. > You need to turn "Simple File Sharing" off, not turn "File Sharing" off. In yet another attempt to cater to the masses, MS introduced a new simplified type of file sharing in XP as an alternative to the standard file sharing that we have always used. They call this new system "Simple File Sharing". XP Home always uses Simple File Sharing. XP Pro defaults to Simple File Sharing if you are using a peer to peer network (no domain controller). If you are configured to use Simple File Sharing, remote users always authenticate using the Guest account and you run into the sort or problem you are facing. To switch to classic file sharing, 1. Double-click My Computer on the desktop. 2. On the Tools menu, click Folder Options. 3. Click the View tab, and then de-select "Use Simple File Sharing" Now you can set proper permissions on your resources and authenticate using accounts with appropriate permissions. See http://support.microsoft.com/kb/304040/ for all the gory details -- Stuart _______________________________________________ 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 Mon Aug 28 10:03:06 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 28 Aug 2006 11:03:06 -0400 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <0A870603A2A816459078203FC07F4CD2BE403A@adl01s055.ilcorp.gov.au> Message-ID: <000801c6cab3$120a9d00$657aa8c0@m6805> Haslett, this is an ACCESS group / SQL Server group, Not a Network Admin group. >Sorry if this sounds harsh but there are reasons that this stuff is taught in detailed courses -> it's just not something you can pick up and try to do off the cuff without some experience or at least willingness to investigate the documentation provided. If that is the case, then throwing out advice like "turn off simple file sharing" is inappropriate advice, at least without a "this will royally screw up your private workgroup file sharing (and not even get you what you are after)" warning. Sorry if THAT sounds harsh, but I am NOT a Notwork Admin (nor are many others on this list), and apparently my workgroup file sharing IS SCREWED UP because I blithely followed "correct" advice. Not only did it screw up my file sharing (which BTW is still not working) but it did NOT provide sufficient assistance to get my the SQL Server registration working. Is this mail list not supposed to be about coming here to ask advice from people more experienced than myself? Is the result of listening to such advice SUPPOSED to be screwing up my workgroup / file sharing and NOT EVEN GETTING what I was asking about answered? If that is the case I suppose I have very little use for this group! And OBTW, I am willing to RTFM. I have been reading the manual all of my adult life! SQL Server is not my strong suite to say the least, and (apparently) security and SQL Server is not a trivial subject. And having RTFM, I am still without my file sharing. But I do appreciate your understanding. I would even bow in your general direction but I don't know where you are. Thanks very much for your (correct) advice, I can't begin to tell you how much help it was. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 28, 2006 10:24 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer Perhaps the advice provided months (a year?) ago when I recall this same (or similar) problem arose, recommending that this type of thing should not be attempted without sufficient training / experience / professional assistance, was good advice? Simple file sharing is the reason you could not connect. Steps to disable it were posted in a previous post. Enabling it is as simple as checking the box instead of unchecking it.. A 1 minute search on google will further provide these details. Furthermore, the documentation for SQL Server - Books On Line, by far the best product documentation that MS has provided, will provide you with plenty of easy to find material on configuring security in SQL Server, which will detail the issues you are requesting on SQL / Windows Authentication. Sorry if this sounds harsh but there are reasons that this stuff is taught in detailed courses -> it's just not something you can pick up and try to do off the cuff without some experience or at least willingness to investigate the documentation provided. And when the (correct) help we provide is thrown back at us with "you screwed my network" then, with all respect -> good luck with it yourself.. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, 28 August 2006 10:30 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] TransferringadatabasetoanotherSQLServer >In yet another attempt to cater to the masses... I AM the masses. >You need to turn "Simple File Sharing" off, not turn "File Sharing" off. I have no idea how to turn "file sharing" on / off. I have turned "simple file sharing" off with the result that the poor huddled masses can no longer see the files on the poor huddled masses other machines, which makes the poor huddled masses most unhappy. Furthermore, in SQL Server EM with SFS turned off, the other machines no longer even show up as available to register a server on, which also makes the poor huddled masses most unhappy. It seems that by following the simple edict "turn off SFS" the poor huddled masses have royally screwed up the private little workgroup in the home office, and can not seem to get it back. Sigh. DETAILED INSTRUCTIONS on how to COMPLETELY implement something are so much appreciated. The poor huddled masses are called the poor huddled masses precisely because they have not spent the hundreds of hours required to become OS administrators. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Monday, August 28, 2006 8:34 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring adatabasetoanotherSQLServer On 28 Aug 2006 at 8:16, JWColby wrote: > This is a network in my home office. Why do I need to turn Simple > File Sharing off, and if I need to do that, how do I replace it's functionality? > > With Simple File Sharing OFF my workstations can no longer see each > other and I get "no permission to use" error messages when trying to > browse for shares in Explorer. > > Furthermore, with SFS off, the other machines do not show up when > browsing in EM for other servers. > You need to turn "Simple File Sharing" off, not turn "File Sharing" off. In yet another attempt to cater to the masses, MS introduced a new simplified type of file sharing in XP as an alternative to the standard file sharing that we have always used. They call this new system "Simple File Sharing". XP Home always uses Simple File Sharing. XP Pro defaults to Simple File Sharing if you are using a peer to peer network (no domain controller). If you are configured to use Simple File Sharing, remote users always authenticate using the Guest account and you run into the sort or problem you are facing. To switch to classic file sharing, 1. Double-click My Computer on the desktop. 2. On the Tools menu, click Folder Options. 3. Click the View tab, and then de-select "Use Simple File Sharing" Now you can set proper permissions on your resources and authenticate using accounts with appropriate permissions. See http://support.microsoft.com/kb/304040/ for all the gory details -- Stuart _______________________________________________ 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 stuart at lexacorp.com.pg Mon Aug 28 16:38:08 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Tue, 29 Aug 2006 07:38:08 +1000 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <000801c6cab3$120a9d00$657aa8c0@m6805> References: <0A870603A2A816459078203FC07F4CD2BE403A@adl01s055.ilcorp.gov.au>, <000801c6cab3$120a9d00$657aa8c0@m6805> Message-ID: <44F3EEE0.963.6A564F70@stuart.lexacorp.com.pg> On 28 Aug 2006 at 11:03, JWColby wrote: > If that is the case, then throwing out advice like "turn off simple file > sharing" is inappropriate advice, at least without a "this will royally > screw up your private workgroup file sharing (and not even get you what you > are after)" warning. Sorry if THAT sounds harsh, but I am NOT a Notwork > Admin (nor are many others on this list), and apparently my workgroup file > sharing IS SCREWED UP because I blithely followed "correct" advice. > Sorry, if this sounds harsh, but. If you don't know the basics of network sharing and user management, you shouldn't be trying to set up multi-user or client-server based database applications. As I posted earlier: "....3. Click the View tab, and then de-select "Use Simple File Sharing" Now you can set proper permissions on your resources and authenticate using accounts with appropriate permissions." If you don't understand the last part, you shouldn't be messing with the first part. This is an SQL Server list. I, and apparently others, assumed that anyone who had set up SQL Server installations using WIndows authentication would have learnt at least the basics of Windows network security. Take a look around http://compnetworking.about.com/od/windowsfilesharing/ or spend ten minutes with Google and "Windows file sharing". -- Stuart From andrew.haslett at ilc.gov.au Mon Aug 28 18:16:05 2006 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Tue, 29 Aug 2006 08:46:05 +0930 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer Message-ID: <0A870603A2A816459078203FC07F4CD2BE403B@adl01s055.ilcorp.gov.au> The ability to research, commit to, and undertake a reasonable level of research yourself is a valuable skill in itself. Despite your belief that you continually RTFM, a large majority of answers provided here contain a link or reference to Books On Line or other easily accessible material online.. Why is this do you think??? I vary rarely give 'step by step / line by line' response that you seem to demand, in any of the forums I am a member of. > I'm more than willing to point users in the right direction, provide reasoning & my experiences, hoping that they will learn to help themselves (fishing rod?), thereby developing the abilities to perhaps solve the problem for themselves (and perhaps others) in the future. You've proved my point perfectly.. You asked the exact same question in the past, didn't learn from it, and are now facing the consequences. If someone else wants to provide that level of help to you, then by all means go ahead, but if you want a "DETAILED INSTRUCTIONS on how to COMPLETELY implement something" then pick up a phone, dial a consultant and pay them for it-> someone who will be able to commit the time required to analyse / design / implement and troubleshoot if required. As much as you'd like to think you can get by with support of a community such as this, when you're talking about Network config / RDBMS infrastructure / Security etc, it is simply na?ve to think that you will not encounter problems.. I would assume anyone with the aforementioned research skills, after reading my suggestion to turn off simple file sharing, would at least spend 5 minutes on google finding out how to do it and hopefully picking up a bit of info on what it entails & impacts upon. Similarly, try searching google for "SQL Server Login Failed Simple File Sharing" and I'm sure you'll get a number of results -> not difficult or time consuming IMO.. If this simple change has stuffed up your network, then you must have other issues or (again) not understand what you have configured in your network to start with. (Could also be that your trying to run 'server-recommended' software and systems on a home based operating system...Again not recommended, and again I believed suggested in these forums in the past..) If you're unwilling to commit time into understanding this then fine, pay someone to do it for you. If you are offended with this suggestion or not willing or able to spend the money, then I'm sorry, but you've taken on the wrong projects, which, if memory serves, was raised as a possibility in this forum when you first indicated taking on this line of work. Bit ironic to ignore that advice but then rely on the same source as a primary means to support your business.. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, 29 August 2006 12:33 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer Haslett, this is an ACCESS group / SQL Server group, Not a Network Admin group. >Sorry if this sounds harsh but there are reasons that this stuff is >taught in detailed courses -> it's just not something you can pick up and try to do off the cuff without some experience or at least willingness to investigate the documentation provided. If that is the case, then throwing out advice like "turn off simple file sharing" is inappropriate advice, at least without a "this will royally screw up your private workgroup file sharing (and not even get you what you are after)" warning. Sorry if THAT sounds harsh, but I am NOT a Notwork Admin (nor are many others on this list), and apparently my workgroup file sharing IS SCREWED UP because I blithely followed "correct" advice. Not only did it screw up my file sharing (which BTW is still not working) but it did NOT provide sufficient assistance to get my the SQL Server registration working. Is this mail list not supposed to be about coming here to ask advice from people more experienced than myself? Is the result of listening to such advice SUPPOSED to be screwing up my workgroup / file sharing and NOT EVEN GETTING what I was asking about answered? If that is the case I suppose I have very little use for this group! And OBTW, I am willing to RTFM. I have been reading the manual all of my adult life! SQL Server is not my strong suite to say the least, and (apparently) security and SQL Server is not a trivial subject. And having RTFM, I am still without my file sharing. But I do appreciate your understanding. I would even bow in your general direction but I don't know where you are. Thanks very much for your (correct) advice, I can't begin to tell you how much help it was. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 28, 2006 10:24 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer Perhaps the advice provided months (a year?) ago when I recall this same (or similar) problem arose, recommending that this type of thing should not be attempted without sufficient training / experience / professional assistance, was good advice? Simple file sharing is the reason you could not connect. Steps to disable it were posted in a previous post. Enabling it is as simple as checking the box instead of unchecking it.. A 1 minute search on google will further provide these details. Furthermore, the documentation for SQL Server - Books On Line, by far the best product documentation that MS has provided, will provide you with plenty of easy to find material on configuring security in SQL Server, which will detail the issues you are requesting on SQL / Windows Authentication. Sorry if this sounds harsh but there are reasons that this stuff is taught in detailed courses -> it's just not something you can pick up and try to do off the cuff without some experience or at least willingness to investigate the documentation provided. And when the (correct) help we provide is thrown back at us with "you screwed my network" then, with all respect -> good luck with it yourself.. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, 28 August 2006 10:30 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] TransferringadatabasetoanotherSQLServer >In yet another attempt to cater to the masses... I AM the masses. >You need to turn "Simple File Sharing" off, not turn "File Sharing" off. I have no idea how to turn "file sharing" on / off. I have turned "simple file sharing" off with the result that the poor huddled masses can no longer see the files on the poor huddled masses other machines, which makes the poor huddled masses most unhappy. Furthermore, in SQL Server EM with SFS turned off, the other machines no longer even show up as available to register a server on, which also makes the poor huddled masses most unhappy. It seems that by following the simple edict "turn off SFS" the poor huddled masses have royally screwed up the private little workgroup in the home office, and can not seem to get it back. Sigh. DETAILED INSTRUCTIONS on how to COMPLETELY implement something are so much appreciated. The poor huddled masses are called the poor huddled masses precisely because they have not spent the hundreds of hours required to become OS administrators. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Monday, August 28, 2006 8:34 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring adatabasetoanotherSQLServer On 28 Aug 2006 at 8:16, JWColby wrote: > This is a network in my home office. Why do I need to turn Simple > File Sharing off, and if I need to do that, how do I replace it's functionality? > > With Simple File Sharing OFF my workstations can no longer see each > other and I get "no permission to use" error messages when trying to > browse for shares in Explorer. > > Furthermore, with SFS off, the other machines do not show up when > browsing in EM for other servers. > You need to turn "Simple File Sharing" off, not turn "File Sharing" off. In yet another attempt to cater to the masses, MS introduced a new simplified type of file sharing in XP as an alternative to the standard file sharing that we have always used. They call this new system "Simple File Sharing". XP Home always uses Simple File Sharing. XP Pro defaults to Simple File Sharing if you are using a peer to peer network (no domain controller). If you are configured to use Simple File Sharing, remote users always authenticate using the Guest account and you run into the sort or problem you are facing. To switch to classic file sharing, 1. Double-click My Computer on the desktop. 2. On the Tools menu, click Folder Options. 3. Click the View tab, and then de-select "Use Simple File Sharing" Now you can set proper permissions on your resources and authenticate using accounts with appropriate permissions. See http://support.microsoft.com/kb/304040/ for all the gory details -- Stuart _______________________________________________ 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 jwcolby at colbyconsulting.com Mon Aug 28 18:28:31 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 28 Aug 2006 19:28:31 -0400 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <44F3EEE0.963.6A564F70@stuart.lexacorp.com.pg> Message-ID: <002801c6caf9$adb31520$657aa8c0@m6805> Stuart, >This is an SQL Server list. I, and apparently others, assumed that anyone who had set up SQL Server installations using Windows authentication would have learnt at least the basics of Windows network security. Give me a break Stuart. I am an Access database person. I have a WFW here at my home office. My clients have network administrators to administer their networks. MY (damn few) clients who use SQL Server have admits to administer them. Now, I have set up SQL Server about a dozen times over the last three years. I have never known anything about Networking, and never required knowing that stuff to do the install. Have you never run the install? You come to a page where it asks you which you want and you select one. The SQL Server install continues. How in the world does that equate to "having to know anything damn thing about any damned thing"? For whatever reason, the installs in the past have always just worked, at least in terms of being able to see the other servers from the various workstations. I have no clue why they just worked, nor have I any clue why they are not now. Apparently you and others assume too much. I assumed that this was a friendly Accessed list, where those who know help those who don't. At least it always has been in the past. If it has morphed into a "got to be a guru to be here" list that is fine, just say so and I will leave 'cause I clearly am not a guru. Perhaps I can talk to the powers that be and they will set up another SQL server list for those of us who are not Database / Network Admits. All of us poor schuss who don't know enough to join this list can muddle around at least trying to help each other. Of course that does beg the question of why you are on THIS list in the first place, if you are such a guru you don't need help, and all the others on this list are such gurus they don't need help. Must be a lonely place. I hope the truth is that I can come here and get more than "turn off simple file sharing" in response to an apparently rather complex issue of two Windows XP machines running SQL Server 2k where the servers cannot see each other. >Now you can set proper permissions on your resources and authenticate using accounts with appropriate permissions." >If you don't understand the last part, you shouldn't be messing with the first part. I can see that you are not interested in helping either. And had Haslett stated that in such no nonsense terms I would not have messed with the simple file sharing. At least my machines could see each other's files before, now I don't even have that. Thanks Stuart, your support is much appreciated (I assume). John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Monday, August 28, 2006 5:38 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer On 28 Aug 2006 at 11:03, JWColby wrote: > If that is the case, then throwing out advice like "turn off simple > file sharing" is inappropriate advice, at least without a "this will > royally screw up your private workgroup file sharing (and not even get > you what you are after)" warning. Sorry if THAT sounds harsh, but I > am NOT a Notwork Admin (nor are many others on this list), and > apparently my workgroup file sharing IS SCREWED UP because I blithely followed "correct" advice. > Sorry, if this sounds harsh, but. If you don't know the basics of network sharing and user management, you shouldn't be trying to set up multi-user or client-server based database applications. As I posted earlier: "....3. Click the View tab, and then de-select "Use Simple File Sharing" Now you can set proper permissions on your resources and authenticate using accounts with appropriate permissions." If you don't understand the last part, you shouldn't be messing with the first part. This is an SQL Server list. I, and apparently others, assumed that anyone who had set up SQL Server installations using WIndows authentication would have learnt at least the basics of Windows network security. Take a look around http://compnetworking.about.com/od/windowsfilesharing/ or spend ten minutes with Google and "Windows file sharing". -- Stuart _______________________________________________ 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 Mon Aug 28 19:23:19 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Mon, 28 Aug 2006 17:23:19 -0700 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <0A870603A2A816459078203FC07F4CD2BE403B@adl01s055.ilcorp.gov.au> Message-ID: <0J4Q007QBH29LP10@l-daemon> To whom it may concern: This is a public forum. I could not just stand by while you dress-down a fellow member, regardless the errors of their ways, at such length, so stridently, on such a personal level and public manner. If you wished to so educate someone please do it off-line. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 28, 2006 4:16 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer The ability to research, commit to, and undertake a reasonable level of research yourself is a valuable skill in itself. Despite your belief that you continually RTFM, a large majority of answers provided here contain a link or reference to Books On Line or other easily accessible material online.. Why is this do you think??? I vary rarely give 'step by step / line by line' response that you seem to demand, in any of the forums I am a member of. > I'm more than willing to point users in the right direction, provide reasoning & my experiences, hoping that they will learn to help themselves (fishing rod?), thereby developing the abilities to perhaps solve the problem for themselves (and perhaps others) in the future. You've proved my point perfectly.. You asked the exact same question in the past, didn't learn from it, and are now facing the consequences. If someone else wants to provide that level of help to you, then by all means go ahead, but if you want a "DETAILED INSTRUCTIONS on how to COMPLETELY implement something" then pick up a phone, dial a consultant and pay them for it-> someone who will be able to commit the time required to analyse / design / implement and troubleshoot if required. As much as you'd like to think you can get by with support of a community such as this, when you're talking about Network config / RDBMS infrastructure / Security etc, it is simply na?ve to think that you will not encounter problems.. I would assume anyone with the aforementioned research skills, after reading my suggestion to turn off simple file sharing, would at least spend 5 minutes on google finding out how to do it and hopefully picking up a bit of info on what it entails & impacts upon. Similarly, try searching google for "SQL Server Login Failed Simple File Sharing" and I'm sure you'll get a number of results -> not difficult or time consuming IMO.. If this simple change has stuffed up your network, then you must have other issues or (again) not understand what you have configured in your network to start with. (Could also be that your trying to run 'server-recommended' software and systems on a home based operating system...Again not recommended, and again I believed suggested in these forums in the past..) If you're unwilling to commit time into understanding this then fine, pay someone to do it for you. If you are offended with this suggestion or not willing or able to spend the money, then I'm sorry, but you've taken on the wrong projects, which, if memory serves, was raised as a possibility in this forum when you first indicated taking on this line of work. Bit ironic to ignore that advice but then rely on the same source as a primary means to support your business.. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, 29 August 2006 12:33 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer Haslett, this is an ACCESS group / SQL Server group, Not a Network Admin group. >Sorry if this sounds harsh but there are reasons that this stuff is >taught in detailed courses -> it's just not something you can pick up and try to do off the cuff without some experience or at least willingness to investigate the documentation provided. If that is the case, then throwing out advice like "turn off simple file sharing" is inappropriate advice, at least without a "this will royally screw up your private workgroup file sharing (and not even get you what you are after)" warning. Sorry if THAT sounds harsh, but I am NOT a Notwork Admin (nor are many others on this list), and apparently my workgroup file sharing IS SCREWED UP because I blithely followed "correct" advice. Not only did it screw up my file sharing (which BTW is still not working) but it did NOT provide sufficient assistance to get my the SQL Server registration working. Is this mail list not supposed to be about coming here to ask advice from people more experienced than myself? Is the result of listening to such advice SUPPOSED to be screwing up my workgroup / file sharing and NOT EVEN GETTING what I was asking about answered? If that is the case I suppose I have very little use for this group! And OBTW, I am willing to RTFM. I have been reading the manual all of my adult life! SQL Server is not my strong suite to say the least, and (apparently) security and SQL Server is not a trivial subject. And having RTFM, I am still without my file sharing. But I do appreciate your understanding. I would even bow in your general direction but I don't know where you are. Thanks very much for your (correct) advice, I can't begin to tell you how much help it was. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 28, 2006 10:24 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer Perhaps the advice provided months (a year?) ago when I recall this same (or similar) problem arose, recommending that this type of thing should not be attempted without sufficient training / experience / professional assistance, was good advice? Simple file sharing is the reason you could not connect. Steps to disable it were posted in a previous post. Enabling it is as simple as checking the box instead of unchecking it.. A 1 minute search on google will further provide these details. Furthermore, the documentation for SQL Server - Books On Line, by far the best product documentation that MS has provided, will provide you with plenty of easy to find material on configuring security in SQL Server, which will detail the issues you are requesting on SQL / Windows Authentication. Sorry if this sounds harsh but there are reasons that this stuff is taught in detailed courses -> it's just not something you can pick up and try to do off the cuff without some experience or at least willingness to investigate the documentation provided. And when the (correct) help we provide is thrown back at us with "you screwed my network" then, with all respect -> good luck with it yourself.. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, 28 August 2006 10:30 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] TransferringadatabasetoanotherSQLServer >In yet another attempt to cater to the masses... I AM the masses. >You need to turn "Simple File Sharing" off, not turn "File Sharing" off. I have no idea how to turn "file sharing" on / off. I have turned "simple file sharing" off with the result that the poor huddled masses can no longer see the files on the poor huddled masses other machines, which makes the poor huddled masses most unhappy. Furthermore, in SQL Server EM with SFS turned off, the other machines no longer even show up as available to register a server on, which also makes the poor huddled masses most unhappy. It seems that by following the simple edict "turn off SFS" the poor huddled masses have royally screwed up the private little workgroup in the home office, and can not seem to get it back. Sigh. DETAILED INSTRUCTIONS on how to COMPLETELY implement something are so much appreciated. The poor huddled masses are called the poor huddled masses precisely because they have not spent the hundreds of hours required to become OS administrators. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Monday, August 28, 2006 8:34 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring adatabasetoanotherSQLServer On 28 Aug 2006 at 8:16, JWColby wrote: > This is a network in my home office. Why do I need to turn Simple > File Sharing off, and if I need to do that, how do I replace it's functionality? > > With Simple File Sharing OFF my workstations can no longer see each > other and I get "no permission to use" error messages when trying to > browse for shares in Explorer. > > Furthermore, with SFS off, the other machines do not show up when > browsing in EM for other servers. > You need to turn "Simple File Sharing" off, not turn "File Sharing" off. In yet another attempt to cater to the masses, MS introduced a new simplified type of file sharing in XP as an alternative to the standard file sharing that we have always used. They call this new system "Simple File Sharing". XP Home always uses Simple File Sharing. XP Pro defaults to Simple File Sharing if you are using a peer to peer network (no domain controller). If you are configured to use Simple File Sharing, remote users always authenticate using the Guest account and you run into the sort or problem you are facing. To switch to classic file sharing, 1. Double-click My Computer on the desktop. 2. On the Tools menu, click Folder Options. 3. Click the View tab, and then de-select "Use Simple File Sharing" Now you can set proper permissions on your resources and authenticate using accounts with appropriate permissions. See http://support.microsoft.com/kb/304040/ for all the gory details -- Stuart _______________________________________________ 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 Mon Aug 28 19:47:25 2006 From: andrew.haslett at ilc.gov.au (Haslett, Andrew) Date: Tue, 29 Aug 2006 10:17:25 +0930 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer Message-ID: <0A870603A2A816459078203FC07F4CD2BE403C@adl01s055.ilcorp.gov.au> Suit yourselves - Seems to be a bit of a 'boys' club who are quite happy to ask for advice but only accept it when its something they want to hear, and ignore it otherwise (demonstrated throughout the post below) The points I made in my post apply to anyone looking to undertake similar issues, and will continue to happen until someone has the guts to say it, irrelevant of who it is aimed at (which is how it should be -> on a public forum, favour or protection should not be given to anyone simply because they are friends, associates or seniority). Ask yourself this -> Would you have made the same post Jim, had it not have been aimed at Mr Colby?. Stark realities occasionally need be surfaced in order for them to sink in.. Irrespective of the target or consequences. Was it harsh? Yup. Could it perhaps prevent someone else from making the same mistakes and undertaking projects without due preparation and planning? Hopefully, and therefore I believe useful. John asked Stuart "Why are you here then?". Some of us prefer to assist others, pass on what knowledge they can and in my case attempt to 'help others, help themselves', as opposed to just feeding of others. I know of a number who have left this (and the Access) list in the past, including myself, for similar reasons and 'Matesmenship' in the upper echelons. Please unsubscribe me from the list. Andrew -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Tuesday, 29 August 2006 9:53 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer To whom it may concern: This is a public forum. I could not just stand by while you dress-down a fellow member, regardless the errors of their ways, at such length, so stridently, on such a personal level and public manner. If you wished to so educate someone please do it off-line. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 28, 2006 4:16 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer The ability to research, commit to, and undertake a reasonable level of research yourself is a valuable skill in itself. Despite your belief that you continually RTFM, a large majority of answers provided here contain a link or reference to Books On Line or other easily accessible material online.. Why is this do you think??? I vary rarely give 'step by step / line by line' response that you seem to demand, in any of the forums I am a member of. > I'm more than willing to point users in the right direction, provide reasoning & my experiences, hoping that they will learn to help themselves (fishing rod?), thereby developing the abilities to perhaps solve the problem for themselves (and perhaps others) in the future. You've proved my point perfectly.. You asked the exact same question in the past, didn't learn from it, and are now facing the consequences. If someone else wants to provide that level of help to you, then by all means go ahead, but if you want a "DETAILED INSTRUCTIONS on how to COMPLETELY implement something" then pick up a phone, dial a consultant and pay them for it-> someone who will be able to commit the time required to analyse / design / implement and troubleshoot if required. As much as you'd like to think you can get by with support of a community such as this, when you're talking about Network config / RDBMS infrastructure / Security etc, it is simply na?ve to think that you will not encounter problems.. I would assume anyone with the aforementioned research skills, after reading my suggestion to turn off simple file sharing, would at least spend 5 minutes on google finding out how to do it and hopefully picking up a bit of info on what it entails & impacts upon. Similarly, try searching google for "SQL Server Login Failed Simple File Sharing" and I'm sure you'll get a number of results -> not difficult or time consuming IMO.. If this simple change has stuffed up your network, then you must have other issues or (again) not understand what you have configured in your network to start with. (Could also be that your trying to run 'server-recommended' software and systems on a home based operating system...Again not recommended, and again I believed suggested in these forums in the past..) If you're unwilling to commit time into understanding this then fine, pay someone to do it for you. If you are offended with this suggestion or not willing or able to spend the money, then I'm sorry, but you've taken on the wrong projects, which, if memory serves, was raised as a possibility in this forum when you first indicated taking on this line of work. Bit ironic to ignore that advice but then rely on the same source as a primary means to support your business.. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, 29 August 2006 12:33 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer Haslett, this is an ACCESS group / SQL Server group, Not a Network Admin group. >Sorry if this sounds harsh but there are reasons that this stuff is >taught in detailed courses -> it's just not something you can pick up and try to do off the cuff without some experience or at least willingness to investigate the documentation provided. If that is the case, then throwing out advice like "turn off simple file sharing" is inappropriate advice, at least without a "this will royally screw up your private workgroup file sharing (and not even get you what you are after)" warning. Sorry if THAT sounds harsh, but I am NOT a Notwork Admin (nor are many others on this list), and apparently my workgroup file sharing IS SCREWED UP because I blithely followed "correct" advice. Not only did it screw up my file sharing (which BTW is still not working) but it did NOT provide sufficient assistance to get my the SQL Server registration working. Is this mail list not supposed to be about coming here to ask advice from people more experienced than myself? Is the result of listening to such advice SUPPOSED to be screwing up my workgroup / file sharing and NOT EVEN GETTING what I was asking about answered? If that is the case I suppose I have very little use for this group! And OBTW, I am willing to RTFM. I have been reading the manual all of my adult life! SQL Server is not my strong suite to say the least, and (apparently) security and SQL Server is not a trivial subject. And having RTFM, I am still without my file sharing. But I do appreciate your understanding. I would even bow in your general direction but I don't know where you are. Thanks very much for your (correct) advice, I can't begin to tell you how much help it was. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 28, 2006 10:24 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer Perhaps the advice provided months (a year?) ago when I recall this same (or similar) problem arose, recommending that this type of thing should not be attempted without sufficient training / experience / professional assistance, was good advice? Simple file sharing is the reason you could not connect. Steps to disable it were posted in a previous post. Enabling it is as simple as checking the box instead of unchecking it.. A 1 minute search on google will further provide these details. Furthermore, the documentation for SQL Server - Books On Line, by far the best product documentation that MS has provided, will provide you with plenty of easy to find material on configuring security in SQL Server, which will detail the issues you are requesting on SQL / Windows Authentication. Sorry if this sounds harsh but there are reasons that this stuff is taught in detailed courses -> it's just not something you can pick up and try to do off the cuff without some experience or at least willingness to investigate the documentation provided. And when the (correct) help we provide is thrown back at us with "you screwed my network" then, with all respect -> good luck with it yourself.. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, 28 August 2006 10:30 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] TransferringadatabasetoanotherSQLServer >In yet another attempt to cater to the masses... I AM the masses. >You need to turn "Simple File Sharing" off, not turn "File Sharing" off. I have no idea how to turn "file sharing" on / off. I have turned "simple file sharing" off with the result that the poor huddled masses can no longer see the files on the poor huddled masses other machines, which makes the poor huddled masses most unhappy. Furthermore, in SQL Server EM with SFS turned off, the other machines no longer even show up as available to register a server on, which also makes the poor huddled masses most unhappy. It seems that by following the simple edict "turn off SFS" the poor huddled masses have royally screwed up the private little workgroup in the home office, and can not seem to get it back. Sigh. DETAILED INSTRUCTIONS on how to COMPLETELY implement something are so much appreciated. The poor huddled masses are called the poor huddled masses precisely because they have not spent the hundreds of hours required to become OS administrators. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Monday, August 28, 2006 8:34 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring adatabasetoanotherSQLServer On 28 Aug 2006 at 8:16, JWColby wrote: > This is a network in my home office. Why do I need to turn Simple > File Sharing off, and if I need to do that, how do I replace it's functionality? > > With Simple File Sharing OFF my workstations can no longer see each > other and I get "no permission to use" error messages when trying to > browse for shares in Explorer. > > Furthermore, with SFS off, the other machines do not show up when > browsing in EM for other servers. > You need to turn "Simple File Sharing" off, not turn "File Sharing" off. In yet another attempt to cater to the masses, MS introduced a new simplified type of file sharing in XP as an alternative to the standard file sharing that we have always used. They call this new system "Simple File Sharing". XP Home always uses Simple File Sharing. XP Pro defaults to Simple File Sharing if you are using a peer to peer network (no domain controller). If you are configured to use Simple File Sharing, remote users always authenticate using the Guest account and you run into the sort or problem you are facing. To switch to classic file sharing, 1. Double-click My Computer on the desktop. 2. On the Tools menu, click Folder Options. 3. Click the View tab, and then de-select "Use Simple File Sharing" Now you can set proper permissions on your resources and authenticate using accounts with appropriate permissions. See http://support.microsoft.com/kb/304040/ for all the gory details -- Stuart _______________________________________________ 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 ssharkins at setel.com Mon Aug 28 20:16:18 2006 From: ssharkins at setel.com (Susan Harkins) Date: Mon, 28 Aug 2006 21:16:18 -0400 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <0A870603A2A816459078203FC07F4CD2BE403C@adl01s055.ilcorp.gov.au> Message-ID: <000301c6cb08$bcb08620$8b32fad1@SUSANONE> Stark realities occasionally need be surfaced in order for them to sink in.. Irrespective of the target or consequences. Was it harsh? Yup. Could it perhaps prevent someone else from making the same mistakes and undertaking projects without due preparation and planning? Hopefully, and therefore I believe useful. ======Sure makes me feel less comfortable asking questions and I am definitely not a JC groupie. :( Susan H. From jwcolby at colbyconsulting.com Mon Aug 28 21:13:32 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 28 Aug 2006 22:13:32 -0400 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <000301c6cb08$bcb08620$8b32fad1@SUSANONE> Message-ID: <002a01c6cb10$ba965f10$657aa8c0@m6805> >======Sure makes me feel less comfortable asking questions and I am definitely not a JC groupie. :( Me too, and I'm not a JC groupie either. ;-) And the man is apparently a SQL Server Guru but can't even unsub himself from the list. Hmmm, I guess we all DO need help once in awhile. ;-) 1) Click on the following link. http://databaseadvisors.com/mailman/listinfo/dba-sqlserver 2) Go about 90% of the way down the page, look for dba-SQLServer Subscribers in big bold letters. 3) Underneath that you will see a text box into which you enter your email address. 4) Click the button Unsubscribe or edit options. Hopefully you can follow the instructions from there. Of course I am kidding (kind of), I think perhaps Haslett might actually be of value to someone, and I certainly don't want him unsubscribing on my account. I do like being promoted to "the upper echelon" though. Has a certain ring to it. "Ahh yes, I am a member of 'the upper echelon'". LOL, that and 5 bucks will buy me a Starbucks Latte. ;-) John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Monday, August 28, 2006 9:16 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer Stark realities occasionally need be surfaced in order for them to sink in.. Irrespective of the target or consequences. Was it harsh? Yup. Could it perhaps prevent someone else from making the same mistakes and undertaking projects without due preparation and planning? Hopefully, and therefore I believe useful. ======Sure makes me feel less comfortable asking questions and I am definitely not a JC groupie. :( Susan H. _______________________________________________ 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 Aug 28 21:16:09 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 28 Aug 2006 22:16:09 -0400 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <0J4Q007QBH29LP10@l-daemon> Message-ID: <002b01c6cb11$1863e400$657aa8c0@m6805> >If you wished to so educate someone please do it off-line. LOL, that's JUST what I need, to have him dress me down offline! John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Monday, August 28, 2006 8:23 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer To whom it may concern: This is a public forum. I could not just stand by while you dress-down a fellow member, regardless the errors of their ways, at such length, so stridently, on such a personal level and public manner. If you wished to so educate someone please do it off-line. Jim From kp at sdsonline.net Mon Aug 28 22:02:58 2006 From: kp at sdsonline.net (Kath Pelletti) Date: Tue, 29 Aug 2006 13:02:58 +1000 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer References: <002a01c6cb10$ba965f10$657aa8c0@m6805> Message-ID: <002801c6cb17$a257fec0$6501a8c0@office> I can't see the point of deliberately *not* helping someone past a certain point. My experience of the lists (here) has been that people generally help as much as they can. They only stop when they simply don't have the time or resources to help further and when that happens they just say so. No need to put people down. But I have noticed that this is not an *ordinary* list in that sense. Kath Pelletti From mikedorism at verizon.net Tue Aug 29 07:39:41 2006 From: mikedorism at verizon.net (Mike & Doris Manning) Date: Tue, 29 Aug 2006 08:39:41 -0400 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <002801c6cb17$a257fec0$6501a8c0@office> Message-ID: <000201c6cb68$3510ab40$2f01a8c0@dorismanning> I agree. We don't all have the resources to go hire a professional or some one more trained than we are. The few times I've been lucky enough to have my company pay for that level of help I've been looked down upon as if I was second class because I just want help understanding what I'm doing...not help actually doing it. Even my company's highly trained Network Admin resorts to Google searches when she hits a rough spot and doesn't know where else to turn next because technology changes so quickly. Database Advisors was built by a group of international "pen pals" who were part of a community where we could share knowledge about Access and other subjects that was getting ready to be shut down. The group believed in it strongly enough that they formed a corporation and put their own resources into it to keep it running. I happen to be a fan of JC {no tomato throwing please} and have learned much from his discussions about frameworks and classes over the years. I've learned a lot from everyone who posts here. I don't always have a use for something they tell me at the time but I can't begin to count how often I've turned to this list or the archives when I hit a rough patch. Long life to the list... Doris Manning mikedorism at verizon.net From rl_stewart at highstream.net Tue Aug 29 09:15:55 2006 From: rl_stewart at highstream.net (Robert L. Stewart) Date: Tue, 29 Aug 2006 10:15:55 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: References: Message-ID: <6.2.3.4.2.20060829101201.022ef998@pop3.highstream.net> As to why we are all here, it is to learn and hopefully help when we KNOW the answer. The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. Detach it. Copy it to the other machine. Attach it. KISS - Keep it Supremely Simple Always works for me. Robert At 08:40 AM 8/29/2006, you wrote: >Date: Tue, 29 Aug 2006 10:17:25 +0930 >From: "Haslett, Andrew" >Subject: Re: [dba-SQLServer] > [AccessD]TransferringadatabasetoanotherSQLServer >To: >Message-ID: > <0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> >Content-Type: text/plain; charset="utf-8" > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite >happy to ask for advice but only accept it when its something they >want to hear, and ignore it otherwise (demonstrated throughout the post below) > >The points I made in my post apply to anyone looking to undertake >similar issues, and will continue to happen until someone has the >guts to say it, irrelevant of who it is aimed at (which is how it >should be -> on a public forum, favour or protection should not be >given to anyone simply because they are friends, associates or seniority). > >Ask yourself this -> Would you have made the same post Jim, had it >not have been aimed at Mr Colby?. > >Stark realities occasionally need be surfaced in order for them to >sink in.. Irrespective of the target or consequences. Was it harsh? >Yup. Could it perhaps prevent someone else from making the same >mistakes and undertaking projects without due preparation and >planning? Hopefully, and therefore I believe useful. > >John asked Stuart "Why are you here then?". Some of us prefer to >assist others, pass on what knowledge they can and in my case >attempt to 'help others, help themselves', as opposed to just >feeding of others. > >I know of a number who have left this (and the Access) list in the >past, including myself, for similar reasons and 'Matesmenship' in >the upper echelons. > >Please unsubscribe me from the list. > >Andrew From jwcolby at colbyconsulting.com Tue Aug 29 10:36:37 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Tue, 29 Aug 2006 11:36:37 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <6.2.3.4.2.20060829101201.022ef998@pop3.highstream.net> Message-ID: <003c01c6cb80$ebd6e7a0$657aa8c0@m6805> >The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. >Detach it. >Copy it to the other machine. >Attach it. In fact that is only one of my two questions, but given my reception on the other question I suppose I should just not ask again. In fact I have RTFM (in advance of even asking AAMOF) and I found stuff about disconnecting / reconnecting possibly causing "orphaned users", this being caused by the use of something like a PK from the OS user to represent the user in the SQL Server login, and even though the user name is the same on the two machines, the UserID is not necessarily the same. It does make me a bit leery of going the disconnect route. I had hoped to get both machines seeing the other (SQL Servers) and then see if I could just query directly out of a table in one SQL Server and transfer the data into the same table (new/empty) in the other SQL Server. I know I can export the data to text files and then re-import back in, but given the fact that the data is hundreds of gigabytes, I don't even want to go there if I can avoid it. Unfortunately I do not know enough about SQL Server / networking to troubleshoot the "why" of two servers not seeing each other, and given that the list Gurus specifically want me to go become a SQL / Notwork DBA before I ask such questions, it seems that I will get no assistance on that here. I have the database on 5 250gb drives, which I suppose I shall disconnect and then simply move the entire disks and pray for the best. There are other forums I belong to though, I'll also go see if anyone can help. This is going to be a lot of data and eventually I will need machines preprocessing and then shipping the results to a central server, so the servers really do eventually need to see each other I think. It should be fun, and I should learn a lot, though perhaps not here. Thanks Stewart, John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart Sent: Tuesday, August 29, 2006 10:16 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server As to why we are all here, it is to learn and hopefully help when we KNOW the answer. The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. Detach it. Copy it to the other machine. Attach it. KISS - Keep it Supremely Simple Always works for me. Robert At 08:40 AM 8/29/2006, you wrote: >Date: Tue, 29 Aug 2006 10:17:25 +0930 >From: "Haslett, Andrew" >Subject: Re: [dba-SQLServer] > [AccessD]TransferringadatabasetoanotherSQLServer >To: >Message-ID: > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> >Content-Type: text/plain; charset="utf-8" > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite >happy to ask for advice but only accept it when its something they want >to hear, and ignore it otherwise (demonstrated throughout the post >below) > >The points I made in my post apply to anyone looking to undertake >similar issues, and will continue to happen until someone has the guts >to say it, irrelevant of who it is aimed at (which is how it should be >-> on a public forum, favour or protection should not be given to >anyone simply because they are friends, associates or seniority). > >Ask yourself this -> Would you have made the same post Jim, had it not >have been aimed at Mr Colby?. > >Stark realities occasionally need be surfaced in order for them to sink >in.. Irrespective of the target or consequences. Was it harsh? >Yup. Could it perhaps prevent someone else from making the same >mistakes and undertaking projects without due preparation and planning? >Hopefully, and therefore I believe useful. > >John asked Stuart "Why are you here then?". Some of us prefer to >assist others, pass on what knowledge they can and in my case attempt >to 'help others, help themselves', as opposed to just feeding of >others. > >I know of a number who have left this (and the Access) list in the >past, including myself, for similar reasons and 'Matesmenship' in the >upper echelons. > >Please unsubscribe me from the list. > >Andrew _______________________________________________ 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 Aug 29 11:47:40 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 09:47:40 -0700 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <0A870603A2A816459078203FC07F4CD2BE403C@adl01s055.ilcorp.gov.au> References: <0A870603A2A816459078203FC07F4CD2BE403C@adl01s055.ilcorp.gov.au> Message-ID: Guys, as the Mod for the list I think we've taken the thread from what it was, advice on helping a member register their server, to personal attacks about how we do research. All of use know that our Google-Fu may not be as good as others, the purpose of the lists are to post and answer questions, Practice good Nettiquette wich basically points to if you are willing to help, post by all means, if you do not have the answer or do not know, OR you are intending to have someone fish, try something like the following: Use BOL (books on line) to search for Key words "XXX" and "YYY" ETC, However that said, we're all adults, you can choose to help, or not. Let's not start a long thread of what should be or what shouldn't, let's keep it civilized. On 8/28/06, Haslett, Andrew wrote: > Suit yourselves - Seems to be a bit of a 'boys' club who are quite happy to ask for advice but only accept it when its something they want to hear, and ignore it otherwise (demonstrated throughout the post below) > > The points I made in my post apply to anyone looking to undertake similar issues, and will continue to happen until someone has the guts to say it, irrelevant of who it is aimed at (which is how it should be -> on a public forum, favour or protection should not be given to anyone simply because they are friends, associates or seniority). > > Ask yourself this -> Would you have made the same post Jim, had it not have been aimed at Mr Colby?. > > Stark realities occasionally need be surfaced in order for them to sink in.. Irrespective of the target or consequences. Was it harsh? Yup. Could it perhaps prevent someone else from making the same mistakes and undertaking projects without due preparation and planning? Hopefully, and therefore I believe useful. > > John asked Stuart "Why are you here then?". Some of us prefer to assist others, pass on what knowledge they can and in my case attempt to 'help others, help themselves', as opposed to just feeding of others. > > I know of a number who have left this (and the Access) list in the past, including myself, for similar reasons and 'Matesmenship' in the upper echelons. > > Please unsubscribe me from the list. > > Andrew > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Tue Aug 29 11:54:07 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 09:54:07 -0700 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <000301c6cb08$bcb08620$8b32fad1@SUSANONE> References: <0A870603A2A816459078203FC07F4CD2BE403C@adl01s055.ilcorp.gov.au> <000301c6cb08$bcb08620$8b32fad1@SUSANONE> Message-ID: I am definitely not a groupie, but I like this list because it's useful. The attempt at harshness has deviated the thread from it's subject to that of an attack. Let's try to get it back on track or kill the thread completely.... On 8/28/06, Susan Harkins wrote: > Stark realities occasionally need be surfaced in order for them to sink in.. > Irrespective of the target or consequences. Was it harsh? Yup. Could it > perhaps prevent someone else from making the same mistakes and undertaking > projects without due preparation and planning? Hopefully, and therefore I > believe useful. > > ======Sure makes me feel less comfortable asking questions and I am > definitely not a JC groupie. :( > > Susan H. -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Tue Aug 29 11:54:51 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 09:54:51 -0700 Subject: [dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer In-Reply-To: <002a01c6cb10$ba965f10$657aa8c0@m6805> References: <000301c6cb08$bcb08620$8b32fad1@SUSANONE> <002a01c6cb10$ba965f10$657aa8c0@m6805> Message-ID: Let's keep on topic, or kill this thread. On 8/28/06, JWColby wrote: > >======Sure makes me feel less comfortable asking questions and I am > definitely not a JC groupie. :( > > Me too, and I'm not a JC groupie either. > > ;-) > > And the man is apparently a SQL Server Guru but can't even unsub himself > from the list. Hmmm, I guess we all DO need help once in awhile. > > ;-) > > 1) Click on the following link. > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > 2) Go about 90% of the way down the page, look for dba-SQLServer Subscribers > in big bold letters. > 3) Underneath that you will see a text box into which you enter your email > address. > 4) Click the button Unsubscribe or edit options. > > Hopefully you can follow the instructions from there. > > Of course I am kidding (kind of), I think perhaps Haslett might actually be > of value to someone, and I certainly don't want him unsubscribing on my > account. > > I do like being promoted to "the upper echelon" though. Has a certain ring > to it. "Ahh yes, I am a member of 'the upper echelon'". LOL, that and 5 > bucks will buy me a Starbucks Latte. ;-) > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan > Harkins > Sent: Monday, August 28, 2006 9:16 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] > [AccessD]TransferringadatabasetoanotherSQLServer > > Stark realities occasionally need be surfaced in order for them to sink in.. > Irrespective of the target or consequences. Was it harsh? Yup. Could it > perhaps prevent someone else from making the same mistakes and undertaking > projects without due preparation and planning? Hopefully, and therefore I > believe useful. > > ======Sure makes me feel less comfortable asking questions and I am > definitely not a JC groupie. :( > > Susan H. > > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Tue Aug 29 12:01:30 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 10:01:30 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <003c01c6cb80$ebd6e7a0$657aa8c0@m6805> References: <6.2.3.4.2.20060829101201.022ef998@pop3.highstream.net> <003c01c6cb80$ebd6e7a0$657aa8c0@m6805> Message-ID: In order to prevent orphaned users, MS put out a script called sp_help_revlogin you create it in the master database, details are on my blog, http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-server.html if you get lost from the links post back and I'll help you through it. On 8/29/06, JWColby wrote: > >The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > >Detach it. > >Copy it to the other machine. > >Attach it. > > In fact that is only one of my two questions, but given my reception on the > other question I suppose I should just not ask again. > > In fact I have RTFM (in advance of even asking AAMOF) and I found stuff > about disconnecting / reconnecting possibly causing "orphaned users", this > being caused by the use of something like a PK from the OS user to represent > the user in the SQL Server login, and even though the user name is the same > on the two machines, the UserID is not necessarily the same. It does make > me a bit leery of going the disconnect route. > > I had hoped to get both machines seeing the other (SQL Servers) and then see > if I could just query directly out of a table in one SQL Server and transfer > the data into the same table (new/empty) in the other SQL Server. I know I > can export the data to text files and then re-import back in, but given the > fact that the data is hundreds of gigabytes, I don't even want to go there > if I can avoid it. > > Unfortunately I do not know enough about SQL Server / networking to > troubleshoot the "why" of two servers not seeing each other, and given that > the list Gurus specifically want me to go become a SQL / Notwork DBA before > I ask such questions, it seems that I will get no assistance on that here. > > I have the database on 5 250gb drives, which I suppose I shall disconnect > and then simply move the entire disks and pray for the best. > > There are other forums I belong to though, I'll also go see if anyone can > help. This is going to be a lot of data and eventually I will need machines > preprocessing and then shipping the results to a central server, so the > servers really do eventually need to see each other I think. It should be > fun, and I should learn a lot, though perhaps not here. > > Thanks Stewart, > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > Stewart > Sent: Tuesday, August 29, 2006 10:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > As to why we are all here, it is to learn and hopefully help when we KNOW > the answer. > > The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > Detach it. > Copy it to the other machine. > Attach it. > > KISS - Keep it Supremely Simple > > Always works for me. > > Robert > > At 08:40 AM 8/29/2006, you wrote: > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > >From: "Haslett, Andrew" > >Subject: Re: [dba-SQLServer] > > [AccessD]TransferringadatabasetoanotherSQLServer > >To: > >Message-ID: > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > >Content-Type: text/plain; charset="utf-8" > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > >happy to ask for advice but only accept it when its something they want > >to hear, and ignore it otherwise (demonstrated throughout the post > >below) > > > >The points I made in my post apply to anyone looking to undertake > >similar issues, and will continue to happen until someone has the guts > >to say it, irrelevant of who it is aimed at (which is how it should be > >-> on a public forum, favour or protection should not be given to > >anyone simply because they are friends, associates or seniority). > > > >Ask yourself this -> Would you have made the same post Jim, had it not > >have been aimed at Mr Colby?. > > > >Stark realities occasionally need be surfaced in order for them to sink > >in.. Irrespective of the target or consequences. Was it harsh? > >Yup. Could it perhaps prevent someone else from making the same > >mistakes and undertaking projects without due preparation and planning? > >Hopefully, and therefore I believe useful. > > > >John asked Stuart "Why are you here then?". Some of us prefer to > >assist others, pass on what knowledge they can and in my case attempt > >to 'help others, help themselves', as opposed to just feeding of > >others. > > > >I know of a number who have left this (and the Access) list in the > >past, including myself, for similar reasons and 'Matesmenship' in the > >upper echelons. > > > >Please unsubscribe me from the list. > > > >Andrew > > > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Tue Aug 29 12:03:19 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 10:03:19 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <003c01c6cb80$ebd6e7a0$657aa8c0@m6805> References: <6.2.3.4.2.20060829101201.022ef998@pop3.highstream.net> <003c01c6cb80$ebd6e7a0$657aa8c0@m6805> Message-ID: John, When you say you couldn't register the server on the other machine, were you still able to ping it? get to it's unc name via \\ServerName? these questions I never saw answered. (maybe I scrolled to quickly on your posts) On 8/29/06, JWColby wrote: > >The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > >Detach it. > >Copy it to the other machine. > >Attach it. > > In fact that is only one of my two questions, but given my reception on the > other question I suppose I should just not ask again. > > In fact I have RTFM (in advance of even asking AAMOF) and I found stuff > about disconnecting / reconnecting possibly causing "orphaned users", this > being caused by the use of something like a PK from the OS user to represent > the user in the SQL Server login, and even though the user name is the same > on the two machines, the UserID is not necessarily the same. It does make > me a bit leery of going the disconnect route. > > I had hoped to get both machines seeing the other (SQL Servers) and then see > if I could just query directly out of a table in one SQL Server and transfer > the data into the same table (new/empty) in the other SQL Server. I know I > can export the data to text files and then re-import back in, but given the > fact that the data is hundreds of gigabytes, I don't even want to go there > if I can avoid it. > > Unfortunately I do not know enough about SQL Server / networking to > troubleshoot the "why" of two servers not seeing each other, and given that > the list Gurus specifically want me to go become a SQL / Notwork DBA before > I ask such questions, it seems that I will get no assistance on that here. > > I have the database on 5 250gb drives, which I suppose I shall disconnect > and then simply move the entire disks and pray for the best. > > There are other forums I belong to though, I'll also go see if anyone can > help. This is going to be a lot of data and eventually I will need machines > preprocessing and then shipping the results to a central server, so the > servers really do eventually need to see each other I think. It should be > fun, and I should learn a lot, though perhaps not here. > > Thanks Stewart, > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > Stewart > Sent: Tuesday, August 29, 2006 10:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > As to why we are all here, it is to learn and hopefully help when we KNOW > the answer. > > The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > Detach it. > Copy it to the other machine. > Attach it. > > KISS - Keep it Supremely Simple > > Always works for me. > > Robert > > At 08:40 AM 8/29/2006, you wrote: > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > >From: "Haslett, Andrew" > >Subject: Re: [dba-SQLServer] > > [AccessD]TransferringadatabasetoanotherSQLServer > >To: > >Message-ID: > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > >Content-Type: text/plain; charset="utf-8" > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > >happy to ask for advice but only accept it when its something they want > >to hear, and ignore it otherwise (demonstrated throughout the post > >below) > > > >The points I made in my post apply to anyone looking to undertake > >similar issues, and will continue to happen until someone has the guts > >to say it, irrelevant of who it is aimed at (which is how it should be > >-> on a public forum, favour or protection should not be given to > >anyone simply because they are friends, associates or seniority). > > > >Ask yourself this -> Would you have made the same post Jim, had it not > >have been aimed at Mr Colby?. > > > >Stark realities occasionally need be surfaced in order for them to sink > >in.. Irrespective of the target or consequences. Was it harsh? > >Yup. Could it perhaps prevent someone else from making the same > >mistakes and undertaking projects without due preparation and planning? > >Hopefully, and therefore I believe useful. > > > >John asked Stuart "Why are you here then?". Some of us prefer to > >assist others, pass on what knowledge they can and in my case attempt > >to 'help others, help themselves', as opposed to just feeding of > >others. > > > >I know of a number who have left this (and the Access) list in the > >past, including myself, for similar reasons and 'Matesmenship' in the > >upper echelons. > > > >Please unsubscribe me from the list. > > > >Andrew > > > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From accessd at shaw.ca Tue Aug 29 11:52:25 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Tue, 29 Aug 2006 09:52:25 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <003c01c6cb80$ebd6e7a0$657aa8c0@m6805> Message-ID: <0J4R00J4WQUO5D30@l-daemon> Hi John: If it just requires moving the index and data files to the other computer, then attaching them that can be done as simply as copying the two important files from computer A to computer B. Given a database named MyDatabase just copy from directory ie: c:\Program Files\Microsoft SQL Server\MSSQL\Data files named MyDatabase.ldf and MyDatabase.mdf to the other computer or simpler yet just attach (MS SQL 2005), Microsoft SQL Server Management Studio > databases > right-mouse-click > select Attach > select Add and then just navigate to your computer that has the (data) MyDatabase.mdf file and select it. Is this what you are asking? HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 8:37 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server >The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. >Detach it. >Copy it to the other machine. >Attach it. In fact that is only one of my two questions, but given my reception on the other question I suppose I should just not ask again. In fact I have RTFM (in advance of even asking AAMOF) and I found stuff about disconnecting / reconnecting possibly causing "orphaned users", this being caused by the use of something like a PK from the OS user to represent the user in the SQL Server login, and even though the user name is the same on the two machines, the UserID is not necessarily the same. It does make me a bit leery of going the disconnect route. I had hoped to get both machines seeing the other (SQL Servers) and then see if I could just query directly out of a table in one SQL Server and transfer the data into the same table (new/empty) in the other SQL Server. I know I can export the data to text files and then re-import back in, but given the fact that the data is hundreds of gigabytes, I don't even want to go there if I can avoid it. Unfortunately I do not know enough about SQL Server / networking to troubleshoot the "why" of two servers not seeing each other, and given that the list Gurus specifically want me to go become a SQL / Notwork DBA before I ask such questions, it seems that I will get no assistance on that here. I have the database on 5 250gb drives, which I suppose I shall disconnect and then simply move the entire disks and pray for the best. There are other forums I belong to though, I'll also go see if anyone can help. This is going to be a lot of data and eventually I will need machines preprocessing and then shipping the results to a central server, so the servers really do eventually need to see each other I think. It should be fun, and I should learn a lot, though perhaps not here. Thanks Stewart, John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart Sent: Tuesday, August 29, 2006 10:16 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server As to why we are all here, it is to learn and hopefully help when we KNOW the answer. The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. Detach it. Copy it to the other machine. Attach it. KISS - Keep it Supremely Simple Always works for me. Robert At 08:40 AM 8/29/2006, you wrote: >Date: Tue, 29 Aug 2006 10:17:25 +0930 >From: "Haslett, Andrew" >Subject: Re: [dba-SQLServer] > [AccessD]TransferringadatabasetoanotherSQLServer >To: >Message-ID: > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> >Content-Type: text/plain; charset="utf-8" > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite >happy to ask for advice but only accept it when its something they want >to hear, and ignore it otherwise (demonstrated throughout the post >below) > >The points I made in my post apply to anyone looking to undertake >similar issues, and will continue to happen until someone has the guts >to say it, irrelevant of who it is aimed at (which is how it should be >-> on a public forum, favour or protection should not be given to >anyone simply because they are friends, associates or seniority). > >Ask yourself this -> Would you have made the same post Jim, had it not >have been aimed at Mr Colby?. > >Stark realities occasionally need be surfaced in order for them to sink >in.. Irrespective of the target or consequences. Was it harsh? >Yup. Could it perhaps prevent someone else from making the same >mistakes and undertaking projects without due preparation and planning? >Hopefully, and therefore I believe useful. > >John asked Stuart "Why are you here then?". Some of us prefer to >assist others, pass on what knowledge they can and in my case attempt >to 'help others, help themselves', as opposed to just feeding of >others. > >I know of a number who have left this (and the Access) list in the >past, including myself, for similar reasons and 'Matesmenship' in the >upper echelons. > >Please unsubscribe me from the list. > >Andrew _______________________________________________ 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 rl_stewart at highstream.net Tue Aug 29 12:14:10 2006 From: rl_stewart at highstream.net (Robert L. Stewart) Date: Tue, 29 Aug 2006 13:14:10 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL In-Reply-To: References: Message-ID: <6.2.3.4.2.20060829131119.022f7818@pop3.highstream.net> Okay John, Now I understand more. Since these are both SQL 2000, if I remember the thread correctly, can you connect to them through DTS on one of the machines? If so, and you have the drive space on the second machine, you can use DTS to move the data between the two machines. I am with you on moving hardware between machines. I hate hardware. But deal with it because I cannot afford a consultant to deal with it for me. Robert At 01:00 PM 8/29/2006, you wrote: >Date: Tue, 29 Aug 2006 11:36:37 -0400 >From: "JWColby" >Subject: Re: [dba-SQLServer] Transferring a database to another SQL > Server >To: >Message-ID: <003c01c6cb80$ebd6e7a0$657aa8c0 at m6805> >Content-Type: text/plain; charset="us-ascii" > > >The simple answer was given to him (JC) in the first post back to him. >Which is why I never chimed in. > > >Detach it. > >Copy it to the other machine. > >Attach it. > >In fact that is only one of my two questions, but given my reception on the >other question I suppose I should just not ask again. > >In fact I have RTFM (in advance of even asking AAMOF) and I found stuff >about disconnecting / reconnecting possibly causing "orphaned users", this >being caused by the use of something like a PK from the OS user to represent >the user in the SQL Server login, and even though the user name is the same >on the two machines, the UserID is not necessarily the same. It does make >me a bit leery of going the disconnect route. > >I had hoped to get both machines seeing the other (SQL Servers) and then see >if I could just query directly out of a table in one SQL Server and transfer >the data into the same table (new/empty) in the other SQL Server. I know I >can export the data to text files and then re-import back in, but given the >fact that the data is hundreds of gigabytes, I don't even want to go there >if I can avoid it. > >Unfortunately I do not know enough about SQL Server / networking to >troubleshoot the "why" of two servers not seeing each other, and given that >the list Gurus specifically want me to go become a SQL / Notwork DBA before >I ask such questions, it seems that I will get no assistance on that here. > >I have the database on 5 250gb drives, which I suppose I shall disconnect >and then simply move the entire disks and pray for the best. > >There are other forums I belong to though, I'll also go see if anyone can >help. This is going to be a lot of data and eventually I will need machines >preprocessing and then shipping the results to a central server, so the >servers really do eventually need to see each other I think. It should be >fun, and I should learn a lot, though perhaps not here. > >Thanks Stewart, > >John W. Colby >Colby Consulting >www.ColbyConsulting.com From tuxedoman888 at gmail.com Tue Aug 29 12:42:25 2006 From: tuxedoman888 at gmail.com (Billy Pang) Date: Tue, 29 Aug 2006 10:42:25 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <003c01c6cb80$ebd6e7a0$657aa8c0@m6805> References: <6.2.3.4.2.20060829101201.022ef998@pop3.highstream.net> <003c01c6cb80$ebd6e7a0$657aa8c0@m6805> Message-ID: <7c8826480608291042l42ed628ft9f557202d216c91@mail.gmail.com> not sure if the following two kbs will help (I haven't followed this entire thread; way too long) but hope you find it useful. How to transfer logins and passwords between instances of SQL Server 7.0 /2000 http://support.microsoft.com/kb/246133/ How to transfer logins and passwords between instances of SQL Server 2005 http://support.microsoft.com/kb/918992/ Billy On 8/29/06, JWColby wrote: > > >The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > >Detach it. > >Copy it to the other machine. > >Attach it. > > In fact that is only one of my two questions, but given my reception on > the > other question I suppose I should just not ask again. > > In fact I have RTFM (in advance of even asking AAMOF) and I found stuff > about disconnecting / reconnecting possibly causing "orphaned users", this > being caused by the use of something like a PK from the OS user to > represent > the user in the SQL Server login, and even though the user name is the > same > on the two machines, the UserID is not necessarily the same. It does make > me a bit leery of going the disconnect route. > > I had hoped to get both machines seeing the other (SQL Servers) and then > see > if I could just query directly out of a table in one SQL Server and > transfer > the data into the same table (new/empty) in the other SQL Server. I know > I > can export the data to text files and then re-import back in, but given > the > fact that the data is hundreds of gigabytes, I don't even want to go there > if I can avoid it. > > Unfortunately I do not know enough about SQL Server / networking to > troubleshoot the "why" of two servers not seeing each other, and given > that > the list Gurus specifically want me to go become a SQL / Notwork DBA > before > I ask such questions, it seems that I will get no assistance on that here. > > I have the database on 5 250gb drives, which I suppose I shall disconnect > and then simply move the entire disks and pray for the best. > > There are other forums I belong to though, I'll also go see if anyone can > help. This is going to be a lot of data and eventually I will need > machines > preprocessing and then shipping the results to a central server, so the > servers really do eventually need to see each other I think. It should be > fun, and I should learn a lot, though perhaps not here. > > Thanks Stewart, > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > Stewart > Sent: Tuesday, August 29, 2006 10:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > As to why we are all here, it is to learn and hopefully help when we KNOW > the answer. > > The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > Detach it. > Copy it to the other machine. > Attach it. > > KISS - Keep it Supremely Simple > > Always works for me. > > Robert > > At 08:40 AM 8/29/2006, you wrote: > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > >From: "Haslett, Andrew" > >Subject: Re: [dba-SQLServer] > > [AccessD]TransferringadatabasetoanotherSQLServer > >To: > >Message-ID: > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > >Content-Type: text/plain; charset="utf-8" > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > >happy to ask for advice but only accept it when its something they want > >to hear, and ignore it otherwise (demonstrated throughout the post > >below) > > > >The points I made in my post apply to anyone looking to undertake > >similar issues, and will continue to happen until someone has the guts > >to say it, irrelevant of who it is aimed at (which is how it should be > >-> on a public forum, favour or protection should not be given to > >anyone simply because they are friends, associates or seniority). > > > >Ask yourself this -> Would you have made the same post Jim, had it not > >have been aimed at Mr Colby?. > > > >Stark realities occasionally need be surfaced in order for them to sink > >in.. Irrespective of the target or consequences. Was it harsh? > >Yup. Could it perhaps prevent someone else from making the same > >mistakes and undertaking projects without due preparation and planning? > >Hopefully, and therefore I believe useful. > > > >John asked Stuart "Why are you here then?". Some of us prefer to > >assist others, pass on what knowledge they can and in my case attempt > >to 'help others, help themselves', as opposed to just feeding of > >others. > > > >I know of a number who have left this (and the Access) list in the > >past, including myself, for similar reasons and 'Matesmenship' in the > >upper echelons. > > > >Please unsubscribe me from the list. > > > >Andrew > > > _______________________________________________ > 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 > > -- Billy Pang http://dbnotes.blogspot.com/ "Once the game is over, the King and the pawn go back in the same box." - Italian proverb From accessd at shaw.ca Tue Aug 29 12:43:13 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Tue, 29 Aug 2006 10:43:13 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: Message-ID: <0J4R0023BT895I10@l-daemon> Fancisco: Now that would have been helpful about a month ago when it took a week to migrate something that should have taken minutes. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, August 29, 2006 10:02 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server In order to prevent orphaned users, MS put out a script called sp_help_revlogin you create it in the master database, details are on my blog, http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-server.htm l if you get lost from the links post back and I'll help you through it. On 8/29/06, JWColby wrote: > >The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > >Detach it. > >Copy it to the other machine. > >Attach it. > > In fact that is only one of my two questions, but given my reception on the > other question I suppose I should just not ask again. > > In fact I have RTFM (in advance of even asking AAMOF) and I found stuff > about disconnecting / reconnecting possibly causing "orphaned users", this > being caused by the use of something like a PK from the OS user to represent > the user in the SQL Server login, and even though the user name is the same > on the two machines, the UserID is not necessarily the same. It does make > me a bit leery of going the disconnect route. > > I had hoped to get both machines seeing the other (SQL Servers) and then see > if I could just query directly out of a table in one SQL Server and transfer > the data into the same table (new/empty) in the other SQL Server. I know I > can export the data to text files and then re-import back in, but given the > fact that the data is hundreds of gigabytes, I don't even want to go there > if I can avoid it. > > Unfortunately I do not know enough about SQL Server / networking to > troubleshoot the "why" of two servers not seeing each other, and given that > the list Gurus specifically want me to go become a SQL / Notwork DBA before > I ask such questions, it seems that I will get no assistance on that here. > > I have the database on 5 250gb drives, which I suppose I shall disconnect > and then simply move the entire disks and pray for the best. > > There are other forums I belong to though, I'll also go see if anyone can > help. This is going to be a lot of data and eventually I will need machines > preprocessing and then shipping the results to a central server, so the > servers really do eventually need to see each other I think. It should be > fun, and I should learn a lot, though perhaps not here. > > Thanks Stewart, > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > Stewart > Sent: Tuesday, August 29, 2006 10:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > As to why we are all here, it is to learn and hopefully help when we KNOW > the answer. > > The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > Detach it. > Copy it to the other machine. > Attach it. > > KISS - Keep it Supremely Simple > > Always works for me. > > Robert > > At 08:40 AM 8/29/2006, you wrote: > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > >From: "Haslett, Andrew" > >Subject: Re: [dba-SQLServer] > > [AccessD]TransferringadatabasetoanotherSQLServer > >To: > >Message-ID: > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > >Content-Type: text/plain; charset="utf-8" > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > >happy to ask for advice but only accept it when its something they want > >to hear, and ignore it otherwise (demonstrated throughout the post > >below) > > > >The points I made in my post apply to anyone looking to undertake > >similar issues, and will continue to happen until someone has the guts > >to say it, irrelevant of who it is aimed at (which is how it should be > >-> on a public forum, favour or protection should not be given to > >anyone simply because they are friends, associates or seniority). > > > >Ask yourself this -> Would you have made the same post Jim, had it not > >have been aimed at Mr Colby?. > > > >Stark realities occasionally need be surfaced in order for them to sink > >in.. Irrespective of the target or consequences. Was it harsh? > >Yup. Could it perhaps prevent someone else from making the same > >mistakes and undertaking projects without due preparation and planning? > >Hopefully, and therefore I believe useful. > > > >John asked Stuart "Why are you here then?". Some of us prefer to > >assist others, pass on what knowledge they can and in my case attempt > >to 'help others, help themselves', as opposed to just feeding of > >others. > > > >I know of a number who have left this (and the Access) list in the > >past, including myself, for similar reasons and 'Matesmenship' in the > >upper echelons. > > > >Please unsubscribe me from the list. > > > >Andrew > > > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 Tue Aug 29 12:48:55 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Tue, 29 Aug 2006 13:48:55 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: Message-ID: <000301c6cb93$683124c0$657aa8c0@m6805> Thanks for this Francisco. I am in the process of tearing my two machines apart to move the physical drives from one to the other. We'll see how it all goes. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, August 29, 2006 1:02 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server In order to prevent orphaned users, MS put out a script called sp_help_revlogin you create it in the master database, details are on my blog, http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-server.htm l if you get lost from the links post back and I'll help you through it. On 8/29/06, JWColby wrote: > >The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > >Detach it. > >Copy it to the other machine. > >Attach it. > > In fact that is only one of my two questions, but given my reception > on the other question I suppose I should just not ask again. > > In fact I have RTFM (in advance of even asking AAMOF) and I found > stuff about disconnecting / reconnecting possibly causing "orphaned > users", this being caused by the use of something like a PK from the > OS user to represent the user in the SQL Server login, and even though > the user name is the same on the two machines, the UserID is not > necessarily the same. It does make me a bit leery of going the disconnect route. > > I had hoped to get both machines seeing the other (SQL Servers) and > then see if I could just query directly out of a table in one SQL > Server and transfer the data into the same table (new/empty) in the > other SQL Server. I know I can export the data to text files and then > re-import back in, but given the fact that the data is hundreds of > gigabytes, I don't even want to go there if I can avoid it. > > Unfortunately I do not know enough about SQL Server / networking to > troubleshoot the "why" of two servers not seeing each other, and given > that the list Gurus specifically want me to go become a SQL / Notwork > DBA before I ask such questions, it seems that I will get no assistance on that here. > > I have the database on 5 250gb drives, which I suppose I shall > disconnect and then simply move the entire disks and pray for the best. > > There are other forums I belong to though, I'll also go see if anyone > can help. This is going to be a lot of data and eventually I will > need machines preprocessing and then shipping the results to a central > server, so the servers really do eventually need to see each other I > think. It should be fun, and I should learn a lot, though perhaps not here. > > Thanks Stewart, > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > Stewart > Sent: Tuesday, August 29, 2006 10:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > Server > > As to why we are all here, it is to learn and hopefully help when we > KNOW the answer. > > The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > Detach it. > Copy it to the other machine. > Attach it. > > KISS - Keep it Supremely Simple > > Always works for me. > > Robert > > At 08:40 AM 8/29/2006, you wrote: > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > >From: "Haslett, Andrew" > >Subject: Re: [dba-SQLServer] > > [AccessD]TransferringadatabasetoanotherSQLServer > >To: > >Message-ID: > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > >Content-Type: text/plain; charset="utf-8" > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > >happy to ask for advice but only accept it when its something they > >want to hear, and ignore it otherwise (demonstrated throughout the > >post > >below) > > > >The points I made in my post apply to anyone looking to undertake > >similar issues, and will continue to happen until someone has the > >guts to say it, irrelevant of who it is aimed at (which is how it > >should be > >-> on a public forum, favour or protection should not be given to > >anyone simply because they are friends, associates or seniority). > > > >Ask yourself this -> Would you have made the same post Jim, had it > >not have been aimed at Mr Colby?. > > > >Stark realities occasionally need be surfaced in order for them to > >sink in.. Irrespective of the target or consequences. Was it harsh? > >Yup. Could it perhaps prevent someone else from making the same > >mistakes and undertaking projects without due preparation and planning? > >Hopefully, and therefore I believe useful. > > > >John asked Stuart "Why are you here then?". Some of us prefer to > >assist others, pass on what knowledge they can and in my case attempt > >to 'help others, help themselves', as opposed to just feeding of > >others. > > > >I know of a number who have left this (and the Access) list in the > >past, including myself, for similar reasons and 'Matesmenship' in the > >upper echelons. > > > >Please unsubscribe me from the list. > > > >Andrew > > > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 Aug 29 13:22:54 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 11:22:54 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <000301c6cb93$683124c0$657aa8c0@m6805> References: <000301c6cb93$683124c0$657aa8c0@m6805> Message-ID: So I never knew if your machine could see the other, or was just not registering on the 2nd server. I ask because i've had situations where you can see the other server by navigting to it, but cannot register it locally. On 8/29/06, JWColby wrote: > Thanks for this Francisco. I am in the process of tearing my two machines > apart to move the physical drives from one to the other. We'll see how it > all goes. > > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco > Tapia > Sent: Tuesday, August 29, 2006 1:02 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > In order to prevent orphaned users, MS put out a script called > sp_help_revlogin you create it in the master database, details are on my > blog, > > http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-server.htm > l > > if you get lost from the links post back and I'll help you through it. > > > On 8/29/06, JWColby wrote: > > >The simple answer was given to him (JC) in the first post back to him. > > Which is why I never chimed in. > > > > >Detach it. > > >Copy it to the other machine. > > >Attach it. > > > > In fact that is only one of my two questions, but given my reception > > on the other question I suppose I should just not ask again. > > > > In fact I have RTFM (in advance of even asking AAMOF) and I found > > stuff about disconnecting / reconnecting possibly causing "orphaned > > users", this being caused by the use of something like a PK from the > > OS user to represent the user in the SQL Server login, and even though > > the user name is the same on the two machines, the UserID is not > > necessarily the same. It does make me a bit leery of going the disconnect > route. > > > > I had hoped to get both machines seeing the other (SQL Servers) and > > then see if I could just query directly out of a table in one SQL > > Server and transfer the data into the same table (new/empty) in the > > other SQL Server. I know I can export the data to text files and then > > re-import back in, but given the fact that the data is hundreds of > > gigabytes, I don't even want to go there if I can avoid it. > > > > Unfortunately I do not know enough about SQL Server / networking to > > troubleshoot the "why" of two servers not seeing each other, and given > > that the list Gurus specifically want me to go become a SQL / Notwork > > DBA before I ask such questions, it seems that I will get no assistance on > that here. > > > > I have the database on 5 250gb drives, which I suppose I shall > > disconnect and then simply move the entire disks and pray for the best. > > > > There are other forums I belong to though, I'll also go see if anyone > > can help. This is going to be a lot of data and eventually I will > > need machines preprocessing and then shipping the results to a central > > server, so the servers really do eventually need to see each other I > > think. It should be fun, and I should learn a lot, though perhaps not > here. > > > > Thanks Stewart, > > > > John W. Colby > > Colby Consulting > > www.ColbyConsulting.com > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > > Stewart > > Sent: Tuesday, August 29, 2006 10:16 AM > > To: dba-sqlserver at databaseadvisors.com > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > Server > > > > As to why we are all here, it is to learn and hopefully help when we > > KNOW the answer. > > > > The simple answer was given to him (JC) in the first post back to him. > > Which is why I never chimed in. > > > > Detach it. > > Copy it to the other machine. > > Attach it. > > > > KISS - Keep it Supremely Simple > > > > Always works for me. > > > > Robert > > > > At 08:40 AM 8/29/2006, you wrote: > > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > > >From: "Haslett, Andrew" > > >Subject: Re: [dba-SQLServer] > > > [AccessD]TransferringadatabasetoanotherSQLServer > > >To: > > >Message-ID: > > > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > > >Content-Type: text/plain; charset="utf-8" > > > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > > >happy to ask for advice but only accept it when its something they > > >want to hear, and ignore it otherwise (demonstrated throughout the > > >post > > >below) > > > > > >The points I made in my post apply to anyone looking to undertake > > >similar issues, and will continue to happen until someone has the > > >guts to say it, irrelevant of who it is aimed at (which is how it > > >should be > > >-> on a public forum, favour or protection should not be given to > > >anyone simply because they are friends, associates or seniority). > > > > > >Ask yourself this -> Would you have made the same post Jim, had it > > >not have been aimed at Mr Colby?. > > > > > >Stark realities occasionally need be surfaced in order for them to > > >sink in.. Irrespective of the target or consequences. Was it harsh? > > >Yup. Could it perhaps prevent someone else from making the same > > >mistakes and undertaking projects without due preparation and planning? > > >Hopefully, and therefore I believe useful. > > > > > >John asked Stuart "Why are you here then?". Some of us prefer to > > >assist others, pass on what knowledge they can and in my case attempt > > >to 'help others, help themselves', as opposed to just feeding of > > >others. > > > > > >I know of a number who have left this (and the Access) list in the > > >past, including myself, for similar reasons and 'Matesmenship' in the > > >upper echelons. > > > > > >Please unsubscribe me from the list. > > > > > >Andrew > > > > > > _______________________________________________ > > 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 > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Tue Aug 29 13:25:29 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 11:25:29 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <0J4R0023BT895I10@l-daemon> References: <0J4R0023BT895I10@l-daemon> Message-ID: Jim, :) I must have not seen your post, sorry, for what it's worth it's always on my sig. I use the site quite often myself because I couldn't remember where I would all this stuff, gmail was one place, but then found that other people could use it too, btw, if you have any tips you'd like to add please do forward them on. -- -Francisco http://sqlthis.blogspot.com | Tsql and More... On 8/29/06, Jim Lawrence wrote: > Fancisco: Now that would have been helpful about a month ago when it took a > week to migrate something that should have taken minutes. > > Jim > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco > Tapia > Sent: Tuesday, August 29, 2006 10:02 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > In order to prevent orphaned users, MS put out a script called > sp_help_revlogin you create it in the master database, details are on > my blog, > > http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-server.htm > l > > if you get lost from the links post back and I'll help you through it. > > > On 8/29/06, JWColby wrote: > > >The simple answer was given to him (JC) in the first post back to him. > > Which is why I never chimed in. > > > > >Detach it. > > >Copy it to the other machine. > > >Attach it. > > > > In fact that is only one of my two questions, but given my reception on > the > > other question I suppose I should just not ask again. > > > > In fact I have RTFM (in advance of even asking AAMOF) and I found stuff > > about disconnecting / reconnecting possibly causing "orphaned users", this > > being caused by the use of something like a PK from the OS user to > represent > > the user in the SQL Server login, and even though the user name is the > same > > on the two machines, the UserID is not necessarily the same. It does make > > me a bit leery of going the disconnect route. > > > > I had hoped to get both machines seeing the other (SQL Servers) and then > see > > if I could just query directly out of a table in one SQL Server and > transfer > > the data into the same table (new/empty) in the other SQL Server. I know > I > > can export the data to text files and then re-import back in, but given > the > > fact that the data is hundreds of gigabytes, I don't even want to go there > > if I can avoid it. > > > > Unfortunately I do not know enough about SQL Server / networking to > > troubleshoot the "why" of two servers not seeing each other, and given > that > > the list Gurus specifically want me to go become a SQL / Notwork DBA > before > > I ask such questions, it seems that I will get no assistance on that here. > > > > I have the database on 5 250gb drives, which I suppose I shall disconnect > > and then simply move the entire disks and pray for the best. > > > > There are other forums I belong to though, I'll also go see if anyone can > > help. This is going to be a lot of data and eventually I will need > machines > > preprocessing and then shipping the results to a central server, so the > > servers really do eventually need to see each other I think. It should be > > fun, and I should learn a lot, though perhaps not here. > > > > Thanks Stewart, > > > > John W. Colby > > Colby Consulting > > www.ColbyConsulting.com > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > > Stewart > > Sent: Tuesday, August 29, 2006 10:16 AM > > To: dba-sqlserver at databaseadvisors.com > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > > > As to why we are all here, it is to learn and hopefully help when we KNOW > > the answer. > > > > The simple answer was given to him (JC) in the first post back to him. > > Which is why I never chimed in. > > > > Detach it. > > Copy it to the other machine. > > Attach it. > > > > KISS - Keep it Supremely Simple > > > > Always works for me. > > > > Robert > > > > At 08:40 AM 8/29/2006, you wrote: > > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > > >From: "Haslett, Andrew" > > >Subject: Re: [dba-SQLServer] > > > [AccessD]TransferringadatabasetoanotherSQLServer > > >To: > > >Message-ID: > > > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > > >Content-Type: text/plain; charset="utf-8" > > > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > > >happy to ask for advice but only accept it when its something they want > > >to hear, and ignore it otherwise (demonstrated throughout the post > > >below) > > > > > >The points I made in my post apply to anyone looking to undertake > > >similar issues, and will continue to happen until someone has the guts > > >to say it, irrelevant of who it is aimed at (which is how it should be > > >-> on a public forum, favour or protection should not be given to > > >anyone simply because they are friends, associates or seniority). > > > > > >Ask yourself this -> Would you have made the same post Jim, had it not > > >have been aimed at Mr Colby?. > > > > > >Stark realities occasionally need be surfaced in order for them to sink > > >in.. Irrespective of the target or consequences. Was it harsh? > > >Yup. Could it perhaps prevent someone else from making the same > > >mistakes and undertaking projects without due preparation and planning? > > >Hopefully, and therefore I believe useful. > > > > > >John asked Stuart "Why are you here then?". Some of us prefer to > > >assist others, pass on what knowledge they can and in my case attempt > > >to 'help others, help themselves', as opposed to just feeding of > > >others. > > > > > >I know of a number who have left this (and the Access) list in the > > >past, including myself, for similar reasons and 'Matesmenship' in the > > >upper echelons. > > > > > >Please unsubscribe me from the list. > > > > > >Andrew > > > > > > _______________________________________________ > > 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 > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > _______________________________________________ > 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 http://sqlthis.blogspot.com | Tsql and More... From jwcolby at colbyconsulting.com Tue Aug 29 13:28:33 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Tue, 29 Aug 2006 14:28:33 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: Message-ID: <000401c6cb98$f0affa10$657aa8c0@m6805> Francisco, Yes, I could ping the other server. I have a 4 (currently) machine WFW network. I set up the internal IP range to 192.168.122.100-200, simply because I was getting collisions with clients when I tried to set up VPN. All of the machines can ping the others. I have always had issues with WFW and file sharing, sometimes it works, sometimes it doesn't, not sure why. IIRC there is a service that has to run on each machine which broadcasts to the other machines the local assigned IP address of that machine, kind of a "I'm here" kind of thing and also listen for such broadcasts from other machines? As I have said, I an not a notwork guy. In any event I had one of my old (three years now I think) AMD64 2ghz 2gbyte machines already running. It had SQL Server installed on it and I was using SQL Server on that machine to work on this rather large db. The response was not stellar when it came to doing things like shrinking a 200gbyte file back down, creating an index on a field etc. It would take off and run all day, essentially preventing me from doing anything else on that table, and really even on the SQL Server because so much horsepower was being used. So, says I, I'll go get an AMD X2 3800, a new motherboard and see if that helps, which is where I am now. I got the new machine set up, installed SQL Server on it and it couldn't "see" the other SQL Server instance running on my existing server. Nor could the existing SQL Server see the new SQL Server. In the past I had FOUR machines all running SQL Server and all could see each other, i.e. if you wanted to register the others, they were available and could be registered - at least IIRC. This was about a year or so ago now. So anyways, here I am with a new machine and no "coms" between them. And of course now even my pitiful little file sharing is broke so I can't just copy the files over the network, I have to physically move the disks. I have a gigabit switch between all of my machines and I am MOVING DISKS!!! Yea, I am not happy. 8-( And if course I need to go study hard and become a SQL Server Admin and Notwork admin so that I can dare to ask questions. I'll figure it out eventually but right now I need to get some work done, so I am moving disks. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, August 29, 2006 1:03 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server John, When you say you couldn't register the server on the other machine, were you still able to ping it? get to it's unc name via \\ServerName? these questions I never saw answered. (maybe I scrolled to quickly on your posts) On 8/29/06, JWColby wrote: > >The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > >Detach it. > >Copy it to the other machine. > >Attach it. > > In fact that is only one of my two questions, but given my reception > on the other question I suppose I should just not ask again. > > In fact I have RTFM (in advance of even asking AAMOF) and I found > stuff about disconnecting / reconnecting possibly causing "orphaned > users", this being caused by the use of something like a PK from the > OS user to represent the user in the SQL Server login, and even though > the user name is the same on the two machines, the UserID is not > necessarily the same. It does make me a bit leery of going the disconnect route. > > I had hoped to get both machines seeing the other (SQL Servers) and > then see if I could just query directly out of a table in one SQL > Server and transfer the data into the same table (new/empty) in the > other SQL Server. I know I can export the data to text files and then > re-import back in, but given the fact that the data is hundreds of > gigabytes, I don't even want to go there if I can avoid it. > > Unfortunately I do not know enough about SQL Server / networking to > troubleshoot the "why" of two servers not seeing each other, and given > that the list Gurus specifically want me to go become a SQL / Notwork > DBA before I ask such questions, it seems that I will get no assistance on that here. > > I have the database on 5 250gb drives, which I suppose I shall > disconnect and then simply move the entire disks and pray for the best. > > There are other forums I belong to though, I'll also go see if anyone > can help. This is going to be a lot of data and eventually I will > need machines preprocessing and then shipping the results to a central > server, so the servers really do eventually need to see each other I > think. It should be fun, and I should learn a lot, though perhaps not here. > > Thanks Stewart, > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > Stewart > Sent: Tuesday, August 29, 2006 10:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > Server > > As to why we are all here, it is to learn and hopefully help when we > KNOW the answer. > > The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > Detach it. > Copy it to the other machine. > Attach it. > > KISS - Keep it Supremely Simple > > Always works for me. > > Robert > > At 08:40 AM 8/29/2006, you wrote: > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > >From: "Haslett, Andrew" > >Subject: Re: [dba-SQLServer] > > [AccessD]TransferringadatabasetoanotherSQLServer > >To: > >Message-ID: > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > >Content-Type: text/plain; charset="utf-8" > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > >happy to ask for advice but only accept it when its something they > >want to hear, and ignore it otherwise (demonstrated throughout the > >post > >below) > > > >The points I made in my post apply to anyone looking to undertake > >similar issues, and will continue to happen until someone has the > >guts to say it, irrelevant of who it is aimed at (which is how it > >should be > >-> on a public forum, favour or protection should not be given to > >anyone simply because they are friends, associates or seniority). > > > >Ask yourself this -> Would you have made the same post Jim, had it > >not have been aimed at Mr Colby?. > > > >Stark realities occasionally need be surfaced in order for them to > >sink in.. Irrespective of the target or consequences. Was it harsh? > >Yup. Could it perhaps prevent someone else from making the same > >mistakes and undertaking projects without due preparation and planning? > >Hopefully, and therefore I believe useful. > > > >John asked Stuart "Why are you here then?". Some of us prefer to > >assist others, pass on what knowledge they can and in my case attempt > >to 'help others, help themselves', as opposed to just feeding of > >others. > > > >I know of a number who have left this (and the Access) list in the > >past, including myself, for similar reasons and 'Matesmenship' in the > >upper echelons. > > > >Please unsubscribe me from the list. > > > >Andrew > > > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 Tue Aug 29 13:34:30 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Tue, 29 Aug 2006 14:34:30 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <0J4R00J4WQUO5D30@l-daemon> Message-ID: <000601c6cb99$c50c24a0$657aa8c0@m6805> Yes, that is what I was asking kinda. In this case all I need to do is move the entire database. In the future I really want to have one machine process data from text files, do address correction / validation, get tables entirely set up and functioning and then transfer just that table to another server. Or perhaps even leave the table out on the machine it started on and attach to the table from the other server instance. ATM, neither machine can see the other, ether disk shares, nor server instances. I suspect that file shares will be the easiest of the two problems to fix and I need to get that happening regardless. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Tuesday, August 29, 2006 12:52 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Hi John: If it just requires moving the index and data files to the other computer, then attaching them that can be done as simply as copying the two important files from computer A to computer B. Given a database named MyDatabase just copy from directory ie: c:\Program Files\Microsoft SQL Server\MSSQL\Data files named MyDatabase.ldf and MyDatabase.mdf to the other computer or simpler yet just attach (MS SQL 2005), Microsoft SQL Server Management Studio > databases > right-mouse-click > select Attach > select Add and then just navigate to your computer that has the (data) MyDatabase.mdf file and select it. Is this what you are asking? HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 8:37 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server >The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. >Detach it. >Copy it to the other machine. >Attach it. In fact that is only one of my two questions, but given my reception on the other question I suppose I should just not ask again. In fact I have RTFM (in advance of even asking AAMOF) and I found stuff about disconnecting / reconnecting possibly causing "orphaned users", this being caused by the use of something like a PK from the OS user to represent the user in the SQL Server login, and even though the user name is the same on the two machines, the UserID is not necessarily the same. It does make me a bit leery of going the disconnect route. I had hoped to get both machines seeing the other (SQL Servers) and then see if I could just query directly out of a table in one SQL Server and transfer the data into the same table (new/empty) in the other SQL Server. I know I can export the data to text files and then re-import back in, but given the fact that the data is hundreds of gigabytes, I don't even want to go there if I can avoid it. Unfortunately I do not know enough about SQL Server / networking to troubleshoot the "why" of two servers not seeing each other, and given that the list Gurus specifically want me to go become a SQL / Notwork DBA before I ask such questions, it seems that I will get no assistance on that here. I have the database on 5 250gb drives, which I suppose I shall disconnect and then simply move the entire disks and pray for the best. There are other forums I belong to though, I'll also go see if anyone can help. This is going to be a lot of data and eventually I will need machines preprocessing and then shipping the results to a central server, so the servers really do eventually need to see each other I think. It should be fun, and I should learn a lot, though perhaps not here. Thanks Stewart, John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart Sent: Tuesday, August 29, 2006 10:16 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server As to why we are all here, it is to learn and hopefully help when we KNOW the answer. The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. Detach it. Copy it to the other machine. Attach it. KISS - Keep it Supremely Simple Always works for me. Robert At 08:40 AM 8/29/2006, you wrote: >Date: Tue, 29 Aug 2006 10:17:25 +0930 >From: "Haslett, Andrew" >Subject: Re: [dba-SQLServer] > [AccessD]TransferringadatabasetoanotherSQLServer >To: >Message-ID: > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> >Content-Type: text/plain; charset="utf-8" > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite >happy to ask for advice but only accept it when its something they want >to hear, and ignore it otherwise (demonstrated throughout the post >below) > >The points I made in my post apply to anyone looking to undertake >similar issues, and will continue to happen until someone has the guts >to say it, irrelevant of who it is aimed at (which is how it should be >-> on a public forum, favour or protection should not be given to >anyone simply because they are friends, associates or seniority). > >Ask yourself this -> Would you have made the same post Jim, had it not >have been aimed at Mr Colby?. > >Stark realities occasionally need be surfaced in order for them to sink >in.. Irrespective of the target or consequences. Was it harsh? >Yup. Could it perhaps prevent someone else from making the same >mistakes and undertaking projects without due preparation and planning? >Hopefully, and therefore I believe useful. > >John asked Stuart "Why are you here then?". Some of us prefer to >assist others, pass on what knowledge they can and in my case attempt >to 'help others, help themselves', as opposed to just feeding of >others. > >I know of a number who have left this (and the Access) list in the >past, including myself, for similar reasons and 'Matesmenship' in the >upper echelons. > >Please unsubscribe me from the list. > >Andrew _______________________________________________ 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 jwcolby at colbyconsulting.com Tue Aug 29 14:56:34 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Tue, 29 Aug 2006 15:56:34 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: Message-ID: <000c01c6cba5$3f067cf0$657aa8c0@m6805> >I ask because I've had situations where you can see the other server by navigating to it, but cannot register it locally. And what does this mean? Navigate to it as in using Windows Explorer? Or by using something inside of SQL Server? BTW, I moved the drives, remapped them on the new machine so that the drives are mapped to the same drive letters that they were on the old machine. I can locate and attach only one of the three files that made up the SQL Server on the other machine. Now, when I detached the drives in SQL Server on the original machine, I immediately went in and reattached the files and all three reattached. On the new machine, the files can be seen by windows explorer, and can be found and the attach attempted by SQL Server, but SQL Server claims that the other two files are not SQL Server files. Luckily the one big table APPEARS to be in then one that did attach correctly. Any way to figure out why the second and third files are not attaching? If trying to use just the one file, is this database now corrupted? I mean 2 out of three files are no longer there, and they had SOMETHING in them because they would only compress to 50g down from 150g. They might have had index stuff because the last thing I did was create a PK (autoincrement) which of course went out and built an index and stuff. The PK field is in the table. So se whether the index is though. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, August 29, 2006 2:23 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server So I never knew if your machine could see the other, or was just not registering on the 2nd server. I ask because i've had situations where you can see the other server by navigting to it, but cannot register it locally. On 8/29/06, JWColby wrote: > Thanks for this Francisco. I am in the process of tearing my two > machines apart to move the physical drives from one to the other. > We'll see how it all goes. > > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > Francisco Tapia > Sent: Tuesday, August 29, 2006 1:02 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > Server > > In order to prevent orphaned users, MS put out a script called > sp_help_revlogin you create it in the master database, details are on > my blog, > > http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-serv > er.htm > l > > if you get lost from the links post back and I'll help you through it. > > > On 8/29/06, JWColby wrote: > > >The simple answer was given to him (JC) in the first post back to him. > > Which is why I never chimed in. > > > > >Detach it. > > >Copy it to the other machine. > > >Attach it. > > > > In fact that is only one of my two questions, but given my reception > > on the other question I suppose I should just not ask again. > > > > In fact I have RTFM (in advance of even asking AAMOF) and I found > > stuff about disconnecting / reconnecting possibly causing "orphaned > > users", this being caused by the use of something like a PK from the > > OS user to represent the user in the SQL Server login, and even > > though the user name is the same on the two machines, the UserID is > > not necessarily the same. It does make me a bit leery of going the > > disconnect > route. > > > > I had hoped to get both machines seeing the other (SQL Servers) and > > then see if I could just query directly out of a table in one SQL > > Server and transfer the data into the same table (new/empty) in the > > other SQL Server. I know I can export the data to text files and > > then re-import back in, but given the fact that the data is hundreds > > of gigabytes, I don't even want to go there if I can avoid it. > > > > Unfortunately I do not know enough about SQL Server / networking to > > troubleshoot the "why" of two servers not seeing each other, and > > given that the list Gurus specifically want me to go become a SQL / > > Notwork DBA before I ask such questions, it seems that I will get no > > assistance on > that here. > > > > I have the database on 5 250gb drives, which I suppose I shall > > disconnect and then simply move the entire disks and pray for the best. > > > > There are other forums I belong to though, I'll also go see if > > anyone can help. This is going to be a lot of data and eventually I > > will need machines preprocessing and then shipping the results to a > > central server, so the servers really do eventually need to see each > > other I think. It should be fun, and I should learn a lot, though > > perhaps not > here. > > > > Thanks Stewart, > > > > John W. Colby > > Colby Consulting > > www.ColbyConsulting.com > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > > Stewart > > Sent: Tuesday, August 29, 2006 10:16 AM > > To: dba-sqlserver at databaseadvisors.com > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > Server > > > > As to why we are all here, it is to learn and hopefully help when we > > KNOW the answer. > > > > The simple answer was given to him (JC) in the first post back to him. > > Which is why I never chimed in. > > > > Detach it. > > Copy it to the other machine. > > Attach it. > > > > KISS - Keep it Supremely Simple > > > > Always works for me. > > > > Robert > > > > At 08:40 AM 8/29/2006, you wrote: > > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > > >From: "Haslett, Andrew" > > >Subject: Re: [dba-SQLServer] > > > [AccessD]TransferringadatabasetoanotherSQLServer > > >To: > > >Message-ID: > > > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > > >Content-Type: text/plain; charset="utf-8" > > > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > > >happy to ask for advice but only accept it when its something they > > >want to hear, and ignore it otherwise (demonstrated throughout the > > >post > > >below) > > > > > >The points I made in my post apply to anyone looking to undertake > > >similar issues, and will continue to happen until someone has the > > >guts to say it, irrelevant of who it is aimed at (which is how it > > >should be > > >-> on a public forum, favour or protection should not be given to > > >anyone simply because they are friends, associates or seniority). > > > > > >Ask yourself this -> Would you have made the same post Jim, had it > > >not have been aimed at Mr Colby?. > > > > > >Stark realities occasionally need be surfaced in order for them to > > >sink in.. Irrespective of the target or consequences. Was it harsh? > > >Yup. Could it perhaps prevent someone else from making the same > > >mistakes and undertaking projects without due preparation and planning? > > >Hopefully, and therefore I believe useful. > > > > > >John asked Stuart "Why are you here then?". Some of us prefer to > > >assist others, pass on what knowledge they can and in my case > > >attempt to 'help others, help themselves', as opposed to just > > >feeding of others. > > > > > >I know of a number who have left this (and the Access) list in the > > >past, including myself, for similar reasons and 'Matesmenship' in > > >the upper echelons. > > > > > >Please unsubscribe me from the list. > > > > > >Andrew > > > > > > _______________________________________________ > > 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 > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 Aug 29 15:19:18 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 13:19:18 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <000c01c6cba5$3f067cf0$657aa8c0@m6805> References: <000c01c6cba5$3f067cf0$657aa8c0@m6805> Message-ID: Yes when I ment navigate I ment via Windows Explorer. I was only able to get to them via Sql Server after I updated the client network utility and made sure that both the TCP/IP Named pipes. This next q' sounds silly but... are you all patched up on your sql server? On 8/29/06, JWColby wrote: > >I ask because I've had situations where you can see the other server by > navigating to it, but cannot register it locally. > > And what does this mean? Navigate to it as in using Windows Explorer? Or > by using something inside of SQL Server? > > BTW, I moved the drives, remapped them on the new machine so that the drives > are mapped to the same drive letters that they were on the old machine. I > can locate and attach only one of the three files that made up the SQL > Server on the other machine. Now, when I detached the drives in SQL Server > on the original machine, I immediately went in and reattached the files and > all three reattached. On the new machine, the files can be seen by windows > explorer, and can be found and the attach attempted by SQL Server, but SQL > Server claims that the other two files are not SQL Server files. > > Luckily the one big table APPEARS to be in then one that did attach > correctly. Any way to figure out why the second and third files are not > attaching? If trying to use just the one file, is this database now > corrupted? I mean 2 out of three files are no longer there, and they had > SOMETHING in them because they would only compress to 50g down from 150g. > They might have had index stuff because the last thing I did was create a PK > (autoincrement) which of course went out and built an index and stuff. The > PK field is in the table. So se whether the index is though. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco > Tapia > Sent: Tuesday, August 29, 2006 2:23 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > So I never knew if your machine could see the other, or was just not > registering on the 2nd server. I ask because i've had situations where you > can see the other server by navigting to it, but cannot register it locally. > > On 8/29/06, JWColby wrote: > > Thanks for this Francisco. I am in the process of tearing my two > > machines apart to move the physical drives from one to the other. > > We'll see how it all goes. > > > > > > John W. Colby > > Colby Consulting > > www.ColbyConsulting.com > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > Francisco Tapia > > Sent: Tuesday, August 29, 2006 1:02 PM > > To: dba-sqlserver at databaseadvisors.com > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > Server > > > > In order to prevent orphaned users, MS put out a script called > > sp_help_revlogin you create it in the master database, details are on > > my blog, > > > > http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-serv > > er.htm > > l > > > > if you get lost from the links post back and I'll help you through it. > > > > > > On 8/29/06, JWColby wrote: > > > >The simple answer was given to him (JC) in the first post back to him. > > > Which is why I never chimed in. > > > > > > >Detach it. > > > >Copy it to the other machine. > > > >Attach it. > > > > > > In fact that is only one of my two questions, but given my reception > > > on the other question I suppose I should just not ask again. > > > > > > In fact I have RTFM (in advance of even asking AAMOF) and I found > > > stuff about disconnecting / reconnecting possibly causing "orphaned > > > users", this being caused by the use of something like a PK from the > > > OS user to represent the user in the SQL Server login, and even > > > though the user name is the same on the two machines, the UserID is > > > not necessarily the same. It does make me a bit leery of going the > > > disconnect > > route. > > > > > > I had hoped to get both machines seeing the other (SQL Servers) and > > > then see if I could just query directly out of a table in one SQL > > > Server and transfer the data into the same table (new/empty) in the > > > other SQL Server. I know I can export the data to text files and > > > then re-import back in, but given the fact that the data is hundreds > > > of gigabytes, I don't even want to go there if I can avoid it. > > > > > > Unfortunately I do not know enough about SQL Server / networking to > > > troubleshoot the "why" of two servers not seeing each other, and > > > given that the list Gurus specifically want me to go become a SQL / > > > Notwork DBA before I ask such questions, it seems that I will get no > > > assistance on > > that here. > > > > > > I have the database on 5 250gb drives, which I suppose I shall > > > disconnect and then simply move the entire disks and pray for the best. > > > > > > There are other forums I belong to though, I'll also go see if > > > anyone can help. This is going to be a lot of data and eventually I > > > will need machines preprocessing and then shipping the results to a > > > central server, so the servers really do eventually need to see each > > > other I think. It should be fun, and I should learn a lot, though > > > perhaps not > > here. > > > > > > Thanks Stewart, > > > > > > John W. Colby > > > Colby Consulting > > > www.ColbyConsulting.com > > > > > > -----Original Message----- > > > From: dba-sqlserver-bounces at databaseadvisors.com > > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert > L. > > > Stewart > > > Sent: Tuesday, August 29, 2006 10:16 AM > > > To: dba-sqlserver at databaseadvisors.com > > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > > Server > > > > > > As to why we are all here, it is to learn and hopefully help when we > > > KNOW the answer. > > > > > > The simple answer was given to him (JC) in the first post back to him. > > > Which is why I never chimed in. > > > > > > Detach it. > > > Copy it to the other machine. > > > Attach it. > > > > > > KISS - Keep it Supremely Simple > > > > > > Always works for me. > > > > > > Robert > > > > > > At 08:40 AM 8/29/2006, you wrote: > > > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > > > >From: "Haslett, Andrew" > > > >Subject: Re: [dba-SQLServer] > > > > [AccessD]TransferringadatabasetoanotherSQLServer > > > >To: > > > >Message-ID: > > > > > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > > > >Content-Type: text/plain; charset="utf-8" > > > > > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > > > >happy to ask for advice but only accept it when its something they > > > >want to hear, and ignore it otherwise (demonstrated throughout the > > > >post > > > >below) > > > > > > > >The points I made in my post apply to anyone looking to undertake > > > >similar issues, and will continue to happen until someone has the > > > >guts to say it, irrelevant of who it is aimed at (which is how it > > > >should be > > > >-> on a public forum, favour or protection should not be given to > > > >anyone simply because they are friends, associates or seniority). > > > > > > > >Ask yourself this -> Would you have made the same post Jim, had it > > > >not have been aimed at Mr Colby?. > > > > > > > >Stark realities occasionally need be surfaced in order for them to > > > >sink in.. Irrespective of the target or consequences. Was it harsh? > > > >Yup. Could it perhaps prevent someone else from making the same > > > >mistakes and undertaking projects without due preparation and planning? > > > >Hopefully, and therefore I believe useful. > > > > > > > >John asked Stuart "Why are you here then?". Some of us prefer to > > > >assist others, pass on what knowledge they can and in my case > > > >attempt to 'help others, help themselves', as opposed to just > > > >feeding of others. > > > > > > > >I know of a number who have left this (and the Access) list in the > > > >past, including myself, for similar reasons and 'Matesmenship' in > > > >the upper echelons. > > > > > > > >Please unsubscribe me from the list. > > > > > > > >Andrew > > > > > > > > > _______________________________________________ > > > 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 > > http://pcthis.blogspot.com |PC news with out the jargon! > > http://sqlthis.blogspot.com | Tsql and More... > > _______________________________________________ > > 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 > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Tue Aug 29 15:30:41 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 13:30:41 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <000c01c6cba5$3f067cf0$657aa8c0@m6805> References: <000c01c6cba5$3f067cf0$657aa8c0@m6805> Message-ID: Indexes are generally created in the default filegroup (generally the first one you start with) unless you explicitly tell it to create the index in another filegroup. It is really bizar that the two other files will not even attach, especially if you're using the exact same command as before. I'll have to dig around here to see If I have any notes on that. -- Francisco On 8/29/06, JWColby wrote: > >I ask because I've had situations where you can see the other server by > navigating to it, but cannot register it locally. > > And what does this mean? Navigate to it as in using Windows Explorer? Or > by using something inside of SQL Server? > > BTW, I moved the drives, remapped them on the new machine so that the drives > are mapped to the same drive letters that they were on the old machine. I > can locate and attach only one of the three files that made up the SQL > Server on the other machine. Now, when I detached the drives in SQL Server > on the original machine, I immediately went in and reattached the files and > all three reattached. On the new machine, the files can be seen by windows > explorer, and can be found and the attach attempted by SQL Server, but SQL > Server claims that the other two files are not SQL Server files. > > Luckily the one big table APPEARS to be in then one that did attach > correctly. Any way to figure out why the second and third files are not > attaching? If trying to use just the one file, is this database now > corrupted? I mean 2 out of three files are no longer there, and they had > SOMETHING in them because they would only compress to 50g down from 150g. > They might have had index stuff because the last thing I did was create a PK > (autoincrement) which of course went out and built an index and stuff. The > PK field is in the table. So se whether the index is though. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco > Tapia > Sent: Tuesday, August 29, 2006 2:23 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > So I never knew if your machine could see the other, or was just not > registering on the 2nd server. I ask because i've had situations where you > can see the other server by navigting to it, but cannot register it locally. > > On 8/29/06, JWColby wrote: > > Thanks for this Francisco. I am in the process of tearing my two > > machines apart to move the physical drives from one to the other. > > We'll see how it all goes. > > > > > > John W. Colby > > Colby Consulting > > www.ColbyConsulting.com > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > Francisco Tapia > > Sent: Tuesday, August 29, 2006 1:02 PM > > To: dba-sqlserver at databaseadvisors.com > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > Server > > > > In order to prevent orphaned users, MS put out a script called > > sp_help_revlogin you create it in the master database, details are on > > my blog, > > > > http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-serv > > er.htm > > l > > > > if you get lost from the links post back and I'll help you through it. > > > > > > On 8/29/06, JWColby wrote: > > > >The simple answer was given to him (JC) in the first post back to him. > > > Which is why I never chimed in. > > > > > > >Detach it. > > > >Copy it to the other machine. > > > >Attach it. > > > > > > In fact that is only one of my two questions, but given my reception > > > on the other question I suppose I should just not ask again. > > > > > > In fact I have RTFM (in advance of even asking AAMOF) and I found > > > stuff about disconnecting / reconnecting possibly causing "orphaned > > > users", this being caused by the use of something like a PK from the > > > OS user to represent the user in the SQL Server login, and even > > > though the user name is the same on the two machines, the UserID is > > > not necessarily the same. It does make me a bit leery of going the > > > disconnect > > route. > > > > > > I had hoped to get both machines seeing the other (SQL Servers) and > > > then see if I could just query directly out of a table in one SQL > > > Server and transfer the data into the same table (new/empty) in the > > > other SQL Server. I know I can export the data to text files and > > > then re-import back in, but given the fact that the data is hundreds > > > of gigabytes, I don't even want to go there if I can avoid it. > > > > > > Unfortunately I do not know enough about SQL Server / networking to > > > troubleshoot the "why" of two servers not seeing each other, and > > > given that the list Gurus specifically want me to go become a SQL / > > > Notwork DBA before I ask such questions, it seems that I will get no > > > assistance on > > that here. > > > > > > I have the database on 5 250gb drives, which I suppose I shall > > > disconnect and then simply move the entire disks and pray for the best. > > > > > > There are other forums I belong to though, I'll also go see if > > > anyone can help. This is going to be a lot of data and eventually I > > > will need machines preprocessing and then shipping the results to a > > > central server, so the servers really do eventually need to see each > > > other I think. It should be fun, and I should learn a lot, though > > > perhaps not > > here. > > > > > > Thanks Stewart, > > > > > > John W. Colby > > > Colby Consulting > > > www.ColbyConsulting.com > > > > > > -----Original Message----- > > > From: dba-sqlserver-bounces at databaseadvisors.com > > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert > L. > > > Stewart > > > Sent: Tuesday, August 29, 2006 10:16 AM > > > To: dba-sqlserver at databaseadvisors.com > > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > > Server > > > > > > As to why we are all here, it is to learn and hopefully help when we > > > KNOW the answer. > > > > > > The simple answer was given to him (JC) in the first post back to him. > > > Which is why I never chimed in. > > > > > > Detach it. > > > Copy it to the other machine. > > > Attach it. > > > > > > KISS - Keep it Supremely Simple > > > > > > Always works for me. > > > > > > Robert > > > > > > At 08:40 AM 8/29/2006, you wrote: > > > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > > > >From: "Haslett, Andrew" > > > >Subject: Re: [dba-SQLServer] > > > > [AccessD]TransferringadatabasetoanotherSQLServer > > > >To: > > > >Message-ID: > > > > > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > > > >Content-Type: text/plain; charset="utf-8" > > > > > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > > > >happy to ask for advice but only accept it when its something they > > > >want to hear, and ignore it otherwise (demonstrated throughout the > > > >post > > > >below) > > > > > > > >The points I made in my post apply to anyone looking to undertake > > > >similar issues, and will continue to happen until someone has the > > > >guts to say it, irrelevant of who it is aimed at (which is how it > > > >should be > > > >-> on a public forum, favour or protection should not be given to > > > >anyone simply because they are friends, associates or seniority). > > > > > > > >Ask yourself this -> Would you have made the same post Jim, had it > > > >not have been aimed at Mr Colby?. > > > > > > > >Stark realities occasionally need be surfaced in order for them to > > > >sink in.. Irrespective of the target or consequences. Was it harsh? > > > >Yup. Could it perhaps prevent someone else from making the same > > > >mistakes and undertaking projects without due preparation and planning? > > > >Hopefully, and therefore I believe useful. > > > > > > > >John asked Stuart "Why are you here then?". Some of us prefer to > > > >assist others, pass on what knowledge they can and in my case > > > >attempt to 'help others, help themselves', as opposed to just > > > >feeding of others. > > > > > > > >I know of a number who have left this (and the Access) list in the > > > >past, including myself, for similar reasons and 'Matesmenship' in > > > >the upper echelons. > > > > > > > >Please unsubscribe me from the list. > > > > > > > >Andrew > > > > > > > > > _______________________________________________ > > > 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 > > http://pcthis.blogspot.com |PC news with out the jargon! > > http://sqlthis.blogspot.com | Tsql and More... > > _______________________________________________ > > 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 > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From artful at rogers.com Tue Aug 29 15:38:12 2006 From: artful at rogers.com (artful at rogers.com) Date: Tue, 29 Aug 2006 13:38:12 -0700 (PDT) Subject: [dba-SQLServer] SQL Injection and Sprocs Message-ID: <20060829203812.85433.qmail@web88210.mail.re2.yahoo.com> Rightly or wrongly, I have been under the impression that the saftest method of avoiding SQL injection attacks is by using Sprocs exclusively. My theory is that Sproc parameters are typed, and also handled differently, than variables that might be plugged into a dynamic SQL statement. Have you ever seen an example that proves my theory incorrect? I.e. imagine some form that obtains three variables from a user, then fires a sproc and passes it these three variables. To spice up the argument, imagine that one textbox is text, one numeric and one date. I have done various experiments on this scenario, and I cannot come up with a single case that fools the underlying sproc. Can you? Thanks, Arthur From fhtapia at gmail.com Tue Aug 29 15:48:42 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 13:48:42 -0700 Subject: [dba-SQLServer] [SQL2K] Reporting Services 2000, 2nd Y Axis Chart In-Reply-To: <1238747390_69872264@mail.sswug.org> References: <967769968_69856829@mail.sswug.org> <1238747390_69872264@mail.sswug.org> Message-ID: For those of you who were sitting at the edge of your seat just waiting for the conclusion of the TrendLine capper, this is the solution I was happy with. DECLARE @TrendTable TABLE (PID INT IDENTITY (1,1), XColumn smalldatetime, YColumn1 REAL, YColumn2 INT, Trend REAL) --- /* At this point populate the @TrendTable with your data, the Xcolumn is of course plotted data on the x axis, On this example I've put in a Y column and a 2nd Y column for your charting needs, YColumn1 is the column that will be trended. */ --- DECLARE @n REAL DECLARE @sumX REAL DECLARE @sumY REAL DECLARE @sumXY REAL DECLARE @sumX2 REAL DECLARE @sumY2 REAL DECLARE @sumX_2 REAL DECLARE @sumY_2 REAL DECLARE @m REAL DECLARE @b REAL DECLARE @r REAL SELECT @n = COUNT(*), @sumX=SUM(PID), @sumY=SUM(YColumn1), @sumXY=SUM(PID*YColumn1), @sumX2=SUM(POWER(PID,2)), @sumY2=SUM(POWER(YColumn1,2)) FROM @TrendTable SELECT @sumX_2 = POWER(@sumX,2), @sumY_2 = POWER(@sumY,2) --slope SELECT @m = (@n*@sumXY- at sumX*@sumY)/(@n*@sumX2- at sumX_2) --y intercept SELECT @b = (@sumY- at m*@sumX)/@n --r SELECT @r = (@n*@sumXY- at sumX*@sumY)/SQRT((@n*@sumX2- at sumX_2)*(@n*@sumY2- at sumY_2)) UPDATE @TrendTable SET Trend = @m * PID + @b SELECT * FROM @TrendTable On 8/14/06, Francisco Tapia wrote: > Robert, > I have 2 data points, one is the installs, and the other is the avg > # of fails, I wanted to trend the Avg # fails, but RS doesn't do that, > and it doesn't seem to allow you to have a 2nd Y axis. I am looking > into creating my own trendline manually, so I will just need to live > w/o the 2nd y axis. > > On 8/11/06, MacQueen, Robert wrote: > > > > > > Francisco, > > Not clear on this - are you saying you want the second Y-Axis to be a trend > > line, or you would like a trendline created on the data in the second > > Y-axis. If the former, the chart control allows for multiple data values - > > in the chart properties, go to the Data tab and click on Add in the Values > > area of the form. If the latter, I did not see anything that allows a > > trend-line to be added. Excel has that feature, but I did not see an option > > to add that in Reporting Services chart properties, and Rep Svcs BOL does > > not mention it. > > > > Robert > > > > ________________________________ > > From: listbounces at sswug.org [mailto:listbounces at sswug.org] On Behalf Of > > Francisco Tapia > > Sent: Thursday, August 10, 2006 5:50 PM > > To: dba-sqlserver at databaseadvisors.com; RepSvcs; SQL Server > > 2k List > > Subject: [SQL2K] Reporting Services 2000, 2nd Y Axis Chart > > > > > > (sorry for the cross-post) > > > > I've been googling for the answer all yesterday afternoon, and today > > morning, but to no avail, > > I have a report that looks a bit like the following: > > Month, Fail, Installed > > 1/1/2000, 3, 300 > > 2/1/2000, 1.5, 256 > > 3/1/2000, 2.5, 280 > > ... > > ... > > The purpose it to graph the report with one of the series on a second y > > axis, then on this 2nd axis I'm supposed to generate a trend line. Any > > advice on this in Sql Server Reporting services (2000) would be much > > appreciated. > > > > > > > > Thanks, > > > > -- > > -Francisco > > http://pcthis.blogspot.com |PC news with out the jargon! > > http://sqlthis.blogspot.com | Tsql and More... > > > > ------ > > For archives, see http://www.sswug.org/archives > > For list assistance, contact members at sswug.org > > To unsubscribe, email lists at sswug.org with > > UNSUBSCRIBE SQL2K in the body of the message. > > > > > > ------ > > For archives, see http://www.sswug.org/archives > > For list assistance, contact members at sswug.org > > To unsubscribe, email lists at sswug.org with > > UNSUBSCRIBE SQL2K in the body of the message. > > > > > > > -- > -Francisco > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > > > ------ > For archives, see http://www.sswug.org/archives > For list assistance, contact members at sswug.org > To unsubscribe, email lists at sswug.org with > UNSUBSCRIBE SQL2K in the body of the message. > > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Tue Aug 29 15:50:15 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 13:50:15 -0700 Subject: [dba-SQLServer] SQL Injection and Sprocs In-Reply-To: <20060829203812.85433.qmail@web88210.mail.re2.yahoo.com> References: <20060829203812.85433.qmail@web88210.mail.re2.yahoo.com> Message-ID: There is one bad form, A developer who used to work here took it upon himself to use a "global" sproc, in wich it takes an @nText parameter and executes it in the stored procedure. blah! (note used to work here) On 8/29/06, artful at rogers.com wrote: > Rightly or wrongly, I have been under the impression that the saftest method of avoiding SQL injection attacks is by using Sprocs exclusively. My theory is that Sproc parameters are typed, and also handled differently, than variables that might be plugged into a dynamic SQL statement. > > Have you ever seen an example that proves my theory incorrect? I.e. imagine some form that obtains three variables from a user, then fires a sproc and passes it these three variables. To spice up the argument, imagine that one textbox is text, one numeric and one date. > > I have done various experiments on this scenario, and I cannot come up with a single case that fools the underlying sproc. Can you? > > Thanks, > Arthur > > _______________________________________________ > 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! http://sqlthis.blogspot.com | Tsql and More... From jwcolby at colbyconsulting.com Tue Aug 29 16:04:30 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Tue, 29 Aug 2006 17:04:30 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: Message-ID: <000e01c6cbae$b9c5e4e0$657aa8c0@m6805> >This next q' sounds silly but... are you all patched up on your sql server? No that is not at all silly, and since the answer is "I don't know" the assumption could be "NO". I will look at that. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, August 29, 2006 4:19 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Yes when I ment navigate I ment via Windows Explorer. I was only able to get to them via Sql Server after I updated the client network utility and made sure that both the TCP/IP Named pipes. This next q' sounds silly but... are you all patched up on your sql server? On 8/29/06, JWColby wrote: > >I ask because I've had situations where you can see the other server > >by > navigating to it, but cannot register it locally. > > And what does this mean? Navigate to it as in using Windows Explorer? > Or by using something inside of SQL Server? > > BTW, I moved the drives, remapped them on the new machine so that the > drives are mapped to the same drive letters that they were on the old > machine. I can locate and attach only one of the three files that > made up the SQL Server on the other machine. Now, when I detached the > drives in SQL Server on the original machine, I immediately went in > and reattached the files and all three reattached. On the new > machine, the files can be seen by windows explorer, and can be found > and the attach attempted by SQL Server, but SQL Server claims that the other two files are not SQL Server files. > > Luckily the one big table APPEARS to be in then one that did attach > correctly. Any way to figure out why the second and third files are > not attaching? If trying to use just the one file, is this database > now corrupted? I mean 2 out of three files are no longer there, and > they had SOMETHING in them because they would only compress to 50g down from 150g. > They might have had index stuff because the last thing I did was > create a PK > (autoincrement) which of course went out and built an index and stuff. > The PK field is in the table. So se whether the index is though. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > Francisco Tapia > Sent: Tuesday, August 29, 2006 2:23 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > Server > > So I never knew if your machine could see the other, or was just not > registering on the 2nd server. I ask because i've had situations > where you can see the other server by navigting to it, but cannot register it locally. > > On 8/29/06, JWColby wrote: > > Thanks for this Francisco. I am in the process of tearing my two > > machines apart to move the physical drives from one to the other. > > We'll see how it all goes. > > > > > > John W. Colby > > Colby Consulting > > www.ColbyConsulting.com > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > Francisco Tapia > > Sent: Tuesday, August 29, 2006 1:02 PM > > To: dba-sqlserver at databaseadvisors.com > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > Server > > > > In order to prevent orphaned users, MS put out a script called > > sp_help_revlogin you create it in the master database, details are > > on my blog, > > > > http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-se > > rv > > er.htm > > l > > > > if you get lost from the links post back and I'll help you through it. > > > > > > On 8/29/06, JWColby wrote: > > > >The simple answer was given to him (JC) in the first post back to him. > > > Which is why I never chimed in. > > > > > > >Detach it. > > > >Copy it to the other machine. > > > >Attach it. > > > > > > In fact that is only one of my two questions, but given my > > > reception on the other question I suppose I should just not ask again. > > > > > > In fact I have RTFM (in advance of even asking AAMOF) and I found > > > stuff about disconnecting / reconnecting possibly causing > > > "orphaned users", this being caused by the use of something like a > > > PK from the OS user to represent the user in the SQL Server login, > > > and even though the user name is the same on the two machines, the > > > UserID is not necessarily the same. It does make me a bit leery > > > of going the disconnect > > route. > > > > > > I had hoped to get both machines seeing the other (SQL Servers) > > > and then see if I could just query directly out of a table in one > > > SQL Server and transfer the data into the same table (new/empty) > > > in the other SQL Server. I know I can export the data to text > > > files and then re-import back in, but given the fact that the data > > > is hundreds of gigabytes, I don't even want to go there if I can avoid it. > > > > > > Unfortunately I do not know enough about SQL Server / networking > > > to troubleshoot the "why" of two servers not seeing each other, > > > and given that the list Gurus specifically want me to go become a > > > SQL / Notwork DBA before I ask such questions, it seems that I > > > will get no assistance on > > that here. > > > > > > I have the database on 5 250gb drives, which I suppose I shall > > > disconnect and then simply move the entire disks and pray for the best. > > > > > > There are other forums I belong to though, I'll also go see if > > > anyone can help. This is going to be a lot of data and eventually > > > I will need machines preprocessing and then shipping the results > > > to a central server, so the servers really do eventually need to > > > see each other I think. It should be fun, and I should learn a > > > lot, though perhaps not > > here. > > > > > > Thanks Stewart, > > > > > > John W. Colby > > > Colby Consulting > > > www.ColbyConsulting.com > > > > > > -----Original Message----- > > > From: dba-sqlserver-bounces at databaseadvisors.com > > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > > Robert > L. > > > Stewart > > > Sent: Tuesday, August 29, 2006 10:16 AM > > > To: dba-sqlserver at databaseadvisors.com > > > Subject: Re: [dba-SQLServer] Transferring a database to another > > > SQL Server > > > > > > As to why we are all here, it is to learn and hopefully help when > > > we KNOW the answer. > > > > > > The simple answer was given to him (JC) in the first post back to him. > > > Which is why I never chimed in. > > > > > > Detach it. > > > Copy it to the other machine. > > > Attach it. > > > > > > KISS - Keep it Supremely Simple > > > > > > Always works for me. > > > > > > Robert > > > > > > At 08:40 AM 8/29/2006, you wrote: > > > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > > > >From: "Haslett, Andrew" > > > >Subject: Re: [dba-SQLServer] > > > > [AccessD]TransferringadatabasetoanotherSQLServer > > > >To: > > > >Message-ID: > > > > > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > > > >Content-Type: text/plain; charset="utf-8" > > > > > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are > > > >quite happy to ask for advice but only accept it when its > > > >something they want to hear, and ignore it otherwise > > > >(demonstrated throughout the post > > > >below) > > > > > > > >The points I made in my post apply to anyone looking to undertake > > > >similar issues, and will continue to happen until someone has the > > > >guts to say it, irrelevant of who it is aimed at (which is how it > > > >should be > > > >-> on a public forum, favour or protection should not be given to > > > >anyone simply because they are friends, associates or seniority). > > > > > > > >Ask yourself this -> Would you have made the same post Jim, had > > > >it not have been aimed at Mr Colby?. > > > > > > > >Stark realities occasionally need be surfaced in order for them > > > >to sink in.. Irrespective of the target or consequences. Was it harsh? > > > >Yup. Could it perhaps prevent someone else from making the same > > > >mistakes and undertaking projects without due preparation and planning? > > > >Hopefully, and therefore I believe useful. > > > > > > > >John asked Stuart "Why are you here then?". Some of us prefer to > > > >assist others, pass on what knowledge they can and in my case > > > >attempt to 'help others, help themselves', as opposed to just > > > >feeding of others. > > > > > > > >I know of a number who have left this (and the Access) list in > > > >the past, including myself, for similar reasons and > > > >'Matesmenship' in the upper echelons. > > > > > > > >Please unsubscribe me from the list. > > > > > > > >Andrew > > > > > > > > > _______________________________________________ > > > 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 > > http://pcthis.blogspot.com |PC news with out the jargon! > > http://sqlthis.blogspot.com | Tsql and More... > > _______________________________________________ > > 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 > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From stuart at lexacorp.com.pg Tue Aug 29 16:31:21 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Wed, 30 Aug 2006 07:31:21 +1000 Subject: [dba-SQLServer] SQL Injection and Sprocs In-Reply-To: <20060829203812.85433.qmail@web88210.mail.re2.yahoo.com> References: <20060829203812.85433.qmail@web88210.mail.re2.yahoo.com> Message-ID: <44F53EC9.31096.6F766FFA@stuart.lexacorp.com.pg> On 29 Aug 2006 at 13:38, artful at rogers.com wrote: > Rightly or wrongly, I have been under the impression that the saftest method > of avoiding SQL injection attacks is by using Sprocs exclusively. My theory > is that Sproc parameters are typed, and also handled differently, than > variables that might be plugged into a dynamic SQL statement. > > Have you ever seen an example that proves my theory incorrect? No :-) > I.e. imagine > some form that obtains three variables from a user, then fires a sproc and > passes it these three variables. To spice up the argument, imagine that one > textbox is text, one numeric and one date. > > I have done various experiments on this scenario, and I cannot come up with > a single case that fools the underlying sproc. Can you? The risk in SQL Injection is feeding a syntactically correct SQL statement at the end of you SQL string by appending malformed user-input strings when you build and execute a dynamic string in code. By forcing these user-input parameters into sproc parameters, they become "just data" inside the sproc and there is no way for them to actually be executed. -- Stuart From fhtapia at gmail.com Tue Aug 29 16:33:07 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 29 Aug 2006 14:33:07 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <000e01c6cbae$b9c5e4e0$657aa8c0@m6805> References: <000e01c6cbae$b9c5e4e0$657aa8c0@m6805> Message-ID: I'm also guessing we're working with SS2000, so you do want to patch to SP4. On 8/29/06, JWColby wrote: > >This next q' sounds silly but... are you all patched up on your sql server? > > No that is not at all silly, and since the answer is "I don't know" the > assumption could be "NO". > > I will look at that. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco > Tapia > Sent: Tuesday, August 29, 2006 4:19 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > Yes when I ment navigate I ment via Windows Explorer. I was only able to > get to them via Sql Server after I updated the client network utility and > made sure that both the TCP/IP Named pipes. > > This next q' sounds silly but... are you all patched up on your sql server? > > > > On 8/29/06, JWColby wrote: > > >I ask because I've had situations where you can see the other server > > >by > > navigating to it, but cannot register it locally. > > > > And what does this mean? Navigate to it as in using Windows Explorer? > > Or by using something inside of SQL Server? > > > > BTW, I moved the drives, remapped them on the new machine so that the > > drives are mapped to the same drive letters that they were on the old > > machine. I can locate and attach only one of the three files that > > made up the SQL Server on the other machine. Now, when I detached the > > drives in SQL Server on the original machine, I immediately went in > > and reattached the files and all three reattached. On the new > > machine, the files can be seen by windows explorer, and can be found > > and the attach attempted by SQL Server, but SQL Server claims that the > other two files are not SQL Server files. > > > > Luckily the one big table APPEARS to be in then one that did attach > > correctly. Any way to figure out why the second and third files are > > not attaching? If trying to use just the one file, is this database > > now corrupted? I mean 2 out of three files are no longer there, and > > they had SOMETHING in them because they would only compress to 50g down > from 150g. > > They might have had index stuff because the last thing I did was > > create a PK > > (autoincrement) which of course went out and built an index and stuff. > > The PK field is in the table. So se whether the index is though. > > > > John W. Colby > > Colby Consulting > > www.ColbyConsulting.com > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > Francisco Tapia > > Sent: Tuesday, August 29, 2006 2:23 PM > > To: dba-sqlserver at databaseadvisors.com > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > Server > > > > So I never knew if your machine could see the other, or was just not > > registering on the 2nd server. I ask because i've had situations > > where you can see the other server by navigting to it, but cannot register > it locally. > > > > On 8/29/06, JWColby wrote: > > > Thanks for this Francisco. I am in the process of tearing my two > > > machines apart to move the physical drives from one to the other. > > > We'll see how it all goes. > > > > > > > > > John W. Colby > > > Colby Consulting > > > www.ColbyConsulting.com > > > > > > -----Original Message----- > > > From: dba-sqlserver-bounces at databaseadvisors.com > > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > > Francisco Tapia > > > Sent: Tuesday, August 29, 2006 1:02 PM > > > To: dba-sqlserver at databaseadvisors.com > > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > > Server > > > > > > In order to prevent orphaned users, MS put out a script called > > > sp_help_revlogin you create it in the master database, details are > > > on my blog, > > > > > > http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-se > > > rv > > > er.htm > > > l > > > > > > if you get lost from the links post back and I'll help you through it. > > > > > > > > > On 8/29/06, JWColby wrote: > > > > >The simple answer was given to him (JC) in the first post back to > him. > > > > Which is why I never chimed in. > > > > > > > > >Detach it. > > > > >Copy it to the other machine. > > > > >Attach it. > > > > > > > > In fact that is only one of my two questions, but given my > > > > reception on the other question I suppose I should just not ask again. > > > > > > > > In fact I have RTFM (in advance of even asking AAMOF) and I found > > > > stuff about disconnecting / reconnecting possibly causing > > > > "orphaned users", this being caused by the use of something like a > > > > PK from the OS user to represent the user in the SQL Server login, > > > > and even though the user name is the same on the two machines, the > > > > UserID is not necessarily the same. It does make me a bit leery > > > > of going the disconnect > > > route. > > > > > > > > I had hoped to get both machines seeing the other (SQL Servers) > > > > and then see if I could just query directly out of a table in one > > > > SQL Server and transfer the data into the same table (new/empty) > > > > in the other SQL Server. I know I can export the data to text > > > > files and then re-import back in, but given the fact that the data > > > > is hundreds of gigabytes, I don't even want to go there if I can avoid > it. > > > > > > > > Unfortunately I do not know enough about SQL Server / networking > > > > to troubleshoot the "why" of two servers not seeing each other, > > > > and given that the list Gurus specifically want me to go become a > > > > SQL / Notwork DBA before I ask such questions, it seems that I > > > > will get no assistance on > > > that here. > > > > > > > > I have the database on 5 250gb drives, which I suppose I shall > > > > disconnect and then simply move the entire disks and pray for the > best. > > > > > > > > There are other forums I belong to though, I'll also go see if > > > > anyone can help. This is going to be a lot of data and eventually > > > > I will need machines preprocessing and then shipping the results > > > > to a central server, so the servers really do eventually need to > > > > see each other I think. It should be fun, and I should learn a > > > > lot, though perhaps not > > > here. > > > > > > > > Thanks Stewart, > > > > > > > > John W. Colby > > > > Colby Consulting > > > > www.ColbyConsulting.com > > > > > > > > -----Original Message----- > > > > From: dba-sqlserver-bounces at databaseadvisors.com > > > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > > > Robert > > L. > > > > Stewart > > > > Sent: Tuesday, August 29, 2006 10:16 AM > > > > To: dba-sqlserver at databaseadvisors.com > > > > Subject: Re: [dba-SQLServer] Transferring a database to another > > > > SQL Server > > > > > > > > As to why we are all here, it is to learn and hopefully help when > > > > we KNOW the answer. > > > > > > > > The simple answer was given to him (JC) in the first post back to him. > > > > Which is why I never chimed in. > > > > > > > > Detach it. > > > > Copy it to the other machine. > > > > Attach it. > > > > > > > > KISS - Keep it Supremely Simple > > > > > > > > Always works for me. > > > > > > > > Robert > > > > > > > > At 08:40 AM 8/29/2006, you wrote: > > > > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > > > > >From: "Haslett, Andrew" > > > > >Subject: Re: [dba-SQLServer] > > > > > [AccessD]TransferringadatabasetoanotherSQLServer > > > > >To: > > > > >Message-ID: > > > > > > > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > > > > >Content-Type: text/plain; charset="utf-8" > > > > > > > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are > > > > >quite happy to ask for advice but only accept it when its > > > > >something they want to hear, and ignore it otherwise > > > > >(demonstrated throughout the post > > > > >below) > > > > > > > > > >The points I made in my post apply to anyone looking to undertake > > > > >similar issues, and will continue to happen until someone has the > > > > >guts to say it, irrelevant of who it is aimed at (which is how it > > > > >should be > > > > >-> on a public forum, favour or protection should not be given to > > > > >anyone simply because they are friends, associates or seniority). > > > > > > > > > >Ask yourself this -> Would you have made the same post Jim, had > > > > >it not have been aimed at Mr Colby?. > > > > > > > > > >Stark realities occasionally need be surfaced in order for them > > > > >to sink in.. Irrespective of the target or consequences. Was it > harsh? > > > > >Yup. Could it perhaps prevent someone else from making the same > > > > >mistakes and undertaking projects without due preparation and > planning? > > > > >Hopefully, and therefore I believe useful. > > > > > > > > > >John asked Stuart "Why are you here then?". Some of us prefer to > > > > >assist others, pass on what knowledge they can and in my case > > > > >attempt to 'help others, help themselves', as opposed to just > > > > >feeding of others. > > > > > > > > > >I know of a number who have left this (and the Access) list in > > > > >the past, including myself, for similar reasons and > > > > >'Matesmenship' in the upper echelons. > > > > > > > > > >Please unsubscribe me from the list. > > > > > > > > > >Andrew > > > > > > > > > > > > _______________________________________________ > > > > 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 > > > http://pcthis.blogspot.com |PC news with out the jargon! > > > http://sqlthis.blogspot.com | Tsql and More... > > > _______________________________________________ > > > 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 > > http://pcthis.blogspot.com |PC news with out the jargon! > > http://sqlthis.blogspot.com | Tsql and More... > > _______________________________________________ > > 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 > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From stuart at lexacorp.com.pg Tue Aug 29 16:33:21 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Wed, 30 Aug 2006 07:33:21 +1000 Subject: [dba-SQLServer] SQL Injection and Sprocs In-Reply-To: References: <20060829203812.85433.qmail@web88210.mail.re2.yahoo.com>, Message-ID: <44F53F41.23674.6F784305@stuart.lexacorp.com.pg> On 29 Aug 2006 at 13:50, Francisco Tapia wrote: > There is one bad form, A developer who used to work here took it upon > himself to use a "global" sproc, in wich it takes an @nText parameter > and executes it in the stored procedure. blah! Ouch! Let me rephrase my last post: By forcing these user-input parameters into sproc parameters, they become "just data" inside the sproc and there is no way for them to actually be executed.......unless the sproc is deliberately written to execute the parameter :-( -- Stuart From accessd at shaw.ca Tue Aug 29 17:20:24 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Tue, 29 Aug 2006 15:20:24 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <000601c6cb99$c50c24a0$657aa8c0@m6805> Message-ID: <0J4S0076V61AO1H0@l-daemon> Hi John: Is one of your computers a server like 2000 or 2003? If so you can connect in about half dozen steps. Wait for confirmation... Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 11:35 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Yes, that is what I was asking kinda. In this case all I need to do is move the entire database. In the future I really want to have one machine process data from text files, do address correction / validation, get tables entirely set up and functioning and then transfer just that table to another server. Or perhaps even leave the table out on the machine it started on and attach to the table from the other server instance. ATM, neither machine can see the other, ether disk shares, nor server instances. I suspect that file shares will be the easiest of the two problems to fix and I need to get that happening regardless. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Tuesday, August 29, 2006 12:52 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Hi John: If it just requires moving the index and data files to the other computer, then attaching them that can be done as simply as copying the two important files from computer A to computer B. Given a database named MyDatabase just copy from directory ie: c:\Program Files\Microsoft SQL Server\MSSQL\Data files named MyDatabase.ldf and MyDatabase.mdf to the other computer or simpler yet just attach (MS SQL 2005), Microsoft SQL Server Management Studio > databases > right-mouse-click > select Attach > select Add and then just navigate to your computer that has the (data) MyDatabase.mdf file and select it. Is this what you are asking? HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 8:37 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server >The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. >Detach it. >Copy it to the other machine. >Attach it. In fact that is only one of my two questions, but given my reception on the other question I suppose I should just not ask again. In fact I have RTFM (in advance of even asking AAMOF) and I found stuff about disconnecting / reconnecting possibly causing "orphaned users", this being caused by the use of something like a PK from the OS user to represent the user in the SQL Server login, and even though the user name is the same on the two machines, the UserID is not necessarily the same. It does make me a bit leery of going the disconnect route. I had hoped to get both machines seeing the other (SQL Servers) and then see if I could just query directly out of a table in one SQL Server and transfer the data into the same table (new/empty) in the other SQL Server. I know I can export the data to text files and then re-import back in, but given the fact that the data is hundreds of gigabytes, I don't even want to go there if I can avoid it. Unfortunately I do not know enough about SQL Server / networking to troubleshoot the "why" of two servers not seeing each other, and given that the list Gurus specifically want me to go become a SQL / Notwork DBA before I ask such questions, it seems that I will get no assistance on that here. I have the database on 5 250gb drives, which I suppose I shall disconnect and then simply move the entire disks and pray for the best. There are other forums I belong to though, I'll also go see if anyone can help. This is going to be a lot of data and eventually I will need machines preprocessing and then shipping the results to a central server, so the servers really do eventually need to see each other I think. It should be fun, and I should learn a lot, though perhaps not here. Thanks Stewart, John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart Sent: Tuesday, August 29, 2006 10:16 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server As to why we are all here, it is to learn and hopefully help when we KNOW the answer. The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. Detach it. Copy it to the other machine. Attach it. KISS - Keep it Supremely Simple Always works for me. Robert At 08:40 AM 8/29/2006, you wrote: >Date: Tue, 29 Aug 2006 10:17:25 +0930 >From: "Haslett, Andrew" >Subject: Re: [dba-SQLServer] > [AccessD]TransferringadatabasetoanotherSQLServer >To: >Message-ID: > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> >Content-Type: text/plain; charset="utf-8" > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite >happy to ask for advice but only accept it when its something they want >to hear, and ignore it otherwise (demonstrated throughout the post >below) > >The points I made in my post apply to anyone looking to undertake >similar issues, and will continue to happen until someone has the guts >to say it, irrelevant of who it is aimed at (which is how it should be >-> on a public forum, favour or protection should not be given to >anyone simply because they are friends, associates or seniority). > >Ask yourself this -> Would you have made the same post Jim, had it not >have been aimed at Mr Colby?. > >Stark realities occasionally need be surfaced in order for them to sink >in.. Irrespective of the target or consequences. Was it harsh? >Yup. Could it perhaps prevent someone else from making the same >mistakes and undertaking projects without due preparation and planning? >Hopefully, and therefore I believe useful. > >John asked Stuart "Why are you here then?". Some of us prefer to >assist others, pass on what knowledge they can and in my case attempt >to 'help others, help themselves', as opposed to just feeding of >others. > >I know of a number who have left this (and the Access) list in the >past, including myself, for similar reasons and 'Matesmenship' in the >upper echelons. > >Please unsubscribe me from the list. > >Andrew _______________________________________________ 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 artful at rogers.com Tue Aug 29 17:35:20 2006 From: artful at rogers.com (artful at rogers.com) Date: Tue, 29 Aug 2006 15:35:20 -0700 (PDT) Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <0J4R0023BT895I10@l-daemon> Message-ID: <20060829223520.37079.qmail@web88205.mail.re2.yahoo.com> Methinks this is not the esteemed Francisco's fault ----- Original Message ---- From: Jim Lawrence To: dba-sqlserver at databaseadvisors.com Sent: Tuesday, August 29, 2006 1:43:13 PM Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Fancisco: Now that would have been helpful about a month ago when it took a week to migrate something that should have taken minutes. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, August 29, 2006 10:02 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server In order to prevent orphaned users, MS put out a script called sp_help_revlogin you create it in the master database, details are on my blog, http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-server.htm l if you get lost from the links post back and I'll help you through it. On 8/29/06, JWColby wrote: > >The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > >Detach it. > >Copy it to the other machine. > >Attach it. > > In fact that is only one of my two questions, but given my reception on the > other question I suppose I should just not ask again. > > In fact I have RTFM (in advance of even asking AAMOF) and I found stuff > about disconnecting / reconnecting possibly causing "orphaned users", this > being caused by the use of something like a PK from the OS user to represent > the user in the SQL Server login, and even though the user name is the same > on the two machines, the UserID is not necessarily the same. It does make > me a bit leery of going the disconnect route. > > I had hoped to get both machines seeing the other (SQL Servers) and then see > if I could just query directly out of a table in one SQL Server and transfer > the data into the same table (new/empty) in the other SQL Server. I know I > can export the data to text files and then re-import back in, but given the > fact that the data is hundreds of gigabytes, I don't even want to go there > if I can avoid it. > > Unfortunately I do not know enough about SQL Server / networking to > troubleshoot the "why" of two servers not seeing each other, and given that > the list Gurus specifically want me to go become a SQL / Notwork DBA before > I ask such questions, it seems that I will get no assistance on that here. > > I have the database on 5 250gb drives, which I suppose I shall disconnect > and then simply move the entire disks and pray for the best. > > There are other forums I belong to though, I'll also go see if anyone can > help. This is going to be a lot of data and eventually I will need machines > preprocessing and then shipping the results to a central server, so the > servers really do eventually need to see each other I think. It should be > fun, and I should learn a lot, though perhaps not here. > > Thanks Stewart, > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > Stewart > Sent: Tuesday, August 29, 2006 10:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > As to why we are all here, it is to learn and hopefully help when we KNOW > the answer. > > The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > Detach it. > Copy it to the other machine. > Attach it. > > KISS - Keep it Supremely Simple > > Always works for me. > > Robert > > At 08:40 AM 8/29/2006, you wrote: > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > >From: "Haslett, Andrew" > >Subject: Re: [dba-SQLServer] > > [AccessD]TransferringadatabasetoanotherSQLServer > >To: > >Message-ID: > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > >Content-Type: text/plain; charset="utf-8" > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > >happy to ask for advice but only accept it when its something they want > >to hear, and ignore it otherwise (demonstrated throughout the post > >below) > > > >The points I made in my post apply to anyone looking to undertake > >similar issues, and will continue to happen until someone has the guts > >to say it, irrelevant of who it is aimed at (which is how it should be > >-> on a public forum, favour or protection should not be given to > >anyone simply because they are friends, associates or seniority). > > > >Ask yourself this -> Would you have made the same post Jim, had it not > >have been aimed at Mr Colby?. > > > >Stark realities occasionally need be surfaced in order for them to sink > >in.. Irrespective of the target or consequences. Was it harsh? > >Yup. Could it perhaps prevent someone else from making the same > >mistakes and undertaking projects without due preparation and planning? > >Hopefully, and therefore I believe useful. > > > >John asked Stuart "Why are you here then?". Some of us prefer to > >assist others, pass on what knowledge they can and in my case attempt > >to 'help others, help themselves', as opposed to just feeding of > >others. > > > >I know of a number who have left this (and the Access) list in the > >past, including myself, for similar reasons and 'Matesmenship' in the > >upper echelons. > > > >Please unsubscribe me from the list. > > > >Andrew > > > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 artful at rogers.com Tue Aug 29 17:54:45 2006 From: artful at rogers.com (artful at rogers.com) Date: Tue, 29 Aug 2006 15:54:45 -0700 (PDT) Subject: [dba-SQLServer] SQL Injection and Sprocs In-Reply-To: <44F53EC9.31096.6F766FFA@stuart.lexacorp.com.pg> Message-ID: <20060829225445.74843.qmail@web88207.mail.re2.yahoo.com> Precisely my thoughts on this, but as I like to pretend that I am open-minded and always willing to step back from an opinion once it has been refuted, I thought to invite disproof. I have yet to see one, but as any logician knows, the absence of disproof does not constitute proof. I would dearly love to see an injection attack that can defeat the sproc+params approach. A. ----- Original Message ---- From: Stuart McLachlan To: dba-sqlserver at databaseadvisors.com Sent: Tuesday, August 29, 2006 5:31:21 PM Subject: Re: [dba-SQLServer] SQL Injection and Sprocs On 29 Aug 2006 at 13:38, artful at rogers.com wrote: > Rightly or wrongly, I have been under the impression that the saftest method > of avoiding SQL injection attacks is by using Sprocs exclusively. My theory > is that Sproc parameters are typed, and also handled differently, than > variables that might be plugged into a dynamic SQL statement. > > Have you ever seen an example that proves my theory incorrect? No :-) From accessd at shaw.ca Tue Aug 29 17:54:24 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Tue, 29 Aug 2006 15:54:24 -0700 Subject: [dba-SQLServer] SQL Injection and Sprocs In-Reply-To: <20060829203812.85433.qmail@web88210.mail.re2.yahoo.com> Message-ID: <0J4S007ZI7LYO1K0@l-daemon> Hi Arthur: Unfortunately that is not the case. About a years and a half ago, in a training session down in Redmond, given by some guru named Dino Esposito, that was working for a company named Wintellect/Expoware and I watched how he cracked SQL servers. It wasn't as super easy as with SQL strings but Sprocs, if they were not done just so could be used to dump the server stats... at that point the game is all over. It just takes a bit of persistence before long everything is open. I would love to give you further details but I fried a memory stick with all the specifics before it was downloaded... so sad. You might be able to track down info at www.Wintellect.com or at http://weblogs.asp.net/despos/ Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Tuesday, August 29, 2006 1:38 PM To: Alexander Karmanov; Andrei Pascal; Dejan Sunderic Cc: dba-SQLServer Subject: [dba-SQLServer] SQL Injection and Sprocs Rightly or wrongly, I have been under the impression that the saftest method of avoiding SQL injection attacks is by using Sprocs exclusively. My theory is that Sproc parameters are typed, and also handled differently, than variables that might be plugged into a dynamic SQL statement. Have you ever seen an example that proves my theory incorrect? I.e. imagine some form that obtains three variables from a user, then fires a sproc and passes it these three variables. To spice up the argument, imagine that one textbox is text, one numeric and one date. I have done various experiments on this scenario, and I cannot come up with a single case that fools the underlying sproc. Can you? Thanks, Arthur _______________________________________________ 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 Aug 29 17:59:11 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Tue, 29 Aug 2006 15:59:11 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <20060829223520.37079.qmail@web88205.mail.re2.yahoo.com> Message-ID: <0J4S007L77TXOBK0@l-daemon> Definitely not Franciso's fault... I never asked as I did not know that I did not know until I knew. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Tuesday, August 29, 2006 3:35 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Methinks this is not the esteemed Francisco's fault ----- Original Message ---- From: Jim Lawrence To: dba-sqlserver at databaseadvisors.com Sent: Tuesday, August 29, 2006 1:43:13 PM Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Fancisco: Now that would have been helpful about a month ago when it took a week to migrate something that should have taken minutes. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, August 29, 2006 10:02 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server In order to prevent orphaned users, MS put out a script called sp_help_revlogin you create it in the master database, details are on my blog, http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-server.htm l if you get lost from the links post back and I'll help you through it. On 8/29/06, JWColby wrote: > >The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > >Detach it. > >Copy it to the other machine. > >Attach it. > > In fact that is only one of my two questions, but given my reception on the > other question I suppose I should just not ask again. > > In fact I have RTFM (in advance of even asking AAMOF) and I found stuff > about disconnecting / reconnecting possibly causing "orphaned users", this > being caused by the use of something like a PK from the OS user to represent > the user in the SQL Server login, and even though the user name is the same > on the two machines, the UserID is not necessarily the same. It does make > me a bit leery of going the disconnect route. > > I had hoped to get both machines seeing the other (SQL Servers) and then see > if I could just query directly out of a table in one SQL Server and transfer > the data into the same table (new/empty) in the other SQL Server. I know I > can export the data to text files and then re-import back in, but given the > fact that the data is hundreds of gigabytes, I don't even want to go there > if I can avoid it. > > Unfortunately I do not know enough about SQL Server / networking to > troubleshoot the "why" of two servers not seeing each other, and given that > the list Gurus specifically want me to go become a SQL / Notwork DBA before > I ask such questions, it seems that I will get no assistance on that here. > > I have the database on 5 250gb drives, which I suppose I shall disconnect > and then simply move the entire disks and pray for the best. > > There are other forums I belong to though, I'll also go see if anyone can > help. This is going to be a lot of data and eventually I will need machines > preprocessing and then shipping the results to a central server, so the > servers really do eventually need to see each other I think. It should be > fun, and I should learn a lot, though perhaps not here. > > Thanks Stewart, > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > Stewart > Sent: Tuesday, August 29, 2006 10:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > As to why we are all here, it is to learn and hopefully help when we KNOW > the answer. > > The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > Detach it. > Copy it to the other machine. > Attach it. > > KISS - Keep it Supremely Simple > > Always works for me. > > Robert > > At 08:40 AM 8/29/2006, you wrote: > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > >From: "Haslett, Andrew" > >Subject: Re: [dba-SQLServer] > > [AccessD]TransferringadatabasetoanotherSQLServer > >To: > >Message-ID: > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > >Content-Type: text/plain; charset="utf-8" > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > >happy to ask for advice but only accept it when its something they want > >to hear, and ignore it otherwise (demonstrated throughout the post > >below) > > > >The points I made in my post apply to anyone looking to undertake > >similar issues, and will continue to happen until someone has the guts > >to say it, irrelevant of who it is aimed at (which is how it should be > >-> on a public forum, favour or protection should not be given to > >anyone simply because they are friends, associates or seniority). > > > >Ask yourself this -> Would you have made the same post Jim, had it not > >have been aimed at Mr Colby?. > > > >Stark realities occasionally need be surfaced in order for them to sink > >in.. Irrespective of the target or consequences. Was it harsh? > >Yup. Could it perhaps prevent someone else from making the same > >mistakes and undertaking projects without due preparation and planning? > >Hopefully, and therefore I believe useful. > > > >John asked Stuart "Why are you here then?". Some of us prefer to > >assist others, pass on what knowledge they can and in my case attempt > >to 'help others, help themselves', as opposed to just feeding of > >others. > > > >I know of a number who have left this (and the Access) list in the > >past, including myself, for similar reasons and 'Matesmenship' in the > >upper echelons. > > > >Please unsubscribe me from the list. > > > >Andrew > > > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 jwcolby at colbyconsulting.com Tue Aug 29 19:11:05 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Tue, 29 Aug 2006 20:11:05 -0400 Subject: [dba-SQLServer] Seeing mapped drives In-Reply-To: <000e01c6cbae$b9c5e4e0$657aa8c0@m6805> Message-ID: <001201c6cbc8$cb741d00$657aa8c0@m6805> Just an update, I can MAP a network drive from workstation A on workstation B using "Net Use SomeDrive SomePath". That proves something I am sure. I still cannot "browse" for the other machine using windows explorer and My Network Places. Clicking on Microsoft Windows network from any of my machines causes windows to "go away" (stop responding) for 30 seconds or so, then the same when I try to see the workgroup. That eventually times out saying "ColbyConsulting is not accessible.. See your notwork admin..." (we've already covered that subject ;-) John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 5:05 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server >This next q' sounds silly but... are you all patched up on your sql server? No that is not at all silly, and since the answer is "I don't know" the assumption could be "NO". I will look at that. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, August 29, 2006 4:19 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Yes when I ment navigate I ment via Windows Explorer. I was only able to get to them via Sql Server after I updated the client network utility and made sure that both the TCP/IP Named pipes. This next q' sounds silly but... are you all patched up on your sql server? On 8/29/06, JWColby wrote: > >I ask because I've had situations where you can see the other server > >by > navigating to it, but cannot register it locally. > > And what does this mean? Navigate to it as in using Windows Explorer? > Or by using something inside of SQL Server? > > BTW, I moved the drives, remapped them on the new machine so that the > drives are mapped to the same drive letters that they were on the old > machine. I can locate and attach only one of the three files that > made up the SQL Server on the other machine. Now, when I detached the > drives in SQL Server on the original machine, I immediately went in > and reattached the files and all three reattached. On the new > machine, the files can be seen by windows explorer, and can be found > and the attach attempted by SQL Server, but SQL Server claims that the other two files are not SQL Server files. > > Luckily the one big table APPEARS to be in then one that did attach > correctly. Any way to figure out why the second and third files are > not attaching? If trying to use just the one file, is this database > now corrupted? I mean 2 out of three files are no longer there, and > they had SOMETHING in them because they would only compress to 50g > down from 150g. > They might have had index stuff because the last thing I did was > create a PK > (autoincrement) which of course went out and built an index and stuff. > The PK field is in the table. So se whether the index is though. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > Francisco Tapia > Sent: Tuesday, August 29, 2006 2:23 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > Server > > So I never knew if your machine could see the other, or was just not > registering on the 2nd server. I ask because i've had situations > where you can see the other server by navigting to it, but cannot > register it locally. > > On 8/29/06, JWColby wrote: > > Thanks for this Francisco. I am in the process of tearing my two > > machines apart to move the physical drives from one to the other. > > We'll see how it all goes. > > > > > > John W. Colby > > Colby Consulting > > www.ColbyConsulting.com > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > Francisco Tapia > > Sent: Tuesday, August 29, 2006 1:02 PM > > To: dba-sqlserver at databaseadvisors.com > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > Server > > > > In order to prevent orphaned users, MS put out a script called > > sp_help_revlogin you create it in the master database, details are > > on my blog, > > > > http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql-se > > rv > > er.htm > > l > > > > if you get lost from the links post back and I'll help you through it. > > > > > > On 8/29/06, JWColby wrote: > > > >The simple answer was given to him (JC) in the first post back to him. > > > Which is why I never chimed in. > > > > > > >Detach it. > > > >Copy it to the other machine. > > > >Attach it. > > > > > > In fact that is only one of my two questions, but given my > > > reception on the other question I suppose I should just not ask again. > > > > > > In fact I have RTFM (in advance of even asking AAMOF) and I found > > > stuff about disconnecting / reconnecting possibly causing > > > "orphaned users", this being caused by the use of something like a > > > PK from the OS user to represent the user in the SQL Server login, > > > and even though the user name is the same on the two machines, the > > > UserID is not necessarily the same. It does make me a bit leery > > > of going the disconnect > > route. > > > > > > I had hoped to get both machines seeing the other (SQL Servers) > > > and then see if I could just query directly out of a table in one > > > SQL Server and transfer the data into the same table (new/empty) > > > in the other SQL Server. I know I can export the data to text > > > files and then re-import back in, but given the fact that the data > > > is hundreds of gigabytes, I don't even want to go there if I can > > > avoid it. > > > > > > Unfortunately I do not know enough about SQL Server / networking > > > to troubleshoot the "why" of two servers not seeing each other, > > > and given that the list Gurus specifically want me to go become a > > > SQL / Notwork DBA before I ask such questions, it seems that I > > > will get no assistance on > > that here. > > > > > > I have the database on 5 250gb drives, which I suppose I shall > > > disconnect and then simply move the entire disks and pray for the best. > > > > > > There are other forums I belong to though, I'll also go see if > > > anyone can help. This is going to be a lot of data and eventually > > > I will need machines preprocessing and then shipping the results > > > to a central server, so the servers really do eventually need to > > > see each other I think. It should be fun, and I should learn a > > > lot, though perhaps not > > here. > > > > > > Thanks Stewart, > > > > > > John W. Colby > > > Colby Consulting > > > www.ColbyConsulting.com > > > > > > -----Original Message----- > > > From: dba-sqlserver-bounces at databaseadvisors.com > > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > > Robert > L. > > > Stewart > > > Sent: Tuesday, August 29, 2006 10:16 AM > > > To: dba-sqlserver at databaseadvisors.com > > > Subject: Re: [dba-SQLServer] Transferring a database to another > > > SQL Server > > > > > > As to why we are all here, it is to learn and hopefully help when > > > we KNOW the answer. > > > > > > The simple answer was given to him (JC) in the first post back to him. > > > Which is why I never chimed in. > > > > > > Detach it. > > > Copy it to the other machine. > > > Attach it. > > > > > > KISS - Keep it Supremely Simple > > > > > > Always works for me. > > > > > > Robert > > > > > > At 08:40 AM 8/29/2006, you wrote: > > > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > > > >From: "Haslett, Andrew" > > > >Subject: Re: [dba-SQLServer] > > > > [AccessD]TransferringadatabasetoanotherSQLServer > > > >To: > > > >Message-ID: > > > > > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > > > >Content-Type: text/plain; charset="utf-8" > > > > > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are > > > >quite happy to ask for advice but only accept it when its > > > >something they want to hear, and ignore it otherwise > > > >(demonstrated throughout the post > > > >below) > > > > > > > >The points I made in my post apply to anyone looking to undertake > > > >similar issues, and will continue to happen until someone has the > > > >guts to say it, irrelevant of who it is aimed at (which is how it > > > >should be > > > >-> on a public forum, favour or protection should not be given to > > > >anyone simply because they are friends, associates or seniority). > > > > > > > >Ask yourself this -> Would you have made the same post Jim, had > > > >it not have been aimed at Mr Colby?. > > > > > > > >Stark realities occasionally need be surfaced in order for them > > > >to sink in.. Irrespective of the target or consequences. Was it harsh? > > > >Yup. Could it perhaps prevent someone else from making the same > > > >mistakes and undertaking projects without due preparation and planning? > > > >Hopefully, and therefore I believe useful. > > > > > > > >John asked Stuart "Why are you here then?". Some of us prefer to > > > >assist others, pass on what knowledge they can and in my case > > > >attempt to 'help others, help themselves', as opposed to just > > > >feeding of others. > > > > > > > >I know of a number who have left this (and the Access) list in > > > >the past, including myself, for similar reasons and > > > >'Matesmenship' in the upper echelons. > > > > > > > >Please unsubscribe me from the list. > > > > > > > >Andrew > > > > > > > > > _______________________________________________ > > > 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 > > http://pcthis.blogspot.com |PC news with out the jargon! > > http://sqlthis.blogspot.com | Tsql and More... > > _______________________________________________ > > 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 > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 Tue Aug 29 19:12:13 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Tue, 29 Aug 2006 20:12:13 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <0J4S0076V61AO1H0@l-daemon> Message-ID: <001301c6cbc8$f2d215f0$657aa8c0@m6805> Nope. All machines are Windows XP Professional. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Tuesday, August 29, 2006 6:20 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Hi John: Is one of your computers a server like 2000 or 2003? If so you can connect in about half dozen steps. Wait for confirmation... Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 11:35 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Yes, that is what I was asking kinda. In this case all I need to do is move the entire database. In the future I really want to have one machine process data from text files, do address correction / validation, get tables entirely set up and functioning and then transfer just that table to another server. Or perhaps even leave the table out on the machine it started on and attach to the table from the other server instance. ATM, neither machine can see the other, ether disk shares, nor server instances. I suspect that file shares will be the easiest of the two problems to fix and I need to get that happening regardless. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Tuesday, August 29, 2006 12:52 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Hi John: If it just requires moving the index and data files to the other computer, then attaching them that can be done as simply as copying the two important files from computer A to computer B. Given a database named MyDatabase just copy from directory ie: c:\Program Files\Microsoft SQL Server\MSSQL\Data files named MyDatabase.ldf and MyDatabase.mdf to the other computer or simpler yet just attach (MS SQL 2005), Microsoft SQL Server Management Studio > databases > right-mouse-click > select Attach > select Add and then just navigate to your computer that has the (data) MyDatabase.mdf file and select it. Is this what you are asking? HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 8:37 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server >The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. >Detach it. >Copy it to the other machine. >Attach it. In fact that is only one of my two questions, but given my reception on the other question I suppose I should just not ask again. In fact I have RTFM (in advance of even asking AAMOF) and I found stuff about disconnecting / reconnecting possibly causing "orphaned users", this being caused by the use of something like a PK from the OS user to represent the user in the SQL Server login, and even though the user name is the same on the two machines, the UserID is not necessarily the same. It does make me a bit leery of going the disconnect route. I had hoped to get both machines seeing the other (SQL Servers) and then see if I could just query directly out of a table in one SQL Server and transfer the data into the same table (new/empty) in the other SQL Server. I know I can export the data to text files and then re-import back in, but given the fact that the data is hundreds of gigabytes, I don't even want to go there if I can avoid it. Unfortunately I do not know enough about SQL Server / networking to troubleshoot the "why" of two servers not seeing each other, and given that the list Gurus specifically want me to go become a SQL / Notwork DBA before I ask such questions, it seems that I will get no assistance on that here. I have the database on 5 250gb drives, which I suppose I shall disconnect and then simply move the entire disks and pray for the best. There are other forums I belong to though, I'll also go see if anyone can help. This is going to be a lot of data and eventually I will need machines preprocessing and then shipping the results to a central server, so the servers really do eventually need to see each other I think. It should be fun, and I should learn a lot, though perhaps not here. Thanks Stewart, John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart Sent: Tuesday, August 29, 2006 10:16 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server As to why we are all here, it is to learn and hopefully help when we KNOW the answer. The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. Detach it. Copy it to the other machine. Attach it. KISS - Keep it Supremely Simple Always works for me. Robert At 08:40 AM 8/29/2006, you wrote: >Date: Tue, 29 Aug 2006 10:17:25 +0930 >From: "Haslett, Andrew" >Subject: Re: [dba-SQLServer] > [AccessD]TransferringadatabasetoanotherSQLServer >To: >Message-ID: > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> >Content-Type: text/plain; charset="utf-8" > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite >happy to ask for advice but only accept it when its something they want >to hear, and ignore it otherwise (demonstrated throughout the post >below) > >The points I made in my post apply to anyone looking to undertake >similar issues, and will continue to happen until someone has the guts >to say it, irrelevant of who it is aimed at (which is how it should be >-> on a public forum, favour or protection should not be given to >anyone simply because they are friends, associates or seniority). > >Ask yourself this -> Would you have made the same post Jim, had it not >have been aimed at Mr Colby?. > >Stark realities occasionally need be surfaced in order for them to sink >in.. Irrespective of the target or consequences. Was it harsh? >Yup. Could it perhaps prevent someone else from making the same >mistakes and undertaking projects without due preparation and planning? >Hopefully, and therefore I believe useful. > >John asked Stuart "Why are you here then?". Some of us prefer to >assist others, pass on what knowledge they can and in my case attempt >to 'help others, help themselves', as opposed to just feeding of >others. > >I know of a number who have left this (and the Access) list in the >past, including myself, for similar reasons and 'Matesmenship' in the >upper echelons. > >Please unsubscribe me from the list. > >Andrew _______________________________________________ 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 jlawrenc1 at shaw.ca Tue Aug 29 21:41:52 2006 From: jlawrenc1 at shaw.ca (Jim Lawrence) Date: Tue, 29 Aug 2006 19:41:52 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <001301c6cbc8$f2d215f0$657aa8c0@m6805> Message-ID: <0J4S00KZXI510RE0@l-daemon> Hi John: You have an interesting catch 22 situation. MS SQL server will not fully optimize on just a work station and needs a server based environment to be able to deliver all of its services. There are some issues with WFWG and SQL server... as you are well aware. So now that you have simple networking off you will have to add a user(s) to one station and another one to the other; see your computer management on each box to do this: c:\windows\system32\compmgmt.msc. Then go to the root of each station and each drive and share it. It default names will be c$ (c drive) d$ (d drive) etc. Make sure that every new user you create on one computer is part of the administration group (god-like). If one station called 'station1' has a god-like user named 'user1' with password 'password1' which have been added to the station1's c$ and d$ share (high-light drive root, right-mouse click, select properties, tab security, add button, select new god-like user, tick all rights, apply and OK.) All another station has to do to have complete access is to 'log in to' station1 using user1, password1. Note c$ and d$ are hidden shares so you will have to key them in directly I hope the above makes sense as I am typing fast as I can as I am 10 minutes late already. Will ask any questions later. Jim PS This from a security stand-point is an absolute no-no but do we care, full connection is the name of the game. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 5:12 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Nope. All machines are Windows XP Professional. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Tuesday, August 29, 2006 6:20 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Hi John: Is one of your computers a server like 2000 or 2003? If so you can connect in about half dozen steps. Wait for confirmation... Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 11:35 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Yes, that is what I was asking kinda. In this case all I need to do is move the entire database. In the future I really want to have one machine process data from text files, do address correction / validation, get tables entirely set up and functioning and then transfer just that table to another server. Or perhaps even leave the table out on the machine it started on and attach to the table from the other server instance. ATM, neither machine can see the other, ether disk shares, nor server instances. I suspect that file shares will be the easiest of the two problems to fix and I need to get that happening regardless. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Tuesday, August 29, 2006 12:52 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Hi John: If it just requires moving the index and data files to the other computer, then attaching them that can be done as simply as copying the two important files from computer A to computer B. Given a database named MyDatabase just copy from directory ie: c:\Program Files\Microsoft SQL Server\MSSQL\Data files named MyDatabase.ldf and MyDatabase.mdf to the other computer or simpler yet just attach (MS SQL 2005), Microsoft SQL Server Management Studio > databases > right-mouse-click > select Attach > select Add and then just navigate to your computer that has the (data) MyDatabase.mdf file and select it. Is this what you are asking? HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 8:37 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server >The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. >Detach it. >Copy it to the other machine. >Attach it. In fact that is only one of my two questions, but given my reception on the other question I suppose I should just not ask again. In fact I have RTFM (in advance of even asking AAMOF) and I found stuff about disconnecting / reconnecting possibly causing "orphaned users", this being caused by the use of something like a PK from the OS user to represent the user in the SQL Server login, and even though the user name is the same on the two machines, the UserID is not necessarily the same. It does make me a bit leery of going the disconnect route. I had hoped to get both machines seeing the other (SQL Servers) and then see if I could just query directly out of a table in one SQL Server and transfer the data into the same table (new/empty) in the other SQL Server. I know I can export the data to text files and then re-import back in, but given the fact that the data is hundreds of gigabytes, I don't even want to go there if I can avoid it. Unfortunately I do not know enough about SQL Server / networking to troubleshoot the "why" of two servers not seeing each other, and given that the list Gurus specifically want me to go become a SQL / Notwork DBA before I ask such questions, it seems that I will get no assistance on that here. I have the database on 5 250gb drives, which I suppose I shall disconnect and then simply move the entire disks and pray for the best. There are other forums I belong to though, I'll also go see if anyone can help. This is going to be a lot of data and eventually I will need machines preprocessing and then shipping the results to a central server, so the servers really do eventually need to see each other I think. It should be fun, and I should learn a lot, though perhaps not here. Thanks Stewart, John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart Sent: Tuesday, August 29, 2006 10:16 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server As to why we are all here, it is to learn and hopefully help when we KNOW the answer. The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. Detach it. Copy it to the other machine. Attach it. KISS - Keep it Supremely Simple Always works for me. Robert At 08:40 AM 8/29/2006, you wrote: >Date: Tue, 29 Aug 2006 10:17:25 +0930 >From: "Haslett, Andrew" >Subject: Re: [dba-SQLServer] > [AccessD]TransferringadatabasetoanotherSQLServer >To: >Message-ID: > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> >Content-Type: text/plain; charset="utf-8" > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite >happy to ask for advice but only accept it when its something they want >to hear, and ignore it otherwise (demonstrated throughout the post >below) > >The points I made in my post apply to anyone looking to undertake >similar issues, and will continue to happen until someone has the guts >to say it, irrelevant of who it is aimed at (which is how it should be >-> on a public forum, favour or protection should not be given to >anyone simply because they are friends, associates or seniority). > >Ask yourself this -> Would you have made the same post Jim, had it not >have been aimed at Mr Colby?. > >Stark realities occasionally need be surfaced in order for them to sink >in.. Irrespective of the target or consequences. Was it harsh? >Yup. Could it perhaps prevent someone else from making the same >mistakes and undertaking projects without due preparation and planning? >Hopefully, and therefore I believe useful. > >John asked Stuart "Why are you here then?". Some of us prefer to >assist others, pass on what knowledge they can and in my case attempt >to 'help others, help themselves', as opposed to just feeding of >others. > >I know of a number who have left this (and the Access) list in the >past, including myself, for similar reasons and 'Matesmenship' in the >upper echelons. > >Please unsubscribe me from the list. > >Andrew _______________________________________________ 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 _______________________________________________ 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 Tue Aug 29 22:10:51 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Tue, 29 Aug 2006 23:10:51 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: Message-ID: <001701c6cbe1$e7ed0c30$657aa8c0@m6805> It's (both servers are) now patched to SP4. And it now allows me to register the other server instance. Yeaaaa. I am now directly copying data from one server / database to the other server / database using the export wizard and a view. This is good stuff since it allows me to do what I am looking for later. Thanks Francisco, much appreciated. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, August 29, 2006 5:33 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server I'm also guessing we're working with SS2000, so you do want to patch to SP4. On 8/29/06, JWColby wrote: > >This next q' sounds silly but... are you all patched up on your sql server? > > No that is not at all silly, and since the answer is "I don't know" > the assumption could be "NO". > > I will look at that. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > Francisco Tapia > Sent: Tuesday, August 29, 2006 4:19 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > Server > > Yes when I ment navigate I ment via Windows Explorer. I was only able > to get to them via Sql Server after I updated the client network > utility and made sure that both the TCP/IP Named pipes. > > This next q' sounds silly but... are you all patched up on your sql server? > > > > On 8/29/06, JWColby wrote: > > >I ask because I've had situations where you can see the other > > >server by > > navigating to it, but cannot register it locally. > > > > And what does this mean? Navigate to it as in using Windows Explorer? > > Or by using something inside of SQL Server? > > > > BTW, I moved the drives, remapped them on the new machine so that > > the drives are mapped to the same drive letters that they were on > > the old machine. I can locate and attach only one of the three > > files that made up the SQL Server on the other machine. Now, when I > > detached the drives in SQL Server on the original machine, I > > immediately went in and reattached the files and all three > > reattached. On the new machine, the files can be seen by windows > > explorer, and can be found and the attach attempted by SQL Server, > > but SQL Server claims that the > other two files are not SQL Server files. > > > > Luckily the one big table APPEARS to be in then one that did attach > > correctly. Any way to figure out why the second and third files are > > not attaching? If trying to use just the one file, is this database > > now corrupted? I mean 2 out of three files are no longer there, and > > they had SOMETHING in them because they would only compress to 50g > > down > from 150g. > > They might have had index stuff because the last thing I did was > > create a PK > > (autoincrement) which of course went out and built an index and stuff. > > The PK field is in the table. So se whether the index is though. > > > > John W. Colby > > Colby Consulting > > www.ColbyConsulting.com > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > Francisco Tapia > > Sent: Tuesday, August 29, 2006 2:23 PM > > To: dba-sqlserver at databaseadvisors.com > > Subject: Re: [dba-SQLServer] Transferring a database to another SQL > > Server > > > > So I never knew if your machine could see the other, or was just not > > registering on the 2nd server. I ask because i've had situations > > where you can see the other server by navigting to it, but cannot > > register > it locally. > > > > On 8/29/06, JWColby wrote: > > > Thanks for this Francisco. I am in the process of tearing my two > > > machines apart to move the physical drives from one to the other. > > > We'll see how it all goes. > > > > > > > > > John W. Colby > > > Colby Consulting > > > www.ColbyConsulting.com > > > > > > -----Original Message----- > > > From: dba-sqlserver-bounces at databaseadvisors.com > > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > > Francisco Tapia > > > Sent: Tuesday, August 29, 2006 1:02 PM > > > To: dba-sqlserver at databaseadvisors.com > > > Subject: Re: [dba-SQLServer] Transferring a database to another > > > SQL Server > > > > > > In order to prevent orphaned users, MS put out a script called > > > sp_help_revlogin you create it in the master database, details are > > > on my blog, > > > > > > http://sqlthis.blogspot.com/2006/01/migrating-logins-from-one-sql- > > > se > > > rv > > > er.htm > > > l > > > > > > if you get lost from the links post back and I'll help you through it. > > > > > > > > > On 8/29/06, JWColby wrote: > > > > >The simple answer was given to him (JC) in the first post back > > > > >to > him. > > > > Which is why I never chimed in. > > > > > > > > >Detach it. > > > > >Copy it to the other machine. > > > > >Attach it. > > > > > > > > In fact that is only one of my two questions, but given my > > > > reception on the other question I suppose I should just not ask again. > > > > > > > > In fact I have RTFM (in advance of even asking AAMOF) and I > > > > found stuff about disconnecting / reconnecting possibly causing > > > > "orphaned users", this being caused by the use of something like > > > > a PK from the OS user to represent the user in the SQL Server > > > > login, and even though the user name is the same on the two > > > > machines, the UserID is not necessarily the same. It does make > > > > me a bit leery of going the disconnect > > > route. > > > > > > > > I had hoped to get both machines seeing the other (SQL Servers) > > > > and then see if I could just query directly out of a table in > > > > one SQL Server and transfer the data into the same table > > > > (new/empty) in the other SQL Server. I know I can export the > > > > data to text files and then re-import back in, but given the > > > > fact that the data is hundreds of gigabytes, I don't even want > > > > to go there if I can avoid > it. > > > > > > > > Unfortunately I do not know enough about SQL Server / networking > > > > to troubleshoot the "why" of two servers not seeing each other, > > > > and given that the list Gurus specifically want me to go become > > > > a SQL / Notwork DBA before I ask such questions, it seems that I > > > > will get no assistance on > > > that here. > > > > > > > > I have the database on 5 250gb drives, which I suppose I shall > > > > disconnect and then simply move the entire disks and pray for > > > > the > best. > > > > > > > > There are other forums I belong to though, I'll also go see if > > > > anyone can help. This is going to be a lot of data and > > > > eventually I will need machines preprocessing and then shipping > > > > the results to a central server, so the servers really do > > > > eventually need to see each other I think. It should be fun, > > > > and I should learn a lot, though perhaps not > > > here. > > > > > > > > Thanks Stewart, > > > > > > > > John W. Colby > > > > Colby Consulting > > > > www.ColbyConsulting.com > > > > > > > > -----Original Message----- > > > > From: dba-sqlserver-bounces at databaseadvisors.com > > > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > > > > Robert > > L. > > > > Stewart > > > > Sent: Tuesday, August 29, 2006 10:16 AM > > > > To: dba-sqlserver at databaseadvisors.com > > > > Subject: Re: [dba-SQLServer] Transferring a database to another > > > > SQL Server > > > > > > > > As to why we are all here, it is to learn and hopefully help > > > > when we KNOW the answer. > > > > > > > > The simple answer was given to him (JC) in the first post back to him. > > > > Which is why I never chimed in. > > > > > > > > Detach it. > > > > Copy it to the other machine. > > > > Attach it. > > > > > > > > KISS - Keep it Supremely Simple > > > > > > > > Always works for me. > > > > > > > > Robert > > > > > > > > At 08:40 AM 8/29/2006, you wrote: > > > > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > > > > >From: "Haslett, Andrew" > > > > >Subject: Re: [dba-SQLServer] > > > > > [AccessD]TransferringadatabasetoanotherSQLServer > > > > >To: > > > > >Message-ID: > > > > > > > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au > > > > >> > > > > >Content-Type: text/plain; charset="utf-8" > > > > > > > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are > > > > >quite happy to ask for advice but only accept it when its > > > > >something they want to hear, and ignore it otherwise > > > > >(demonstrated throughout the post > > > > >below) > > > > > > > > > >The points I made in my post apply to anyone looking to > > > > >undertake similar issues, and will continue to happen until > > > > >someone has the guts to say it, irrelevant of who it is aimed > > > > >at (which is how it should be > > > > >-> on a public forum, favour or protection should not be given > > > > >-> to > > > > >anyone simply because they are friends, associates or seniority). > > > > > > > > > >Ask yourself this -> Would you have made the same post Jim, had > > > > >it not have been aimed at Mr Colby?. > > > > > > > > > >Stark realities occasionally need be surfaced in order for them > > > > >to sink in.. Irrespective of the target or consequences. Was > > > > >it > harsh? > > > > >Yup. Could it perhaps prevent someone else from making the > > > > >same mistakes and undertaking projects without due preparation > > > > >and > planning? > > > > >Hopefully, and therefore I believe useful. > > > > > > > > > >John asked Stuart "Why are you here then?". Some of us prefer to > > > > >assist others, pass on what knowledge they can and in my case > > > > >attempt to 'help others, help themselves', as opposed to just > > > > >feeding of others. > > > > > > > > > >I know of a number who have left this (and the Access) list in > > > > >the past, including myself, for similar reasons and > > > > >'Matesmenship' in the upper echelons. > > > > > > > > > >Please unsubscribe me from the list. > > > > > > > > > >Andrew > > > > > > > > > > > > _______________________________________________ > > > > 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 > > > http://pcthis.blogspot.com |PC news with out the jargon! > > > http://sqlthis.blogspot.com | Tsql and More... > > > _______________________________________________ > > > 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 > > http://pcthis.blogspot.com |PC news with out the jargon! > > http://sqlthis.blogspot.com | Tsql and More... > > _______________________________________________ > > 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 > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > _______________________________________________ > 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 http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 Aug 30 08:02:17 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Wed, 30 Aug 2006 09:02:17 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: <001701c6cbe1$e7ed0c30$657aa8c0@m6805> Message-ID: <000501c6cc34$86094d00$657aa8c0@m6805> Thanks to everyone for their assistance. I now have both my servers registered in EM on each server (they can see each other) and I have successfully exported data directly from one to the other. Likewise, I am back in business with the workgroup file sharing, it turned out to be as simple as changing the name of my workgroup and running the wizard again. Thanks again, John W. Colby Colby Consulting www.ColbyConsulting.com From mwp.reid at qub.ac.uk Wed Aug 30 03:02:25 2006 From: mwp.reid at qub.ac.uk (Martin Reid) Date: Wed, 30 Aug 2006 09:02:25 +0100 Subject: [dba-SQLServer] Transferring a database to another SQL Server References: <0J4S00KZXI510RE0@l-daemon> Message-ID: John You may want to consider Virtural Server OS for this. Its worth looking at.Set up Windows Virtual Server 2005 which is free and work from there. I have emailed you a contact of list who deals with all my server side stuff in the University. He may be slow to respond but he knows this stuff inside out and should be able to advise or at least give you access to someone who is an expert (no disrespect to all here) on the network and OS side of things. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of Jim Lawrence Sent: Wed 30/08/2006 03:41 To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Hi John: You have an interesting catch 22 situation. MS SQL server will not fully optimize on just a work station and needs a server based environment to be able to deliver all of its services. There are some issues with WFWG and SQL server... as you are well aware. So now that you have simple networking off you will have to add a user(s) to one station and another one to the other; see your computer management on each box to do this: c:\windows\system32\compmgmt.msc. Then go to the root of each station and each drive and share it. It default names will be c$ (c drive) d$ (d drive) etc. Make sure that every new user you create on one computer is part of the administration group (god-like). If one station called 'station1' has a god-like user named 'user1' with password 'password1' which have been added to the station1's c$ and d$ share (high-light drive root, right-mouse click, select properties, tab security, add button, select new god-like user, tick all rights, apply and OK.) All another station has to do to have complete access is to 'log in to' station1 using user1, password1. Note c$ and d$ are hidden shares so you will have to key them in directly I hope the above makes sense as I am typing fast as I can as I am 10 minutes late already. Will ask any questions later. Jim PS This from a security stand-point is an absolute no-no but do we care, full connection is the name of the game. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 5:12 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Nope. All machines are Windows XP Professional. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Tuesday, August 29, 2006 6:20 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Hi John: Is one of your computers a server like 2000 or 2003? If so you can connect in about half dozen steps. Wait for confirmation... Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 11:35 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Yes, that is what I was asking kinda. In this case all I need to do is move the entire database. In the future I really want to have one machine process data from text files, do address correction / validation, get tables entirely set up and functioning and then transfer just that table to another server. Or perhaps even leave the table out on the machine it started on and attach to the table from the other server instance. ATM, neither machine can see the other, ether disk shares, nor server instances. I suspect that file shares will be the easiest of the two problems to fix and I need to get that happening regardless. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Tuesday, August 29, 2006 12:52 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Hi John: If it just requires moving the index and data files to the other computer, then attaching them that can be done as simply as copying the two important files from computer A to computer B. Given a database named MyDatabase just copy from directory ie: c:\Program Files\Microsoft SQL Server\MSSQL\Data files named MyDatabase.ldf and MyDatabase.mdf to the other computer or simpler yet just attach (MS SQL 2005), Microsoft SQL Server Management Studio > databases > right-mouse-click > select Attach > select Add and then just navigate to your computer that has the (data) MyDatabase.mdf file and select it. Is this what you are asking? HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Tuesday, August 29, 2006 8:37 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server >The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. >Detach it. >Copy it to the other machine. >Attach it. In fact that is only one of my two questions, but given my reception on the other question I suppose I should just not ask again. In fact I have RTFM (in advance of even asking AAMOF) and I found stuff about disconnecting / reconnecting possibly causing "orphaned users", this being caused by the use of something like a PK from the OS user to represent the user in the SQL Server login, and even though the user name is the same on the two machines, the UserID is not necessarily the same. It does make me a bit leery of going the disconnect route. I had hoped to get both machines seeing the other (SQL Servers) and then see if I could just query directly out of a table in one SQL Server and transfer the data into the same table (new/empty) in the other SQL Server. I know I can export the data to text files and then re-import back in, but given the fact that the data is hundreds of gigabytes, I don't even want to go there if I can avoid it. Unfortunately I do not know enough about SQL Server / networking to troubleshoot the "why" of two servers not seeing each other, and given that the list Gurus specifically want me to go become a SQL / Notwork DBA before I ask such questions, it seems that I will get no assistance on that here. I have the database on 5 250gb drives, which I suppose I shall disconnect and then simply move the entire disks and pray for the best. There are other forums I belong to though, I'll also go see if anyone can help. This is going to be a lot of data and eventually I will need machines preprocessing and then shipping the results to a central server, so the servers really do eventually need to see each other I think. It should be fun, and I should learn a lot, though perhaps not here. Thanks Stewart, John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart Sent: Tuesday, August 29, 2006 10:16 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server As to why we are all here, it is to learn and hopefully help when we KNOW the answer. The simple answer was given to him (JC) in the first post back to him. Which is why I never chimed in. Detach it. Copy it to the other machine. Attach it. KISS - Keep it Supremely Simple Always works for me. Robert At 08:40 AM 8/29/2006, you wrote: >Date: Tue, 29 Aug 2006 10:17:25 +0930 >From: "Haslett, Andrew" >Subject: Re: [dba-SQLServer] > [AccessD]TransferringadatabasetoanotherSQLServer >To: >Message-ID: > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> >Content-Type: text/plain; charset="utf-8" > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite >happy to ask for advice but only accept it when its something they want >to hear, and ignore it otherwise (demonstrated throughout the post >below) > >The points I made in my post apply to anyone looking to undertake >similar issues, and will continue to happen until someone has the guts >to say it, irrelevant of who it is aimed at (which is how it should be >-> on a public forum, favour or protection should not be given to >anyone simply because they are friends, associates or seniority). > >Ask yourself this -> Would you have made the same post Jim, had it not >have been aimed at Mr Colby?. > >Stark realities occasionally need be surfaced in order for them to sink >in.. Irrespective of the target or consequences. Was it harsh? >Yup. Could it perhaps prevent someone else from making the same >mistakes and undertaking projects without due preparation and planning? >Hopefully, and therefore I believe useful. > >John asked Stuart "Why are you here then?". Some of us prefer to >assist others, pass on what knowledge they can and in my case attempt >to 'help others, help themselves', as opposed to just feeding of >others. > >I know of a number who have left this (and the Access) list in the >past, including myself, for similar reasons and 'Matesmenship' in the >upper echelons. > >Please unsubscribe me from the list. > >Andrew _______________________________________________ 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 _______________________________________________ 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 Wed Aug 30 10:21:37 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Wed, 30 Aug 2006 11:21:37 -0400 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: Message-ID: <000f01c6cc47$fd1b0ab0$657aa8c0@m6805> Martin, In fact, ATM I am good to go. I may indeed run into services that SQL Server cannot perform due to the fact that it is running on a workstation OS but I just feel that I am not up to the task of becoming a Server Admin kinda guy just to get this stuff happening. Last week I actually tried installing SBS 2003 but promptly got bogged down in stuff I do not understand and don't have (or at least have never had) any need to understand. I do not want to be a Notwork guy, that is a discipline all its own and requires a lot of specialized knowledge to be good at. I am a one man show here, I have two small kids and a wife (a life in other words) and only have time to be good at a couple of things. I would love to get good at SQL Server but have just never had the opportunity. When you are a consultant you do what your clients are willing to pay you for, and to this point I have specialized in and earned a good living at Access. Yea yea, you have to study the new areas you want to learn, but you still have to have an opportunity to actually WORK in it to ever get really good at it. Otherwise everything you learn will soon be forgotten. With luck this client and this SQL Server database will provide me the means (opportunity) to become good at SQL Server. With more luck, the list members will be patient, kind and generous and I will be able to leverage this opportunity and add some valuable new skills. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Martin Reid Sent: Wednesday, August 30, 2006 4:02 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server John You may want to consider Virtural Server OS for this. Its worth looking at.Set up Windows Virtual Server 2005 which is free and work from there. I have emailed you a contact of list who deals with all my server side stuff in the University. He may be slow to respond but he knows this stuff inside out and should be able to advise or at least give you access to someone who is an expert (no disrespect to all here) on the network and OS side of things. Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of Jim Lawrence Sent: Wed 30/08/2006 03:41 To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server Hi John: You have an interesting catch 22 situation. MS SQL server will not fully optimize on just a work station and needs a server based environment to be able to deliver all of its services. There are some issues with WFWG and SQL server... as you are well aware. So now that you have simple networking off you will have to add a user(s) to one station and another one to the other; see your computer management on each box to do this: c:\windows\system32\compmgmt.msc. Then go to the root of each station and each drive and share it. It default names will be c$ (c drive) d$ (d drive) etc. Make sure that every new user you create on one computer is part of the administration group (god-like). If one station called 'station1' has a god-like user named 'user1' with password 'password1' which have been added to the station1's c$ and d$ share (high-light drive root, right-mouse click, select properties, tab security, add button, select new god-like user, tick all rights, apply and OK.) All another station has to do to have complete access is to 'log in to' station1 using user1, password1. Note c$ and d$ are hidden shares so you will have to key them in directly I hope the above makes sense as I am typing fast as I can as I am 10 minutes late already. Will ask any questions later. Jim PS This from a security stand-point is an absolute no-no but do we care, full connection is the name of the game. From fhtapia at gmail.com Wed Aug 30 11:15:46 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Wed, 30 Aug 2006 09:15:46 -0700 Subject: [dba-SQLServer] Transferring a database to another SQL Server In-Reply-To: References: <0J4S00KZXI510RE0@l-daemon> Message-ID: Either platform works either the VMware Server wich is also free as in beer, or the Virtual Server from MS, FYI, i've had better luck w/ the VMware server than the MS one. (FYI). -- Francisco On 8/30/06, Martin Reid wrote: > John > > You may want to consider Virtural Server OS for this. Its worth looking at.Set up Windows Virtual Server 2005 which is free and work from there. > > I have emailed you a contact of list who deals with all my server side stuff in the University. He may be slow to respond but he knows this stuff inside out and should be able to advise or at least give you access to someone who is an expert (no disrespect to all here) on the network and OS side of things. > > Martin > > Martin WP Reid > Training and Assessment Unit > Riddle Hall > Belfast > > tel: 02890 974477 > > > ________________________________ > > From: dba-sqlserver-bounces at databaseadvisors.com on behalf of Jim Lawrence > Sent: Wed 30/08/2006 03:41 > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > > > Hi John: > > You have an interesting catch 22 situation. MS SQL server will not fully > optimize on just a work station and needs a server based environment to be > able to deliver all of its services. There are some issues with WFWG and SQL > server... as you are well aware. > > So now that you have simple networking off you will have to add a user(s) to > one station and another one to the other; see your computer management on > each box to do this: > > c:\windows\system32\compmgmt.msc. > > Then go to the root of each station and each drive and share it. It default > names will be c$ (c drive) d$ (d drive) etc. Make sure that every new user > you create on one computer is part of the administration group (god-like). > > If one station called 'station1' has a god-like user named 'user1' with > password 'password1' which have been added to the station1's c$ and d$ share > (high-light drive root, right-mouse click, select properties, tab security, > add button, select new god-like user, tick all rights, apply and OK.) All > another station has to do to have complete access is to 'log in to' station1 > using user1, password1. > > Note c$ and d$ are hidden shares so you will have to key them in directly > > I hope the above makes sense as I am typing fast as I can as I am 10 minutes > late already. Will ask any questions later. > > Jim > > PS This from a security stand-point is an absolute no-no but do we care, > full connection is the name of the game. > > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby > Sent: Tuesday, August 29, 2006 5:12 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > Nope. All machines are Windows XP Professional. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim > Lawrence > Sent: Tuesday, August 29, 2006 6:20 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > Hi John: > > Is one of your computers a server like 2000 or 2003? If so you can connect > in about half dozen steps. > > Wait for confirmation... > > Jim > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby > Sent: Tuesday, August 29, 2006 11:35 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > Yes, that is what I was asking kinda. In this case all I need to do is move > the entire database. In the future I really want to have one machine > process data from text files, do address correction / validation, get tables > entirely set up and functioning and then transfer just that table to another > server. Or perhaps even leave the table out on the machine it started on > and attach to the table from the other server instance. > > ATM, neither machine can see the other, ether disk shares, nor server > instances. I suspect that file shares will be the easiest of the two > problems to fix and I need to get that happening regardless. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim > Lawrence > Sent: Tuesday, August 29, 2006 12:52 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > Hi John: > > If it just requires moving the index and data files to the other computer, > then attaching them that can be done as simply as copying the two important > files from computer A to computer B. Given a database named MyDatabase just > copy from directory ie: c:\Program Files\Microsoft SQL Server\MSSQL\Data > files named MyDatabase.ldf and MyDatabase.mdf to the other computer or > simpler yet just attach (MS SQL 2005), Microsoft SQL Server Management > Studio > databases > right-mouse-click > select Attach > select Add and then > just navigate to your computer that has the (data) MyDatabase.mdf file and > select it. > > Is this what you are asking? > > HTH > Jim > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby > Sent: Tuesday, August 29, 2006 8:37 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > >The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > >Detach it. > >Copy it to the other machine. > >Attach it. > > In fact that is only one of my two questions, but given my reception on the > other question I suppose I should just not ask again. > > In fact I have RTFM (in advance of even asking AAMOF) and I found stuff > about disconnecting / reconnecting possibly causing "orphaned users", this > being caused by the use of something like a PK from the OS user to represent > the user in the SQL Server login, and even though the user name is the same > on the two machines, the UserID is not necessarily the same. It does make > me a bit leery of going the disconnect route. > > I had hoped to get both machines seeing the other (SQL Servers) and then see > if I could just query directly out of a table in one SQL Server and transfer > the data into the same table (new/empty) in the other SQL Server. I know I > can export the data to text files and then re-import back in, but given the > fact that the data is hundreds of gigabytes, I don't even want to go there > if I can avoid it. > > Unfortunately I do not know enough about SQL Server / networking to > troubleshoot the "why" of two servers not seeing each other, and given that > the list Gurus specifically want me to go become a SQL / Notwork DBA before > I ask such questions, it seems that I will get no assistance on that here. > > I have the database on 5 250gb drives, which I suppose I shall disconnect > and then simply move the entire disks and pray for the best. > > There are other forums I belong to though, I'll also go see if anyone can > help. This is going to be a lot of data and eventually I will need machines > preprocessing and then shipping the results to a central server, so the > servers really do eventually need to see each other I think. It should be > fun, and I should learn a lot, though perhaps not here. > > Thanks Stewart, > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. > Stewart > Sent: Tuesday, August 29, 2006 10:16 AM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Transferring a database to another SQL Server > > As to why we are all here, it is to learn and hopefully help when we KNOW > the answer. > > The simple answer was given to him (JC) in the first post back to him. > Which is why I never chimed in. > > Detach it. > Copy it to the other machine. > Attach it. > > KISS - Keep it Supremely Simple > > Always works for me. > > Robert > > At 08:40 AM 8/29/2006, you wrote: > >Date: Tue, 29 Aug 2006 10:17:25 +0930 > >From: "Haslett, Andrew" > >Subject: Re: [dba-SQLServer] > > [AccessD]TransferringadatabasetoanotherSQLServer > >To: > >Message-ID: > > > ><0A870603A2A816459078203FC07F4CD2BE403C at adl01s055.ilcorp.gov.au> > >Content-Type: text/plain; charset="utf-8" > > > >Suit yourselves - Seems to be a bit of a 'boys' club who are quite > >happy to ask for advice but only accept it when its something they want > >to hear, and ignore it otherwise (demonstrated throughout the post > >below) > > > >The points I made in my post apply to anyone looking to undertake > >similar issues, and will continue to happen until someone has the guts > >to say it, irrelevant of who it is aimed at (which is how it should be > >-> on a public forum, favour or protection should not be given to > >anyone simply because they are friends, associates or seniority). > > > >Ask yourself this -> Would you have made the same post Jim, had it not > >have been aimed at Mr Colby?. > > > >Stark realities occasionally need be surfaced in order for them to sink > >in.. Irrespective of the target or consequences. Was it harsh? > >Yup. Could it perhaps prevent someone else from making the same > >mistakes and undertaking projects without due preparation and planning? > >Hopefully, and therefore I believe useful. > > > >John asked Stuart "Why are you here then?". Some of us prefer to > >assist others, pass on what knowledge they can and in my case attempt > >to 'help others, help themselves', as opposed to just feeding of > >others. > > > >I know of a number who have left this (and the Access) list in the > >past, including myself, for similar reasons and 'Matesmenship' in the > >upper echelons. > > > >Please unsubscribe me from the list. > > > >Andrew > > > _______________________________________________ > 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 > > _______________________________________________ > 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 > > > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... From artful at rogers.com Wed Aug 30 12:51:24 2006 From: artful at rogers.com (artful at rogers.com) Date: Wed, 30 Aug 2006 10:51:24 -0700 (PDT) Subject: [dba-SQLServer] Embed a MapPoint map in an RS report? Message-ID: <20060830175124.76337.qmail@web88210.mail.re2.yahoo.com> Can this be done? If so, how so? TIA, Arthur From fhtapia at gmail.com Wed Aug 30 13:38:27 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Wed, 30 Aug 2006 11:38:27 -0700 Subject: [dba-SQLServer] Embed a MapPoint map in an RS report? In-Reply-To: <20060830175124.76337.qmail@web88210.mail.re2.yahoo.com> References: <20060830175124.76337.qmail@web88210.mail.re2.yahoo.com> Message-ID: Haven't tried, but it is an image isn't it? I'll try it later today when I get a chance. On 8/30/06, artful at rogers.com wrote: > Can this be done? If so, how so? > > TIA, > Arthur > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From jwcolby at colbyconsulting.com Thu Aug 31 06:54:07 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Thu, 31 Aug 2006 07:54:07 -0400 Subject: [dba-SQLServer] Which machine does the work? Message-ID: <000901c6ccf4$2b134ed0$657aa8c0@m6805> I have two machines, both running SQL Server instances. MachineA has registered the database on MachineA and the database on MachineB. MachineB has done likewise. MachineA holds a database with a table to which I want to add an index. If I open EM on MachineB, select the database on MachineA, open a table in design view and "add an index", where is the work performed? Does MachineB actually do anything? Or does MachineB simply send a command to the SQL Server instance on MachineA telling it to add the index and all of the work is performed on MachineA? John W. Colby Colby Consulting www.ColbyConsulting.com From mikedorism at verizon.net Thu Aug 31 07:22:36 2006 From: mikedorism at verizon.net (Mike & Doris Manning) Date: Thu, 31 Aug 2006 08:22:36 -0400 Subject: [dba-SQLServer] Which machine does the work? In-Reply-To: <000901c6ccf4$2b134ed0$657aa8c0@m6805> Message-ID: <000601c6ccf8$25ba9b60$2f01a8c0@dorismanning> Machine B is doing the work. To truly understand everything that is happening inside your SQL Server installation, you need to invest in software that allows you to read the log files so you can follow the transactions. Doris Manning mikedorism at verizon.net -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Thursday, August 31, 2006 7:54 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Which machine does the work? I have two machines, both running SQL Server instances. MachineA has registered the database on MachineA and the database on MachineB. MachineB has done likewise. MachineA holds a database with a table to which I want to add an index. If I open EM on MachineB, select the database on MachineA, open a table in design view and "add an index", where is the work performed? Does MachineB actually do anything? Or does MachineB simply send a command to the SQL Server instance on MachineA telling it to add the index and all of the work is performed on MachineA? John W. Colby Colby Consulting www.ColbyConsulting.com From stuart at lexacorp.com.pg Thu Aug 31 07:33:44 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Thu, 31 Aug 2006 22:33:44 +1000 Subject: [dba-SQLServer] Which machine does the work? In-Reply-To: <000901c6ccf4$2b134ed0$657aa8c0@m6805> References: <000901c6ccf4$2b134ed0$657aa8c0@m6805> Message-ID: <44F763C8.10286.5C16564@stuart.lexacorp.com.pg> On 31 Aug 2006 at 7:54, JWColby wrote: > I have two machines, both running SQL Server instances. MachineA has > registered the database on MachineA and the database on MachineB. MachineB > has done likewise. I think you mean you have registered the *Server* on MachineB in EM on MachineA and vice versa. You don't register databases, you register servers. > MachineA holds a database with a table to which I want > to add an index. If I open EM on MachineB, select the database on MachineA, > open a table in design view and "add an index", where is the work performed? > Does MachineB actually do anything? No, >Or does MachineB simply send a command > to the SQL Server instance on MachineA telling it to add the index and all > of the work is performed on MachineA? Yes. Whatever server has the database attached to it does all the work on that database. That's the whole point of a client/server application. Think what happens if you install EM on a MachineC with no SQL Server instance running on it. When you register the instances on MachineA and MachineB, you can do anything you like with them, but there is no MachineC instance to do any of the work - it has to be done by the instance which actually hosts the database. -- Stuart From jwcolby at colbyconsulting.com Thu Aug 31 07:48:46 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Thu, 31 Aug 2006 08:48:46 -0400 Subject: [dba-SQLServer] Which machine does the work? In-Reply-To: <000601c6ccf8$25ba9b60$2f01a8c0@dorismanning> Message-ID: <001201c6ccfb$cd346b20$657aa8c0@m6805> The reason I ask is to understand what resources I am tying up where and what tasks it makes sense to do where. I am in the process of building an index on a field in a table on MachineA. I did so from an instance of EM on MachineB. MachineB shows virtually no CPU Usage, but MachineA shows an average of around 10-12% CPU usage. MachineB does show some light network traffic but it is very light, perhaps 5 packets per second both transmitted and received. I have a 1 gbit switch that the machines talk to each over and when I look at network traffic in Task Manager on MachineB, the traffic is so light that it is literally a flat line at the very bottom of the graph. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mike & Doris Manning Sent: Thursday, August 31, 2006 8:23 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Which machine does the work? Machine B is doing the work. To truly understand everything that is happening inside your SQL Server installation, you need to invest in software that allows you to read the log files so you can follow the transactions. Doris Manning mikedorism at verizon.net -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Thursday, August 31, 2006 7:54 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Which machine does the work? I have two machines, both running SQL Server instances. MachineA has registered the database on MachineA and the database on MachineB. MachineB has done likewise. MachineA holds a database with a table to which I want to add an index. If I open EM on MachineB, select the database on MachineA, open a table in design view and "add an index", where is the work performed? Does MachineB actually do anything? Or does MachineB simply send a command to the SQL Server instance on MachineA telling it to add the index and all of the work is performed on MachineA? John W. Colby Colby Consulting www.ColbyConsulting.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 Thu Aug 31 08:26:16 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Thu, 31 Aug 2006 09:26:16 -0400 Subject: [dba-SQLServer] Which machine does the work? In-Reply-To: <44F763C8.10286.5C16564@stuart.lexacorp.com.pg> Message-ID: <001301c6cd01$0ad23ed0$657aa8c0@m6805> Thanks Stuart, that is what I suspected. I am trying to get a handle on how to distribute work on the machines, i.e. actual machine cycles. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Thursday, August 31, 2006 8:34 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Which machine does the work? On 31 Aug 2006 at 7:54, JWColby wrote: > I have two machines, both running SQL Server instances. MachineA has > registered the database on MachineA and the database on MachineB. MachineB > has done likewise. I think you mean you have registered the *Server* on MachineB in EM on MachineA and vice versa. You don't register databases, you register servers. > MachineA holds a database with a table to which I want to add an > index. If I open EM on MachineB, select the database on MachineA, > open a table in design view and "add an index", where is the work performed? > Does MachineB actually do anything? No, >Or does MachineB simply send a command > to the SQL Server instance on MachineA telling it to add the index and >all of the work is performed on MachineA? Yes. Whatever server has the database attached to it does all the work on that database. That's the whole point of a client/server application. Think what happens if you install EM on a MachineC with no SQL Server instance running on it. When you register the instances on MachineA and MachineB, you can do anything you like with them, but there is no MachineC instance to do any of the work - it has to be done by the instance which actually hosts the database. -- Stuart _______________________________________________ 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 Thu Aug 31 09:05:22 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Thu, 31 Aug 2006 10:05:22 -0400 Subject: [dba-SQLServer] Using 4 gbytes of RAM Message-ID: <001401c6cd06$80a4a710$657aa8c0@m6805> Is anyone using a machine with more than two gig of Ram? I am reading things about doing this and there seems to be a lot of confusion on the matter. Much of the confusion seems to come from the fact that until the 64 bit versions of the X86 processors, the "internals" of the processor were all 32 bits which limited direct generation of addresses to 4 gig. All of my machines are 64 bit (AMD) processors so theoretically they can use more than 4 gig but how? Everyone seems to agree that in XP32, only 4 gig is available to work with and that things like video cards and other "machine stuff" eats into that. Thus regardless of anything, you will end up with less than 4 gig due to that, perhaps as little as 3.25 gig. After that, confusion reigns, at least in my mind. Understand that I am discussing Windows XP 32 specifically, although anyone is welcome to chip in what they "know" regarding other windows versions as long as they specify what version they are discussing. The next thing that is discussed is that the OS itself reserves 2 gig for itself (which includes the video etc AFAICT), leaving up to 2 gig for EACH APPLICATION, implying that any application can have / use up to 2 gig. Some claim that if you have 4 gig, the swap file won't be used since that is part of the 4 gig available. It seems illogical since each application can use up to 2 gig. However I have created a separate partition to hold my swap file and tried to create one of 6 gig and Windows refused, limiting the size of the swap file to 4 gig. So I am trying to figure out what the reality is. If a machine has 4 gig physical ram, and "machine stuff" uses (for argument's sake) .75 gig, is the .75 gig of physical ram simply unused? Is it used by the OS for buffers? What about the swap file? If you have a 4 gig swap file, would you have 7.25 "total available memory" for Windows use? Does this indeed then limit the APPLICATIONS to 5.25 gig of "total" memory and 2 gig of physical memory? And what happens if you manage to get (for the sake of argument) 8 gig stuffed into a machine. Some motherboards claim to handle that much but can Windows XP 32 actually use it? Can Windows XP 64? If you need this much memory is Windows XP 64 a way to get at the memory? If you are still using 32 bit apps, will it actually map as much as 2 gig of physical memory to the 32 bit apps so that (for example) 3 high powered memory hungry 32 bit apps actually had 2 gig available to each of them all the time? If anyone has run across any authoritive (on-line) reading on the subject I would love to look at it. John W. Colby Colby Consulting www.ColbyConsulting.com