From jwcolby at ColbyConsulting.com  Sun Jan  1 10:21:37 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Sun, 1 Jan 2006 11:21:37 -0500
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <FA2FBFCAE6E4CC40990C321ED0BC6892BB223E@acsanchor1.corp.acsalaska.com>
Message-ID: <200601011622.k01GMZV13704@databaseadvisors.com>

What data type is used to store Boolean values in SQL Server?


John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/



From harkinsss at bellsouth.net  Sun Jan  1 10:24:29 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Sun, 1 Jan 2006 11:24:29 -0500
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <200601011622.k01GMZV13704@databaseadvisors.com>
Message-ID: <20060101162430.ONEF8357.ibm57aec.bellsouth.net@SUSANONE>

bit

Susan H. 

What data type is used to store Boolean values in SQL Server?





From jwcolby at ColbyConsulting.com  Sun Jan  1 11:46:25 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Sun, 1 Jan 2006 12:46:25 -0500
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <20060101162430.ONEF8357.ibm57aec.bellsouth.net@SUSANONE>
Message-ID: <200601011747.k01HlQV01651@databaseadvisors.com>

So what happens internally?  Does SQL Server pack/unpack as many y/n
(boolean) values as will fit in an integer or something like that? 


John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/
-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: Sunday, January 01, 2006 11:24 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Yes/No in SQL Server

bit

Susan H. 

What data type is used to store Boolean values in SQL Server?



_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From harkinsss at bellsouth.net  Sun Jan  1 11:51:47 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Sun, 1 Jan 2006 12:51:47 -0500
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <200601011747.k01HlQV01651@databaseadvisors.com>
Message-ID: <20060101175149.PETN8357.ibm57aec.bellsouth.net@SUSANONE>

You're gonna need Martin for that one. :) 

Susan H. 

So what happens internally?  Does SQL Server pack/unpack as many y/n
(boolean) values as will fit in an integer or something like that? 



From ridermark at gmail.com  Sun Jan  1 12:03:05 2006
From: ridermark at gmail.com (Mark Rider)
Date: Sun, 1 Jan 2006 12:03:05 -0600
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <200601011747.k01HlQV01651@databaseadvisors.com>
References: <20060101162430.ONEF8357.ibm57aec.bellsouth.net@SUSANONE>
	<200601011747.k01HlQV01651@databaseadvisors.com>
Message-ID: <a74f31780601011003m44d47166g94c4aa314f182a3f@mail.gmail.com>

AFAIK, the bit is eiher 0 or 1.  USually 0 is False (NO) and 1 is True
(YES). I use bit values to determine if something needs to be changed or has
been changed - for example a Midified filed is set to "0"  at the outset and
then a bunch of calculations are done.  If the value returned by the
calculations has changed from the original value, I change the Modified
Field to "1" so that further changes to the value are ignored.

What are you trying to accomplish?

On 1/1/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> So what happens internally?  Does SQL Server pack/unpack as many y/n
> (boolean) values as will fit in an integer or something like that?
>
>
> John W. Colby
> www.ColbyConsulting.com
>
> Contribute your unused CPU cycles to a good cause:
> http://folding.stanford.edu/
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
> Harkins
> Sent: Sunday, January 01, 2006 11:24 AM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] Yes/No in SQL Server
>
> bit
>
> Susan H.
>
> What data type is used to store Boolean values in SQL Server?
>
>
>
> _______________________________________________
> 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
>
>


--
Mark Rider
http://commonsensesecurity.info

There are 10 kinds of people in the world:
Those who understand binary and those who don't.


From ggonzalez at cccis.com  Sun Jan  1 12:08:06 2006
From: ggonzalez at cccis.com (ggonzalez at cccis.com)
Date: Sun, 1 Jan 2006 12:08:06 -0600
Subject: [dba-SQLServer] Gumaro Gonzalez is out of the office.
Message-ID: <OF34DF2F79.79534F8D-ON862570E9.00639E58-862570E9.00639E58@cccis.com>

I will be out of the office starting  12/28/2005 and will not return until
01/09/2006.

I will respond to your message when I return.




From jwcolby at ColbyConsulting.com  Sun Jan  1 13:26:34 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Sun, 1 Jan 2006 14:26:34 -0500
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <a74f31780601011003m44d47166g94c4aa314f182a3f@mail.gmail.com>
Message-ID: <200601011927.k01JRZV26289@databaseadvisors.com>

Just flags that something is true / false.  In Access there is a Boolean
datatype (T/F), which I couldn't find in SQL Server.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/
-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mark Rider
Sent: Sunday, January 01, 2006 1:03 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Yes/No in SQL Server

AFAIK, the bit is eiher 0 or 1.  USually 0 is False (NO) and 1 is True
(YES). I use bit values to determine if something needs to be changed or has
been changed - for example a Midified filed is set to "0"  at the outset and
then a bunch of calculations are done.  If the value returned by the
calculations has changed from the original value, I change the Modified
Field to "1" so that further changes to the value are ignored.

What are you trying to accomplish?

On 1/1/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> So what happens internally?  Does SQL Server pack/unpack as many y/n
> (boolean) values as will fit in an integer or something like that?
>
>
> John W. Colby
> www.ColbyConsulting.com
>
> Contribute your unused CPU cycles to a good cause:
> http://folding.stanford.edu/
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan 
> Harkins
> Sent: Sunday, January 01, 2006 11:24 AM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] Yes/No in SQL Server
>
> bit
>
> Susan H.
>
> What data type is used to store Boolean values in SQL Server?
>
>
>
> _______________________________________________
> 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
>
>


--
Mark Rider
http://commonsensesecurity.info

There are 10 kinds of people in the world:
Those who understand binary and those who don't.
_______________________________________________
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  Sun Jan  1 13:59:32 2006
From: mwp.reid at qub.ac.uk (Martin)
Date: Sun, 1 Jan 2006 19:59:32 -0000
Subject: [dba-SQLServer] Yes/No in SQL Server
Message-ID: <200601012000.k01K0PV01365@databaseadvisors.com>

John

Its just a bit data type 0 or 1 representing T or F.
 martin


-----Original Message-----
    From: "Mark Rider"<ridermark at gmail.com>
    Sent: 01/01/06 18:03:05
    To: "dba-sqlserver at databaseadvisors.com"<dba-sqlserver at databaseadvisors.com>
    Subject: Re: [dba-SQLServer] Yes/No in SQL Server
    
    AFAIK, the bit is eiher 0 or 1.  USually 0 is False (NO) and 1 is True
    (YES). I use bit values to determine if something needs to be changed or has
    been changed - for example a Midified filed is set to "0"  at the outset and
    then a bunch of calculations are done.  If the value returned by the
    calculations has changed from the original value, I change the Modified
    Field to "1" so that further changes to the value are ignored.
    
    What are you trying to accomplish?
    
    On 1/1/06, John Colby <jwcolby at colbyconsulting.com> wrote:
    >
    > So what happens internally?  Does SQL Server pack/unpack as many y/n
    > (boolean) values as will fit in an integer or something like that?
    >
    >
    > John W. Colby
    > www.ColbyConsulting.com
    >
    > Contribute your unused CPU cycles to a good cause:
    > http://folding.stanford.edu/
    > -----Original Message-----
    > From: dba-sqlserver-bounces at databaseadvisors.com
    > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
    > Harkins
    > Sent: Sunday, January 01, 2006 11:24 AM
    > To: dba-sqlserver at databaseadvisors.com
    > Subject: Re: [dba-SQLServer] Yes/No in SQL Server
    >
    > bit
    >
    > Susan H.
    >
    > What data type is used to store Boolean values in SQL Server?
    >
    >
    >
    > _______________________________________________
    > 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
    >
    >
    
    
    --
    Mark Rider
    http://commonsensesecurity.info
    
    There are 10 kinds of people in the world:
    Those who understand binary and those who don't.
    _______________________________________________
    dba-SQLServer mailing list
    dba-SQLServer at databaseadvisors.com
    http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
    http://www.databaseadvisors.com
    



From dwaters at usinternet.com  Sun Jan  1 14:09:45 2006
From: dwaters at usinternet.com (Dan Waters)
Date: Sun, 1 Jan 2006 14:09:45 -0600
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <13819569.1136145706783.JavaMail.root@sniper16>
Message-ID: <000001c60f0f$4f8f8650$0200a8c0@danwaters>

John,

I checked a table that I upsized into SSE 2005.  A previous Yes/No is now a
bit, and the data displays as True or False in the table column.

Dan Waters

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Martin
Sent: Sunday, January 01, 2006 2:00 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Yes/No in SQL Server

John

Its just a bit data type 0 or 1 representing T or F.
 martin


-----Original Message-----
    From: "Mark Rider"<ridermark at gmail.com>
    Sent: 01/01/06 18:03:05
    To:
"dba-sqlserver at databaseadvisors.com"<dba-sqlserver at databaseadvisors.com>
    Subject: Re: [dba-SQLServer] Yes/No in SQL Server
    
    AFAIK, the bit is eiher 0 or 1.  USually 0 is False (NO) and 1 is True
    (YES). I use bit values to determine if something needs to be changed or
has
    been changed - for example a Midified filed is set to "0"  at the outset
and
    then a bunch of calculations are done.  If the value returned by the
    calculations has changed from the original value, I change the Modified
    Field to "1" so that further changes to the value are ignored.
    
    What are you trying to accomplish?
    
    On 1/1/06, John Colby <jwcolby at colbyconsulting.com> wrote:
    >
    > So what happens internally?  Does SQL Server pack/unpack as many y/n
    > (boolean) values as will fit in an integer or something like that?
    >
    >
    > John W. Colby
    > www.ColbyConsulting.com
    >
    > Contribute your unused CPU cycles to a good cause:
    > http://folding.stanford.edu/
    > -----Original Message-----
    > From: dba-sqlserver-bounces at databaseadvisors.com
    > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
    > Harkins
    > Sent: Sunday, January 01, 2006 11:24 AM
    > To: dba-sqlserver at databaseadvisors.com
    > Subject: Re: [dba-SQLServer] Yes/No in SQL Server
    >
    > bit
    >
    > Susan H.
    >
    > What data type is used to store Boolean values in SQL Server?
    >
    >
    >
    > _______________________________________________
    > 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
    >
    >
    
    
    --
    Mark Rider
    http://commonsensesecurity.info
    
    There are 10 kinds of people in the world:
    Those who understand binary and those who don't.
    _______________________________________________
    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 shait at mindspring.com  Sun Jan  1 14:29:49 2006
From: shait at mindspring.com (Stephen Hait)
Date: Sun, 1 Jan 2006 15:29:49 -0500
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <000001c60f0f$4f8f8650$0200a8c0@danwaters>
References: <13819569.1136145706783.JavaMail.root@sniper16>
	<000001c60f0f$4f8f8650$0200a8c0@danwaters>
Message-ID: <bb9d2d1e0601011229s1a769d67k265382f9f1087972@mail.gmail.com>

On 1/1/06, Dan Waters <dwaters at usinternet.com> wrote:
>
> John,
>
> I checked a table that I upsized into SSE 2005.  A previous Yes/No is now
> a
> bit, and the data displays as True or False in the table column.


One other point that may not be immediately obvious: in Access, yes/no
values are stored as -1 or 0; in SQL Server bit values are stored as 1 or 0.


Stephen


From accessd at shaw.ca  Sun Jan  1 14:53:29 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Sun, 01 Jan 2006 12:53:29 -0800
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <200601011622.k01GMZV13704@databaseadvisors.com>
Message-ID: <000a01c60f15$6b847310$017ba8c0@xpserver>

Hi John:

The bit data type; 1 and 0. Note; SQL is different from Access. Access uses
-1 for true and 0 for false (yes/no) and SQL uses 1 for true and 0 for
false.

HTH
Jim 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: January 1, 2006 8:22 AM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Yes/No in SQL Server

What data type is used to store Boolean values in SQL Server?


John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From tuxedo_man at hotmail.com  Sun Jan  1 15:31:55 2006
From: tuxedo_man at hotmail.com (Billy Pang)
Date: Sun, 01 Jan 2006 21:31:55 +0000
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <200601011747.k01HlQV01651@databaseadvisors.com>
Message-ID: <BAY102-F2990A16572099C27E11B94E52A0@phx.gbl>

from bol "Microsoft? SQL Server? optimizes the storage used for bit columns. 
If there are 8 or fewer bit columns in a table, the columns are stored as 1 
byte. If there are from 9 through 16 bit columns, they are stored as 2 
bytes, and so on."


>From: "John Colby" <jwcolby at colbyconsulting.com>
>Reply-To: dba-sqlserver at databaseadvisors.com
>To: <dba-sqlserver at databaseadvisors.com>
>Subject: Re: [dba-SQLServer] Yes/No in SQL Server
>Date: Sun, 1 Jan 2006 12:46:25 -0500
>
>So what happens internally?  Does SQL Server pack/unpack as many y/n
>(boolean) values as will fit in an integer or something like that?
>
>
>John W. Colby
>www.ColbyConsulting.com
>
>Contribute your unused CPU cycles to a good cause:
>http://folding.stanford.edu/
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
>Harkins
>Sent: Sunday, January 01, 2006 11:24 AM
>To: dba-sqlserver at databaseadvisors.com
>Subject: Re: [dba-SQLServer] Yes/No in SQL Server
>
>bit
>
>Susan H.
>
>What data type is used to store Boolean values in SQL Server?
>
>
>
>_______________________________________________
>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  Sun Jan  1 15:59:56 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Sun, 1 Jan 2006 16:59:56 -0500
Subject: [dba-SQLServer] Yes/No in SQL Server
In-Reply-To: <BAY102-F2990A16572099C27E11B94E52A0@phx.gbl>
Message-ID: <200601012201.k01M11V06149@databaseadvisors.com>

That is what I was wondering.  Thanks!


John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/
-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Billy Pang
Sent: Sunday, January 01, 2006 4:32 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Yes/No in SQL Server

from bol "Microsoft. SQL Server optimizes the storage used for bit columns.

If there are 8 or fewer bit columns in a table, the columns are stored as 1
byte. If there are from 9 through 16 bit columns, they are stored as 2
bytes, and so on."


>From: "John Colby" <jwcolby at colbyconsulting.com>
>Reply-To: dba-sqlserver at databaseadvisors.com
>To: <dba-sqlserver at databaseadvisors.com>
>Subject: Re: [dba-SQLServer] Yes/No in SQL Server
>Date: Sun, 1 Jan 2006 12:46:25 -0500
>
>So what happens internally?  Does SQL Server pack/unpack as many y/n
>(boolean) values as will fit in an integer or something like that?
>
>
>John W. Colby
>www.ColbyConsulting.com
>
>Contribute your unused CPU cycles to a good cause:
>http://folding.stanford.edu/
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan 
>Harkins
>Sent: Sunday, January 01, 2006 11:24 AM
>To: dba-sqlserver at databaseadvisors.com
>Subject: Re: [dba-SQLServer] Yes/No in SQL Server
>
>bit
>
>Susan H.
>
>What data type is used to store Boolean values in SQL Server?
>
>
>
>_______________________________________________
>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 Jan  2 10:48:40 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Mon, 2 Jan 2006 11:48:40 -0500
Subject: [dba-SQLServer] Free Visual Studio e-learning from Microsoft
Message-ID: <000401c60fbc$63510440$647aa8c0@ColbyM6805>

I just ran across this.

http://msdn.microsoft.com/vstudio/learning/elearning_promo/default.aspx

It is a limited time offer which expires very soon.  One free course.  I am
examining it further now.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/



From darrend at nimble.com.au  Sun Jan  8 04:33:38 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Sun, 8 Jan 2006 21:33:38 +1100
Subject: [dba-SQLServer] Access to SQL Q
Message-ID: <20060108103343.SOSJ3168.omta02ps.mx.bigpond.com@DENZILLAP>

Hi all
Cross posted to AccessD
I have just discovered a significant (and disturbing for me) difference in SQL
and Access that
I never thought about - I'll explain the problem hoping that someone can explain
any work around options I have
 
In SQL I use the following SQL to return 31159 Records - That's the expected
number by the way
 
SELECT I.InvoiceNo, ARP.PointsAmount as Pending
FROM Invoice as I
LEFT JOIN AccountRewardPoints  ARP
ON ARP.InvoiceNo = I.InvoiceNo
AND ARP.PointsStatusCode = 'PP'
Order By I.InvoiceNo
 
In Access if I use that SQL It errors on the Join - IE I can't create joins on
what is 
kind of a Criteria - in this case PP on the PointStatusCode field
 
I am learning the reason
 
When I paste the same SQL into the SQL query designer in enterprise manager (The
one that looks like Access's Query Designer)
- You get there by...
Right clicking ANY SQL table in Enterprise Manager
Select OPEN TABLE
Select QUERY
 
When I do this I see an unusual join line/link that goes not from a field to a
field as you expect in Access
but from the Table name to Table name with a small F and a small X next to each
other to signify the join type
 
I appreciate this means show me all and I mean ALL records (In my case) from
Invoice table IE 31159 of 'em
And it actually creates a Join on the PP Criteria - I think
 
That's all well and good - but how do I get something like that happening in
Access?
 
<big sigh>
 
Darren


From djkr at msn.com  Sun Jan  8 05:57:00 2006
From: djkr at msn.com (DJK(John) Robinson)
Date: Sun, 8 Jan 2006 11:57:00 -0000
Subject: [dba-SQLServer] Access to SQL Q
In-Reply-To: <20060108103343.SOSJ3168.omta02ps.mx.bigpond.com@DENZILLAP>
Message-ID: <BAY106-DAV170A99EBE4DA5C13E32FC9D2230@phx.gbl>

(See reply on AccessD)
J


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: 08 January 2006 10:34
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Access to SQL Q


Hi all
Cross posted to AccessD
I have just discovered a significant (and disturbing for me) difference in
SQL and Access that I never thought about - I'll explain the problem hoping
that someone can explain any work around options I have
 
In SQL I use the following SQL to return 31159 Records - That's the expected
number by the way
 
SELECT I.InvoiceNo, ARP.PointsAmount as Pending
FROM Invoice as I
LEFT JOIN AccountRewardPoints  ARP
ON ARP.InvoiceNo = I.InvoiceNo
AND ARP.PointsStatusCode = 'PP'
Order By I.InvoiceNo
 
In Access if I use that SQL It errors on the Join - IE I can't create joins
on what is 
kind of a Criteria - in this case PP on the PointStatusCode field
 
I am learning the reason
 
When I paste the same SQL into the SQL query designer in enterprise manager
(The one that looks like Access's Query Designer)
- You get there by...
Right clicking ANY SQL table in Enterprise Manager
Select OPEN TABLE
Select QUERY
 
When I do this I see an unusual join line/link that goes not from a field to
a field as you expect in Access but from the Table name to Table name with a
small F and a small X next to each other to signify the join type
 
I appreciate this means show me all and I mean ALL records (In my case) from
Invoice table IE 31159 of 'em And it actually creates a Join on the PP
Criteria - I think
 
That's all well and good - but how do I get something like that happening in
Access?
 
<big sigh>
 
Darren
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From harkinsss at bellsouth.net  Thu Jan 12 10:41:32 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Thu, 12 Jan 2006 11:41:32 -0500
Subject: [dba-SQLServer] SQL Server Express question on information schema
	views
Message-ID: <20060112164131.KKQK12654.ibm67aec.bellsouth.net@SUSANONE>

I can't figure out the syntax for information schema views. 
 
Using this article for 2000, I can get information using this syntax:
 
SELECT * 
FROM db.INFORMATION_SCHEMA.view
WHERE TABLE_NAME = tablename
 
Seems to me, that I shouldn't need a WHERE clause to identify the table. Any
help on this one?
 
Susan Harkins


From harkinsss at bellsouth.net  Thu Jan 12 10:45:44 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Thu, 12 Jan 2006 11:45:44 -0500
Subject: [dba-SQLServer] SQL Server Express question on information
	schemaviews
In-Reply-To: <20060112164131.KKQK12654.ibm67aec.bellsouth.net@SUSANONE>
Message-ID: <20060112164543.KMSI12654.ibm67aec.bellsouth.net@SUSANONE>

I'm sorry, I forgot the link:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_
ia-iz_4pbn.asp 

I didn't find this article or the links to each specific view very helpful. 

Susan H. 

I can't figure out the syntax for information schema views. 
 
Using this article for 2000, I can get information using this syntax:
 
SELECT *
FROM db.INFORMATION_SCHEMA.view
WHERE TABLE_NAME = tablename
 
Seems to me, that I shouldn't need a WHERE clause to identify the table. Any
help on this one?



From harkinsss at bellsouth.net  Thu Jan 12 10:50:41 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Thu, 12 Jan 2006 11:50:41 -0500
Subject: [dba-SQLServer] SQL Server Express question on information
	schemaviews
In-Reply-To: <20060112164131.KKQK12654.ibm67aec.bellsouth.net@SUSANONE>
Message-ID: <20060112165040.KPIP12654.ibm67aec.bellsouth.net@SUSANONE>

Nevermind... ;) 

Thanks anyway. 

Susan H.  

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: Thursday, January 12, 2006 11:42 AM
To: SQL Server List
Subject: [dba-SQLServer] SQL Server Express question on information
schemaviews

I can't figure out the syntax for information schema views. 
 
Using this article for 2000, I can get information using this syntax:
 
SELECT *
FROM db.INFORMATION_SCHEMA.view
WHERE TABLE_NAME = tablename
 
Seems to me, that I shouldn't need a WHERE clause to identify the table. Any
help on this one?
 
Susan Harkins
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.17/226 - Release Date: 1/10/2006
 



From accessd at shaw.ca  Thu Jan 12 12:25:28 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Thu, 12 Jan 2006 10:25:28 -0800
Subject: [dba-SQLServer] SQL Server Express question on
 informationschemaviews
In-Reply-To: <20060112165040.KPIP12654.ibm67aec.bellsouth.net@SUSANONE>
Message-ID: <000701c617a5$90978690$017ba8c0@xpserver>

Susan... and the answer is??

Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: January 12, 2006 8:51 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL Server Express question on
informationschemaviews

Nevermind... ;) 

Thanks anyway. 

Susan H.  

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: Thursday, January 12, 2006 11:42 AM
To: SQL Server List
Subject: [dba-SQLServer] SQL Server Express question on information
schemaviews

I can't figure out the syntax for information schema views. 
 
Using this article for 2000, I can get information using this syntax:
 
SELECT *
FROM db.INFORMATION_SCHEMA.view
WHERE TABLE_NAME = tablename
 
Seems to me, that I shouldn't need a WHERE clause to identify the table. Any
help on this one?
 
Susan Harkins
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.17/226 - Release Date: 1/10/2006
 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From harkinsss at bellsouth.net  Thu Jan 12 12:54:53 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Thu, 12 Jan 2006 13:54:53 -0500
Subject: [dba-SQLServer] SQL Server Express question on
	informationschemaviews
In-Reply-To: <000701c617a5$90978690$017ba8c0@xpserver>
Message-ID: <20060112185452.CJIG12303.ibm60aec.bellsouth.net@SUSANONE>

I was expecting something that isn't... ;) 

I don't think there's another syntax, but there might be. Simply put, the
table contains the information for all tables. The WHERE clause is the
simplest way to restrict what you see. If there's another syntax, I haven't
found it. I tried them all. 

Susan H. 


Susan... and the answer is??


Nevermind... ;) 

Thanks anyway. 

Susan H.  


I can't figure out the syntax for information schema views. 
 
Using this article for 2000, I can get information using this syntax:
 
SELECT *
FROM db.INFORMATION_SCHEMA.view
WHERE TABLE_NAME = tablename
 
Seems to me, that I shouldn't need a WHERE clause to identify the table. Any
help on this one?
 
Susan Harkins
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.17/226 - Release Date: 1/10/2006
 

_______________________________________________
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

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.17/226 - Release Date: 1/10/2006
 



From Joyce.Major at acsalaska.com  Thu Jan 12 13:41:39 2006
From: Joyce.Major at acsalaska.com (Major, Joyce)
Date: Thu, 12 Jan 2006 10:41:39 -0900
Subject: [dba-SQLServer] Selecting Text field
Message-ID: <FA2FBFCAE6E4CC40990C321ED0BC689201337B49@acsanchor1.corp.acsalaska.com>

I posted this in December, but never got a response.  Maybe someone can
help?

 

I am using the following query to read a field defined as Text in SQL
Server 2000.  It is returning the length of the field as 1756 and won't
let me get at any more of the field.  In reality, this particular record
has a field length of close to 10,000 for the field in question.  The
purchased application (I can't see the code it uses) returns all of the
data, but I can only get at part of it using Enterprise Manager.  Does
anyone have suggestions or methods that they have used successfully?

 

DECLARE @textpointer varbinary(16),

            @textlength integer

SELECT @textpointer = TEXTPTR(C536870930),

            @textlength = DATALENGTH(C536870930) - 1000

FROM T97

WHERE C1 = 'TMS643891'

READTEXT T97.C536870930 @textpointer @textlength 1000

 

Joyce Major

(907) 564-1294 Ofc

(907) 529-0147 Cell

(907) 564-8596 Fax

jmajor at acsalaska.com

 


***********************************************************************************
This transmittal may contain confidential information intended solely for
the addressee. If you are not the intended recipient, you are hereby
notified that you have received this transmittal in error; any review,
dissemination, distribution or copying of this transmittal is strictly
prohibited. If you have received this communication in error, please notify
us immediately by reply or by telephone (collect at 907-564-1000) and ask to
speak with the message sender. In addition, please immediately delete this
message and all attachments. Thank you. ACS




From harkinsss at bellsouth.net  Thu Jan 12 14:15:00 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Thu, 12 Jan 2006 15:15:00 -0500
Subject: [dba-SQLServer] Another Express question
Message-ID: <20060112201459.OBSF12654.ibm67aec.bellsouth.net@SUSANONE>

Has anyone tried Management Studios query editor to create a stored
procedure? It seems a bit awkward -- I found it easier to use insert the
appropriate SQL statement into the template and execute it to save it. 
 
Any comments? Maybe I'm doing something wrong? 
 
In the stored procedure template, I clicked the Design Query button and used
it as if I were creating a view. It did update the template, but very oddly
-- the SQL statement was at the top of the template instead of inside the
CREATE PROCEDURE statement as I had expected. Perhaps the query editor isn't
really supposed to work with stored procedures? 
 
Susan H. 


From accessd at shaw.ca  Thu Jan 12 18:56:50 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Thu, 12 Jan 2006 16:56:50 -0800
Subject: [dba-SQLServer] Another Express question
In-Reply-To: <20060112201459.OBSF12654.ibm67aec.bellsouth.net@SUSANONE>
Message-ID: <001201c617dc$3cce39f0$017ba8c0@xpserver>

Hi Susan:

I am not sure what the issue is but when I am building a SP, I may use the
template to initiate the creation, make any appropriate changes to match my
requirements, test until the desired results ate obtained, create a new SP
and cut and paste resultant query into the new SP. I understand you can
create your own templates but should not be able to over-write system the
template/samples.

Jim   

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: January 12, 2006 12:15 PM
To: SQL Server List
Subject: [dba-SQLServer] Another Express question

Has anyone tried Management Studios query editor to create a stored
procedure? It seems a bit awkward -- I found it easier to use insert the
appropriate SQL statement into the template and execute it to save it. 
 
Any comments? Maybe I'm doing something wrong? 
 
In the stored procedure template, I clicked the Design Query button and used
it as if I were creating a view. It did update the template, but very oddly
-- the SQL statement was at the top of the template instead of inside the
CREATE PROCEDURE statement as I had expected. Perhaps the query editor isn't
really supposed to work with stored procedures? 
 
Susan H. 
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From harkinsss at bellsouth.net  Thu Jan 12 19:44:59 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Thu, 12 Jan 2006 20:44:59 -0500
Subject: [dba-SQLServer] Another Express question
In-Reply-To: <001201c617dc$3cce39f0$017ba8c0@xpserver>
Message-ID: <20060113014521.UXLG11466.ibm58aec.bellsouth.net@SUSANONE>

You can click the Design Query button to open a query window and build the
query graphically. When you close that window the code does appear in the
template, but at the top -- not after the CREATE PROCEDURE statement, as I
had expected. 

I wasn't expecting a graphic designer at all, but if you click the button
it's there. I'm wondering if it appears by mistake, or if the feature's just
not finished, or if I'm just not using it correctly. 

Using the template is fine -- but since the query design window does open
and the code is transferred to the template when you close it, it seems like
it's "supposed" to be that way, regardless of how clumsy it seems to be. 

Susan H. 

Hi Susan:

I am not sure what the issue is but when I am building a SP, I may use the
template to initiate the creation, make any appropriate changes to match my
requirements, test until the desired results ate obtained, create a new SP
and cut and paste resultant query into the new SP. I understand you can
create your own templates but should not be able to over-write system the
template/samples.

Jim   

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: January 12, 2006 12:15 PM
To: SQL Server List
Subject: [dba-SQLServer] Another Express question

Has anyone tried Management Studios query editor to create a stored
procedure? It seems a bit awkward -- I found it easier to use insert the
appropriate SQL statement into the template and execute it to save it. 
 
Any comments? Maybe I'm doing something wrong? 
 
In the stored procedure template, I clicked the Design Query button and used
it as if I were creating a view. It did update the template, but very oddly
-- the SQL statement was at the top of the template instead of inside the
CREATE PROCEDURE statement as I had expected. Perhaps the query editor isn't
really supposed to work with stored procedures? 
 
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

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.17/226 - Release Date: 1/10/2006
 



From listmaster at databaseadvisors.com  Thu Jan 12 20:48:24 2006
From: listmaster at databaseadvisors.com (Bryan Carbonnell)
Date: Thu, 12 Jan 2006 21:48:24 -0500
Subject: [dba-SQLServer] Administrivia - DBA's New Executive Officers.
Message-ID: <43C6CEA8.24082.46E416@listmaster.databaseadvisors.com>

The Board of Directors of Database Advisors recently held elections 
for the executive committee for the upcoming year.

The Executive Officers for 2006 are:
President: John Bartow
Vice-President: Reuben Cummings
Secretary: Donna Cook
Treasurer: Keith Williamson

Congratulations to all.


-- 
Bryan Carbonnell - listmaster at databaseadvisors.com
Normal people worry me.




From fhtapia at gmail.com  Thu Jan 12 21:17:44 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Thu, 12 Jan 2006 19:17:44 -0800
Subject: [dba-SQLServer] Selecting Text field
In-Reply-To: <FA2FBFCAE6E4CC40990C321ED0BC689201337B49@acsanchor1.corp.acsalaska.com>
References: <FA2FBFCAE6E4CC40990C321ED0BC689201337B49@acsanchor1.corp.acsalaska.com>
Message-ID: <b874372a0601121917w10da7696p9c2affe794b55aad@mail.gmail.com>

EM will only give you back so much data, and if you do this in QA you're
also limited on how much data is returned, if you are writing your own
application you can use ado to define the field as a text field however, if
you just need the data, use Access as an ADP and get to the field as needed.
Access 2002/2003 are better for this kind of thing...

On 1/12/06, Major, Joyce <Joyce.Major at acsalaska.com> wrote:
>
> I posted this in December, but never got a response.  Maybe someone can
> help?
>
>
>
> I am using the following query to read a field defined as Text in SQL
> Server 2000.  It is returning the length of the field as 1756 and won't
> let me get at any more of the field.  In reality, this particular record
> has a field length of close to 10,000 for the field in question.  The
> purchased application (I can't see the code it uses) returns all of the
> data, but I can only get at part of it using Enterprise Manager.  Does
> anyone have suggestions or methods that they have used successfully?
>
>
>
> DECLARE @textpointer varbinary(16),
>
>             @textlength integer
>
> SELECT @textpointer = TEXTPTR(C536870930),
>
>             @textlength = DATALENGTH(C536870930) - 1000
>
> FROM T97
>
> WHERE C1 = 'TMS643891'
>
> READTEXT T97.C536870930 @textpointer @textlength 1000
>
>
>
> Joyce Major
>
> (907) 564-1294 Ofc
>
> (907) 529-0147 Cell
>
> (907) 564-8596 Fax
>
> jmajor at acsalaska.com
>
>
>
>
>
> ***********************************************************************************
> This transmittal may contain confidential information intended solely for
> the addressee. If you are not the intended recipient, you are hereby
> notified that you have received this transmittal in error; any review,
> dissemination, distribution or copying of this transmittal is strictly
> prohibited. If you have received this communication in error, please
> notify
> us immediately by reply or by telephone (collect at 907-564-1000) and ask
> to
> speak with the message sender. In addition, please immediately delete this
> message and all attachments. Thank you. ACS
>
>
> _______________________________________________
> 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 harkinsss at bellsouth.net  Sat Jan 14 12:19:29 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Sat, 14 Jan 2006 13:19:29 -0500
Subject: [dba-SQLServer] trigger help
Message-ID: <000501c61937$16cb5d80$a6b3d6d1@SUSANONE>

I'm using Express Management Studio to create a trigger that uses the
temporary inserted table to update inventory -- simple example, but I get an
error that the schema in the target table doesn't match the trigger schema.
My guess is it doesn't like the use of inserted as a table name because at
the time I'm creating the trigger it doesn't exist. If that's the case, I
don't know how to get around that. 
 
Here's the trigger:
 
CREATE TRIGGER UpdateInventory ON Sales.dbo.Orders
AFTER INSERT
AS 
BEGIN
    UPDATE Products
    SET Products.InStock = (Products.InStock - Inserted.Qty)
    FROM Products JOIN Inserted ON Products.ProdID - Inserted.ProdID
END
GO
 
I've checked the column names, just to be sure, and they above in correct in
that respect. I've run into trouble using the inserted temporary table
before, but I don't remember how I skirted it. 
 
Susan H. 
 


From newsgrps at dalyn.co.nz  Sat Jan 14 12:42:21 2006
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Sun, 15 Jan 2006 07:42:21 +1300
Subject: [dba-SQLServer] trigger help
In-Reply-To: <000501c61937$16cb5d80$a6b3d6d1@SUSANONE>
References: <000501c61937$16cb5d80$a6b3d6d1@SUSANONE>
Message-ID: <7.0.0.16.0.20060115073950.01a43358@dalyn.co.nz>

I think I have got round similar problems by creating the table as a 
normal table, creating the trigger and saving it, then deleting the table.

HTH

David Emerson
Dalyn Software Ltd
New Zealand

At 15/01/2006, you wrote:
>I'm using Express Management Studio to create a trigger that uses the
>temporary inserted table to update inventory -- simple example, but I get an
>error that the schema in the target table doesn't match the trigger schema.
>My guess is it doesn't like the use of inserted as a table name because at
>the time I'm creating the trigger it doesn't exist. If that's the case, I
>don't know how to get around that.
>
>Here's the trigger:
>
>CREATE TRIGGER UpdateInventory ON Sales.dbo.Orders
>AFTER INSERT
>AS
>BEGIN
>     UPDATE Products
>     SET Products.InStock = (Products.InStock - Inserted.Qty)
>     FROM Products JOIN Inserted ON Products.ProdID - Inserted.ProdID
>END
>GO
>
>I've checked the column names, just to be sure, and they above in correct in
>that respect. I've run into trouble using the inserted temporary table
>before, but I don't remember how I skirted it.
>
>Susan H.



From harkinsss at bellsouth.net  Sat Jan 14 13:04:11 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Sat, 14 Jan 2006 14:04:11 -0500
Subject: [dba-SQLServer] trigger help
In-Reply-To: <7.0.0.16.0.20060115073950.01a43358@dalyn.co.nz>
Message-ID: <001901c6193d$4e501b50$a6b3d6d1@SUSANONE>

Have I misunderstood inserted, as a temp table then? I thought SQL Server
created and used this table internally -- which  of course creates a problem
if you try to create a trigger before SQL Server creates the table. In my
case, I've already inserted records, so the table should exist, or at least.
Does SS create and destroy the table for each insert? Or does it exist for
the life of the db? 

You created a table using the name inserted with the appropriate schema,
created the trigger, and then deleted your table? 

Susan H.  


I think I have got round similar problems by creating the table as a normal
table, creating the trigger and saving it, then deleting the table.

HTH

David Emerson
Dalyn Software Ltd
New Zealand

At 15/01/2006, you wrote:
>I'm using Express Management Studio to create a trigger that uses the 
>temporary inserted table to update inventory -- simple example, but I 
>get an error that the schema in the target table doesn't match the trigger
schema.
>My guess is it doesn't like the use of inserted as a table name because 
>at the time I'm creating the trigger it doesn't exist. If that's the 
>case, I don't know how to get around that.
>
>Here's the trigger:
>
>CREATE TRIGGER UpdateInventory ON Sales.dbo.Orders AFTER INSERT AS 
>BEGIN
>     UPDATE Products
>     SET Products.InStock = (Products.InStock - Inserted.Qty)
>     FROM Products JOIN Inserted ON Products.ProdID - Inserted.ProdID 
>END GO
>
>I've checked the column names, just to be sure, and they above in 
>correct in that respect. I've run into trouble using the inserted 
>temporary table before, but I don't remember how I skirted it.
>
>Susan H.

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.17/226 - Release Date: 1/10/2006
 



From mwp.reid at qub.ac.uk  Sat Jan 14 13:14:27 2006
From: mwp.reid at qub.ac.uk (mwp.reid at qub.ac.uk)
Date: Sat, 14 Jan 2006 19:14:27 -0000
Subject: [dba-SQLServer] trigger help
Message-ID: <200601141914.k0EJEIV11812@databaseadvisors.com>

The table exists within the life time of the trigger. 

Try it using query analyser and see if it works. Its my birthday party now so if it dosnt work give me a shout and I will check in the morning.

U sure this isn?t  an sql express issue not a trigger issue?

-----Original Message-----
    From: "Susan Harkins"<harkinsss at bellsouth.net>
    Sent: 1/14/06 7:04:11 PM
    To: "dba-sqlserver at databaseadvisors.com"<dba-sqlserver at databaseadvisors.com>
    Subject: Re: [dba-SQLServer] trigger help
    
    Have I misunderstood inserted, as a temp table then? I thought SQL Server
    created and used this table internally -- which  of course creates a problem
    if you try to create a trigger before SQL Server creates the table. In my
    case, I've already inserted records, so the table should exist, or at least.
    Does SS create and destroy the table for each insert? Or does it exist for
    the life of the db? 
    
    You created a table using the name inserted with the appropriate schema,
    created the trigger, and then deleted your table? 
    
    Susan H.  
    
    
    I think I have got round similar problems by creating the table as a normal
    table, creating the trigger and saving it, then deleting the table.
    
    HTH
    
    David Emerson
    Dalyn Software Ltd
    New Zealand
    
    At 15/01/2006, you wrote:
    >I'm using Express Management Studio to create a trigger that uses the 
    >temporary inserted table to update inventory -- simple example, but I 
    >get an error that the schema in the target table doesn't match the trigger
    schema.
    >My guess is it doesn't like the use of inserted as a table name because 
    >at the time I'm creating the trigger it doesn't exist. If that's the 
    >case, I don't know how to get around that.
    >
    >Here's the trigger:
    >
    >CREATE TRIGGER UpdateInventory ON Sales.dbo.Orders AFTER INSERT AS 
    >BEGIN
    >     UPDATE Products
    >     SET Products.InStock = (Products.InStock - Inserted.Qty)
    >     FROM Products JOIN Inserted ON Products.ProdID - Inserted.ProdID 
    >END GO
    >
    >I've checked the column names, just to be sure, and they above in 
    >correct in that respect. I've run into trouble using the inserted 
    >temporary table before, but I don't remember how I skirted it.
    >
    >Susan H.
    
    _______________________________________________
    dba-SQLServer mailing list
    dba-SQLServer at databaseadvisors.com
    http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
    http://www.databaseadvisors.com
    
    --
    No virus found in this incoming message.
    Checked by AVG Free Edition.
    Version: 7.1.371 / Virus Database: 267.14.17/226 - Release Da    

[Message truncated. Tap Edit->Mark for Download to get remaining portion.]



From newsgrps at dalyn.co.nz  Sat Jan 14 13:31:07 2006
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Sun, 15 Jan 2006 08:31:07 +1300
Subject: [dba-SQLServer] trigger help
In-Reply-To: <001901c6193d$4e501b50$a6b3d6d1@SUSANONE>
References: <7.0.0.16.0.20060115073950.01a43358@dalyn.co.nz>
	<001901c6193d$4e501b50$a6b3d6d1@SUSANONE>
Message-ID: <7.0.0.16.0.20060115082505.01a9c9d8@dalyn.co.nz>

I had a situation where I needed to create a table using fieldnames 
based on other data, then run a query based on the new 
table.  However, because the table wasn't permanent I couldn't create 
the query.  What I did was create a normal table (tblTableName), base 
the query on that (SELECT * FROM tblTableName).  Once the query was 
saved I could delete the table.  Since the query was only run when 
the temporary table was created it worked.  Mind you, the tables I 
created were not internal temp ones as I needed to access them 
outside of the sproc that created them.  The sproc deleted the 
previous copy of the table before creating the new one based on new data.

David Emerson
Dalyn Software Ltd
New Zealand

At 15/01/2006, you wrote:
>Have I misunderstood inserted, as a temp table then? I thought SQL Server
>created and used this table internally -- which  of course creates a problem
>if you try to create a trigger before SQL Server creates the table. In my
>case, I've already inserted records, so the table should exist, or at least.
>Does SS create and destroy the table for each insert? Or does it exist for
>the life of the db?
>
>You created a table using the name inserted with the appropriate schema,
>created the trigger, and then deleted your table?
>
>Susan H.
>
>
>I think I have got round similar problems by creating the table as a normal
>table, creating the trigger and saving it, then deleting the table.
>
>HTH
>
>David Emerson
>Dalyn Software Ltd
>New Zealand
>
>At 15/01/2006, you wrote:
> >I'm using Express Management Studio to create a trigger that uses the
> >temporary inserted table to update inventory -- simple example, but I
> >get an error that the schema in the target table doesn't match the trigger
>schema.
> >My guess is it doesn't like the use of inserted as a table name because
> >at the time I'm creating the trigger it doesn't exist. If that's the
> >case, I don't know how to get around that.
> >
> >Here's the trigger:
> >
> >CREATE TRIGGER UpdateInventory ON Sales.dbo.Orders AFTER INSERT AS
> >BEGIN
> >     UPDATE Products
> >     SET Products.InStock = (Products.InStock - Inserted.Qty)
> >     FROM Products JOIN Inserted ON Products.ProdID - Inserted.ProdID
> >END GO
> >
> >I've checked the column names, just to be sure, and they above in
> >correct in that respect. I've run into trouble using the inserted
> >temporary table before, but I don't remember how I skirted it.
> >
> >Susan H.
>
>_______________________________________________
>dba-SQLServer mailing list
>dba-SQLServer at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
>http://www.databaseadvisors.com
>
>--
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.371 / Virus Database: 267.14.17/226 - Release Date: 1/10/2006
>
>
>_______________________________________________
>dba-SQLServer mailing list
>dba-SQLServer at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
>http://www.databaseadvisors.com



From harkinsss at bellsouth.net  Sat Jan 14 13:33:25 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Sat, 14 Jan 2006 14:33:25 -0500
Subject: [dba-SQLServer] trigger help
In-Reply-To: <200601141914.k0EJEIV11812@databaseadvisors.com>
Message-ID: <001d01c61941$6439b530$a6b3d6d1@SUSANONE>

HAPPY BIRTHDAY!!!!!!! 

Why are you on the computer????? :) This may be an Express problem, but I
wanted to check first. I do remember having this problem with SQL Server 200
in the Query Analyzer -- but I don't remember how I eventually resolved it.
The problem may not have been the temp table at all -- I just don't
remember. 

The problem is that I can't create the trigger. 

I'm going to create a temp inserted table and see if that keeps MS from
throwing this particular error -- if it does, as David suggested -- it's a
workaround. I just want to make sure it's necessary and not some silly
mistake or assumption I'm making. 

Susan H. 


The table exists within the life time of the trigger. 

Try it using query analyser and see if it works. Its my birthday party now
so if it dosnt work give me a shout and I will check in the morning.

U sure this isn't  an sql express issue not a trigger issue?




From mwp.reid at qub.ac.uk  Sat Jan 14 13:47:50 2006
From: mwp.reid at qub.ac.uk (mwp.reid at qub.ac.uk)
Date: Sat, 14 Jan 2006 19:47:50 -0000
Subject: [dba-SQLServer] trigger help
Message-ID: <200601141947.k0EJlfV20768@databaseadvisors.com>

Thanks

Just checking for email

Of now. Let me know if it works. Will have a look tomorrow anyway

Martin



-----Original Message-----
    From: "Susan Harkins"<harkinsss at bellsouth.net>
    Sent: 1/14/06 7:33:25 PM
    To: "dba-sqlserver at databaseadvisors.com"<dba-sqlserver at databaseadvisors.com>
    Subject: Re: [dba-SQLServer] trigger help
    
    HAPPY BIRTHDAY!!!!!!! 
    
    Why are you on the computer????? :) This may be an Express problem, but I
    wanted to check first. I do remember having this problem with SQL Server 200
    in the Query Analyzer -- but I don't remember how I eventually resolved it.
    The problem may not have been the temp table at all -- I just don't
    remember. 
    
    The problem is that I can't create the trigger. 
    
    I'm going to create a temp inserted table and see if that keeps MS from
    throwing this particular error -- if it does, as David suggested -- it's a
    workaround. I just want to make sure it's necessary and not some silly
    mistake or assumption I'm making. 
    
    Susan H. 
    
    
    The table exists within the life time of the trigger. 
    
    Try it using query analyser and see if it works. Its my birthday party now
    so if it dosnt work give me a shout and I will check in the morning.
    
    U sure this isn't  an sql express issue not a trigger issue?
    
    
    _______________________________________________
    dba-SQLServer mailing list
    dba-SQLServer at databaseadvisors.com
    http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
    http://www.databaseadvisors.com
    



From harkinsss at bellsouth.net  Sun Jan 15 09:23:58 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Sun, 15 Jan 2006 10:23:58 -0500
Subject: [dba-SQLServer] trigger help
In-Reply-To: <7.0.0.16.0.20060115082505.01a9c9d8@dalyn.co.nz>
Message-ID: <000001c619e7$b5aad790$b2b3d6d1@SUSANONE>

Well, once I deleted the END statement from the template it ran fine. 

Guys, what don't I know here? It doesn't seem right to me that an END
statement would've caused this problem. 

Susan H. 

I had a situation where I needed to create a table using fieldnames based on
other data, then run a query based on the new table.  However, because the
table wasn't permanent I couldn't create the query.  What I did was create a
normal table (tblTableName), base the query on that (SELECT * FROM
tblTableName).  Once the query was saved I could delete the table.  Since
the query was only run when the temporary table was created it worked.  Mind
you, the tables I created were not internal temp ones as I needed to access
them outside of the sproc that created them.  The sproc deleted the previous
copy of the table before creating the new one based on new data.




From accessd at shaw.ca  Sun Jan 15 12:28:40 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Sun, 15 Jan 2006 10:28:40 -0800
Subject: [dba-SQLServer] trigger help
In-Reply-To: <000001c619e7$b5aad790$b2b3d6d1@SUSANONE>
Message-ID: <001401c61a01$823e7aa0$017ba8c0@xpserver>

Susan:

It is sometimes confusing using the SP language where there is no 'end of
section/code'. The snippet either runs out of lines to process and
terminates or new 'structure' is started. Very confusing for us VB guys that
are use to a clean start and finish structure.

Jim 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: January 15, 2006 7:24 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] trigger help

Well, once I deleted the END statement from the template it ran fine. 

Guys, what don't I know here? It doesn't seem right to me that an END
statement would've caused this problem. 

Susan H. 

I had a situation where I needed to create a table using fieldnames based on
other data, then run a query based on the new table.  However, because the
table wasn't permanent I couldn't create the query.  What I did was create a
normal table (tblTableName), base the query on that (SELECT * FROM
tblTableName).  Once the query was saved I could delete the table.  Since
the query was only run when the temporary table was created it worked.  Mind
you, the tables I created were not internal temp ones as I needed to access
them outside of the sproc that created them.  The sproc deleted the previous
copy of the table before creating the new one based on new data.


_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From harkinsss at bellsouth.net  Sun Jan 15 13:05:41 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Sun, 15 Jan 2006 14:05:41 -0500
Subject: [dba-SQLServer] trigger help
In-Reply-To: <001401c61a01$823e7aa0$017ba8c0@xpserver>
Message-ID: <001e01c61a06$ae661750$98b3d6d1@SUSANONE>

It was entirely my fault, I just didn't see it at first. I had entered the
code myself and deleted the BEGIN statement, so that END statement way out
of sight just wasn't correct -- my own fault. :( 

Susan H. 

Susan:

It is sometimes confusing using the SP language where there is no 'end of
section/code'. The snippet either runs out of lines to process and
terminates or new 'structure' is started. Very confusing for us VB guys that
are use to a clean start and finish structure.




From newsgrps at dalyn.co.nz  Sun Jan 15 15:01:18 2006
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Mon, 16 Jan 2006 10:01:18 +1300
Subject: [dba-SQLServer] Shrinking Log File
Message-ID: <7.0.0.16.0.20060116091933.00f510f0@dalyn.co.nz>

I have restored an SQL2K bak file from a different server to my stand 
alone development computer.

In the Shrink File box for the database in Enterprise Manager the log 
file is showing 13779MB in size with 113MB space used.

Under shrink action I have tried Shrink File To 150MB but an error 
8985 appears saying it can't find file SQLbe_Log in sysfiles.  The 
strange thing is that the name refers to the original file that this 
data base was created from over 3 years ago.  The database that I am 
trying to shrink is called SQLLtdbe_Log.  This name doesn't appear in 
the database file list.

If I just delete the log file, will a new one be created?  As this is 
just for testing purposes I don't need to be able to recover any 
previous transactions.

Regards

David Emerson
Dalyn Software Ltd
999 Moonshine Rd, RD 1
Judgeford, Porirua  6006
Phone    (04) 235-6782
Fax      (04) 235-6783
Mob      (027) 280-9348 



From harkinsss at bellsouth.net  Sun Jan 15 19:45:54 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Sun, 15 Jan 2006 20:45:54 -0500
Subject: [dba-SQLServer] server logs are empty
Message-ID: <000001c61a3e$988279a0$c8b3d6d1@SUSANONE>

My SQL Server Express server logs are empty. Does anyone know if this
feature is working yet? 
 
Susan H. 



From newsgrps at dalyn.co.nz  Sun Jan 15 21:39:01 2006
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Mon, 16 Jan 2006 16:39:01 +1300
Subject: [dba-SQLServer] Shrinking Log File
In-Reply-To: <7.0.0.16.0.20060116091933.00f510f0@dalyn.co.nz>
References: <7.0.0.16.0.20060116091933.00f510f0@dalyn.co.nz>
Message-ID: <7.0.0.16.0.20060116163411.01abaeb0@dalyn.co.nz>

OK, Now I have tried the following in Query Analyser:

DBCC SHRINKFILE (2, 150)

This came up with the following error message in the messages pane:

Cannot shrink log file 2 (egasSQLLtdbe_log) because all logical log 
files are in use.

How do I free up logical log files?

David

At 16/01/2006, you wrote:
>I have restored an SQL2K bak file from a different server to my stand
>alone development computer.
>
>In the Shrink File box for the database in Enterprise Manager the log
>file is showing 13779MB in size with 113MB space used.
>
>Under shrink action I have tried Shrink File To 150MB but an error
>8985 appears saying it can't find file SQLbe_Log in sysfiles.  The
>strange thing is that the name refers to the original file that this
>data base was created from over 3 years ago.  The database that I am
>trying to shrink is called SQLLtdbe_Log.  This name doesn't appear in
>the database file list.
>
>If I just delete the log file, will a new one be created?  As this is
>just for testing purposes I don't need to be able to recover any
>previous transactions.
>
>Regards
>
>David Emerson
>Dalyn Software Ltd
>999 Moonshine Rd, RD 1
>Judgeford, Porirua  6006
>Phone    (04) 235-6782
>Fax      (04) 235-6783
>Mob      (027) 280-9348



From shait at mindspring.com  Mon Jan 16 07:19:36 2006
From: shait at mindspring.com (Stephen Hait)
Date: Mon, 16 Jan 2006 08:19:36 -0500
Subject: [dba-SQLServer] Shrinking Log File
In-Reply-To: <7.0.0.16.0.20060116163411.01abaeb0@dalyn.co.nz>
References: <7.0.0.16.0.20060116091933.00f510f0@dalyn.co.nz>
	<7.0.0.16.0.20060116163411.01abaeb0@dalyn.co.nz>
Message-ID: <bb9d2d1e0601160519i6ff08f49h7f7648f04975f177@mail.gmail.com>

If it doesn't matter if the log file is usable, you could try:
1 detach database.
2 rename or delete log file.
3 execute code below to have sqlserver generate a new transaction log of
about 500k.
EXEC sp_attach_single_file_db @dbname = 'yourDBname',
@physname = 'd:\full\path\to\your\yourDBname_data.mdf'

Regards,
Stephen

On 1/15/06, David Emerson <newsgrps at dalyn.co.nz> wrote:
>
> OK, Now I have tried the following in Query Analyser:
>
> DBCC SHRINKFILE (2, 150)
>
> This came up with the following error message in the messages pane:
>
> Cannot shrink log file 2 (egasSQLLtdbe_log) because all logical log
> files are in use.
>
> How do I free up logical log files?
>
> David
>
> At 16/01/2006, you wrote:
> >I have restored an SQL2K bak file from a different server to my stand
> >alone development computer.
> >
> >In the Shrink File box for the database in Enterprise Manager the log
> >file is showing 13779MB in size with 113MB space used.
> >
> >Under shrink action I have tried Shrink File To 150MB but an error
> >8985 appears saying it can't find file SQLbe_Log in sysfiles.  The
> >strange thing is that the name refers to the original file that this
> >data base was created from over 3 years ago.  The database that I am
> >trying to shrink is called SQLLtdbe_Log.  This name doesn't appear in
> >the database file list.
> >
> >If I just delete the log file, will a new one be created?  As this is
> >just for testing purposes I don't need to be able to recover any
> >previous transactions.
> >
> >Regards
> >
> >David Emerson
> >Dalyn Software Ltd
> >999 Moonshine Rd, RD 1
> >Judgeford, Porirua  6006
> >Phone    (04) 235-6782
> >Fax      (04) 235-6783
> >Mob      (027) 280-9348
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>


From rosewbalan at rediffmail.com  Mon Jan 16 12:56:43 2006
From: rosewbalan at rediffmail.com (Rose Balan)
Date: 16 Jan 2006 18:56:43 -0000
Subject: [dba-SQLServer] Table Scripts
Message-ID: <20060116185643.4394.qmail@webmail18.rediffmail.com>


I am new to SQL...

I have some doubt regarding table structure scrips...

using sp_helptext 'procedure name' I got the procedure scripT, I don't know how to create the script for tables using system stored procedures.

Thanks and Regards
RWB

From artful at rogers.com  Mon Jan 16 13:26:52 2006
From: artful at rogers.com (Arthur Fuller)
Date: Mon, 16 Jan 2006 14:26:52 -0500
Subject: [dba-SQLServer] Table Scripts
In-Reply-To: <20060116185643.4394.qmail@webmail18.rediffmail.com>
Message-ID: <05cf01c61ad2$cde6ff00$8e01a8c0@rock>

I'm not sure exactly what you need to do, but if you open Enterprise Manager
(2000) or SQL Management Studio (2005), expand the databases treenode and
then the Databases node, then right-click on the table of interest, you get
a menu (which varies slightly from 2000 to 2005, but in both cases includes
the ability to generate a DDL (Data Definition Language) script that can
create the table of interest.
At that point you have several options. You can do this repeatedly for
several tables, pasting the resultant scripts into your text editor and then
saving that text file to something.sql, then execute it from Query Analyzer
(2000) or New Query (2005). Using this copy-paste technique, you can build
up a script that will create as many tables as desired.
On the other hand, if you want ALL the tables in a given database, you might
want instead to create a copy of the database then nuke all its rows, so you
end up with all the check constraints, stored procedures, UDFs and so on,
but with no data.
There is even a road between these two. You could back up a current copy,
nuke all the user-specific rows and preserve the user-generic rows (i.e.
lookup tables consisting of city names, product categories, etc.).
It is very simple to generate table scripts (as outlined above). However, a
table script does not constitute a database script, which is why I sketched
the options above: they break down to a) some tables from the source
database; b) the whole source database but no data; and c) the whole
database with some data.
HTH,
Arthur

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Rose Balan
Sent: January 16, 2006 1:57 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Table Scripts


I am new to SQL...

I have some doubt regarding table structure scrips...

using sp_helptext 'procedure name' I got the procedure scripT, I don't know
how to create the script for tables using system stored procedures.

Thanks and Regards
RWB
_______________________________________________
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 Jan 16 16:46:08 2006
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Tue, 17 Jan 2006 11:46:08 +1300
Subject: [dba-SQLServer] Shrinking Log File
In-Reply-To: <bb9d2d1e0601160519i6ff08f49h7f7648f04975f177@mail.gmail.co
 m>
References: <7.0.0.16.0.20060116091933.00f510f0@dalyn.co.nz>
	<7.0.0.16.0.20060116163411.01abaeb0@dalyn.co.nz>
	<bb9d2d1e0601160519i6ff08f49h7f7648f04975f177@mail.gmail.com>
Message-ID: <7.0.0.16.0.20060117114044.01a7b9d0@dalyn.co.nz>

Thanks Stephen.  That solved my immediate problem.

Now my problem is that the files backed up from the end of last year 
are restoring fine with transaction logs in the size 
expected.  However, when I try to restore a back up file from this 
year (I have 2 from 2 different databases) the transaction log is way 
out of proportion to the actual size used (eg 13779MB in size with 
113MB space used).  The original files on the server are closer to 
what I would expect them to be but for some reason the backups are 
not restoring well.

Any thoughts on what went wrong.

David

At 17/01/2006, Stephen Hait wrote:
>If it doesn't matter if the log file is usable, you could try:
>1 detach database.
>2 rename or delete log file.
>3 execute code below to have sqlserver generate a new transaction log of
>about 500k.
>EXEC sp_attach_single_file_db @dbname = 'yourDBname',
>@physname = 'd:\full\path\to\your\yourDBname_data.mdf'
>
>Regards,
>Stephen
>
>On 1/15/06, David Emerson <newsgrps at dalyn.co.nz> wrote:
> >
> > OK, Now I have tried the following in Query Analyser:
> >
> > DBCC SHRINKFILE (2, 150)
> >
> > This came up with the following error message in the messages pane:
> >
> > Cannot shrink log file 2 (egasSQLLtdbe_log) because all logical log
> > files are in use.
> >
> > How do I free up logical log files?
> >
> > David
> >
> > At 16/01/2006, you wrote:
> > >I have restored an SQL2K bak file from a different server to my stand
> > >alone development computer.
> > >
> > >In the Shrink File box for the database in Enterprise Manager the log
> > >file is showing 13779MB in size with 113MB space used.
> > >
> > >Under shrink action I have tried Shrink File To 150MB but an error
> > >8985 appears saying it can't find file SQLbe_Log in sysfiles.  The
> > >strange thing is that the name refers to the original file that this
> > >data base was created from over 3 years ago.  The database that I am
> > >trying to shrink is called SQLLtdbe_Log.  This name doesn't appear in
> > >the database file list.
> > >
> > >If I just delete the log file, will a new one be created?  As this is
> > >just for testing purposes I don't need to be able to recover any
> > >previous transactions.
> > >
> > >Regards
> > >
> > >David Emerson
> > >Dalyn Software Ltd
> > >999 Moonshine Rd, RD 1
> > >Judgeford, Porirua  6006
> > >Phone    (04) 235-6782
> > >Fax      (04) 235-6783
> > >Mob      (027) 280-9348



From harkinsss at bellsouth.net  Mon Jan 16 17:51:33 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Mon, 16 Jan 2006 18:51:33 -0500
Subject: [dba-SQLServer] Express question
Message-ID: <002401c61af7$c88dd360$ccb3d6d1@SUSANONE>

Does anyone know if you can backup to filegroups in SQL Server Express? I
can't make it work, although I can create a filegroup. 
 
Susan H. 



From KP at sdsonline.net  Mon Jan 16 18:32:01 2006
From: KP at sdsonline.net (Kath Pelletti)
Date: Tue, 17 Jan 2006 11:32:01 +1100
Subject: [dba-SQLServer] Buy sql server 2005
Message-ID: <001a01c61afd$6f1f5410$6501a8c0@user>

Hi everyone - happy new year.

I need to order a copy of Sql Server 2005 for a new project I need to write. I've never used / bought it before. Can someone point me to the version I need?

I notice that there is a MS Sql Server 2005 Developer edition (only $85 AUS). Will that give me everything I need? And can you tell me which version my client will need so that I can help them to work out costs ?

Thanks all.

Also, can I assume that Visual Studio 2005 Professional Edition includes everything I need to code vb.net and asp.net apps? 

Thanks. 

Kath


From accessd at shaw.ca  Mon Jan 16 19:25:39 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Mon, 16 Jan 2006 17:25:39 -0800
Subject: [dba-SQLServer] Buy sql server 2005
In-Reply-To: <001a01c61afd$6f1f5410$6501a8c0@user>
Message-ID: <000401c61b04$ed1fef30$017ba8c0@xpserver>

Hi Kath:

It should be everything you need. The only package above this one is the
'enterprise' version and as I understand it, the Enterprise version has the
ability to use more memory, CPUs and hard drive space. 

HTH
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Kath
Pelletti
Sent: January 16, 2006 4:32 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Buy sql server 2005

Hi everyone - happy new year.

I need to order a copy of Sql Server 2005 for a new project I need to write.
I've never used / bought it before. Can someone point me to the version I
need?

I notice that there is a MS Sql Server 2005 Developer edition (only $85
AUS). Will that give me everything I need? And can you tell me which version
my client will need so that I can help them to work out costs ?

Thanks all.

Also, can I assume that Visual Studio 2005 Professional Edition includes
everything I need to code vb.net and asp.net apps? 

Thanks. 

Kath
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From harkinsss at bellsouth.net  Tue Jan 17 08:58:24 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Tue, 17 Jan 2006 09:58:24 -0500
Subject: [dba-SQLServer] Properties window
Message-ID: <003c01c61b76$77c6b580$ccb3d6d1@SUSANONE>

All of the Properties window for tables in Express are grayed out -- for
every table, period. Could someone check theirs for me? 
 
Just a right-click on the table and choose Properties. 
 
Susan H. 



From shait at mindspring.com  Tue Jan 17 09:28:56 2006
From: shait at mindspring.com (Stephen Hait)
Date: Tue, 17 Jan 2006 10:28:56 -0500
Subject: [dba-SQLServer] Shrinking Log File
In-Reply-To: <7.0.0.16.0.20060117114044.01a7b9d0@dalyn.co.nz>
References: <7.0.0.16.0.20060116091933.00f510f0@dalyn.co.nz>
	<7.0.0.16.0.20060116163411.01abaeb0@dalyn.co.nz>
	<bb9d2d1e0601160519i6ff08f49h7f7648f04975f177@mail.gmail.com>
	<7.0.0.16.0.20060117114044.01a7b9d0@dalyn.co.nz>
Message-ID: <bb9d2d1e0601170728y181dbfc9wa78928fae6863a2f@mail.gmail.com>

I don't know why you have that situation. Do you actually need the log files
for anything? If not and you need to restore the associated data files,
couldn't you just get rid of them after the restore?

Stephen

On 1/16/06, David Emerson <newsgrps at dalyn.co.nz> wrote:
>
> Thanks Stephen.  That solved my immediate problem.
>
> Now my problem is that the files backed up from the end of last year
> are restoring fine with transaction logs in the size
> expected.  However, when I try to restore a back up file from this
> year (I have 2 from 2 different databases) the transaction log is way
> out of proportion to the actual size used (eg 13779MB in size with
> 113MB space used).  The original files on the server are closer to
> what I would expect them to be but for some reason the backups are
> not restoring well.
>
> Any thoughts on what went wrong.
>
> David
>
>


From dwaters at usinternet.com  Tue Jan 17 09:32:20 2006
From: dwaters at usinternet.com (Dan Waters)
Date: Tue, 17 Jan 2006 09:32:20 -0600
Subject: [dba-SQLServer] Properties window
In-Reply-To: <24362088.1137510016175.JavaMail.root@sniper21>
Message-ID: <001001c61b7b$35485ce0$0200a8c0@danwaters>

Hi Susan,

Yes - mine are grayed out as well.  But I looked at those properties and
realized that the ones on this list are 'stable' properties anyway - not
stuff that needs changing.

In the left pane of the properties window you can select Extended
Properties.  Those can be changed, and are probably what you're looking for.

And, it looks as though you can add properties that you want.

Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: Tuesday, January 17, 2006 8:58 AM
To: SQLList
Subject: [dba-SQLServer] Properties window

All of the Properties window for tables in Express are grayed out -- for
every table, period. Could someone check theirs for me? 
 
Just a right-click on the table and choose Properties. 
 
Susan H. 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From harkinsss at bellsouth.net  Tue Jan 17 09:56:26 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Tue, 17 Jan 2006 10:56:26 -0500
Subject: [dba-SQLServer] Properties window
In-Reply-To: <001001c61b7b$35485ce0$0200a8c0@danwaters>
Message-ID: <002501c61b7e$934d8c40$d2b3d6d1@SUSANONE>

 I'm trying to change the filegroup for a table, I should be able to do that
-- but that window's the only place I can find the Filegroup property. 

Susan H. 

Hi Susan,

Yes - mine are grayed out as well.  But I looked at those properties and
realized that the ones on this list are 'stable' properties anyway - not
stuff that needs changing.

In the left pane of the properties window you can select Extended
Properties.  Those can be changed, and are probably what you're looking for.

And, it looks as though you can add properties that you want.




From dwaters at usinternet.com  Tue Jan 17 10:41:00 2006
From: dwaters at usinternet.com (Dan Waters)
Date: Tue, 17 Jan 2006 10:41:00 -0600
Subject: [dba-SQLServer] Properties window
In-Reply-To: <1724961.1137513775363.JavaMail.root@sniper20>
Message-ID: <000001c61b84$cceb3f00$0200a8c0@danwaters>

Well - I'm so new to SQL Server that I don't know what a filegroup is for!

Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: Tuesday, January 17, 2006 9:56 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Properties window

 I'm trying to change the filegroup for a table, I should be able to do that
-- but that window's the only place I can find the Filegroup property. 

Susan H. 

Hi Susan,

Yes - mine are grayed out as well.  But I looked at those properties and
realized that the ones on this list are 'stable' properties anyway - not
stuff that needs changing.

In the left pane of the properties window you can select Extended
Properties.  Those can be changed, and are probably what you're looking for.

And, it looks as though you can add properties that you want.


_______________________________________________
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  Tue Jan 17 10:45:56 2006
From: mwp.reid at qub.ac.uk (Martin Reid)
Date: Tue, 17 Jan 2006 16:45:56 -0000
Subject: [dba-SQLServer] Properties window
References: <000001c61b84$cceb3f00$0200a8c0@danwaters>
Message-ID: <002001c61b85$7d07c7a0$9111758f@aine>

Check the properties of the database itself as opposed to the table.

Martin


----- Original Message ----- 
From: "Dan Waters" <dwaters at usinternet.com>
To: <dba-sqlserver at databaseadvisors.com>
Sent: Tuesday, January 17, 2006 4:41 PM
Subject: Re: [dba-SQLServer] Properties window


> Well - I'm so new to SQL Server that I don't know what a filegroup is for!
>
> Dan
>
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
> Harkins
> Sent: Tuesday, January 17, 2006 9:56 AM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] Properties window
>
> I'm trying to change the filegroup for a table, I should be able to do 
> that
> -- but that window's the only place I can find the Filegroup property.
>
> Susan H.
>
> Hi Susan,
>
> Yes - mine are grayed out as well.  But I looked at those properties and
> realized that the ones on this list are 'stable' properties anyway - not
> stuff that needs changing.
>
> In the left pane of the properties window you can select Extended
> Properties.  Those can be changed, and are probably what you're looking 
> for.
>
> And, it looks as though you can add properties that you want.
>
>
> _______________________________________________
> 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 martyconnelly at shaw.ca  Tue Jan 17 13:53:42 2006
From: martyconnelly at shaw.ca (MartyConnelly)
Date: Tue, 17 Jan 2006 11:53:42 -0800
Subject: [dba-SQLServer] Free SQL Server 2005 Development Training from
	Microsoft next week
References: <000001c61b84$cceb3f00$0200a8c0@danwaters>
	<002001c61b85$7d07c7a0$9111758f@aine>
Message-ID: <43CD4B46.5010902@shaw.ca>

Free SQL Server 2005 Development Training 
<http://go.microsoft.com/?linkid=4405931>
January 23 and 24, 11:00 A.M. - 3:00 P.M. or 4:00 P.M. - 8:00 P.M. 
Eastern time Microsoft and HP have teamed up to bring you an intensive, 
8-hour class to update your database development skills to SQL Server 
2005. This session teaches the skills necessary to design, build, query 
and develop enterprise SQL Server 2005 databases and servers.

-- 
Marty Connelly
Victoria, B.C.
Canada





From newsgrps at dalyn.co.nz  Tue Jan 17 16:12:46 2006
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Wed, 18 Jan 2006 11:12:46 +1300
Subject: [dba-SQLServer] Shrinking Log File
In-Reply-To: <bb9d2d1e0601170728y181dbfc9wa78928fae6863a2f@mail.gmail.co
 m>
References: <7.0.0.16.0.20060116091933.00f510f0@dalyn.co.nz>
	<7.0.0.16.0.20060116163411.01abaeb0@dalyn.co.nz>
	<bb9d2d1e0601160519i6ff08f49h7f7648f04975f177@mail.gmail.com>
	<7.0.0.16.0.20060117114044.01a7b9d0@dalyn.co.nz>
	<bb9d2d1e0601170728y181dbfc9wa78928fae6863a2f@mail.gmail.com>
Message-ID: <7.0.0.16.0.20060118111042.01a8e108@dalyn.co.nz>

I can (and did thanks to your help).  However, because they are 14GB 
in size I need to make sure I have that much spare space on my hard 
drive!  Also the fact that there is so much wasted space in the file 
(and I can't shrink it) is a cause for concern.  What else is waiting 
to jump out and bite me?

David

At 18/01/2006, you wrote:
>I don't know why you have that situation. Do you actually need the log files
>for anything? If not and you need to restore the associated data files,
>couldn't you just get rid of them after the restore?
>
>Stephen
>
>On 1/16/06, David Emerson <newsgrps at dalyn.co.nz> wrote:
> >
> > Thanks Stephen.  That solved my immediate problem.
> >
> > Now my problem is that the files backed up from the end of last year
> > are restoring fine with transaction logs in the size
> > expected.  However, when I try to restore a back up file from this
> > year (I have 2 from 2 different databases) the transaction log is way
> > out of proportion to the actual size used (eg 13779MB in size with
> > 113MB space used).  The original files on the server are closer to
> > what I would expect them to be but for some reason the backups are
> > not restoring well.
> >
> > Any thoughts on what went wrong.
> >
> > David
> >
> >
>_______________________________________________
>dba-SQLServer mailing list
>dba-SQLServer at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
>http://www.databaseadvisors.com



From shait at mindspring.com  Tue Jan 17 17:03:59 2006
From: shait at mindspring.com (Stephen Hait)
Date: Tue, 17 Jan 2006 18:03:59 -0500
Subject: [dba-SQLServer] Shrinking Log File
In-Reply-To: <7.0.0.16.0.20060118111042.01a8e108@dalyn.co.nz>
References: <7.0.0.16.0.20060116091933.00f510f0@dalyn.co.nz>
	<7.0.0.16.0.20060116163411.01abaeb0@dalyn.co.nz>
	<bb9d2d1e0601160519i6ff08f49h7f7648f04975f177@mail.gmail.com>
	<7.0.0.16.0.20060117114044.01a7b9d0@dalyn.co.nz>
	<bb9d2d1e0601170728y181dbfc9wa78928fae6863a2f@mail.gmail.com>
	<7.0.0.16.0.20060118111042.01a8e108@dalyn.co.nz>
Message-ID: <bb9d2d1e0601171503o28f2f674v40f9986633808295@mail.gmail.com>

Are your log files growing astronomically after you restore and then delete
the logs? If so, see if you can determine what is causing the rapid growth.
A large number of table inserts or updates can cause log files to bloat so
if this is a frequent occurence, you should try to shrink the logs after
these operations.

Other than that, I'm not really sure.

Regards,
Stephen

On 1/17/06, David Emerson <newsgrps at dalyn.co.nz> wrote:
>
> I can (and did thanks to your help).  However, because they are 14GB
> in size I need to make sure I have that much spare space on my hard
> drive!  Also the fact that there is so much wasted space in the file
> (and I can't shrink it) is a cause for concern.  What else is waiting
> to jump out and bite me?
>
> David
>
> At 18/01/2006, you wrote:
> >I don't know why you have that situation. Do you actually need the log
> files
> >for anything? If not and you need to restore the associated data files,
> >couldn't you just get rid of them after the restore?
> >
> >Stephen
> >
> >On 1/16/06, David Emerson <newsgrps at dalyn.co.nz> wrote:
> > >
> > > Thanks Stephen.  That solved my immediate problem.
> > >
> > > Now my problem is that the files backed up from the end of last year
> > > are restoring fine with transaction logs in the size
> > > expected.  However, when I try to restore a back up file from this
> > > year (I have 2 from 2 different databases) the transaction log is way
> > > out of proportion to the actual size used (eg 13779MB in size with
> > > 113MB space used).  The original files on the server are closer to
> > > what I would expect them to be but for some reason the backups are
> > > not restoring well.
> > >
> > > Any thoughts on what went wrong.
> > >
> > > 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 newsgrps at dalyn.co.nz  Tue Jan 17 17:25:17 2006
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Wed, 18 Jan 2006 12:25:17 +1300
Subject: [dba-SQLServer] Shrinking Log File
In-Reply-To: <bb9d2d1e0601171503o28f2f674v40f9986633808295@mail.gmail.co
 m>
References: <7.0.0.16.0.20060116091933.00f510f0@dalyn.co.nz>
	<7.0.0.16.0.20060116163411.01abaeb0@dalyn.co.nz>
	<bb9d2d1e0601160519i6ff08f49h7f7648f04975f177@mail.gmail.com>
	<7.0.0.16.0.20060117114044.01a7b9d0@dalyn.co.nz>
	<bb9d2d1e0601170728y181dbfc9wa78928fae6863a2f@mail.gmail.com>
	<7.0.0.16.0.20060118111042.01a8e108@dalyn.co.nz>
	<bb9d2d1e0601171503o28f2f674v40f9986633808295@mail.gmail.com>
Message-ID: <7.0.0.16.0.20060118122224.01aa8bc0@dalyn.co.nz>

It is the restored files that are so large - ie they are that large 
when they are being restored.  Something funny seems to be happening 
between when they are backed up and when they are restored.  The size 
seems to be empty space because the shrink process indicated that 
there is 95% empty space!

David

At 18/01/2006, you wrote:
>Are your log files growing astronomically after you restore and then delete
>the logs? If so, see if you can determine what is causing the rapid growth.
>A large number of table inserts or updates can cause log files to bloat so
>if this is a frequent occurence, you should try to shrink the logs after
>these operations.
>
>Other than that, I'm not really sure.
>
>Regards,
>Stephen
>
>On 1/17/06, David Emerson <newsgrps at dalyn.co.nz> wrote:
> >
> > I can (and did thanks to your help).  However, because they are 14GB
> > in size I need to make sure I have that much spare space on my hard
> > drive!  Also the fact that there is so much wasted space in the file
> > (and I can't shrink it) is a cause for concern.  What else is waiting
> > to jump out and bite me?
> >
> > David
> >
> > At 18/01/2006, you wrote:
> > >I don't know why you have that situation. Do you actually need the log
> > files
> > >for anything? If not and you need to restore the associated data files,
> > >couldn't you just get rid of them after the restore?
> > >
> > >Stephen
> > >
> > >On 1/16/06, David Emerson <newsgrps at dalyn.co.nz> wrote:
> > > >
> > > > Thanks Stephen.  That solved my immediate problem.
> > > >
> > > > Now my problem is that the files backed up from the end of last year
> > > > are restoring fine with transaction logs in the size
> > > > expected.  However, when I try to restore a back up file from this
> > > > year (I have 2 from 2 different databases) the transaction log is way
> > > > out of proportion to the actual size used (eg 13779MB in size with
> > > > 113MB space used).  The original files on the server are closer to
> > > > what I would expect them to be but for some reason the backups are
> > > > not restoring well.
> > > >
> > > > Any thoughts on what went wrong.
> > > >
> > > > David



From KP at sdsonline.net  Tue Jan 17 17:27:09 2006
From: KP at sdsonline.net (Kath Pelletti)
Date: Wed, 18 Jan 2006 10:27:09 +1100
Subject: [dba-SQLServer] Buy sql server 2005
References: <000401c61b04$ed1fef30$017ba8c0@xpserver>
Message-ID: <005101c61bbd$8a2383b0$6501a8c0@user>

Thanks Jim.

Kath
  ----- Original Message ----- 
  From: Jim Lawrence 
  To: dba-sqlserver at databaseadvisors.com 
  Sent: Tuesday, January 17, 2006 12:25 PM
  Subject: Re: [dba-SQLServer] Buy sql server 2005


  Hi Kath:

  It should be everything you need. The only package above this one is the
  'enterprise' version and as I understand it, the Enterprise version has the
  ability to use more memory, CPUs and hard drive space. 

  HTH
  Jim

  -----Original Message-----
  From: dba-sqlserver-bounces at databaseadvisors.com
  [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Kath
  Pelletti
  Sent: January 16, 2006 4:32 PM
  To: dba-sqlserver at databaseadvisors.com
  Subject: [dba-SQLServer] Buy sql server 2005

  Hi everyone - happy new year.

  I need to order a copy of Sql Server 2005 for a new project I need to write.
  I've never used / bought it before. Can someone point me to the version I
  need?

  I notice that there is a MS Sql Server 2005 Developer edition (only $85
  AUS). Will that give me everything I need? And can you tell me which version
  my client will need so that I can help them to work out costs ?

  Thanks all.

  Also, can I assume that Visual Studio 2005 Professional Edition includes
  everything I need to code vb.net and asp.net apps? 

  Thanks. 

  Kath
  _______________________________________________
  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 djkr at msn.com  Tue Jan 17 17:49:27 2006
From: djkr at msn.com (DJK(John) Robinson)
Date: Tue, 17 Jan 2006 23:49:27 -0000
Subject: [dba-SQLServer] Free SQL Server 2005 Development Training
	fromMicrosoft next week
In-Reply-To: <43CD4B46.5010902@shaw.ca>
Message-ID: <BAY106-DAV142B1EECB611DB4D9DB1E1D21A0@phx.gbl>

"0 places available" for those now, and for the ASP.NET ones in February
too.
John


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of
MartyConnelly
Sent: 17 January 2006 19:54
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Free SQL Server 2005 Development Training
fromMicrosoft next week


Free SQL Server 2005 Development Training 
<http://go.microsoft.com/?linkid=4405931>
January 23 and 24, 11:00 A.M. - 3:00 P.M. or 4:00 P.M. - 8:00 P.M. 
Eastern time Microsoft and HP have teamed up to bring you an intensive, 
8-hour class to update your database development skills to SQL Server 
2005. This session teaches the skills necessary to design, build, query 
and develop enterprise SQL Server 2005 databases and servers.

-- 
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 harkinsss at bellsouth.net  Tue Jan 17 17:49:51 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Tue, 17 Jan 2006 18:49:51 -0500
Subject: [dba-SQLServer] Properties window
In-Reply-To: <002001c61b85$7d07c7a0$9111758f@aine>
Message-ID: <000601c61bc0$b5fbd9d0$c7b3d6d1@SUSANONE>

Martin, those are grayed out too. 

I can see the property I need in the table's general page -- just can't do
anything with it, or any of them for that matter. It isn't available on any
of the other pages. 

Susan H. 

Check the properties of the database itself as opposed to the table.

Martin




From jwcolby at ColbyConsulting.com  Wed Jan 18 22:50:10 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Wed, 18 Jan 2006 23:50:10 -0500
Subject: [dba-SQLServer] SQL Server express
Message-ID: <001a01c61cb3$d4617bc0$647aa8c0@ColbyM6805>

I stumbled across this (via the Database Advisor's website)

http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx

It has a good discussion of how to get SQL Server express running, the
browser service running, and all set to go for running the upsize wizard in
order to use SQL Server Express from Access.

John W. Colby
www.ColbyConsulting.com 




From martyconnelly at shaw.ca  Thu Jan 19 11:28:17 2006
From: martyconnelly at shaw.ca (MartyConnelly)
Date: Thu, 19 Jan 2006 09:28:17 -0800
Subject: [dba-SQLServer] SQL Server express
References: <001a01c61cb3$d4617bc0$647aa8c0@ColbyM6805>
Message-ID: <43CFCC31.8040100@shaw.ca>

Just remember some of that applies to the original Beta , there was 
another Beta then the released product


John Colby wrote:

>I stumbled across this (via the Database Advisor's website)
>
>http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
>
>It has a good discussion of how to get SQL Server express running, the
>browser service running, and all set to go for running the upsize wizard in
>order to use SQL Server Express from Access.
>
>John W. Colby
>www.ColbyConsulting.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 jwcolby at ColbyConsulting.com  Thu Jan 19 11:35:43 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Thu, 19 Jan 2006 12:35:43 -0500
Subject: [dba-SQLServer] SQL Server express
In-Reply-To: <43CFCC31.8040100@shaw.ca>
Message-ID: <005201c61d1e$c699f240$647aa8c0@ColbyM6805>

I used this info to get SQL Server express working with Access to do an
upsize.  The key was starting the "browser service" for SQL Server Express
which apparently publishes the name of the SQL Server instances. Once I did
that, the upsize went flawlessly.

John W. Colby
www.ColbyConsulting.com 


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of
MartyConnelly
Sent: Thursday, January 19, 2006 12:28 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL Server express

Just remember some of that applies to the original Beta , there was another
Beta then the released product


John Colby wrote:

>I stumbled across this (via the Database Advisor's website)
>
>http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
>
>It has a good discussion of how to get SQL Server express running, the
>browser service running, and all set to go for running the upsize wizard in
>order to use SQL Server Express from Access.
>
>John W. Colby
>www.ColbyConsulting.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



_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From harkinsss at bellsouth.net  Thu Jan 19 11:56:11 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Thu, 19 Jan 2006 12:56:11 -0500
Subject: [dba-SQLServer] SQL Server express
In-Reply-To: <43CFCC31.8040100@shaw.ca>
Message-ID: <000301c61d21$a47e1350$d7b3d6d1@SUSANONE>

And we're expecting at least one more release. I have to tell you -- the
Express version has been the biggest pia where requirements and installation
are concerned. I've never had a beta cause so much disruption and work. :( 

Susan H. 

Just remember some of that applies to the original Beta , there was another
Beta then the released product





From darrend at nimble.com.au  Thu Jan 19 18:16:52 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Fri, 20 Jan 2006 11:16:52 +1100
Subject: [dba-SQLServer] SQL - What's a null in Reporting Services
Message-ID: <20060120001658.ZCDY15112.omta03ps.mx.bigpond.com@DENZILLAP>

Hello all

In Access to test for null and replace it with x I would do something like

Iif(isnull([SomeField]),"NothingThere","SomethingThere")

When I try this in a text box in reporting services it says

Replace Null with System.DBNull

So I did and now get the error...

dBNull is a type in system and cannot be used as an expression

<Sigh>

Anyone know what the correct syntax should be to test for Null and put in my own
value if true and 

Leave the FieldValue if not true?

Many thanks

Darren



From ebarro at verizon.net  Thu Jan 19 18:33:06 2006
From: ebarro at verizon.net (Eric Barro)
Date: Thu, 19 Jan 2006 16:33:06 -0800
Subject: [dba-SQLServer] SQL - What's a null in Reporting Services
In-Reply-To: <20060120001658.ZCDY15112.omta03ps.mx.bigpond.com@DENZILLAP>
Message-ID: <0ITD006PE876MLBA@vms048.mailsrvcs.net>

If IsDBNull 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: Thursday, January 19, 2006 4:17 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] SQL - What's a null in Reporting Services

Hello all

In Access to test for null and replace it with x I would do something like

Iif(isnull([SomeField]),"NothingThere","SomethingThere")

When I try this in a text box in reporting services it says

Replace Null with System.DBNull

So I did and now get the error...

dBNull is a type in system and cannot be used as an expression

<Sigh>

Anyone know what the correct syntax should be to test for Null and put in my
own value if true and 

Leave the FieldValue if not true?

Many thanks

Darren

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


__________ NOD32 1.1372 (20060119) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com




From darrend at nimble.com.au  Thu Jan 19 20:40:56 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Fri, 20 Jan 2006 13:40:56 +1100
Subject: [dba-SQLServer] SQL - What's a null in Reporting Services)
In-Reply-To: <000001c61d58$1589fc90$92b3d6d1@SUSANONE>
Message-ID: <20060120024111.BXRO17345.omta04ps.mx.bigpond.com@DENZILLAP>

Hi Susan and Hi Eric
Many thanks
I used Coalesce in the underlying SQL

Many thanks

DD
 



-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: Thursday, January 19, 2006 7:17 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] SQL - What's a null in Reporting Services

Hello all

In Access to test for null and replace it with x I would do something like

Iif(isnull([SomeField]),"NothingThere","SomethingThere")

When I try this in a text box in reporting services it says

Replace Null with System.DBNull

So I did and now get the error...

dBNull is a type in system and cannot be used as an expression

<Sigh>

Anyone know what the correct syntax should be to test for Null and put in my own
value if true and 

Leave the FieldValue if not true?

Many thanks

Darren

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 1/14/2006
 



From ebarro at verizon.net  Thu Jan 19 21:05:32 2006
From: ebarro at verizon.net (Eric Barro)
Date: Thu, 19 Jan 2006 19:05:32 -0800
Subject: [dba-SQLServer] SQL - What's a null in Reporting Services)
In-Reply-To: <20060120024111.BXRO17345.omta04ps.mx.bigpond.com@DENZILLAP>
Message-ID: <0ITD0060GF99C6I8@vms048.mailsrvcs.net>

ISNULL(x, y) is more efficient than COALESCE. ISNULL returns x if it's not
null otherwise it returns y. Use COALESCE if you have more than 1 value to
evaluate. It returns the first non-null value. 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: Thursday, January 19, 2006 6:41 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL - What's a null in Reporting Services)

Hi Susan and Hi Eric
Many thanks
I used Coalesce in the underlying SQL

Many thanks

DD
 



-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: Thursday, January 19, 2006 7:17 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] SQL - What's a null in Reporting Services

Hello all

In Access to test for null and replace it with x I would do something like

Iif(isnull([SomeField]),"NothingThere","SomethingThere")

When I try this in a text box in reporting services it says

Replace Null with System.DBNull

So I did and now get the error...

dBNull is a type in system and cannot be used as an expression

<Sigh>

Anyone know what the correct syntax should be to test for Null and put in my
own value if true and 

Leave the FieldValue if not true?

Many thanks

Darren

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 1/14/2006
 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


__________ NOD32 1.1372 (20060119) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com




From jwcolby at ColbyConsulting.com  Thu Jan 19 22:23:28 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Thu, 19 Jan 2006 23:23:28 -0500
Subject: [dba-SQLServer] Preparing for upsizing
Message-ID: <00aa01c61d79$440a1e80$647aa8c0@ColbyM6805>

I am preparing for upsizing a client's access database.  In order to do this
I needed to search all the objects looking for SQL statements and save them
as saved queries.  In order to do this with forms I created the following
two functions:

FindSQL opens each form in the database in design view, then passes the name
of the form and the form's RecordSource off to a function BldSavedQuery.  It
then looks for all controls in the form's control collection looking for
combos and list boxes, and does the same with them.

BldSavedQuery looks for issues like nothing in the SQL statement passed in,
the "QryName" already being the name of a query or table, and if neither of
those conditions exist, then it tries to build a named query def.  If it
succeeds (the SQL passed in is valid and the name passed in is not already a
saved query) it creates a saved query and passes the name back to FindSQL
which then stores the saved query name back in place of the SQL statement.
When all processing is finished, the form is then saved and closed.

It works reasonably well.  The only things found so far are delimited lists
instead of SQL statements and what appear to be saved query names where the
saved query was deleted.  Only about 17 of those, all but one are delimited
lists.  It took me ~ 2 hours to write / debug this code and saved me who
knows how much time manually hunting for these things.

I now have to do the same thing for reports, though there are so few I might
just do them manually.

Function BldSavedQuery(strQryName As String, strSQL As String) As String
On Error GoTo Err_BldSavedQuery
Dim tdf As DAO.TableDef
Dim qdf As DAO.QueryDef
Dim qdfs As DAO.QueryDefs
Dim db As DAO.Database
Dim lstrQryName As String
    
    '
    'This object has nothing in the rowsource/recordsource (probably an
unbound form)
    '
    If strSQL = "" Then
        BldSavedQuery = ""
        GoTo Exit_BldSavedQuery
    End If
    Set db = CurrentDb
    '
    'Check to see if the strsql is the name of a table
    '
    On Error Resume Next
    Set tdf = db.TableDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
    '
    'Check if the strSQL is a query name
    '
    Set qdf = db.QueryDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
On Error GoTo Err_BldSavedQuery
    
    lstrQryName = "q" & strQryName
    Set qdfs = db.QueryDefs
    Set qdf = New QueryDef
    With qdf
        .SQL = strSQL
        .Name = lstrQryName
    End With
    qdfs.Append qdf
    qdfs.Refresh
    BldSavedQuery = qdf.Name
Exit_BldSavedQuery:
On Error Resume Next
    If Not (qdf Is Nothing) Then qdf.Close: Set qdf = Nothing
    Set qdfs = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing
Exit Function
Err_BldSavedQuery:
    Select Case Err
    Case 3012   'Query already exists
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " already exists, but this
control has a SQL statement in the rowsource"
        Resume Exit_BldSavedQuery
    Case 3129   'Not an SQL statement - mostly delimited lists or deleted
saved query names
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " not a sql statement in the
rowsource but not a saved query or table either"
        Debug.Print vbTab & "Rowsource: " & strSQL
        Resume Exit_BldSavedQuery
    Case Else
        MsgBox Err.Description, , "Error in Function
basFindSQL.BldSavedQuery"
        Resume Exit_BldSavedQuery
    End Select
    Resume 0    '.FOR TROUBLESHOOTING
End Function
'
'This module will find all sql statements in objects such as forms, combos
and list boxes
'and save them as saved queries in the name format:
'
'qfrmName
'qfrmname-CboName
'qfrmName-LstName
'
Function FindSQL()
On Error GoTo Err_FindSQL
Dim db As DAO.Database
Dim doc As DAO.Document
Dim frm As Form
Dim ctl As Control
Dim strQryName As String
    Set db = CurrentDb
    For Each doc In db.Containers(2).Documents
        DoCmd.OpenForm doc.Name, acDesign
        Set frm = Forms(doc.Name)
        strQryName = BldSavedQuery(frm.Name, frm.RecordSource)
        If Len(strQryName) > 0 Then
            frm.RecordSource = strQryName
        End If
        For Each ctl In frm.Controls
            Select Case ctl.ControlType
            Case acComboBox, acListBox
                strQryName = BldSavedQuery(frm.Name & "-" & ctl.Name,
ctl.RowSource)
                If Len(strQryName) > 0 Then
                    ctl.RowSource = strQryName
                End If
            Case Else
            End Select
            
        Next ctl
        DoCmd.Close acForm, doc.Name, acSaveYes
    Next doc
Exit_FindSQL:
On Error Resume Next
    If Not (frm Is Nothing) Then frm.Close: Set frm = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing
Exit Function
Err_FindSQL:
        MsgBox Err.Description, , "Error in Function basFindSQL.FindSQL"
        Resume Exit_FindSQL
    Resume 0    '.FOR TROUBLESHOOTING
End Function

John W. Colby
www.ColbyConsulting.com 




From dwaters at usinternet.com  Fri Jan 20 09:09:54 2006
From: dwaters at usinternet.com (Dan Waters)
Date: Fri, 20 Jan 2006 09:09:54 -0600
Subject: [dba-SQLServer] Preparing for upsizing
In-Reply-To: <14268053.1137731208602.JavaMail.root@sniper17>
Message-ID: <000701c61dd3$91d1f980$0200a8c0@danwaters>

John,

There's nothing quite like making your own tools!

Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: Thursday, January 19, 2006 10:23 PM
To: 'Access Developers discussion and problem solving';
dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Preparing for upsizing

I am preparing for upsizing a client's access database.  In order to do this
I needed to search all the objects looking for SQL statements and save them
as saved queries.  In order to do this with forms I created the following
two functions:

FindSQL opens each form in the database in design view, then passes the name
of the form and the form's RecordSource off to a function BldSavedQuery.  It
then looks for all controls in the form's control collection looking for
combos and list boxes, and does the same with them.

BldSavedQuery looks for issues like nothing in the SQL statement passed in,
the "QryName" already being the name of a query or table, and if neither of
those conditions exist, then it tries to build a named query def.  If it
succeeds (the SQL passed in is valid and the name passed in is not already a
saved query) it creates a saved query and passes the name back to FindSQL
which then stores the saved query name back in place of the SQL statement.
When all processing is finished, the form is then saved and closed.

It works reasonably well.  The only things found so far are delimited lists
instead of SQL statements and what appear to be saved query names where the
saved query was deleted.  Only about 17 of those, all but one are delimited
lists.  It took me ~ 2 hours to write / debug this code and saved me who
knows how much time manually hunting for these things.

I now have to do the same thing for reports, though there are so few I might
just do them manually.

Function BldSavedQuery(strQryName As String, strSQL As String) As String
On Error GoTo Err_BldSavedQuery
Dim tdf As DAO.TableDef
Dim qdf As DAO.QueryDef
Dim qdfs As DAO.QueryDefs
Dim db As DAO.Database
Dim lstrQryName As String
    
    '
    'This object has nothing in the rowsource/recordsource (probably an
unbound form)
    '
    If strSQL = "" Then
        BldSavedQuery = ""
        GoTo Exit_BldSavedQuery
    End If
    Set db = CurrentDb
    '
    'Check to see if the strsql is the name of a table
    '
    On Error Resume Next
    Set tdf = db.TableDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
    '
    'Check if the strSQL is a query name
    '
    Set qdf = db.QueryDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
On Error GoTo Err_BldSavedQuery
    
    lstrQryName = "q" & strQryName
    Set qdfs = db.QueryDefs
    Set qdf = New QueryDef
    With qdf
        .SQL = strSQL
        .Name = lstrQryName
    End With
    qdfs.Append qdf
    qdfs.Refresh
    BldSavedQuery = qdf.Name
Exit_BldSavedQuery:
On Error Resume Next
    If Not (qdf Is Nothing) Then qdf.Close: Set qdf = Nothing
    Set qdfs = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing
Exit Function
Err_BldSavedQuery:
    Select Case Err
    Case 3012   'Query already exists
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " already exists, but this
control has a SQL statement in the rowsource"
        Resume Exit_BldSavedQuery
    Case 3129   'Not an SQL statement - mostly delimited lists or deleted
saved query names
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " not a sql statement in the
rowsource but not a saved query or table either"
        Debug.Print vbTab & "Rowsource: " & strSQL
        Resume Exit_BldSavedQuery
    Case Else
        MsgBox Err.Description, , "Error in Function
basFindSQL.BldSavedQuery"
        Resume Exit_BldSavedQuery
    End Select
    Resume 0    '.FOR TROUBLESHOOTING
End Function
'
'This module will find all sql statements in objects such as forms, combos
and list boxes
'and save them as saved queries in the name format:
'
'qfrmName
'qfrmname-CboName
'qfrmName-LstName
'
Function FindSQL()
On Error GoTo Err_FindSQL
Dim db As DAO.Database
Dim doc As DAO.Document
Dim frm As Form
Dim ctl As Control
Dim strQryName As String
    Set db = CurrentDb
    For Each doc In db.Containers(2).Documents
        DoCmd.OpenForm doc.Name, acDesign
        Set frm = Forms(doc.Name)
        strQryName = BldSavedQuery(frm.Name, frm.RecordSource)
        If Len(strQryName) > 0 Then
            frm.RecordSource = strQryName
        End If
        For Each ctl In frm.Controls
            Select Case ctl.ControlType
            Case acComboBox, acListBox
                strQryName = BldSavedQuery(frm.Name & "-" & ctl.Name,
ctl.RowSource)
                If Len(strQryName) > 0 Then
                    ctl.RowSource = strQryName
                End If
            Case Else
            End Select
            
        Next ctl
        DoCmd.Close acForm, doc.Name, acSaveYes
    Next doc
Exit_FindSQL:
On Error Resume Next
    If Not (frm Is Nothing) Then frm.Close: Set frm = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing
Exit Function
Err_FindSQL:
        MsgBox Err.Description, , "Error in Function basFindSQL.FindSQL"
        Resume Exit_FindSQL
    Resume 0    '.FOR TROUBLESHOOTING
End Function

John W. Colby
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  Fri Jan 20 18:08:02 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Fri, 20 Jan 2006 19:08:02 -0500
Subject: [dba-SQLServer] Upsize wizard and named queries
Message-ID: <00fc01c61e1e$bf4bb5e0$647aa8c0@ColbyM6805>

I thought that someone said I needed to pull all SQL out of properties and
create named queries so that the upsize wizard could upsize them.  I did so
but I am not seeing any indication that the saved queries are being upsized?
Are they supposed to?  If so, what will happen?  Will the queries be deleted
from the query tab?  What happens to the object properties
(form/combo/list)?  Or is this only for ADPs?  If it is only for ADPs how do
I manually upsize the queries and then how do I replace the queries in the
object properties with the SPs or whatever the equivalent is in SQL Server.

Confused in CT

John W. Colby
www.ColbyConsulting.com 




From harkinsss at bellsouth.net  Fri Jan 20 18:50:25 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Fri, 20 Jan 2006 19:50:25 -0500
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <00fc01c61e1e$bf4bb5e0$647aa8c0@ColbyM6805>
Message-ID: <001f01c61e24$bfcd0c20$9eb3d6d1@SUSANONE>

I thought that someone said I needed to pull all SQL out of properties and
create named queries so that the upsize wizard could upsize them.  I did so
but I am not seeing any indication that the saved queries are being upsized?

=======Not all queries will upsize correctly. If you have the book that
Martin and I did together, he mentions a number of problems you have to fix
before upsizing. I'd look up the page if I had a copy handy, but I don't
right this minute. If you don't have it, Martin or I could probably create a
short list of gotchas. 

Susan H. 



From jwcolby at ColbyConsulting.com  Fri Jan 20 21:41:11 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Fri, 20 Jan 2006 22:41:11 -0500
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <001f01c61e24$bfcd0c20$9eb3d6d1@SUSANONE>
Message-ID: <00fe01c61e3c$864ad500$647aa8c0@ColbyM6805>

Oh yea, I'm reading up on the "gotchas" and it looks like darned few of my
queries will upsize correctly.  It's interesting now because all of the
literature out there discusses upsizing to ADPs and now that is a dead end
road.  Luckily in this specific case the client is using 2002 so I can at
least do conversions one by one from queries to SPs, where the most effect
is gained.

Does anyone have any experience with how the performance compares between
jet with large recordsets and SQL Server "emulating" jet over ODBC
connections (linked tables)?  IOW, If I just upsize the tables and replace
the links to the MDB with links to SQL Server tables will the database take
a huge performance hit?  This specific db is a smallish (10 active users)
"call center" kind of database where users enter tiny little records re the
calls they place, but they do look at data about 150k people, divided by
state etc.  I think I could fairly rapidly upgrade the main form to use SPs
to pull just the small set of people data they need to work with which would
speed up that main form dramatically I think, even over JET.


John W. Colby
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: Friday, January 20, 2006 7:50 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Upsize wizard and named queries

I thought that someone said I needed to pull all SQL out of properties and
create named queries so that the upsize wizard could upsize them.  I did so
but I am not seeing any indication that the saved queries are being upsized?

=======Not all queries will upsize correctly. If you have the book that
Martin and I did together, he mentions a number of problems you have to fix
before upsizing. I'd look up the page if I had a copy handy, but I don't
right this minute. If you don't have it, Martin or I could probably create a
short list of gotchas. 

Susan H. 

_______________________________________________
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 Jan 21 00:37:12 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Fri, 20 Jan 2006 22:37:12 -0800
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <00fe01c61e3c$864ad500$647aa8c0@ColbyM6805>
Message-ID: <001201c61e55$1c843e40$017ba8c0@xpserver>

Hi John:

I have been working with ODBC and ADO-OLE connections for a number of years.
(almost 10.) IMHO with a SQL server as the BE and connecting with ODBC the
performance can be faster, doing UPDATE and DELETE but retrieving large
Recordsets should be avoided.... it can be very slow and even an MDB would
be faster.

IMHO do not waste your time and effort with ODBC. Go straight to ADO-OLE. It
is simpler to connect, to maintain, using its disconnected architecture is
much more stable and the performance is far superior.... With all/most of
the queries in SPs, the whole system will be really optimized.     

I have never had any luck with automated upsizing with queries and have
always had to do them manually. It would be best to assume that you will
have to manually build them all and go from there.

HTH
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: January 20, 2006 7:41 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Upsize wizard and named queries

Oh yea, I'm reading up on the "gotchas" and it looks like darned few of my
queries will upsize correctly.  It's interesting now because all of the
literature out there discusses upsizing to ADPs and now that is a dead end
road.  Luckily in this specific case the client is using 2002 so I can at
least do conversions one by one from queries to SPs, where the most effect
is gained.

Does anyone have any experience with how the performance compares between
jet with large recordsets and SQL Server "emulating" jet over ODBC
connections (linked tables)?  IOW, If I just upsize the tables and replace
the links to the MDB with links to SQL Server tables will the database take
a huge performance hit?  This specific db is a smallish (10 active users)
"call center" kind of database where users enter tiny little records re the
calls they place, but they do look at data about 150k people, divided by
state etc.  I think I could fairly rapidly upgrade the main form to use SPs
to pull just the small set of people data they need to work with which would
speed up that main form dramatically I think, even over JET.


John W. Colby
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: Friday, January 20, 2006 7:50 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Upsize wizard and named queries

I thought that someone said I needed to pull all SQL out of properties and
create named queries so that the upsize wizard could upsize them.  I did so
but I am not seeing any indication that the saved queries are being upsized?

=======Not all queries will upsize correctly. If you have the book that
Martin and I did together, he mentions a number of problems you have to fix
before upsizing. I'd look up the page if I had a copy handy, but I don't
right this minute. If you don't have it, Martin or I could probably create a
short list of gotchas. 

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



From mwp.reid at qub.ac.uk  Sat Jan 21 02:49:05 2006
From: mwp.reid at qub.ac.uk (mwp.reid at qub.ac.uk)
Date: Sat, 21 Jan 2006 08:49:05 -0000
Subject: [dba-SQLServer] Upsize wizard and named queries
Message-ID: <200601210848.k0L8mtV10355@databaseadvisors.com>

Jc

I did a large up size and odbc pulling large recordsets was way to slow. ADO and redid them all was the only way to go. Just changed everything to match. I was using 2003 as well which nade it easier. Also used upsizing pro and performance pro really worth getting as well for pre upsizing reports.

Each case is different of course.

Martin

-----Original Message-----
    From: "John Colby"<jwcolby at colbyconsulting.com>
    Sent: 1/21/06 12:08:02 AM
    To: "'Access Developers discussion and problem solving'"<accessd at databaseadvisors.com>, "dba-sqlserver at databaseadvisors.com"<dba-sqlserver at databaseadvisors.com>
    Subject: [dba-SQLServer] Upsize wizard and named queries
    
    I thought that someone said I needed to pull all SQL out of properties and
    create named queries so that the upsize wizard could upsize them.  I did so
    but I am not seeing any indication that the saved queries are being upsized?
    Are they supposed to?  If so, what will happen?  Will the queries be deleted
    from the query tab?  What happens to the object properties
    (form/combo/list)?  Or is this only for ADPs?  If it is only for ADPs how do
    I manually upsize the queries and then how do I replace the queries in the
    object properties with the SPs or whatever the equivalent is in SQL Server.
    
    Confused in CT
    
    John W. Colby
    www.ColbyConsulting.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  Sat Jan 21 02:49:05 2006
From: mwp.reid at qub.ac.uk (mwp.reid at qub.ac.uk)
Date: Sat, 21 Jan 2006 08:49:05 -0000
Subject: [dba-SQLServer] Upsize wizard and named queries
Message-ID: <200601210848.k0L8mtV10361@databaseadvisors.com>

John

I would try that. Just link the tables and see how it goes. 

How about local caching then update back to sql server. Static recordsets you could pull down locally then pass the updates back if it turns out go be slow. Its also possible to populate local tables in the mdb of lookup values etc from sql server to help with speed. 

martin


-----Original Message-----
    From: "John Colby"<jwcolby at colbyconsulting.com>
    Sent: 1/21/06 3:41:11 AM
    To: "dba-sqlserver at databaseadvisors.com"<dba-sqlserver at databaseadvisors.com>
    Subject: Re: [dba-SQLServer] Upsize wizard and named queries
    
    Oh yea, I'm reading up on the "gotchas" and it looks like darned few of my
    queries will upsize correctly.  It's interesting now because all of the
    literature out there discusses upsizing to ADPs and now that is a dead end
    road.  Luckily in this specific case the client is using 2002 so I can at
    least do conversions one by one from queries to SPs, where the most effect
    is gained.
    
    Does anyone have any experience with how the performance compares between
    jet with large recordsets and SQL Server "emulating" jet over ODBC
    connections (linked tables)?  IOW, If I just upsize the tables and replace
    the links to the MDB with links to SQL Server tables will the database take
    a huge performance hit?  This specific db is a smallish (10 active users)
    "call center" kind of database where users enter tiny little records re the
    calls they place, but they do look at data about 150k people, divided by
    state etc.  I think I could fairly rapidly upgrade the main form to use SPs
    to pull just the small set of people data they need to work with which would
    speed up that main form dramatically I think, even over JET.
    
    
    John W. Colby
    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: Friday, January 20, 2006 7:50 PM
    To: dba-sqlserver at databaseadvisors.com
    Subject: Re: [dba-SQLServer] Upsize wizard and named queries
    
    I thought that someone said I needed to pull all SQL out of properties and
    create named queries so that the upsize wizard could upsize them.  I did so
    but I am not seeing any indication that the saved queries are being upsized?
    
    =======Not all queries will upsize correctly. If you have the book that
    Martin and I did together, he mentions a number of problems you have to fix
    before upsizing. I'd look up the page if I had a copy handy, but I don't
    right this minute. If you don't have it, Martin or I could probably create a
    short list of gotchas. 
    
    Susan    

[Message truncated. Tap Edit->Mark for Download to get remaining portion.]



From harkinsss at bellsouth.net  Sat Jan 21 09:28:44 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Sat, 21 Jan 2006 10:28:44 -0500
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <001201c61e55$1c843e40$017ba8c0@xpserver>
Message-ID: <000c01c61e9f$675513a0$dfb3d6d1@SUSANONE>

 
IMHO do not waste your time and effort with ODBC. Go straight to ADO-OLE. It
is simpler to connect, to maintain, using its disconnected architecture is
much more stable and the performance is far superior.... With all/most of
the queries in SPs, the whole system will be really optimized.     

========And has the advantage of being readily connected/switched to any
number of products. I advise anyone working with mdbs to use ADO-OLE if
there's ANY possibility of foreign connections or upsizing. 

Susan H. 



From mikedorism at verizon.net  Sat Jan 21 10:11:44 2006
From: mikedorism at verizon.net (Mike & Doris Manning)
Date: Sat, 21 Jan 2006 11:11:44 -0500
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <001201c61e55$1c843e40$017ba8c0@xpserver>
Message-ID: <000001c61ea5$608e3f50$2f01a8c0@dorismanning>

John,

The biggest problem with connecting to SQL Server through Access is that
Access automatically limits the connection string packet size to 4096.  I
have yet to find any way to change that within Access.  This is one reason
why I've been slowly moving all my company's apps over to VB.Net.  There, I
can control the connection by changing the packet size to 32767 which is as
wide as it can go.

Doris Manning
mikedorism at verizon.net





From Erwin.Craps at ithelps.be  Mon Jan 23 03:11:56 2006
From: Erwin.Craps at ithelps.be (Erwin Craps - IT Helps)
Date: Mon, 23 Jan 2006 10:11:56 +0100
Subject: [dba-SQLServer] Preparing for upsizing
Message-ID: <46B976F2B698FF46A4FE7636509B22DF1B62C8@stekelbes.ithelps.local>


I was thinking about writing such a tool to, in order to upsize one of
my biggest database. I'm postponing this upsize already for a year or
two now, and I supose it will be not until after the summer holiday...


But I was considering to first store the SQL strings in a table , run a
grouping on it/analyse to minimize the number of queries and posibly to
improve them (manualy), and afterwards alter the forms/reports.

This to avoid to have 1 query per combo/listbox.

Erwin








-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Dan
Waters
Sent: Friday, January 20, 2006 4:10 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing

John,

There's nothing quite like making your own tools!

Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John
Colby
Sent: Thursday, January 19, 2006 10:23 PM
To: 'Access Developers discussion and problem solving';
dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Preparing for upsizing

I am preparing for upsizing a client's access database.  In order to do
this I needed to search all the objects looking for SQL statements and
save them as saved queries.  In order to do this with forms I created
the following two functions:

FindSQL opens each form in the database in design view, then passes the
name of the form and the form's RecordSource off to a function
BldSavedQuery.  It then looks for all controls in the form's control
collection looking for combos and list boxes, and does the same with
them.

BldSavedQuery looks for issues like nothing in the SQL statement passed
in, the "QryName" already being the name of a query or table, and if
neither of those conditions exist, then it tries to build a named query
def.  If it succeeds (the SQL passed in is valid and the name passed in
is not already a saved query) it creates a saved query and passes the
name back to FindSQL which then stores the saved query name back in
place of the SQL statement.
When all processing is finished, the form is then saved and closed.

It works reasonably well.  The only things found so far are delimited
lists instead of SQL statements and what appear to be saved query names
where the saved query was deleted.  Only about 17 of those, all but one
are delimited lists.  It took me ~ 2 hours to write / debug this code
and saved me who knows how much time manually hunting for these things.

I now have to do the same thing for reports, though there are so few I
might just do them manually.

Function BldSavedQuery(strQryName As String, strSQL As String) As String
On Error GoTo Err_BldSavedQuery Dim tdf As DAO.TableDef Dim qdf As
DAO.QueryDef Dim qdfs As DAO.QueryDefs Dim db As DAO.Database Dim
lstrQryName As String
    
    '
    'This object has nothing in the rowsource/recordsource (probably an
unbound form)
    '
    If strSQL = "" Then
        BldSavedQuery = ""
        GoTo Exit_BldSavedQuery
    End If
    Set db = CurrentDb
    '
    'Check to see if the strsql is the name of a table
    '
    On Error Resume Next
    Set tdf = db.TableDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
    '
    'Check if the strSQL is a query name
    '
    Set qdf = db.QueryDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
On Error GoTo Err_BldSavedQuery
    
    lstrQryName = "q" & strQryName
    Set qdfs = db.QueryDefs
    Set qdf = New QueryDef
    With qdf
        .SQL = strSQL
        .Name = lstrQryName
    End With
    qdfs.Append qdf
    qdfs.Refresh
    BldSavedQuery = qdf.Name
Exit_BldSavedQuery:
On Error Resume Next
    If Not (qdf Is Nothing) Then qdf.Close: Set qdf = Nothing
    Set qdfs = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
Err_BldSavedQuery:
    Select Case Err
    Case 3012   'Query already exists
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " already exists, but this
control has a SQL statement in the rowsource"
        Resume Exit_BldSavedQuery
    Case 3129   'Not an SQL statement - mostly delimited lists or
deleted
saved query names
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " not a sql statement in
the rowsource but not a saved query or table either"
        Debug.Print vbTab & "Rowsource: " & strSQL
        Resume Exit_BldSavedQuery
    Case Else
        MsgBox Err.Description, , "Error in Function
basFindSQL.BldSavedQuery"
        Resume Exit_BldSavedQuery
    End Select
    Resume 0    '.FOR TROUBLESHOOTING
End Function
'
'This module will find all sql statements in objects such as forms,
combos and list boxes 'and save them as saved queries in the name
format:
'
'qfrmName
'qfrmname-CboName
'qfrmName-LstName
'
Function FindSQL()
On Error GoTo Err_FindSQL
Dim db As DAO.Database
Dim doc As DAO.Document
Dim frm As Form
Dim ctl As Control
Dim strQryName As String
    Set db = CurrentDb
    For Each doc In db.Containers(2).Documents
        DoCmd.OpenForm doc.Name, acDesign
        Set frm = Forms(doc.Name)
        strQryName = BldSavedQuery(frm.Name, frm.RecordSource)
        If Len(strQryName) > 0 Then
            frm.RecordSource = strQryName
        End If
        For Each ctl In frm.Controls
            Select Case ctl.ControlType
            Case acComboBox, acListBox
                strQryName = BldSavedQuery(frm.Name & "-" & ctl.Name,
ctl.RowSource)
                If Len(strQryName) > 0 Then
                    ctl.RowSource = strQryName
                End If
            Case Else
            End Select
            
        Next ctl
        DoCmd.Close acForm, doc.Name, acSaveYes
    Next doc
Exit_FindSQL:
On Error Resume Next
    If Not (frm Is Nothing) Then frm.Close: Set frm = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
Err_FindSQL:
        MsgBox Err.Description, , "Error in Function basFindSQL.FindSQL"
        Resume Exit_FindSQL
    Resume 0    '.FOR TROUBLESHOOTING
End Function

John W. Colby
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 dwaters at usinternet.com  Mon Jan 23 09:02:20 2006
From: dwaters at usinternet.com (Dan Waters)
Date: Mon, 23 Jan 2006 09:02:20 -0600
Subject: [dba-SQLServer] Preparing for upsizing
In-Reply-To: <11926045.1138008593720.JavaMail.root@sniper38>
Message-ID: <000001c6202e$02f56960$0200a8c0@danwaters>

Hi Erwin,

You might consider such a tool that is sold by SSW.  I have NOT used this,
but you can get a 1 year license for $100.  That's worth a couple of hours!

http://www.ssw.com.au/ssw/UpsizingPro/

I remember a couple of people on this list saying that they had a good
experience with it.

Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Erwin Craps
- IT Helps
Sent: Monday, January 23, 2006 3:12 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing


I was thinking about writing such a tool to, in order to upsize one of
my biggest database. I'm postponing this upsize already for a year or
two now, and I supose it will be not until after the summer holiday...


But I was considering to first store the SQL strings in a table , run a
grouping on it/analyse to minimize the number of queries and posibly to
improve them (manualy), and afterwards alter the forms/reports.

This to avoid to have 1 query per combo/listbox.

Erwin








-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Dan
Waters
Sent: Friday, January 20, 2006 4:10 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing

John,

There's nothing quite like making your own tools!

Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John
Colby
Sent: Thursday, January 19, 2006 10:23 PM
To: 'Access Developers discussion and problem solving';
dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Preparing for upsizing

I am preparing for upsizing a client's access database.  In order to do
this I needed to search all the objects looking for SQL statements and
save them as saved queries.  In order to do this with forms I created
the following two functions:

FindSQL opens each form in the database in design view, then passes the
name of the form and the form's RecordSource off to a function
BldSavedQuery.  It then looks for all controls in the form's control
collection looking for combos and list boxes, and does the same with
them.

BldSavedQuery looks for issues like nothing in the SQL statement passed
in, the "QryName" already being the name of a query or table, and if
neither of those conditions exist, then it tries to build a named query
def.  If it succeeds (the SQL passed in is valid and the name passed in
is not already a saved query) it creates a saved query and passes the
name back to FindSQL which then stores the saved query name back in
place of the SQL statement.
When all processing is finished, the form is then saved and closed.

It works reasonably well.  The only things found so far are delimited
lists instead of SQL statements and what appear to be saved query names
where the saved query was deleted.  Only about 17 of those, all but one
are delimited lists.  It took me ~ 2 hours to write / debug this code
and saved me who knows how much time manually hunting for these things.

I now have to do the same thing for reports, though there are so few I
might just do them manually.

Function BldSavedQuery(strQryName As String, strSQL As String) As String
On Error GoTo Err_BldSavedQuery Dim tdf As DAO.TableDef Dim qdf As
DAO.QueryDef Dim qdfs As DAO.QueryDefs Dim db As DAO.Database Dim
lstrQryName As String
    
    '
    'This object has nothing in the rowsource/recordsource (probably an
unbound form)
    '
    If strSQL = "" Then
        BldSavedQuery = ""
        GoTo Exit_BldSavedQuery
    End If
    Set db = CurrentDb
    '
    'Check to see if the strsql is the name of a table
    '
    On Error Resume Next
    Set tdf = db.TableDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
    '
    'Check if the strSQL is a query name
    '
    Set qdf = db.QueryDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
On Error GoTo Err_BldSavedQuery
    
    lstrQryName = "q" & strQryName
    Set qdfs = db.QueryDefs
    Set qdf = New QueryDef
    With qdf
        .SQL = strSQL
        .Name = lstrQryName
    End With
    qdfs.Append qdf
    qdfs.Refresh
    BldSavedQuery = qdf.Name
Exit_BldSavedQuery:
On Error Resume Next
    If Not (qdf Is Nothing) Then qdf.Close: Set qdf = Nothing
    Set qdfs = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
Err_BldSavedQuery:
    Select Case Err
    Case 3012   'Query already exists
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " already exists, but this
control has a SQL statement in the rowsource"
        Resume Exit_BldSavedQuery
    Case 3129   'Not an SQL statement - mostly delimited lists or
deleted
saved query names
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " not a sql statement in
the rowsource but not a saved query or table either"
        Debug.Print vbTab & "Rowsource: " & strSQL
        Resume Exit_BldSavedQuery
    Case Else
        MsgBox Err.Description, , "Error in Function
basFindSQL.BldSavedQuery"
        Resume Exit_BldSavedQuery
    End Select
    Resume 0    '.FOR TROUBLESHOOTING
End Function
'
'This module will find all sql statements in objects such as forms,
combos and list boxes 'and save them as saved queries in the name
format:
'
'qfrmName
'qfrmname-CboName
'qfrmName-LstName
'
Function FindSQL()
On Error GoTo Err_FindSQL
Dim db As DAO.Database
Dim doc As DAO.Document
Dim frm As Form
Dim ctl As Control
Dim strQryName As String
    Set db = CurrentDb
    For Each doc In db.Containers(2).Documents
        DoCmd.OpenForm doc.Name, acDesign
        Set frm = Forms(doc.Name)
        strQryName = BldSavedQuery(frm.Name, frm.RecordSource)
        If Len(strQryName) > 0 Then
            frm.RecordSource = strQryName
        End If
        For Each ctl In frm.Controls
            Select Case ctl.ControlType
            Case acComboBox, acListBox
                strQryName = BldSavedQuery(frm.Name & "-" & ctl.Name,
ctl.RowSource)
                If Len(strQryName) > 0 Then
                    ctl.RowSource = strQryName
                End If
            Case Else
            End Select
            
        Next ctl
        DoCmd.Close acForm, doc.Name, acSaveYes
    Next doc
Exit_FindSQL:
On Error Resume Next
    If Not (frm Is Nothing) Then frm.Close: Set frm = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
Err_FindSQL:
        MsgBox Err.Description, , "Error in Function basFindSQL.FindSQL"
        Resume Exit_FindSQL
    Resume 0    '.FOR TROUBLESHOOTING
End Function

John W. Colby
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



From Erwin.Craps at ithelps.be  Mon Jan 23 09:32:53 2006
From: Erwin.Craps at ithelps.be (Erwin Craps - IT Helps)
Date: Mon, 23 Jan 2006 16:32:53 +0100
Subject: [dba-SQLServer] Preparing for upsizing
Message-ID: <46B976F2B698FF46A4FE7636509B22DF1B62D3@stekelbes.ithelps.local>

I believe I already have some stuff from those guys.

I probably should take look at it...


Erwin
 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Dan
Waters
Sent: Monday, January 23, 2006 4:02 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing

Hi Erwin,

You might consider such a tool that is sold by SSW.  I have NOT used
this, but you can get a 1 year license for $100.  That's worth a couple
of hours!

http://www.ssw.com.au/ssw/UpsizingPro/

I remember a couple of people on this list saying that they had a good
experience with it.

Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Erwin
Craps
- IT Helps
Sent: Monday, January 23, 2006 3:12 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing


I was thinking about writing such a tool to, in order to upsize one of
my biggest database. I'm postponing this upsize already for a year or
two now, and I supose it will be not until after the summer holiday...


But I was considering to first store the SQL strings in a table , run a
grouping on it/analyse to minimize the number of queries and posibly to
improve them (manualy), and afterwards alter the forms/reports.

This to avoid to have 1 query per combo/listbox.

Erwin








-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Dan
Waters
Sent: Friday, January 20, 2006 4:10 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing

John,

There's nothing quite like making your own tools!

Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John
Colby
Sent: Thursday, January 19, 2006 10:23 PM
To: 'Access Developers discussion and problem solving';
dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Preparing for upsizing

I am preparing for upsizing a client's access database.  In order to do
this I needed to search all the objects looking for SQL statements and
save them as saved queries.  In order to do this with forms I created
the following two functions:

FindSQL opens each form in the database in design view, then passes the
name of the form and the form's RecordSource off to a function
BldSavedQuery.  It then looks for all controls in the form's control
collection looking for combos and list boxes, and does the same with
them.

BldSavedQuery looks for issues like nothing in the SQL statement passed
in, the "QryName" already being the name of a query or table, and if
neither of those conditions exist, then it tries to build a named query
def.  If it succeeds (the SQL passed in is valid and the name passed in
is not already a saved query) it creates a saved query and passes the
name back to FindSQL which then stores the saved query name back in
place of the SQL statement.
When all processing is finished, the form is then saved and closed.

It works reasonably well.  The only things found so far are delimited
lists instead of SQL statements and what appear to be saved query names
where the saved query was deleted.  Only about 17 of those, all but one
are delimited lists.  It took me ~ 2 hours to write / debug this code
and saved me who knows how much time manually hunting for these things.

I now have to do the same thing for reports, though there are so few I
might just do them manually.

Function BldSavedQuery(strQryName As String, strSQL As String) As String
On Error GoTo Err_BldSavedQuery Dim tdf As DAO.TableDef Dim qdf As
DAO.QueryDef Dim qdfs As DAO.QueryDefs Dim db As DAO.Database Dim
lstrQryName As String
    
    '
    'This object has nothing in the rowsource/recordsource (probably an
unbound form)
    '
    If strSQL = "" Then
        BldSavedQuery = ""
        GoTo Exit_BldSavedQuery
    End If
    Set db = CurrentDb
    '
    'Check to see if the strsql is the name of a table
    '
    On Error Resume Next
    Set tdf = db.TableDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
    '
    'Check if the strSQL is a query name
    '
    Set qdf = db.QueryDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
On Error GoTo Err_BldSavedQuery
    
    lstrQryName = "q" & strQryName
    Set qdfs = db.QueryDefs
    Set qdf = New QueryDef
    With qdf
        .SQL = strSQL
        .Name = lstrQryName
    End With
    qdfs.Append qdf
    qdfs.Refresh
    BldSavedQuery = qdf.Name
Exit_BldSavedQuery:
On Error Resume Next
    If Not (qdf Is Nothing) Then qdf.Close: Set qdf = Nothing
    Set qdfs = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
Err_BldSavedQuery:
    Select Case Err
    Case 3012   'Query already exists
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " already exists, but this
control has a SQL statement in the rowsource"
        Resume Exit_BldSavedQuery
    Case 3129   'Not an SQL statement - mostly delimited lists or
deleted
saved query names
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " not a sql statement in
the rowsource but not a saved query or table either"
        Debug.Print vbTab & "Rowsource: " & strSQL
        Resume Exit_BldSavedQuery
    Case Else
        MsgBox Err.Description, , "Error in Function
basFindSQL.BldSavedQuery"
        Resume Exit_BldSavedQuery
    End Select
    Resume 0    '.FOR TROUBLESHOOTING
End Function
'
'This module will find all sql statements in objects such as forms,
combos and list boxes 'and save them as saved queries in the name
format:
'
'qfrmName
'qfrmname-CboName
'qfrmName-LstName
'
Function FindSQL()
On Error GoTo Err_FindSQL
Dim db As DAO.Database
Dim doc As DAO.Document
Dim frm As Form
Dim ctl As Control
Dim strQryName As String
    Set db = CurrentDb
    For Each doc In db.Containers(2).Documents
        DoCmd.OpenForm doc.Name, acDesign
        Set frm = Forms(doc.Name)
        strQryName = BldSavedQuery(frm.Name, frm.RecordSource)
        If Len(strQryName) > 0 Then
            frm.RecordSource = strQryName
        End If
        For Each ctl In frm.Controls
            Select Case ctl.ControlType
            Case acComboBox, acListBox
                strQryName = BldSavedQuery(frm.Name & "-" & ctl.Name,
ctl.RowSource)
                If Len(strQryName) > 0 Then
                    ctl.RowSource = strQryName
                End If
            Case Else
            End Select
            
        Next ctl
        DoCmd.Close acForm, doc.Name, acSaveYes
    Next doc
Exit_FindSQL:
On Error Resume Next
    If Not (frm Is Nothing) Then frm.Close: Set frm = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
Err_FindSQL:
        MsgBox Err.Description, , "Error in Function basFindSQL.FindSQL"
        Resume Exit_FindSQL
    Resume 0    '.FOR TROUBLESHOOTING
End Function

John W. Colby
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

_______________________________________________
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 Jan 23 11:45:51 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Mon, 23 Jan 2006 09:45:51 -0800
Subject: [dba-SQLServer] Preparing for upsizing
In-Reply-To: <46B976F2B698FF46A4FE7636509B22DF1B62C8@stekelbes.ithelps.local>
Message-ID: <000901c62044$d9ffe910$017ba8c0@xpserver>

Erwin:

Three months ago I upsized a legacy system. Before the final process was
ran, it took almost a month to build and test the importing and data
manipulation routines. The structure needed some better functionality,
better normalisation, some new tables, loss some tables and a thorough
testing as once the process was started on the live data it had to go
straight through without errors.

The upsize process when started, at 5:00PM Friday night, completed without
an incident by 11:00PM and everyone was online, Monday morning. It was well
worth the preparation time.

My 2 cents worth.
Jim   

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Erwin Craps
- IT Helps
Sent: January 23, 2006 1:12 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing


I was thinking about writing such a tool to, in order to upsize one of
my biggest database. I'm postponing this upsize already for a year or
two now, and I supose it will be not until after the summer holiday...


But I was considering to first store the SQL strings in a table , run a
grouping on it/analyse to minimize the number of queries and posibly to
improve them (manualy), and afterwards alter the forms/reports.

This to avoid to have 1 query per combo/listbox.

Erwin








-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Dan
Waters
Sent: Friday, January 20, 2006 4:10 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing

John,

There's nothing quite like making your own tools!

Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John
Colby
Sent: Thursday, January 19, 2006 10:23 PM
To: 'Access Developers discussion and problem solving';
dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Preparing for upsizing

I am preparing for upsizing a client's access database.  In order to do
this I needed to search all the objects looking for SQL statements and
save them as saved queries.  In order to do this with forms I created
the following two functions:

FindSQL opens each form in the database in design view, then passes the
name of the form and the form's RecordSource off to a function
BldSavedQuery.  It then looks for all controls in the form's control
collection looking for combos and list boxes, and does the same with
them.

BldSavedQuery looks for issues like nothing in the SQL statement passed
in, the "QryName" already being the name of a query or table, and if
neither of those conditions exist, then it tries to build a named query
def.  If it succeeds (the SQL passed in is valid and the name passed in
is not already a saved query) it creates a saved query and passes the
name back to FindSQL which then stores the saved query name back in
place of the SQL statement.
When all processing is finished, the form is then saved and closed.

It works reasonably well.  The only things found so far are delimited
lists instead of SQL statements and what appear to be saved query names
where the saved query was deleted.  Only about 17 of those, all but one
are delimited lists.  It took me ~ 2 hours to write / debug this code
and saved me who knows how much time manually hunting for these things.

I now have to do the same thing for reports, though there are so few I
might just do them manually.

Function BldSavedQuery(strQryName As String, strSQL As String) As String
On Error GoTo Err_BldSavedQuery Dim tdf As DAO.TableDef Dim qdf As
DAO.QueryDef Dim qdfs As DAO.QueryDefs Dim db As DAO.Database Dim
lstrQryName As String
    
    '
    'This object has nothing in the rowsource/recordsource (probably an
unbound form)
    '
    If strSQL = "" Then
        BldSavedQuery = ""
        GoTo Exit_BldSavedQuery
    End If
    Set db = CurrentDb
    '
    'Check to see if the strsql is the name of a table
    '
    On Error Resume Next
    Set tdf = db.TableDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
    '
    'Check if the strSQL is a query name
    '
    Set qdf = db.QueryDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
On Error GoTo Err_BldSavedQuery
    
    lstrQryName = "q" & strQryName
    Set qdfs = db.QueryDefs
    Set qdf = New QueryDef
    With qdf
        .SQL = strSQL
        .Name = lstrQryName
    End With
    qdfs.Append qdf
    qdfs.Refresh
    BldSavedQuery = qdf.Name
Exit_BldSavedQuery:
On Error Resume Next
    If Not (qdf Is Nothing) Then qdf.Close: Set qdf = Nothing
    Set qdfs = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
Err_BldSavedQuery:
    Select Case Err
    Case 3012   'Query already exists
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " already exists, but this
control has a SQL statement in the rowsource"
        Resume Exit_BldSavedQuery
    Case 3129   'Not an SQL statement - mostly delimited lists or
deleted
saved query names
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " not a sql statement in
the rowsource but not a saved query or table either"
        Debug.Print vbTab & "Rowsource: " & strSQL
        Resume Exit_BldSavedQuery
    Case Else
        MsgBox Err.Description, , "Error in Function
basFindSQL.BldSavedQuery"
        Resume Exit_BldSavedQuery
    End Select
    Resume 0    '.FOR TROUBLESHOOTING
End Function
'
'This module will find all sql statements in objects such as forms,
combos and list boxes 'and save them as saved queries in the name
format:
'
'qfrmName
'qfrmname-CboName
'qfrmName-LstName
'
Function FindSQL()
On Error GoTo Err_FindSQL
Dim db As DAO.Database
Dim doc As DAO.Document
Dim frm As Form
Dim ctl As Control
Dim strQryName As String
    Set db = CurrentDb
    For Each doc In db.Containers(2).Documents
        DoCmd.OpenForm doc.Name, acDesign
        Set frm = Forms(doc.Name)
        strQryName = BldSavedQuery(frm.Name, frm.RecordSource)
        If Len(strQryName) > 0 Then
            frm.RecordSource = strQryName
        End If
        For Each ctl In frm.Controls
            Select Case ctl.ControlType
            Case acComboBox, acListBox
                strQryName = BldSavedQuery(frm.Name & "-" & ctl.Name,
ctl.RowSource)
                If Len(strQryName) > 0 Then
                    ctl.RowSource = strQryName
                End If
            Case Else
            End Select
            
        Next ctl
        DoCmd.Close acForm, doc.Name, acSaveYes
    Next doc
Exit_FindSQL:
On Error Resume Next
    If Not (frm Is Nothing) Then frm.Close: Set frm = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
Err_FindSQL:
        MsgBox Err.Description, , "Error in Function basFindSQL.FindSQL"
        Resume Exit_FindSQL
    Resume 0    '.FOR TROUBLESHOOTING
End Function

John W. Colby
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



From Erwin.Craps at ithelps.be  Mon Jan 23 14:48:24 2006
From: Erwin.Craps at ithelps.be (Erwin Craps - IT Helps)
Date: Mon, 23 Jan 2006 21:48:24 +0100
Subject: [dba-SQLServer] Preparing for upsizing
Message-ID: <46B976F2B698FF46A4FE7636509B22DF1B62D7@stekelbes.ithelps.local>


Pfff, a month work, getting discouraged already.
Altough I'm aware theres no magic tool.

I was hoping to migrate the app, without to much change to the code.
Yeah yeah, I still believe in fairytales.
This app is really the app for which I lost sleep, blood, sweat and my
(good?) sense of humor. It's has a huge amount of code and special
tricks in it and its the largest database I have (about 600 MB,
1,608,014 records only in the main table).

And the funny part is that not a single customer works with it.
We at our office are the only ones using it with 3 people, that is
except for the webclient)

I know I will need to upsize one day, but I'm gonna get gray hair of it.
Whats the MDB file size limit again? Maybe I can pull it a couple of
years further...

Maybe in a couple of years MS stops with MDB files and creates us a
wonderfull full analytic and upsize wizard that does the job over a
cofee or two?!

Erwin


 

-----Oorspronkelijk bericht-----
Van: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] Namens Jim Lawrence
Verzonden: maandag 23 januari 2006 18:46
Aan: dba-sqlserver at databaseadvisors.com
Onderwerp: Re: [dba-SQLServer] Preparing for upsizing

Erwin:

Three months ago I upsized a legacy system. Before the final process was
ran, it took almost a month to build and test the importing and data
manipulation routines. The structure needed some better functionality,
better normalisation, some new tables, loss some tables and a thorough
testing as once the process was started on the live data it had to go
straight through without errors.

The upsize process when started, at 5:00PM Friday night, completed
without an incident by 11:00PM and everyone was online, Monday morning.
It was well worth the preparation time.

My 2 cents worth.
Jim   

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Erwin
Craps
- IT Helps
Sent: January 23, 2006 1:12 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing


I was thinking about writing such a tool to, in order to upsize one of
my biggest database. I'm postponing this upsize already for a year or
two now, and I supose it will be not until after the summer holiday...


But I was considering to first store the SQL strings in a table , run a
grouping on it/analyse to minimize the number of queries and posibly to
improve them (manualy), and afterwards alter the forms/reports.

This to avoid to have 1 query per combo/listbox.

Erwin








-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Dan
Waters
Sent: Friday, January 20, 2006 4:10 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing

John,

There's nothing quite like making your own tools!

Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John
Colby
Sent: Thursday, January 19, 2006 10:23 PM
To: 'Access Developers discussion and problem solving';
dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Preparing for upsizing

I am preparing for upsizing a client's access database.  In order to do
this I needed to search all the objects looking for SQL statements and
save them as saved queries.  In order to do this with forms I created
the following two functions:

FindSQL opens each form in the database in design view, then passes the
name of the form and the form's RecordSource off to a function
BldSavedQuery.  It then looks for all controls in the form's control
collection looking for combos and list boxes, and does the same with
them.

BldSavedQuery looks for issues like nothing in the SQL statement passed
in, the "QryName" already being the name of a query or table, and if
neither of those conditions exist, then it tries to build a named query
def.  If it succeeds (the SQL passed in is valid and the name passed in
is not already a saved query) it creates a saved query and passes the
name back to FindSQL which then stores the saved query name back in
place of the SQL statement.
When all processing is finished, the form is then saved and closed.

It works reasonably well.  The only things found so far are delimited
lists instead of SQL statements and what appear to be saved query names
where the saved query was deleted.  Only about 17 of those, all but one
are delimited lists.  It took me ~ 2 hours to write / debug this code
and saved me who knows how much time manually hunting for these things.

I now have to do the same thing for reports, though there are so few I
might just do them manually.

Function BldSavedQuery(strQryName As String, strSQL As String) As String
On Error GoTo Err_BldSavedQuery Dim tdf As DAO.TableDef Dim qdf As
DAO.QueryDef Dim qdfs As DAO.QueryDefs Dim db As DAO.Database Dim
lstrQryName As String
    
    '
    'This object has nothing in the rowsource/recordsource (probably an
unbound form)
    '
    If strSQL = "" Then
        BldSavedQuery = ""
        GoTo Exit_BldSavedQuery
    End If
    Set db = CurrentDb
    '
    'Check to see if the strsql is the name of a table
    '
    On Error Resume Next
    Set tdf = db.TableDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
    '
    'Check if the strSQL is a query name
    '
    Set qdf = db.QueryDefs(strSQL)
    If Err = 0 Then
        GoTo Exit_BldSavedQuery
    End If
    Err.Clear
On Error GoTo Err_BldSavedQuery
    
    lstrQryName = "q" & strQryName
    Set qdfs = db.QueryDefs
    Set qdf = New QueryDef
    With qdf
        .SQL = strSQL
        .Name = lstrQryName
    End With
    qdfs.Append qdf
    qdfs.Refresh
    BldSavedQuery = qdf.Name
Exit_BldSavedQuery:
On Error Resume Next
    If Not (qdf Is Nothing) Then qdf.Close: Set qdf = Nothing
    Set qdfs = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
Err_BldSavedQuery:
    Select Case Err
    Case 3012   'Query already exists
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " already exists, but this
control has a SQL statement in the rowsource"
        Resume Exit_BldSavedQuery
    Case 3129   'Not an SQL statement - mostly delimited lists or
deleted
saved query names
        BldSavedQuery = ""
        Debug.Print "ERROR: " & lstrQryName & " not a sql statement in
the rowsource but not a saved query or table either"
        Debug.Print vbTab & "Rowsource: " & strSQL
        Resume Exit_BldSavedQuery
    Case Else
        MsgBox Err.Description, , "Error in Function
basFindSQL.BldSavedQuery"
        Resume Exit_BldSavedQuery
    End Select
    Resume 0    '.FOR TROUBLESHOOTING
End Function
'
'This module will find all sql statements in objects such as forms,
combos and list boxes 'and save them as saved queries in the name
format:
'
'qfrmName
'qfrmname-CboName
'qfrmName-LstName
'
Function FindSQL()
On Error GoTo Err_FindSQL
Dim db As DAO.Database
Dim doc As DAO.Document
Dim frm As Form
Dim ctl As Control
Dim strQryName As String
    Set db = CurrentDb
    For Each doc In db.Containers(2).Documents
        DoCmd.OpenForm doc.Name, acDesign
        Set frm = Forms(doc.Name)
        strQryName = BldSavedQuery(frm.Name, frm.RecordSource)
        If Len(strQryName) > 0 Then
            frm.RecordSource = strQryName
        End If
        For Each ctl In frm.Controls
            Select Case ctl.ControlType
            Case acComboBox, acListBox
                strQryName = BldSavedQuery(frm.Name & "-" & ctl.Name,
ctl.RowSource)
                If Len(strQryName) > 0 Then
                    ctl.RowSource = strQryName
                End If
            Case Else
            End Select
            
        Next ctl
        DoCmd.Close acForm, doc.Name, acSaveYes
    Next doc
Exit_FindSQL:
On Error Resume Next
    If Not (frm Is Nothing) Then frm.Close: Set frm = Nothing
    If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
Err_FindSQL:
        MsgBox Err.Description, , "Error in Function basFindSQL.FindSQL"
        Resume Exit_FindSQL
    Resume 0    '.FOR TROUBLESHOOTING
End Function

John W. Colby
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

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From dwaters at usinternet.com  Mon Jan 23 15:05:57 2006
From: dwaters at usinternet.com (Dan Waters)
Date: Mon, 23 Jan 2006 15:05:57 -0600
Subject: [dba-SQLServer] Access Connection to SQL Server (was: Upsize
	wizard and named queries)
In-Reply-To: <17931978.1137859992211.JavaMail.root@sniper15>
Message-ID: <000501c62060$cee60c50$0200a8c0@danwaters>

Doris,

Can you give more information on this?  Which versions of Access and SQL
Server are you using.  You said this limits the connection string packet
size, but what impact does that have on the developer?  Or impact on the
users?  

Are you using CurrentProject.Connection or CurrentProject.AccessConnection?

I am about to begin developing a system using Access 2003 as the FE and SQL
Server 2005 as the BE, and would like to know more about this issue.

Thanks!
Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mike &
Doris Manning
Sent: Saturday, January 21, 2006 10:12 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Upsize wizard and named queries

John,

The biggest problem with connecting to SQL Server through Access is that
Access automatically limits the connection string packet size to 4096.  I
have yet to find any way to change that within Access.  This is one reason
why I've been slowly moving all my company's apps over to VB.Net.  There, I
can control the connection by changing the packet size to 32767 which is as
wide as it can go.

Doris Manning
mikedorism at verizon.net



_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From mikedorism at verizon.net  Mon Jan 23 18:38:00 2006
From: mikedorism at verizon.net (Mike & Doris Manning)
Date: Mon, 23 Jan 2006 19:38:00 -0500
Subject: [dba-SQLServer] Access Connection to SQL Server (was:
 Upsizewizard and named queries)
In-Reply-To: <000501c62060$cee60c50$0200a8c0@danwaters>
Message-ID: <000601c6207e$6ef18d10$2f01a8c0@dorismanning>

Access 2003 and SQL Server 2000.

Impact on the developer = none
Impact on the user = HUGE if you have a lot of data coming over at once...

In my case, my main screen contains a list of all open work orders.  Even
with a stored procedure targeting a specific set of work orders, the load
time for a list box bound to the stored procedure is 6 seconds at 4096
packet.  When I moved to VB.Net and changed the packet size to 32767, the
same amount of data took 1 second.  I know that doesn't sound like much of a
savings, but my end users reported a huge difference in response time
throughout the app.

An Access ADP automatically sets up 3 connections to the SQL BE so I found
it more economical to use AccessConnection because that allowed me to use
one of the existing 3 connections instead of launching another one.

Doris Manning
mikedorism at verizon.net





From dwaters at usinternet.com  Mon Jan 23 20:10:34 2006
From: dwaters at usinternet.com (Dan Waters)
Date: Mon, 23 Jan 2006 20:10:34 -0600
Subject: [dba-SQLServer] Access Connection to SQL Server (was:
	Upsizewizard and named queries)
In-Reply-To: <28901975.1138063259312.JavaMail.root@sniper39>
Message-ID: <000201c6208b$5c723790$0200a8c0@danwaters>

Hi Doris,

I did some looking and found this on MSDN:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/
mdrefsqlprovspec.asp

It describes using a service provider called SQLOLEDB, and from what I can
read it does allow changing the Packet Size from the default of 4096 up to
32767.

Something like:  

	Set CN = New ADODB.Connection
	CN.Provider = "SQLOLEDB"
	CN.Properties("Packet Size").Value = 32767

I think it should be possible to use this service provider when creating a
connection to SQL Server from an Access FE.  Although to use bound forms in
an Access FE and SQL Server BE you must use the service provider of
Microsoft.Access.OLEDB.10.0, which is unique to AccessConnection.

I wanted to find out if you have tried using SQLOLEDB as the service
provider, and if so what was your experience.  

My plan is to use an Access .mdb FE and instantiate the connection when the
FE is opened.

And, if anyone else can add to this, please speak up!


Thanks!
Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mike &
Doris Manning
Sent: Monday, January 23, 2006 6:38 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Access Connection to SQL Server (was:
Upsizewizard and named queries)

Access 2003 and SQL Server 2000.

Impact on the developer = none
Impact on the user = HUGE if you have a lot of data coming over at once...

In my case, my main screen contains a list of all open work orders.  Even
with a stored procedure targeting a specific set of work orders, the load
time for a list box bound to the stored procedure is 6 seconds at 4096
packet.  When I moved to VB.Net and changed the packet size to 32767, the
same amount of data took 1 second.  I know that doesn't sound like much of a
savings, but my end users reported a huge difference in response time
throughout the app.

An Access ADP automatically sets up 3 connections to the SQL BE so I found
it more economical to use AccessConnection because that allowed me to use
one of the existing 3 connections instead of launching another one.

Doris Manning
mikedorism at verizon.net



_______________________________________________
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 Jan 23 20:18:50 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Tue, 24 Jan 2006 13:18:50 +1100
Subject: [dba-SQLServer] Reporting Services Q
Message-ID: <20060124021856.JJSF14751.omta05ps.mx.bigpond.com@DENZILLAP>

Hello all
I have a nice little function (from DBA Archives :0((
here 'tis
 
Function GetPath(aPath) As String
' Strips the path name from the supplied file and path name
' leaves the trailing slash on there
Dim foo As Integer, aSlash As Integer
    aSlash = 0
    foo = InStr(aPath, "\")
    While (foo > 0)
        aSlash = foo
        foo = InStr(aSlash + 1, aPath, "\")
    Wend
    If aSlash > 0 Then
        GetPath = Left$(aPath, aSlash)
    Else
        GetPath = aPath
    End If
End Function

 
I have a field on a reporting services report that I want to use this function
on
 
So I paste my little function inside a Macro
By going to...
Macro Explorer
MyMacros
RightClick 
Select  New Module
Enter name of say...modUtils
Paste my little function in between Public Module ModUtils and End module
Save it all - no obvious errors
So far so good
 
Back to RepServices Designer
Then for the value of the text box "txtFileName" I put
=f_getPath(Fields!FileName.Value)
(Originally the value for the text box "txtFileName" was Fields!FileName.Value -
all working fine)
 
So when I go to preview I get the error....
C:\Documents and Settings\darrend\My Documents\Visual Studio Projects\Report
Project1\Report1.rdl The value expression for the textbox 'Filename' contains an
error: [BC30451] Name 'GetPath' is not declared.

So...any suggestions?
O have I totally gort the RepServices placemet of modules and associated
syntaxes wrong?
 
See ya
 
 
 
 
 


From stuart at lexacorp.com.pg  Mon Jan 23 21:14:26 2006
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Tue, 24 Jan 2006 13:14:26 +1000
Subject: [dba-SQLServer] Access Connection to SQL Server (was:
	Upsizewizard and named queries)
In-Reply-To: <000201c6208b$5c723790$0200a8c0@danwaters>
References: <28901975.1138063259312.JavaMail.root@sniper39>
Message-ID: <43D62832.23968.B1FF42C@stuart.lexacorp.com.pg>

On 23 Jan 2006 at 20:10, Dan Waters wrote:

> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/
> mdrefsqlprovspec.asp
> 
> It describes using a service provider called SQLOLEDB, and from what I can
> read it does allow changing the Packet Size from the default of 4096 up to
> 32767.
> 
> Something like:  
> 
>  Set CN = New ADODB.Connection
>  CN.Provider = "SQLOLEDB"
>  CN.Properties("Packet Size").Value = 32767
> 
> I think it should be possible to use this service provider when creating a
> connection to SQL Server from an Access FE.  Although to use bound forms in
> an Access FE and SQL Server BE you must use the service provider of
> Microsoft.Access.OLEDB.10.0, which is unique to AccessConnection.
> 
> I wanted to find out if you have tried using SQLOLEDB as the service
> provider, and if so what was your experience.  
> 
> My plan is to use an Access .mdb FE and instantiate the connection when the
> FE is opened.
> 
> And, if anyone else can add to this, please speak up!
> 

One possible gotcha:
http://support.microsoft.com/?kbid=903002
A "Failed to reserve contiguous memory" error message may be logged in the 
SQL Server error log when users connect to an instance of SQL Server by 
using a network packet size that is larger than 8,060 bytes-- 
Stuart




From accessd at shaw.ca  Mon Jan 23 23:12:16 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Mon, 23 Jan 2006 21:12:16 -0800
Subject: [dba-SQLServer] Access Connection to SQL Server (was:
 Upsizewizard and named queries)
In-Reply-To: <000601c6207e$6ef18d10$2f01a8c0@dorismanning>
Message-ID: <000f01c620a4$be30ea80$017ba8c0@xpserver>

Hi Doris:

Are you really sure of those limitations? Do they exist only when you use an
ODBC connection? Are there other circumstances?

I have tested and recorded, with an Access FE using ADO-OLE, 50,000 plus
records downloaded in less than 2 seconds. That seems to be a lot more than
only a 4096 byte packet.

Comments please 
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mike &
Doris Manning
Sent: January 23, 2006 4:38 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Access Connection to SQL Server (was:
Upsizewizard and named queries)

Access 2003 and SQL Server 2000.

Impact on the developer = none
Impact on the user = HUGE if you have a lot of data coming over at once...

In my case, my main screen contains a list of all open work orders.  Even
with a stored procedure targeting a specific set of work orders, the load
time for a list box bound to the stored procedure is 6 seconds at 4096
packet.  When I moved to VB.Net and changed the packet size to 32767, the
same amount of data took 1 second.  I know that doesn't sound like much of a
savings, but my end users reported a huge difference in response time
throughout the app.

An Access ADP automatically sets up 3 connections to the SQL BE so I found
it more economical to use AccessConnection because that allowed me to use
one of the existing 3 connections instead of launching another one.

Doris Manning
mikedorism at verizon.net



_______________________________________________
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 Jan 24 10:37:13 2006
From: rl_stewart at highstream.net (Robert L. Stewart)
Date: Tue, 24 Jan 2006 10:37:13 -0600
Subject: [dba-SQLServer] Preparing for upsizing
In-Reply-To: <mailman.640.1138079588.18500.dba-sqlserver@databaseadvisor s.com>
References: <mailman.640.1138079588.18500.dba-sqlserver@databaseadvisors.com>
Message-ID: <6.2.3.4.2.20060124103410.0303b100@pop3.highstream.net>

Actually Erwin, I use Erwin (now called AllFusion Data Modeler from 
Computer Associates) to do all my upsizing.  :-)  Yes, it is an 
expensive tool, about $3,000 a seat.  But, it is fast and works great 
with a number of databases.  I can redo a design in about 3 or 4 days 
from Access to almost any database.

At 11:13 PM 1/23/2006, you wrote:
>Date: Mon, 23 Jan 2006 21:48:24 +0100
>From: "Erwin Craps - IT Helps" <Erwin.Craps at ithelps.be>
>Subject: Re: [dba-SQLServer] Preparing for upsizing
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID:
>         <46B976F2B698FF46A4FE7636509B22DF1B62D7 at stekelbes.ithelps.local>
>Content-Type: text/plain;       charset="us-ascii"
>
>
>Pfff, a month work, getting discouraged already.
>Altough I'm aware theres no magic tool.
>
>I was hoping to migrate the app, without to much change to the code.
>Yeah yeah, I still believe in fairytales.
>This app is really the app for which I lost sleep, blood, sweat and my
>(good?) sense of humor. It's has a huge amount of code and special
>tricks in it and its the largest database I have (about 600 MB,
>1,608,014 records only in the main table).
>
>And the funny part is that not a single customer works with it.
>We at our office are the only ones using it with 3 people, that is
>except for the webclient)
>
>I know I will need to upsize one day, but I'm gonna get gray hair of it.
>Whats the MDB file size limit again? Maybe I can pull it a couple of
>years further...
>
>Maybe in a couple of years MS stops with MDB files and creates us a
>wonderfull full analytic and upsize wizard that does the job over a
>cofee or two?!
>
>Erwin
>
>
>
>
>-----Oorspronkelijk bericht-----
>Van: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] Namens Jim Lawrence
>Verzonden: maandag 23 januari 2006 18:46
>Aan: dba-sqlserver at databaseadvisors.com
>Onderwerp: Re: [dba-SQLServer] Preparing for upsizing
>
>Erwin:
>
>Three months ago I upsized a legacy system. Before the final process was
>ran, it took almost a month to build and test the importing and data
>manipulation routines. The structure needed some better functionality,
>better normalisation, some new tables, loss some tables and a thorough
>testing as once the process was started on the live data it had to go
>straight through without errors.
>
>The upsize process when started, at 5:00PM Friday night, completed
>without an incident by 11:00PM and everyone was online, Monday morning.
>It was well worth the preparation time.
>
>My 2 cents worth.
>Jim
>
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Erwin
>Craps
>- IT Helps
>Sent: January 23, 2006 1:12 AM
>To: dba-sqlserver at databaseadvisors.com
>Subject: Re: [dba-SQLServer] Preparing for upsizing
>
>
>I was thinking about writing such a tool to, in order to upsize one of
>my biggest database. I'm postponing this upsize already for a year or
>two now, and I supose it will be not until after the summer holiday...
>
>
>But I was considering to first store the SQL strings in a table , run a
>grouping on it/analyse to minimize the number of queries and posibly to
>improve them (manualy), and afterwards alter the forms/reports.
>
>This to avoid to have 1 query per combo/listbox.
>
>Erwin
>
>
>
>
>
>
>
>
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Dan
>Waters
>Sent: Friday, January 20, 2006 4:10 PM
>To: dba-sqlserver at databaseadvisors.com
>Subject: Re: [dba-SQLServer] Preparing for upsizing
>
>John,
>
>There's nothing quite like making your own tools!
>
>Dan
>
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John
>Colby
>Sent: Thursday, January 19, 2006 10:23 PM
>To: 'Access Developers discussion and problem solving';
>dba-sqlserver at databaseadvisors.com
>Subject: [dba-SQLServer] Preparing for upsizing
>
>I am preparing for upsizing a client's access database.  In order to do
>this I needed to search all the objects looking for SQL statements and
>save them as saved queries.  In order to do this with forms I created
>the following two functions:
>
>FindSQL opens each form in the database in design view, then passes the
>name of the form and the form's RecordSource off to a function
>BldSavedQuery.  It then looks for all controls in the form's control
>collection looking for combos and list boxes, and does the same with
>them.
>
>BldSavedQuery looks for issues like nothing in the SQL statement passed
>in, the "QryName" already being the name of a query or table, and if
>neither of those conditions exist, then it tries to build a named query
>def.  If it succeeds (the SQL passed in is valid and the name passed in
>is not already a saved query) it creates a saved query and passes the
>name back to FindSQL which then stores the saved query name back in
>place of the SQL statement.
>When all processing is finished, the form is then saved and closed.
>
>It works reasonably well.  The only things found so far are delimited
>lists instead of SQL statements and what appear to be saved query names
>where the saved query was deleted.  Only about 17 of those, all but one
>are delimited lists.  It took me ~ 2 hours to write / debug this code
>and saved me who knows how much time manually hunting for these things.
>
>I now have to do the same thing for reports, though there are so few I
>might just do them manually.
>
>Function BldSavedQuery(strQryName As String, strSQL As String) As String
>On Error GoTo Err_BldSavedQuery Dim tdf As DAO.TableDef Dim qdf As
>DAO.QueryDef Dim qdfs As DAO.QueryDefs Dim db As DAO.Database Dim
>lstrQryName As String
>
>     '
>     'This object has nothing in the rowsource/recordsource (probably an
>unbound form)
>     '
>     If strSQL = "" Then
>         BldSavedQuery = ""
>         GoTo Exit_BldSavedQuery
>     End If
>     Set db = CurrentDb
>     '
>     'Check to see if the strsql is the name of a table
>     '
>     On Error Resume Next
>     Set tdf = db.TableDefs(strSQL)
>     If Err = 0 Then
>         GoTo Exit_BldSavedQuery
>     End If
>     Err.Clear
>     '
>     'Check if the strSQL is a query name
>     '
>     Set qdf = db.QueryDefs(strSQL)
>     If Err = 0 Then
>         GoTo Exit_BldSavedQuery
>     End If
>     Err.Clear
>On Error GoTo Err_BldSavedQuery
>
>     lstrQryName = "q" & strQryName
>     Set qdfs = db.QueryDefs
>     Set qdf = New QueryDef
>     With qdf
>         .SQL = strSQL
>         .Name = lstrQryName
>     End With
>     qdfs.Append qdf
>     qdfs.Refresh
>     BldSavedQuery = qdf.Name
>Exit_BldSavedQuery:
>On Error Resume Next
>     If Not (qdf Is Nothing) Then qdf.Close: Set qdf = Nothing
>     Set qdfs = Nothing
>     If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
>Err_BldSavedQuery:
>     Select Case Err
>     Case 3012   'Query already exists
>         BldSavedQuery = ""
>         Debug.Print "ERROR: " & lstrQryName & " already exists, but this
>control has a SQL statement in the rowsource"
>         Resume Exit_BldSavedQuery
>     Case 3129   'Not an SQL statement - mostly delimited lists or
>deleted
>saved query names
>         BldSavedQuery = ""
>         Debug.Print "ERROR: " & lstrQryName & " not a sql statement in
>the rowsource but not a saved query or table either"
>         Debug.Print vbTab & "Rowsource: " & strSQL
>         Resume Exit_BldSavedQuery
>     Case Else
>         MsgBox Err.Description, , "Error in Function
>basFindSQL.BldSavedQuery"
>         Resume Exit_BldSavedQuery
>     End Select
>     Resume 0    '.FOR TROUBLESHOOTING
>End Function
>'
>'This module will find all sql statements in objects such as forms,
>combos and list boxes 'and save them as saved queries in the name
>format:
>'
>'qfrmName
>'qfrmname-CboName
>'qfrmName-LstName
>'
>Function FindSQL()
>On Error GoTo Err_FindSQL
>Dim db As DAO.Database
>Dim doc As DAO.Document
>Dim frm As Form
>Dim ctl As Control
>Dim strQryName As String
>     Set db = CurrentDb
>     For Each doc In db.Containers(2).Documents
>         DoCmd.OpenForm doc.Name, acDesign
>         Set frm = Forms(doc.Name)
>         strQryName = BldSavedQuery(frm.Name, frm.RecordSource)
>         If Len(strQryName) > 0 Then
>             frm.RecordSource = strQryName
>         End If
>         For Each ctl In frm.Controls
>             Select Case ctl.ControlType
>             Case acComboBox, acListBox
>                 strQryName = BldSavedQuery(frm.Name & "-" & ctl.Name,
>ctl.RowSource)
>                 If Len(strQryName) > 0 Then
>                     ctl.RowSource = strQryName
>                 End If
>             Case Else
>             End Select
>
>         Next ctl
>         DoCmd.Close acForm, doc.Name, acSaveYes
>     Next doc
>Exit_FindSQL:
>On Error Resume Next
>     If Not (frm Is Nothing) Then frm.Close: Set frm = Nothing
>     If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit Function
>Err_FindSQL:
>         MsgBox Err.Description, , "Error in Function basFindSQL.FindSQL"
>         Resume Exit_FindSQL
>     Resume 0    '.FOR TROUBLESHOOTING
>End Function
>
>John W. Colby
>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
>
>_______________________________________________
>dba-SQLServer mailing list
>dba-SQLServer at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
>http://www.databaseadvisors.com




From Erwin.Craps at ithelps.be  Tue Jan 24 10:45:53 2006
From: Erwin.Craps at ithelps.be (Erwin Craps - IT Helps)
Date: Tue, 24 Jan 2006 17:45:53 +0100
Subject: [dba-SQLServer] Preparing for upsizing
Message-ID: <46B976F2B698FF46A4FE7636509B22DF1B62DD@stekelbes.ithelps.local>

Aha, the wondertool exists...
When time has arrived I take a look in to it, and maybe I'll mail you
directly in case you would have some spare time :-)
 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert
L. Stewart
Sent: Tuesday, January 24, 2006 5:37 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Preparing for upsizing

Actually Erwin, I use Erwin (now called AllFusion Data Modeler from
Computer Associates) to do all my upsizing.  :-)  Yes, it is an
expensive tool, about $3,000 a seat.  But, it is fast and works great
with a number of databases.  I can redo a design in about 3 or 4 days
from Access to almost any database.

At 11:13 PM 1/23/2006, you wrote:
>Date: Mon, 23 Jan 2006 21:48:24 +0100
>From: "Erwin Craps - IT Helps" <Erwin.Craps at ithelps.be>
>Subject: Re: [dba-SQLServer] Preparing for upsizing
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID:
>
<46B976F2B698FF46A4FE7636509B22DF1B62D7 at stekelbes.ithelps.local>
>Content-Type: text/plain;       charset="us-ascii"
>
>
>Pfff, a month work, getting discouraged already.
>Altough I'm aware theres no magic tool.
>
>I was hoping to migrate the app, without to much change to the code.
>Yeah yeah, I still believe in fairytales.
>This app is really the app for which I lost sleep, blood, sweat and my
>(good?) sense of humor. It's has a huge amount of code and special 
>tricks in it and its the largest database I have (about 600 MB,
>1,608,014 records only in the main table).
>
>And the funny part is that not a single customer works with it.
>We at our office are the only ones using it with 3 people, that is 
>except for the webclient)
>
>I know I will need to upsize one day, but I'm gonna get gray hair of
it.
>Whats the MDB file size limit again? Maybe I can pull it a couple of 
>years further...
>
>Maybe in a couple of years MS stops with MDB files and creates us a 
>wonderfull full analytic and upsize wizard that does the job over a 
>cofee or two?!
>
>Erwin
>
>
>
>
>-----Oorspronkelijk bericht-----
>Van: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] Namens Jim Lawrence
>Verzonden: maandag 23 januari 2006 18:46
>Aan: dba-sqlserver at databaseadvisors.com
>Onderwerp: Re: [dba-SQLServer] Preparing for upsizing
>
>Erwin:
>
>Three months ago I upsized a legacy system. Before the final process 
>was ran, it took almost a month to build and test the importing and 
>data manipulation routines. The structure needed some better 
>functionality, better normalisation, some new tables, loss some tables 
>and a thorough testing as once the process was started on the live data

>it had to go straight through without errors.
>
>The upsize process when started, at 5:00PM Friday night, completed 
>without an incident by 11:00PM and everyone was online, Monday morning.
>It was well worth the preparation time.
>
>My 2 cents worth.
>Jim
>
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Erwin 
>Craps
>- IT Helps
>Sent: January 23, 2006 1:12 AM
>To: dba-sqlserver at databaseadvisors.com
>Subject: Re: [dba-SQLServer] Preparing for upsizing
>
>
>I was thinking about writing such a tool to, in order to upsize one of 
>my biggest database. I'm postponing this upsize already for a year or 
>two now, and I supose it will be not until after the summer holiday...
>
>
>But I was considering to first store the SQL strings in a table , run a

>grouping on it/analyse to minimize the number of queries and posibly to

>improve them (manualy), and afterwards alter the forms/reports.
>
>This to avoid to have 1 query per combo/listbox.
>
>Erwin
>
>
>
>
>
>
>
>
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Dan 
>Waters
>Sent: Friday, January 20, 2006 4:10 PM
>To: dba-sqlserver at databaseadvisors.com
>Subject: Re: [dba-SQLServer] Preparing for upsizing
>
>John,
>
>There's nothing quite like making your own tools!
>
>Dan
>
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John 
>Colby
>Sent: Thursday, January 19, 2006 10:23 PM
>To: 'Access Developers discussion and problem solving'; 
>dba-sqlserver at databaseadvisors.com
>Subject: [dba-SQLServer] Preparing for upsizing
>
>I am preparing for upsizing a client's access database.  In order to do

>this I needed to search all the objects looking for SQL statements and 
>save them as saved queries.  In order to do this with forms I created 
>the following two functions:
>
>FindSQL opens each form in the database in design view, then passes the

>name of the form and the form's RecordSource off to a function 
>BldSavedQuery.  It then looks for all controls in the form's control 
>collection looking for combos and list boxes, and does the same with 
>them.
>
>BldSavedQuery looks for issues like nothing in the SQL statement passed

>in, the "QryName" already being the name of a query or table, and if 
>neither of those conditions exist, then it tries to build a named query

>def.  If it succeeds (the SQL passed in is valid and the name passed in

>is not already a saved query) it creates a saved query and passes the 
>name back to FindSQL which then stores the saved query name back in 
>place of the SQL statement.
>When all processing is finished, the form is then saved and closed.
>
>It works reasonably well.  The only things found so far are delimited 
>lists instead of SQL statements and what appear to be saved query names

>where the saved query was deleted.  Only about 17 of those, all but one

>are delimited lists.  It took me ~ 2 hours to write / debug this code 
>and saved me who knows how much time manually hunting for these things.
>
>I now have to do the same thing for reports, though there are so few I 
>might just do them manually.
>
>Function BldSavedQuery(strQryName As String, strSQL As String) As 
>String On Error GoTo Err_BldSavedQuery Dim tdf As DAO.TableDef Dim qdf 
>As DAO.QueryDef Dim qdfs As DAO.QueryDefs Dim db As DAO.Database Dim 
>lstrQryName As String
>
>     '
>     'This object has nothing in the rowsource/recordsource (probably 
>an unbound form)
>     '
>     If strSQL = "" Then
>         BldSavedQuery = ""
>         GoTo Exit_BldSavedQuery
>     End If
>     Set db = CurrentDb
>     '
>     'Check to see if the strsql is the name of a table
>     '
>     On Error Resume Next
>     Set tdf = db.TableDefs(strSQL)
>     If Err = 0 Then
>         GoTo Exit_BldSavedQuery
>     End If
>     Err.Clear
>     '
>     'Check if the strSQL is a query name
>     '
>     Set qdf = db.QueryDefs(strSQL)
>     If Err = 0 Then
>         GoTo Exit_BldSavedQuery
>     End If
>     Err.Clear
>On Error GoTo Err_BldSavedQuery
>
>     lstrQryName = "q" & strQryName
>     Set qdfs = db.QueryDefs
>     Set qdf = New QueryDef
>     With qdf
>         .SQL = strSQL
>         .Name = lstrQryName
>     End With
>     qdfs.Append qdf
>     qdfs.Refresh
>     BldSavedQuery = qdf.Name
>Exit_BldSavedQuery:
>On Error Resume Next
>     If Not (qdf Is Nothing) Then qdf.Close: Set qdf = Nothing
>     Set qdfs = Nothing
>     If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit 
>Function
>Err_BldSavedQuery:
>     Select Case Err
>     Case 3012   'Query already exists
>         BldSavedQuery = ""
>         Debug.Print "ERROR: " & lstrQryName & " already exists, but 
>this control has a SQL statement in the rowsource"
>         Resume Exit_BldSavedQuery
>     Case 3129   'Not an SQL statement - mostly delimited lists or
>deleted
>saved query names
>         BldSavedQuery = ""
>         Debug.Print "ERROR: " & lstrQryName & " not a sql statement in

>the rowsource but not a saved query or table either"
>         Debug.Print vbTab & "Rowsource: " & strSQL
>         Resume Exit_BldSavedQuery
>     Case Else
>         MsgBox Err.Description, , "Error in Function 
>basFindSQL.BldSavedQuery"
>         Resume Exit_BldSavedQuery
>     End Select
>     Resume 0    '.FOR TROUBLESHOOTING
>End Function
>'
>'This module will find all sql statements in objects such as forms, 
>combos and list boxes 'and save them as saved queries in the name
>format:
>'
>'qfrmName
>'qfrmname-CboName
>'qfrmName-LstName
>'
>Function FindSQL()
>On Error GoTo Err_FindSQL
>Dim db As DAO.Database
>Dim doc As DAO.Document
>Dim frm As Form
>Dim ctl As Control
>Dim strQryName As String
>     Set db = CurrentDb
>     For Each doc In db.Containers(2).Documents
>         DoCmd.OpenForm doc.Name, acDesign
>         Set frm = Forms(doc.Name)
>         strQryName = BldSavedQuery(frm.Name, frm.RecordSource)
>         If Len(strQryName) > 0 Then
>             frm.RecordSource = strQryName
>         End If
>         For Each ctl In frm.Controls
>             Select Case ctl.ControlType
>             Case acComboBox, acListBox
>                 strQryName = BldSavedQuery(frm.Name & "-" & ctl.Name,
>ctl.RowSource)
>                 If Len(strQryName) > 0 Then
>                     ctl.RowSource = strQryName
>                 End If
>             Case Else
>             End Select
>
>         Next ctl
>         DoCmd.Close acForm, doc.Name, acSaveYes
>     Next doc
>Exit_FindSQL:
>On Error Resume Next
>     If Not (frm Is Nothing) Then frm.Close: Set frm = Nothing
>     If Not (db Is Nothing) Then db.Close: Set db = Nothing Exit 
>Function
>Err_FindSQL:
>         MsgBox Err.Description, , "Error in Function
basFindSQL.FindSQL"
>         Resume Exit_FindSQL
>     Resume 0    '.FOR TROUBLESHOOTING
>End Function
>
>John W. Colby
>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
>
>_______________________________________________
>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 harkinsss at bellsouth.net  Tue Jan 24 18:15:00 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Tue, 24 Jan 2006 19:15:00 -0500
Subject: [dba-SQLServer] I've had enough!
Message-ID: <002501c62144$a32065e0$abb3d6d1@SUSANONE>

I hate to bi*ch <cough> -- but I have just had enough of MS. 
 
Anyone working with the Express beta knows that it's a pia to install -- and
I'm not the only one that's had problems. Well, to install Management
Studio, I had to reformat and start over fresh. <fume>
 
I need to download and install VB Express -- and GUESS WHAT??????????? I
have to uninstall everything first!  What made me think that it would just
be an easy process??????? 
 
I am so sick of this I am ready to tell them all thank you just the same,
but I'll use Oracle from now on. I truly am. 
 
Anyone else as sick of this as I am? I mean, there's a whole list of things
you have to uninstall and reinstall -- and if you're reinstaller number one
million four hundred thousand and sixty three, well... they let you slide
and it all works. :( Twice during the beta process I've had to reformat and
start over because there was something that Express didn't like. :( 
 
If I have to reformat and start over again I'm going to catch a plane to
Redmon and kick some MS butt! :( 
 
Susan H. 



From dmcafee at pacbell.net  Tue Jan 24 18:21:44 2006
From: dmcafee at pacbell.net (David McAfee)
Date: Tue, 24 Jan 2006 16:21:44 -0800
Subject: [dba-SQLServer] I've had enough!
In-Reply-To: <002501c62144$a32065e0$abb3d6d1@SUSANONE>
Message-ID: <MAELJIKADABIDLHFDKKNMEMNCHAA.dmcafee@pacbell.net>

Yup. But that's the name of the game if you want to stay on the cutting
edge.

Out of laziness, I tend to let everyone else work out the bugs. I just
recently made the move to XP, so that shows how quick I was to jump on their
latest software :)

D

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Susan
Harkins
Sent: Tuesday, January 24, 2006 4:15 PM
To: SQLList
Subject: [dba-SQLServer] I've had enough!


I hate to bi*ch <cough> -- but I have just had enough of MS.

Anyone working with the Express beta knows that it's a pia to install -- and
I'm not the only one that's had problems. Well, to install Management
Studio, I had to reformat and start over fresh. <fume>

I need to download and install VB Express -- and GUESS WHAT??????????? I
have to uninstall everything first!  What made me think that it would just
be an easy process???????

I am so sick of this I am ready to tell them all thank you just the same,
but I'll use Oracle from now on. I truly am.

Anyone else as sick of this as I am? I mean, there's a whole list of things
you have to uninstall and reinstall -- and if you're reinstaller number one
million four hundred thousand and sixty three, well... they let you slide
and it all works. :( Twice during the beta process I've had to reformat and
start over because there was something that Express didn't like. :(

If I have to reformat and start over again I'm going to catch a plane to
Redmon and kick some MS butt! :(

Susan H.

_______________________________________________
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 Jan 24 18:30:35 2006
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Wed, 25 Jan 2006 10:30:35 +1000
Subject: [dba-SQLServer] I've had enough!
In-Reply-To: <002501c62144$a32065e0$abb3d6d1@SUSANONE>
Message-ID: <43D7534B.5758.47D22A6@stuart.lexacorp.com.pg>

On 24 Jan 2006 at 19:15, Susan Harkins wrote:

> I hate to bi*ch <cough> -- but I have just had enough of MS. 
> 
> Anyone working with the Express beta knows that it's a pia to install -- and
...
> and it all works. :( Twice during the beta process I've had to reformat and
> start over because there was something that Express didn't like. :( 
> 

What does beta mean? :-)


-- 
Stuart




From harkinsss at bellsouth.net  Tue Jan 24 18:36:04 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Tue, 24 Jan 2006 19:36:04 -0500
Subject: [dba-SQLServer] I've had enough!
In-Reply-To: <43D7534B.5758.47D22A6@stuart.lexacorp.com.pg>
Message-ID: <002d01c62147$53d23ec0$abb3d6d1@SUSANONE>

Broken, best as I can figure. :) 

Susan H. 

What does beta mean? :-)




From harkinsss at bellsouth.net  Tue Jan 24 18:31:31 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Tue, 24 Jan 2006 19:31:31 -0500
Subject: [dba-SQLServer] I've had enough!
In-Reply-To: <MAELJIKADABIDLHFDKKNMEMNCHAA.dmcafee@pacbell.net>
Message-ID: <002601c62146$b15a24a0$abb3d6d1@SUSANONE>

I understand the costs and the risks early in a beta's life. At this point
though? No way -- this is just obscene. I didn't know the cutting edge was
gonna make me bleed!!!!!!!!! <groan> 

Now, the interesting thing is -- I downloaded and installed it anyway --
without uninstalling anything. I thought to myself -- surely at this point
it'll all work without all this fuss? 

Well, it's there and I can launch it -- don't know if it actually works yet.
Also, nothing else looks broken -- Express and Management Studio are still
running. 

Now, IF I had uninstalled and reinstalled everything as instructed and
learned later from someone else that I'd wasted my time, I would be even
more furious. 

I don't know what to be mad about -- that fact that I had to uninstall and
reinstall or the fact that I didn't! :) 

Susan H. 

Yup. But that's the name of the game if you want to stay on the cutting
edge.

Out of laziness, I tend to let everyone else work out the bugs. I just
recently made the move to XP, so that shows how quick I was to jump on their
latest software :)

D

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Susan
Harkins
Sent: Tuesday, January 24, 2006 4:15 PM
To: SQLList
Subject: [dba-SQLServer] I've had enough!


I hate to bi*ch <cough> -- but I have just had enough of MS.

Anyone working with the Express beta knows that it's a pia to install -- and
I'm not the only one that's had problems. Well, to install Management
Studio, I had to reformat and start over fresh. <fume>

I need to download and install VB Express -- and GUESS WHAT??????????? I
have to uninstall everything first!  What made me think that it would just
be an easy process???????

I am so sick of this I am ready to tell them all thank you just the same,
but I'll use Oracle from now on. I truly am.

Anyone else as sick of this as I am? I mean, there's a whole list of things
you have to uninstall and reinstall -- and if you're reinstaller number one
million four hundred thousand and sixty three, well... they let you slide
and it all works. :( Twice during the beta process I've had to reformat and
start over because there was something that Express didn't like. :(

If I have to reformat and start over again I'm going to catch a plane to
Redmon and kick some MS butt! :(

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

--
Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 1/14/2006
 



From fhtapia at gmail.com  Tue Jan 24 19:00:47 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Tue, 24 Jan 2006 17:00:47 -0800
Subject: [dba-SQLServer] Peregrine PND
Message-ID: <b874372a0601241700w1c3ac252w85e67413d5bba61a@mail.gmail.com>

I'm going to be in a demo this friday on this system "Peregrine PND" I
googled but did not get any resonable hits, has anybody heard of this CRM or
DB system?  I hear that it's supposed to be for a helpdesk?

Thanks,

--
-Francisco
http://pcthis.blogspot.com |PC news with out the jargon!
http://sqlthis.blogspot.com | Tsql and More...


From accessd at shaw.ca  Tue Jan 24 19:06:55 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Tue, 24 Jan 2006 17:06:55 -0800
Subject: [dba-SQLServer] I've had enough!
In-Reply-To: <002501c62144$a32065e0$abb3d6d1@SUSANONE>
Message-ID: <001901c6214b$a25103c0$017ba8c0@xpserver>

MS has been recommending using the Virtual Server app for loading new
environments within. That may be because there may be some hostility between
older products? In the last few MS product releases they have been giving
away full featured unlimited Virtual Server CDs.

It might be worth installing the product seeing you already have a clean
install.

HTH
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: January 24, 2006 4:15 PM
To: SQLList
Subject: [dba-SQLServer] I've had enough!

I hate to bi*ch <cough> -- but I have just had enough of MS. 
 
Anyone working with the Express beta knows that it's a pia to install -- and
I'm not the only one that's had problems. Well, to install Management
Studio, I had to reformat and start over fresh. <fume>
 
I need to download and install VB Express -- and GUESS WHAT??????????? I
have to uninstall everything first!  What made me think that it would just
be an easy process??????? 
 
I am so sick of this I am ready to tell them all thank you just the same,
but I'll use Oracle from now on. I truly am. 
 
Anyone else as sick of this as I am? I mean, there's a whole list of things
you have to uninstall and reinstall -- and if you're reinstaller number one
million four hundred thousand and sixty three, well... they let you slide
and it all works. :( Twice during the beta process I've had to reformat and
start over because there was something that Express didn't like. :( 
 
If I have to reformat and start over again I'm going to catch a plane to
Redmon and kick some MS butt! :( 
 
Susan H. 

_______________________________________________
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 Jan 24 19:08:52 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Tue, 24 Jan 2006 17:08:52 -0800
Subject: [dba-SQLServer] I've had enough!
In-Reply-To: <002601c62146$b15a24a0$abb3d6d1@SUSANONE>
References: <MAELJIKADABIDLHFDKKNMEMNCHAA.dmcafee@pacbell.net>
	<002601c62146$b15a24a0$abb3d6d1@SUSANONE>
Message-ID: <b874372a0601241708q2be72240ha7646f41f6c98489@mail.gmail.com>

Susan,
    We just upgraded to using Virtual Machines (it's the same really if you
go with virutal pc's)  the beauty is that you can install beta-ware till the
cows come home and work out the bugs without becomeing too frustrated.  I've
been loving them.. I have a functional domain server running on a VM and
it's running Idera's Sql Diagnostic Manager.  nice... i didn't have to
install the software on my machine... now I get to try out sql spotlight on
another set of machines just to test it out... tho quest spotlight is a
little more intrusive because it creates db's at each server and drops off
some client-ware.. i'll need to run a virtulazied version of some of my
servers for the test on that one.. :)

--
Francisco

On 1/24/06, Susan Harkins <harkinsss at bellsouth.net> wrote:
>
> I understand the costs and the risks early in a beta's life. At this point
> though? No way -- this is just obscene. I didn't know the cutting edge was
> gonna make me bleed!!!!!!!!! <groan>
>
> Now, the interesting thing is -- I downloaded and installed it anyway --
> without uninstalling anything. I thought to myself -- surely at this point
> it'll all work without all this fuss?
>
> Well, it's there and I can launch it -- don't know if it actually works
> yet.
> Also, nothing else looks broken -- Express and Management Studio are still
> running.
>
> Now, IF I had uninstalled and reinstalled everything as instructed and
> learned later from someone else that I'd wasted my time, I would be even
> more furious.
>
> I don't know what to be mad about -- that fact that I had to uninstall and
> reinstall or the fact that I didn't! :)
>
> Susan H.
>
> Yup. But that's the name of the game if you want to stay on the cutting
> edge.
>
> Out of laziness, I tend to let everyone else work out the bugs. I just
> recently made the move to XP, so that shows how quick I was to jump on
> their
> latest software :)
>
> D
>
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Susan
> Harkins
> Sent: Tuesday, January 24, 2006 4:15 PM
> To: SQLList
> Subject: [dba-SQLServer] I've had enough!
>
>
> I hate to bi*ch <cough> -- but I have just had enough of MS.
>
> Anyone working with the Express beta knows that it's a pia to install --
> and
> I'm not the only one that's had problems. Well, to install Management
> Studio, I had to reformat and start over fresh. <fume>
>
> I need to download and install VB Express -- and GUESS WHAT??????????? I
> have to uninstall everything first!  What made me think that it would just
> be an easy process???????
>
> I am so sick of this I am ready to tell them all thank you just the same,
> but I'll use Oracle from now on. I truly am.
>
> Anyone else as sick of this as I am? I mean, there's a whole list of
> things
> you have to uninstall and reinstall -- and if you're reinstaller number
> one
> million four hundred thousand and sixty three, well... they let you slide
> and it all works. :( Twice during the beta process I've had to reformat
> and
> start over because there was something that Express didn't like. :(
>
> If I have to reformat and start over again I'm going to catch a plane to
> Redmon and kick some MS butt! :(
>
> 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
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 1/14/2006
>
>
> _______________________________________________
> 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 Jan 24 23:09:47 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Wed, 25 Jan 2006 00:09:47 -0500
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server
Message-ID: <00b201c6216d$9085fd90$647aa8c0@ColbyM6805>

I need a "step by step" if you will of moving some object to SQL Server -
combo or form - where the Access query was filtered and the filter won't
work in SQL Server.  For example a reference to a control on a form.

I know that I have to create a SP in SQL Server that accepts a parameter.
How do I "connect" to that query from Access?  Is it a n ODBC (or other?)
link, just like a table?  Then how do I feed the parameters to the SP out in
SQL server.

I am getting ready to do this and am way under prepared for this.  

Environment:

SQL Server Express 2005
Access (Office) XP or 2003
Fes now talking to the SQL Server BE using the standard (ODBC I think)
"links" that the upsize wizard created when it moved the tables.

The FE seems to work as it did before except slower.  Now if I can start
replacing the slow "Access Queries over ODBC" with "SQL Server SPs with
passed params????" I might be able to see what this is capable of.  I just
haven't a clue how to move to that "SP with Params".

John W. Colby
www.ColbyConsulting.com 




From fhtapia at gmail.com  Tue Jan 24 23:41:19 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Tue, 24 Jan 2006 21:41:19 -0800
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server
In-Reply-To: <00b201c6216d$9085fd90$647aa8c0@ColbyM6805>
References: <00b201c6216d$9085fd90$647aa8c0@ColbyM6805>
Message-ID: <b874372a0601242141j185ebd0cg783880b39b95542a@mail.gmail.com>

John,
    If you intend to use the access front end  with odbc, then I suggest you
take a good look at ODBC pass-through queries.  if you're going to be using
the FE as an ADP then with Access 2003 you can at least call the sproc as
you do with ado and then set the combo box's recrodset to the ado's
recordset.   I find ADPs to be quite fast, in fact I haven't built a classic
Access FE in almost 2 years :|.





On 1/24/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> I need a "step by step" if you will of moving some object to SQL Server -
> combo or form - where the Access query was filtered and the filter won't
> work in SQL Server.  For example a reference to a control on a form.
>
> I know that I have to create a SP in SQL Server that accepts a parameter.
> How do I "connect" to that query from Access?  Is it a n ODBC (or other?)
> link, just like a table?  Then how do I feed the parameters to the SP out
> in
> SQL server.
>
> I am getting ready to do this and am way under prepared for this.
>
> Environment:
>
> SQL Server Express 2005
> Access (Office) XP or 2003
> Fes now talking to the SQL Server BE using the standard (ODBC I think)
> "links" that the upsize wizard created when it moved the tables.
>
> The FE seems to work as it did before except slower.  Now if I can start
> replacing the slow "Access Queries over ODBC" with "SQL Server SPs with
> passed params????" I might be able to see what this is capable of.  I just
> haven't a clue how to move to that "SP with Params".
>
> John W. Colby
> www.ColbyConsulting.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 Jan 24 23:48:42 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Tue, 24 Jan 2006 21:48:42 -0800
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <00fe01c61e3c$864ad500$647aa8c0@ColbyM6805>
References: <001f01c61e24$bfcd0c20$9eb3d6d1@SUSANONE>
	<00fe01c61e3c$864ad500$647aa8c0@ColbyM6805>
Message-ID: <b874372a0601242148v16a2de18gfa020630b723c2e4@mail.gmail.com>

I need to ready why this is a dead end road... tho i am looking at upsizing
my adp to a full blown VB.net app.

On 1/20/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> ...  It's interesting now because all of the
> literature out there discusses upsizing to ADPs and now that is a dead end
> road.  ...




--
-Francisco
http://pcthis.blogspot.com |PC news with out the jargon!
http://sqlthis.blogspot.com | Tsql and More...


From accessd at shaw.ca  Wed Jan 25 00:41:28 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Tue, 24 Jan 2006 22:41:28 -0800
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server
In-Reply-To: <00b201c6216d$9085fd90$647aa8c0@ColbyM6805>
Message-ID: <000b01c6217a$603a5480$017ba8c0@xpserver>

Hi John:

1. Set the ADO objects
2. Create an ADO connection.
3. Create a SP on the SQL that will accept parameters.
4. Set up a recordset to received data from the SP.

5. When the recordset is populated use its data to fill the combo/list box
   (use the old combo box object if you do not have it I will send you a
working copy but I think you do.)

Every time a change is made in the request (filter) processes from 1 to 5
are invoked. If you need code samples I will be glad to send then to you.
	 
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: January 24, 2006 9:10 PM
To: 'Access Developers discussion and problem solving';
dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server

I need a "step by step" if you will of moving some object to SQL Server -
combo or form - where the Access query was filtered and the filter won't
work in SQL Server.  For example a reference to a control on a form.

I know that I have to create a SP in SQL Server that accepts a parameter.
How do I "connect" to that query from Access?  Is it a n ODBC (or other?)
link, just like a table?  Then how do I feed the parameters to the SP out in
SQL server.

I am getting ready to do this and am way under prepared for this.  

Environment:

SQL Server Express 2005
Access (Office) XP or 2003
Fes now talking to the SQL Server BE using the standard (ODBC I think)
"links" that the upsize wizard created when it moved the tables.

The FE seems to work as it did before except slower.  Now if I can start
replacing the slow "Access Queries over ODBC" with "SQL Server SPs with
passed params????" I might be able to see what this is capable of.  I just
haven't a clue how to move to that "SP with Params".

John W. Colby
www.ColbyConsulting.com 


_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From mikedorism at verizon.net  Wed Jan 25 06:48:50 2006
From: mikedorism at verizon.net (Mike & Doris Manning)
Date: Wed, 25 Jan 2006 07:48:50 -0500
Subject: [dba-SQLServer] Access Connection to SQL Server
 (was:	Upsizewizard and named queries)
In-Reply-To: <000201c6208b$5c723790$0200a8c0@danwaters>
Message-ID: <000001c621ad$b20e0580$2f01a8c0@dorismanning>

I have not used SQLOLEDB as the service provider.

Doris Manning
mikedorism at verizon.net





From jwcolby at ColbyConsulting.com  Wed Jan 25 06:58:19 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Wed, 25 Jan 2006 07:58:19 -0500
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <b874372a0601242148v16a2de18gfa020630b723c2e4@mail.gmail.com>
Message-ID: <00bb01c621af$043f0470$647aa8c0@ColbyM6805>

MS has plainly stated that ADPs will not be supported (at least in the same
way) in future versions of Access.  They don't break but the inbuilt editing
of SPs etc go away. 


John W. Colby
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: Wednesday, January 25, 2006 12:49 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Upsize wizard and named queries

I need to ready why this is a dead end road... tho i am looking at upsizing
my adp to a full blown VB.net app.

On 1/20/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> ...  It's interesting now because all of the literature out there 
> discusses upsizing to ADPs and now that is a dead end road.  ...




--
-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 harkinsss at bellsouth.net  Wed Jan 25 08:18:20 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Wed, 25 Jan 2006 09:18:20 -0500
Subject: [dba-SQLServer] I've had enough!
In-Reply-To: <001901c6214b$a25103c0$017ba8c0@xpserver>
Message-ID: <001301c621ba$45844d90$dfb3d6d1@SUSANONE>

This is probably the last time. Once Access 12 is out and about, I probably
will fall by the wayside. I've had enough. I'm writing more and more
non-fiction for kids and MS has spoiled things for me -- well... I had to
sound like sour grapes, but I'm just tired of trying to keep up. 

Susan H. 

MS has been recommending using the Virtual Server app for loading new
environments within. That may be because there may be some hostility between
older products? In the last few MS product releases they have been giving
away full featured unlimited Virtual Server CDs.

It might be worth installing the product seeing you already have a clean
install.




From mwp.reid at qub.ac.uk  Wed Jan 25 08:22:25 2006
From: mwp.reid at qub.ac.uk (Martin Reid)
Date: Wed, 25 Jan 2006 14:22:25 -0000
Subject: [dba-SQLServer] I've had enough!
References: <001301c621ba$45844d90$dfb3d6d1@SUSANONE>
Message-ID: <D0BF9C78D1C45C418541C852C8944FE2025E34@qub-xchange-01.ads.qub.ac.uk>

Funny Susan been thinking that myself. Access 12 is just different not the fun product it was. Took me a week just to work out where at the menu stuff had gone. 
 
Martin

________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of Susan Harkins
Sent: Wed 25/01/2006 14:18
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] I've had enough!



This is probably the last time. Once Access 12 is out and about, I probably
will fall by the wayside. I've had enough. I'm writing more and more
non-fiction for kids and MS has spoiled things for me -- well... I had to
sound like sour grapes, but I'm just tired of trying to keep up.

Susan H.

MS has been recommending using the Virtual Server app for loading new
environments within. That may be because there may be some hostility between
older products? In the last few MS product releases they have been giving
away full featured unlimited Virtual Server CDs.

It might be worth installing the product seeing you already have a clean
install.


_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com




From harkinsss at bellsouth.net  Wed Jan 25 09:08:20 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Wed, 25 Jan 2006 10:08:20 -0500
Subject: [dba-SQLServer] I've had enough!
In-Reply-To: <D0BF9C78D1C45C418541C852C8944FE2025E34@qub-xchange-01.ads.qub.ac.uk>
Message-ID: <001901c621c1$2ec73610$dfb3d6d1@SUSANONE>

As long as MS was producing new and improved stuff, I didn't mind the
changes. But they've turned everything upside down now -- and even that is
probably good, in the long run, for the end users and developers. I only
know that I can't be an expert in x number of technologies to remain
competitive -- especially when they change radically. I have always been one
of MS's biggest fans, but I think I'm finally done with them. Enough is
enough -- especially when computer journalism no longer makes me rich. :) 

Susan H. 


Funny Susan been thinking that myself. Access 12 is just different not the
fun product it was. Took me a week just to work out where at the menu stuff
had gone. 



From dwaters at usinternet.com  Wed Jan 25 10:31:52 2006
From: dwaters at usinternet.com (Dan Waters)
Date: Wed, 25 Jan 2006 10:31:52 -0600
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server
In-Reply-To: <21498663.1138167957755.JavaMail.root@sniper16>
Message-ID: <001101c621cc$d99e8f10$0200a8c0@danwaters>

Franciso,

What service provider(s) do you use in your ADP's?  Why did you select those
providers?

I'm trying to learn about speed, updateability, etc. between and Access FE
and a SQL Server BE.

Thanks,
Dan

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco
Tapia
Sent: Tuesday, January 24, 2006 11:41 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Moving some object's recordsource to SQL Server

John,
    If you intend to use the access front end  with odbc, then I suggest you
take a good look at ODBC pass-through queries.  if you're going to be using
the FE as an ADP then with Access 2003 you can at least call the sproc as
you do with ado and then set the combo box's recrodset to the ado's
recordset.   I find ADPs to be quite fast, in fact I haven't built a classic
Access FE in almost 2 years :|.





On 1/24/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> I need a "step by step" if you will of moving some object to SQL Server -
> combo or form - where the Access query was filtered and the filter won't
> work in SQL Server.  For example a reference to a control on a form.
>
> I know that I have to create a SP in SQL Server that accepts a parameter.
> How do I "connect" to that query from Access?  Is it a n ODBC (or other?)
> link, just like a table?  Then how do I feed the parameters to the SP out
> in
> SQL server.
>
> I am getting ready to do this and am way under prepared for this.
>
> Environment:
>
> SQL Server Express 2005
> Access (Office) XP or 2003
> Fes now talking to the SQL Server BE using the standard (ODBC I think)
> "links" that the upsize wizard created when it moved the tables.
>
> The FE seems to work as it did before except slower.  Now if I can start
> replacing the slow "Access Queries over ODBC" with "SQL Server SPs with
> passed params????" I might be able to see what this is capable of.  I just
> haven't a clue how to move to that "SP with Params".
>
> John W. Colby
> www.ColbyConsulting.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 rl_stewart at highstream.net  Wed Jan 25 11:59:51 2006
From: rl_stewart at highstream.net (Robert L. Stewart)
Date: Wed, 25 Jan 2006 11:59:51 -0600
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server
In-Reply-To: <mailman.1123.1138165795.18500.dba-sqlserver@databaseadviso
	rs.com>
References: <mailman.1123.1138165795.18500.dba-sqlserver@databaseadvisors.com>
Message-ID: <6.2.3.4.2.20060125115832.03109998@pop3.highstream.net>

John,

One way is with a pass-through query, where you rewrite the SQL 
statement for the query with the parameter each time you want to run it.

Robert

At 11:09 PM 1/24/2006, you wrote:
>Date: Wed, 25 Jan 2006 00:09:47 -0500
>From: "John Colby" <jwcolby at ColbyConsulting.com>
>Subject: [dba-SQLServer] Moving some object's recordsource to SQL
>         Server
>To: "'Access Developers discussion and problem solving'"
>         <accessd at databaseadvisors.com>, <dba-sqlserver at databaseadvisors.com>
>Message-ID: <00b201c6216d$9085fd90$647aa8c0 at ColbyM6805>
>Content-Type: text/plain;       charset="us-ascii"
>
>I need a "step by step" if you will of moving some object to SQL Server -
>combo or form - where the Access query was filtered and the filter won't
>work in SQL Server.  For example a reference to a control on a form.
>
>I know that I have to create a SP in SQL Server that accepts a parameter.
>How do I "connect" to that query from Access?  Is it a n ODBC (or other?)
>link, just like a table?  Then how do I feed the parameters to the SP out in
>SQL server.
>
>I am getting ready to do this and am way under prepared for this.
>
>Environment:
>
>SQL Server Express 2005
>Access (Office) XP or 2003
>Fes now talking to the SQL Server BE using the standard (ODBC I think)
>"links" that the upsize wizard created when it moved the tables.
>
>The FE seems to work as it did before except slower.  Now if I can start
>replacing the slow "Access Queries over ODBC" with "SQL Server SPs with
>passed params????" I might be able to see what this is capable of.  I just
>haven't a clue how to move to that "SP with Params".
>
>John W. Colby




From cfoust at infostatsystems.com  Wed Jan 25 12:08:51 2006
From: cfoust at infostatsystems.com (Charlotte Foust)
Date: Wed, 25 Jan 2006 10:08:51 -0800
Subject: [dba-SQLServer] I've had enough!
Message-ID: <F55048AF7E974F429BB24597D7355EEABF57@INFOSERVER04.infostat.local>

Yeah, I've been an MS stalwart since the early days of Windows but I'm
ready to shift into freelance copywriting myself.  Programming isn't as
much fun any more.  :o{

Charlotte Foust


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: Wednesday, January 25, 2006 6:18 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] I've had enough!


This is probably the last time. Once Access 12 is out and about, I
probably will fall by the wayside. I've had enough. I'm writing more and
more non-fiction for kids and MS has spoiled things for me -- well... I
had to sound like sour grapes, but I'm just tired of trying to keep up. 

Susan H. 

MS has been recommending using the Virtual Server app for loading new
environments within. That may be because there may be some hostility
between older products? In the last few MS product releases they have
been giving away full featured unlimited Virtual Server CDs.

It might be worth installing the product seeing you already have a clean
install.


_______________________________________________
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  Wed Jan 25 14:24:22 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Wed, 25 Jan 2006 12:24:22 -0800
Subject: [dba-SQLServer] Textbox (Reporting Services)
Message-ID: <b874372a0601251224pa828494g9ba3ab9cdd13a3da@mail.gmail.com>

I have a textbox in a table that points to sums of values in a recordset, no
problem... i have a 2nd textbox which I want to do calculations on the
results from the textbox26 in this case...

I tried =ReportItems!table1!Textbox26.Value all to no avail... anybody have
any ideas?

--
-Francisco
http://pcthis.blogspot.com |PC news with out the jargon!
http://sqlthis.blogspot.com | Tsql and More...


From harkinsss at bellsouth.net  Wed Jan 25 15:45:06 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Wed, 25 Jan 2006 16:45:06 -0500
Subject: [dba-SQLServer] Textbox (Reporting Services)
In-Reply-To: <b874372a0601251224pa828494g9ba3ab9cdd13a3da@mail.gmail.com>
Message-ID: <001001c621f8$9bd26220$a4b3d6d1@SUSANONE>

How about just plain =Textbox.26.Value -- the textbox is the name of the
control right? It isn't the name of a column in your table, right?

Susan H. 

I tried =ReportItems!table1!Textbox26.Value all to no avail... anybody have
any ideas?




From fhtapia at gmail.com  Wed Jan 25 17:55:28 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Wed, 25 Jan 2006 15:55:28 -0800
Subject: [dba-SQLServer] Textbox (Reporting Services)
In-Reply-To: <001001c621f8$9bd26220$a4b3d6d1@SUSANONE>
References: <b874372a0601251224pa828494g9ba3ab9cdd13a3da@mail.gmail.com>
	<001001c621f8$9bd26220$a4b3d6d1@SUSANONE>
Message-ID: <b874372a0601251555l553a6c0aqcdcb93e4d004e2ec@mail.gmail.com>

it is actually a cell in the footer row of my table1... i didn't think of
creating a textbox and doing it that way tho... :D

On 1/25/06, Susan Harkins <harkinsss at bellsouth.net> wrote:
>
> How about just plain =Textbox.26.Value -- the textbox is the name of the
> control right? It isn't the name of a column in your table, right?
>
> Susan H.
>
> I tried =ReportItems!table1!Textbox26.Value all to no avail... anybody
> have
> any ideas?
>
>
> _______________________________________________
> 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 dmcafee at pacbell.net  Wed Jan 25 18:09:13 2006
From: dmcafee at pacbell.net (David Mcafee)
Date: Wed, 25 Jan 2006 16:09:13 -0800 (PST)
Subject: [dba-SQLServer] Textbox (Reporting Services)
In-Reply-To: <b874372a0601251224pa828494g9ba3ab9cdd13a3da@mail.gmail.com>
Message-ID: <20060126000914.2694.qmail@web80806.mail.yahoo.com>

=SomeFunctionName
  
  or in some even such as OnCurrent or AfterUpdate of someother control set the value.
  
  If this is a report do it in the OnFormat event.
  
  ;)
  
  D

Francisco Tapia <fhtapia at gmail.com> wrote:  I have a textbox in a table that points to sums of values in a recordset, no
problem... i have a 2nd textbox which I want to do calculations on the
results from the textbox26 in this case...

I tried =ReportItems!table1!Textbox26.Value all to no avail... anybody have
any ideas?

--
-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  Wed Jan 25 18:39:11 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Wed, 25 Jan 2006 16:39:11 -0800
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <00bb01c621af$043f0470$647aa8c0@ColbyM6805>
References: <b874372a0601242148v16a2de18gfa020630b723c2e4@mail.gmail.com>
	<00bb01c621af$043f0470$647aa8c0@ColbyM6805>
Message-ID: <b874372a0601251639i391e9a7dr11b775dafd5699e8@mail.gmail.com>

do you have a link?... as for the inline editing of the SPs, that does not
affect me on my platform as I prefer QA than the ADP as sql dev tool.



On 1/25/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> MS has plainly stated that ADPs will not be supported (at least in the
> same
> way) in future versions of Access.  They don't break but the inbuilt
> editing
> of SPs etc go away.
>
>
> John W. Colby
> 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: Wednesday, January 25, 2006 12:49 AM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] Upsize wizard and named queries
>
> I need to ready why this is a dead end road... tho i am looking at
> upsizing
> my adp to a full blown VB.net app.
>
> On 1/20/06, John Colby <jwcolby at colbyconsulting.com> wrote:
> >
> > ...  It's interesting now because all of the literature out there
> > discusses upsizing to ADPs and now that is a dead end road.  ...
>
>
>
>
> --
> -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 jwcolby at ColbyConsulting.com  Wed Jan 25 20:40:48 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Wed, 25 Jan 2006 21:40:48 -0500
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <b874372a0601251639i391e9a7dr11b775dafd5699e8@mail.gmail.com>
Message-ID: <004201c62221$eb0a1710$6f00a8c0@ColbyM6805>

>do you have a link?... as for the inline editing of the SPs, that does not
affect me on my platform as I prefer QA than the ADP as sql dev tool.

http://www.databaseadvisors.com/gazette/sqlexpress.htm

 Thinking about Access and SQL Server 2005
Might I suggest: Plan to plan and test carefully too.
http://lab.msdn.microsoft.com/express/sql/
http://www.tegels.org/qara/

There's been an interesting thread on the SQL Server Newsgroups about this
topic. A developer was trying to create an ADP to work against express and
got this message:

You have connected to a version of SQL Server later than SQL Server 2000.
The version of Visual Studio or Access that you are using was released
before the version of SQL Server to which you are connected. For this
reason, you might encounter problems.

Mary Chipman from Microsoft posted this response:Andy Baron and Mary Chipman

You will not be able to use any of the designers with SQLS 2005 databases,
whether it's SQL Express or the Developer edition. IOW, you won't be able to
create databases, tables, views or any other database objects from an ADP.
The only support that is envisioned is that you will be able to connect an
Access front-end to a SQLS 2005 back end if it is running in SQLS 2000
compatibility mode, so your forms, reports and other local Access objects
should still run. There is no service pack or quick fix being planned as far
as I know because of the amount of work it would entail. If you stop to
think about it, it's pretty hard to see how accomodating new Yukon features
like CLR assemblies and complex data types in the ADP designers could be
achieved without a complete rewrite.

That said, with Access 2003, I was able to connect up to an instance of SQL
2005 (not in 2000 compatibility mode) and work with data with SQL2000
compatible data types. I was also able to stick XML into an XML-typed (but
not strongly-typed) column and have it work as expected.

The bottom line here seems to be that ADPs aren't worth investing new work
into today if you plan to go to SQL Server 2005 with them. However, my
limited testing of Access 2003 as the Frontend and SQL Server 2005 as
backend using linked tables seems to be okay. Time will tell, of course.

microsoft.private.sqlserver2005.dataaccess
http://communities.microsoft.com/newsgroups/default.asp

To amplify what Kent said, there are no plans for supporting designing SQL
Server objects using Access ADPs either now or in the future. You can use
Access to connect to a SQL Server 2005 database in 2000 compatibility mode,
but there is no support for new 2005 functionality being planned. It is
recommended that you use the client tools in SQL Server for creating new SQL
Server objects. There is also support in Whidbey for creating SQL Server
objects.

posted on Friday, August 20, 2004 2:03 PM  


John W. Colby
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: Wednesday, January 25, 2006 7:39 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Upsize wizard and named queries

do you have a link?... as for the inline editing of the SPs, that does not
affect me on my platform as I prefer QA than the ADP as sql dev tool.



On 1/25/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> MS has plainly stated that ADPs will not be supported (at least in the 
> same
> way) in future versions of Access.  They don't break but the inbuilt 
> editing of SPs etc go away.
>
>
> John W. Colby
> www.ColbyConsulting.com



From martyconnelly at shaw.ca  Wed Jan 25 21:07:16 2006
From: martyconnelly at shaw.ca (MartyConnelly)
Date: Wed, 25 Jan 2006 19:07:16 -0800
Subject: [dba-SQLServer] Upsize wizard and named queries
References: <b874372a0601242148v16a2de18gfa020630b723c2e4@mail.gmail.com>
	<00bb01c621af$043f0470$647aa8c0@ColbyM6805>
	<b874372a0601251639i391e9a7dr11b775dafd5699e8@mail.gmail.com>
Message-ID: <43D83CE4.7020807@shaw.ca>

One note on SQL Express being from Mary Chipman dated august 2004
This was on the beta newsgroup which has since been closed
maybe still available here microsoft.private.sqlserver2005.express
She is now working directly for Microsoft. She wrote several books on 
Access.


"You will not be able to use any of the designers with SQLS 2005
databases, whether it's SQL Express or the Developer edition. IOW,
you won't be able to create databases, tables, views or any other
database objects from an ADP. The only support that is envisioned is
that you will be able to connect an Access front-end to a SQLS 2005
back end if it is running in SQLS 2000 compatibility mode, so your
forms, reports and other local Access objects should still run.
There is no service pack or quick fix being planned as far as I know
because of the amount of work it would entail. If you stop to think
about it, it's pretty hard to see how accomodating new Yukon
features like CLR assemblies and complex data types in the ADP
designers could be achieved without a complete rewrite.

That said, with Access 2003, I was able to connect up to an instance
of SQL 2005 (not in 2000 compatibility mode) and work with data with
SQL2000 compatible data types. I was also able to stick XML into an
XML-typed (but not strongly-typed) column and have it work as
expected.

The bottom line here seems to be that ADPs aren't worth investing
new work into today if you plan to go to SQL Server 2005 with them.
However, my limited testing of Access 2003 as the Frontend and SQL
Server 2005 as backend using linked tables seems to be okay. Time
will tell, of course."

http://www.databaseadvisors.com/gazette/sqlexpress.htm

you can access available NG from Web interface like
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.programming 

or access the new MSDN Forums at
http://forums.microsoft.com/msdn/default.aspx?forumgroupid=19&siteid=1

http://lab.msdn.microsoft.com/express/readme/
a SQLExpress NNTP NG should be available soon as a forum as well, but...
but you can try postin here on in the existing SQL hierarchy..


Installing and Registering Visual Studio Express Editions
http://forums.microsoft.com/msdn/showforum.aspx?forumid=24&siteid=1

Francisco Tapia wrote:

>do you have a link?... as for the inline editing of the SPs, that does not
>affect me on my platform as I prefer QA than the ADP as sql dev tool.
>
>
>
>On 1/25/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>  
>
>>MS has plainly stated that ADPs will not be supported (at least in the
>>same
>>way) in future versions of Access.  They don't break but the inbuilt
>>editing
>>of SPs etc go away.
>>
>>
>>John W. Colby
>>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: Wednesday, January 25, 2006 12:49 AM
>>To: dba-sqlserver at databaseadvisors.com
>>Subject: Re: [dba-SQLServer] Upsize wizard and named queries
>>
>>I need to ready why this is a dead end road... tho i am looking at
>>upsizing
>>my adp to a full blown VB.net app.
>>
>>On 1/20/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>>    
>>
>>>...  It's interesting now because all of the literature out there
>>>discusses upsizing to ADPs and now that is a dead end road.  ...
>>>      
>>>
>>
>>
>>--
>>-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
>
>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada





From martyconnelly at shaw.ca  Wed Jan 25 21:13:44 2006
From: martyconnelly at shaw.ca (MartyConnelly)
Date: Wed, 25 Jan 2006 19:13:44 -0800
Subject: [dba-SQLServer] I've had enough!
References: <002501c62144$a32065e0$abb3d6d1@SUSANONE>
Message-ID: <43D83E68.9050608@shaw.ca>

This might help
http://lab.msdn.microsoft.com/express/readme/
look under
1.2. Uninstalling Express Editions
and specifically the link

To download a tool which may help you clean your machine in preparation 
for installing Visual Studio Express Edition Beta 2, please visit this 
link.  Please Note: This tool is not supported or thoroughly tested by 
Microsoft.  This is a free tool and you should use it at your own risk.  
No warranty or support is provided, express or implied.

Or use this forum
Installing and Registering Visual Studio Express Editions
http://forums.microsoft.com/msdn/showforum.aspx?forumid=24&siteid=1




Susan Harkins wrote:

>I hate to bi*ch <cough> -- but I have just had enough of MS. 
> 
>Anyone working with the Express beta knows that it's a pia to install -- and
>I'm not the only one that's had problems. Well, to install Management
>Studio, I had to reformat and start over fresh. <fume>
> 
>I need to download and install VB Express -- and GUESS WHAT??????????? I
>have to uninstall everything first!  What made me think that it would just
>be an easy process??????? 
> 
>I am so sick of this I am ready to tell them all thank you just the same,
>but I'll use Oracle from now on. I truly am. 
> 
>Anyone else as sick of this as I am? I mean, there's a whole list of things
>you have to uninstall and reinstall -- and if you're reinstaller number one
>million four hundred thousand and sixty three, well... they let you slide
>and it all works. :( Twice during the beta process I've had to reformat and
>start over because there was something that Express didn't like. :( 
> 
>If I have to reformat and start over again I'm going to catch a plane to
>Redmon and kick some MS butt! :( 
> 
>Susan H. 
>
>_
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada





From jwcolby at ColbyConsulting.com  Wed Jan 25 22:08:13 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Wed, 25 Jan 2006 23:08:13 -0500
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server
In-Reply-To: <000b01c6217a$603a5480$017ba8c0@xpserver>
Message-ID: <004301c6222e$21337be0$6f00a8c0@ColbyM6805>

Jim,

Please do send code samples.  Let's just discuss this for a minute though.

I am getting a bunch of different answers from build "pass through queries"
to "open ADO record sets" (with painfully little detail).

If I were to do a pass through query, what in the heck is a pass through
query?  These are the kinds of answers that I find frustrating, because they
just don't provide enough substance to do anything with.  If I knew what a
pass through query was, then I would not even be having this conversation.
How do I build one?  What does it look like?  How do I feed it parameters?
How do I reference it in a form or combo?

If I am going to use a recordset, I at least understand this idea, but can I
(for example) build a function that returns an ADO recordset, then set the
rowsource of the form / combo to "=MyADORs()"?  Do I need to set a "form
global" recordset object, get that set, then poke that RS object into the
form/combo's property?  

When I build a stored procedure in SQL Server, how do I make that visible in
Access?  Does it "look like" a linked table, visible in the table tab?  Is
it something similar except in the query window?  Is it just a connection
string in code somewhere?

Does anyone have any links to professionally written articles out on the
internet that show the code, the stored procedures, graphics of the
properties dialog for the object using the recordset/pass through query?

Understand that I am a FE/ JET BE kinda guy up to this point and any answer
that goes something like "use a pass through query" (as the old "microsoft
joke" goes) while perhaps technically correct is simply useless.

Thanks for the offer of details, please do send them my way.

John W. Colby
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: Wednesday, January 25, 2006 1:41 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Moving some object's recordsource to SQL Server

Hi John:

1. Set the ADO objects
2. Create an ADO connection.
3. Create a SP on the SQL that will accept parameters.
4. Set up a recordset to received data from the SP.

5. When the recordset is populated use its data to fill the combo/list box
   (use the old combo box object if you do not have it I will send you a
working copy but I think you do.)

Every time a change is made in the request (filter) processes from 1 to 5
are invoked. If you need code samples I will be glad to send then to you.
	 
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: January 24, 2006 9:10 PM
To: 'Access Developers discussion and problem solving';
dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server

I need a "step by step" if you will of moving some object to SQL Server -
combo or form - where the Access query was filtered and the filter won't
work in SQL Server.  For example a reference to a control on a form.

I know that I have to create a SP in SQL Server that accepts a parameter.
How do I "connect" to that query from Access?  Is it a n ODBC (or other?)
link, just like a table?  Then how do I feed the parameters to the SP out in
SQL server.

I am getting ready to do this and am way under prepared for this.  

Environment:

SQL Server Express 2005
Access (Office) XP or 2003
Fes now talking to the SQL Server BE using the standard (ODBC I think)
"links" that the upsize wizard created when it moved the tables.

The FE seems to work as it did before except slower.  Now if I can start
replacing the slow "Access Queries over ODBC" with "SQL Server SPs with
passed params????" I might be able to see what this is capable of.  I just
haven't a clue how to move to that "SP with Params".

John W. Colby
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 stuart at lexacorp.com.pg  Wed Jan 25 22:47:22 2006
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Thu, 26 Jan 2006 14:47:22 +1000
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server
In-Reply-To: <004301c6222e$21337be0$6f00a8c0@ColbyM6805>
References: <000b01c6217a$603a5480$017ba8c0@xpserver>
Message-ID: <43D8E0FA.27576.A8E968C@stuart.lexacorp.com.pg>

On 25 Jan 2006 at 23:08, John Colby wrote:
> 
> I am getting a bunch of different answers from build "pass through queries"
> to "open ADO record sets" (with painfully little detail).
> 
> If I were to do a pass through query, what in the heck is a pass through
> query?  These are the kinds of answers that I find frustrating, because they
> just don't provide enough substance to do anything with.  If I knew what a
> pass through query was, then I would not even be having this conversation.
> How do I build one?  
> 
>From Access Help:
<quote>
In the Database window, click Queries  under Objects, and then click New on 
the Database window toolbar. 
In the New Query dialog box, click Design View, and then click OK. 
Without adding tables or queries, click Close in the Show Table dialog box. 

On the Query menu, point to SQL Specific, and then click Pass-Through. 
On the toolbar, click Properties  to display the query property sheet. 
In the query property sheet, set the ODBCConnectStr property to specify 
information on the database to which you want to connect. You can type the 
connection information, or click Build , and then enter information about 
the server you're connecting to. 
When you are prompted to save the password in the connection string, select 
Yes if you want the password and logon stored in the connection string 
information. 
</quote>

> What does it look like?  

In the query window, when you open it or when you edit it? :-)
It looks like any othe SQL query in the QueryDefs collection
The SQL would just be "sp_MyStoredProcedure 1" assuming 1 was the value of 
the parameter you want to pass.

> How do I feed it parameters?

Ah-ha, that's the tricky bit - you need to rewrite the querydef before 
executing it.

> How do I reference it in a form or combo?

Here's an example if you are using DAO:

Function GetDataDAO() As Boolean
Dim qry As DAO.QueryDef
Dim rs As DAO.Recordset
Set qry = CurrentDb.QueryDefs("myQuery")
Set qry.SQL = "select * from mytable where id = " & cboIDSelector
Set rs = CurrentDb.OpenRecordset("myQuery")
...
End Function

> If I am going to use a recordset, I at least understand this idea, but can I
> (for example) build a function that returns an ADO recordset, then set the
> rowsource of the form / combo to "=MyADORs()"?  Do I need to set a "form
> global" recordset object, get that set, then poke that RS object into the
> form/combo's property?  
>

If you are using ADO, you don't need to use a passthrough query, you use an 
ADODB.Command:

Function GetDataADO() As Boolean
Dim cmd As ADODB.Command
Dim prm As ADODB.Parameter
Dim rs As ADODB.Recordset
    
cmd.CommandType = adCmdStoredProc
cmd.CommandText = "sp_MyStoredProcedure"
'....
Set prm = cmd.CreateParameter("myParam", adInteger, adParamInput, 4, 
cboIDSelector)
cmd.Parameters.Append prm
Set rs = cmd.Execute
....
End Function

-- 
Stuart




From stuart at lexacorp.com.pg  Wed Jan 25 22:51:30 2006
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Thu, 26 Jan 2006 14:51:30 +1000
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server
In-Reply-To: <43D8E0FA.27576.A8E968C@stuart.lexacorp.com.pg>
References: <004301c6222e$21337be0$6f00a8c0@ColbyM6805>
Message-ID: <43D8E1F2.32560.A925FB9@stuart.lexacorp.com.pg>

On 26 Jan 2006 at 14:47, Stuart McLachlan wrote:

> Set qry.SQL = "select * from mytable where id = " & cboIDSelector

Oops, that line is totally screwed up.

It should be:
qry.SQL = "sp_MyStoredProcedure " & cboIDSelector

i.e.  no "Set" and the SQL is the SP call




-- 
Stuart




From accessd at shaw.ca  Wed Jan 25 23:38:32 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Wed, 25 Jan 2006 21:38:32 -0800
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server
In-Reply-To: <004301c6222e$21337be0$6f00a8c0@ColbyM6805>
Message-ID: <000a01c6223a$be871850$017ba8c0@xpserver>

Hi John:

Do not use pass-through (ODBC) queries, I have found them to be notoriously
unstable and very slow. (Refer to Doris's email a couple of days ago.) Below
is an example that I use to fill list and combo boxes. I sent the same code
sample to Jim Moss and though the pasted together code chunks very carefully
checked I apologies if there is any errors or omissions.

You can probably encapsulate the whole process in a much more sophisticated
set of classes.
 
Here it is. All the parts should be here:

1. Set the ADO objects

Within an Access module:

Public gstrConnection As String
Private mobjConn As ADODB.Connection
Public rsMyRecordset As ADODB.Recordset
....

2. Create an ADO connection.

' To test that the connection is made. Note windows authentication is being
used. I usually attach a Windows user group to the MS SQL security section;
add a login form and everything is rock solid.  

gstrConnection = "Provider=SQLOLEDB; _
			Initial Catalog=MyMSSQLDatabse; _
			Data Source=MyMSSQLServer; _
			Integrated Security=SSPI"

'   Test connection string
Set mobjConn = New ADODB.Connection
mobjConn.ConnectionString = gstrConnection 
mobjConn.Open

' It should connect with no errors...

...

3. Create a SP on the MS SQL server (2005 version... same as SQL 2000) that
will accept parameters.

ALTER PROCEDURE [FindMatchingEmployees]
	@intEmpNumber INT
AS

SELECT RED.EmpNum
FROM RegisteredEmployeesDetail as RED
WHERE RED.EmpNum=@intEmpNumber


4. Set up a recordset to received data from the SP.

Public Function FillEmployeeDetail(lngEmployeeNumber as long) As Boolean
Dim objCmd As ADODB.Command
    
On Error GoTo Err_FillEmployPositions
    
FillEmployeeDetail = False

' It is as easy to pass twenty parameters as one.
' Each must be fully named.
' values can also be return from the SP.
 
Set objCmd = New ADODB.Command
With objCmd
 .ActiveConnection = gstrConnection
 .CommandText = "FindMatchingEmployees"
 .CommandType = adCmdStoredProc
 .Parameters.Append .CreateParameter("@intEmpNumber", adInteger,
adParamInput, , lngEmployeeNumber) 
End With

' Refresh and cleanup
If Not rsEmployeeDetail Is Nothing Then rsEmployeeDetail.close: Set
rsEmployeeDetail = Nothing

Set rsEmployeeDetail = New ADODB.Recordset

With rsEmployeeDetail
 .CursorLocation = adUseClient

 ' There are a number of different ways this can be configured on 
 ' how you want the connection to be handled... same as DAO. I tend
 ' to use disconnected recordsets and do a comparison between a changed
 ' local record and the same server record... under code. 

 .Open objCmd, , adOpenDynamic, adLockOptimistic 
    
 If .BOF = False Or .EOF = False Then .MoveLast End With

FillEmployeeDetail = True

Exit_ FillEmployeeDetail:
 Set objCmd = Nothing
 Exit Function
    
Err_ FillEmployeeDetail:
 ShowErrMsg " FillEmployeeDetail "
 Resume Exit_ FillEmployeeDetail	
    
End Function


5. When the recordset is populated use its data to fill the combo/list box
Populate a combo box:
Section A:

Public Function FillEmployeeList(ctlBox As Control, id As Variant, _
                row As Variant, col As Variant, _
                CODE As Variant) As Variant
    
Dim mvReturnVal As Variant
Dim Status as Boolean

'Common Combo and List box fill function.
'Assumes rsEmployees recordset is the supplied data and has 'equal or more
fields than required in the control.
    
On Error GoTo Err_ FillEmployeeList

Status = false
mvReturnVal = Null

' Populate recordset using a form field and subsequently combobox/list from
If rsMyRecordset Is Nothing Then  
 Status = FillEmployeeDetail(Form.Employee.text)
End if

With rsMyRecordset
 Select Case CODE
  Case acLBInitialize ' Initialize.
   If Status = true then             
    If .BOF = False Or .EOF = False Then
     .MoveFirst
      mvReturnVal = .RecordCount
     Else
      mvReturnVal = 0 
     end if
   else
    mvReturnVal = 0 'error no records
   End If

  Case acLBOpen        ' Open.
   mvReturnVal = Timer ' Generate unique ID for control.
   gvComboTimer = mvReturnVal

  Case acLBGetRowCount ' Get number of rows.
   mvReturnVal = .RecordCount

  Case acLBGetColumnCount ' Get number of columns.
   mvReturnVal = ctlBox.ColumnCount

  Case acLBGetColumnWidth ' Column width.
   mvReturnVal = -1 ' -1 forces use of default width.

  Case acLBGetFormat ' Get format
   mvReturnVal = -1

  Case acLBGetValue  ' Get data.
   .MoveFirst
   .Move (row)
   mvReturnVal = .Fields(col)
 End Select
End With
    
FillEmployeeList = mvReturnVal

Exit_FillEmployeeList:
 Exit Function
    
Err_ FillEmployeeList:
 'Handles error situation caused an apparent unrelated error(s)  'generated
in other modules. (It loses its brains...)  If Err.Number <> 91 Then
  ShowErrMsg "FillEmployeeList"
 End If
 Resume Exit_FillEmployeeList
    
End Function

Section B:
On the form in question a combo box or list named "cmbEmployeeList" in the
"Row Source Type" property is the name of the populating function,
"FillEmployeeList"


I think I have added all the pieces though some of the clean up and
simplification may have moved or removed some minor pieces. There is a lot
more detail but this should get you started. A system similar to this was
used by over a hundred user network extending across the province (state).
To handle reports view my article on populating reports at our DataBase
Advisors site:
http://www.databaseadvisors.com/newsletters/newsletter112003/0311UnboundRepo
rts.htm

HTH
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: January 25, 2006 8:08 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Moving some object's recordsource to SQL Server

Jim,

Please do send code samples.  Let's just discuss this for a minute though.

I am getting a bunch of different answers from build "pass through queries"
to "open ADO record sets" (with painfully little detail).

If I were to do a pass through query, what in the heck is a pass through
query?  These are the kinds of answers that I find frustrating, because they
just don't provide enough substance to do anything with.  If I knew what a
pass through query was, then I would not even be having this conversation.
How do I build one?  What does it look like?  How do I feed it parameters?
How do I reference it in a form or combo?

If I am going to use a recordset, I at least understand this idea, but can I
(for example) build a function that returns an ADO recordset, then set the
rowsource of the form / combo to "=MyADORs()"?  Do I need to set a "form
global" recordset object, get that set, then poke that RS object into the
form/combo's property?  

When I build a stored procedure in SQL Server, how do I make that visible in
Access?  Does it "look like" a linked table, visible in the table tab?  Is
it something similar except in the query window?  Is it just a connection
string in code somewhere?

Does anyone have any links to professionally written articles out on the
internet that show the code, the stored procedures, graphics of the
properties dialog for the object using the recordset/pass through query?

Understand that I am a FE/ JET BE kinda guy up to this point and any answer
that goes something like "use a pass through query" (as the old "microsoft
joke" goes) while perhaps technically correct is simply useless.

Thanks for the offer of details, please do send them my way.

John W. Colby
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: Wednesday, January 25, 2006 1:41 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Moving some object's recordsource to SQL Server

Hi John:

1. Set the ADO objects
2. Create an ADO connection.
3. Create a SP on the SQL that will accept parameters.
4. Set up a recordset to received data from the SP.

5. When the recordset is populated use its data to fill the combo/list box
   (use the old combo box object if you do not have it I will send you a
working copy but I think you do.)

Every time a change is made in the request (filter) processes from 1 to 5
are invoked. If you need code samples I will be glad to send then to you.
	 
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: January 24, 2006 9:10 PM
To: 'Access Developers discussion and problem solving';
dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server

I need a "step by step" if you will of moving some object to SQL Server -
combo or form - where the Access query was filtered and the filter won't
work in SQL Server.  For example a reference to a control on a form.

I know that I have to create a SP in SQL Server that accepts a parameter.
How do I "connect" to that query from Access?  Is it a n ODBC (or other?)
link, just like a table?  Then how do I feed the parameters to the SP out in
SQL server.

I am getting ready to do this and am way under prepared for this.  

Environment:

SQL Server Express 2005
Access (Office) XP or 2003
Fes now talking to the SQL Server BE using the standard (ODBC I think)
"links" that the upsize wizard created when it moved the tables.

The FE seems to work as it did before except slower.  Now if I can start
replacing the slow "Access Queries over ODBC" with "SQL Server SPs with
passed params????" I might be able to see what this is capable of.  I just
haven't a clue how to move to that "SP with Params".

John W. Colby
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



From jwcolby at ColbyConsulting.com  Thu Jan 26 00:30:34 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Thu, 26 Jan 2006 01:30:34 -0500
Subject: [dba-SQLServer] Building a pass through query
In-Reply-To: <43D8E0FA.27576.A8E968C@stuart.lexacorp.com.pg>
Message-ID: <004f01c62242$039fad60$6f00a8c0@ColbyM6805>

Cool, thanks Stuart.

I created a select SP out on the server, with two parameters (people
filtered by state ID and therapist discipline ID).  Tested it out there.  It
looks like this:

set ANSI_NULLS ON
set QUOTED_IDENTIFIER ON
go



-- =============================================
-- Author:		<Author,,Name>
-- Create date: <Create Date,,>
-- Description:	<Description,,>
-- =============================================
ALTER PROCEDURE [dbo].[spFrmCallListFiltered]
	-- Add the parameters for the stored procedure here
	@STID int,
	@DIID int
AS
BEGIN
	-- SET NOCOUNT ON added to prevent extra result sets from
	-- interfering with SELECT statements.
	SET NOCOUNT ON;

    -- Insert statements for procedure here
	SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, tblPeople.PE_Specialty,
tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
tblPeople.PE_Contact1, tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo,
tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
tblPeople.PE_Certification, tblPeople.PE_LIC_Licno, tlkpState_1.ST_Code AS
LicenseState, tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress,
tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell,
tblZipCntydistinct.CountyName, tblPeople.PE_IDDNC, tblPeople.PE_IDIWH,
tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate, tblPeople.PE_HotLead,
tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive,
tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
tblPeople.PE_LIC_IDDI
	FROM tlkpState RIGHT JOIN (tlkpCRF INNER JOIN (tblZipCntydistinct
RIGHT JOIN (tlkpState AS tlkpState_1 INNER JOIN tblPeople ON
tlkpState_1.ST_ID = tblPeople.PE_LIC_IDST) ON tblZipCntydistinct.ZipCode =
tblPeople.PE_Zipcode1) ON tlkpCRF.CRF_ID = tblPeople.PE_IDCRF) ON
tlkpState.ST_ID = tblPeople.PE_IDST
	WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
((tblPeople.PE_LIC_IDDI)=@DIID))
	ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;
END

This query was updateable back in the MDB version but does not appear to be
in SQL Server though I am not entirely (or even marginally) familiar with my
tool yet (SQL Server Management Studio Express - for SQL Server 2005
Express), so I can't really say that it is not.

At any rate, I then created a pass through query back in Access per your
instructions, which worked wonderfully thanks very much.  I hard coded
values for the state and discipline ID and can run the query and get data
from the query.  It definitely is NOT updateable back in Access.  Sigh.  

But hey, I am waaaay further along the path than I was at the beginning of
the night.  When I started I had to download (over the internet) the upsized
SQL Server database tables from the client's machine to my laptop, go get
and install management studio express on my laptop, "mount" the database,
relink the FE to the SQL Server db on my laptop, build my very first SP, and
build my very first pass through query.  I am able to see my FE work using
the "linked" odbc connections to the SQL Server BE, and I am able to at
least view the data from my first pass through query.  I just placed the
pass through query in place of the original query.

spFrmCallListFiltered 9,5

and went from 10 second loads to about 1 second load.  I am not yet actually
modifying the IDs dynamically, i.e. the PT query has the values hard coded
in the "SQL" in the querydef, but this is still amazing to me.  It seems
like I could open the query def and replace the 9,5 with whatever the user
selected from the state and discipline combos, save the query def and
requery the form.  Perhaps not too efficient but still...

Thanks again Stuart for stepping up with a "step by step".  That was enough
to get me going at least.

John W. Colby
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: Wednesday, January 25, 2006 11:47 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Moving some object's recordsource to SQL Server

On 25 Jan 2006 at 23:08, John Colby wrote:
> 
> I am getting a bunch of different answers from build "pass through
queries"
> to "open ADO record sets" (with painfully little detail).
> 
> If I were to do a pass through query, what in the heck is a pass 
> through query?  These are the kinds of answers that I find 
> frustrating, because they just don't provide enough substance to do 
> anything with.  If I knew what a pass through query was, then I would not
even be having this conversation.
> How do I build one?  
> 
>From Access Help:
<quote>
In the Database window, click Queries  under Objects, and then click New on
the Database window toolbar. 
In the New Query dialog box, click Design View, and then click OK. 
Without adding tables or queries, click Close in the Show Table dialog box. 

On the Query menu, point to SQL Specific, and then click Pass-Through. 
On the toolbar, click Properties  to display the query property sheet. 
In the query property sheet, set the ODBCConnectStr property to specify
information on the database to which you want to connect. You can type the
connection information, or click Build , and then enter information about
the server you're connecting to. 
When you are prompted to save the password in the connection string, select
Yes if you want the password and logon stored in the connection string
information. 
</quote>

> What does it look like?  

In the query window, when you open it or when you edit it? :-) It looks like
any othe SQL query in the QueryDefs collection The SQL would just be
"sp_MyStoredProcedure 1" assuming 1 was the value of the parameter you want
to pass.

> How do I feed it parameters?

Ah-ha, that's the tricky bit - you need to rewrite the querydef before
executing it.

> How do I reference it in a form or combo?

Here's an example if you are using DAO:

Function GetDataDAO() As Boolean
Dim qry As DAO.QueryDef
Dim rs As DAO.Recordset
Set qry = CurrentDb.QueryDefs("myQuery") Set qry.SQL = "select * from
mytable where id = " & cboIDSelector Set rs =
CurrentDb.OpenRecordset("myQuery")
...
End Function

> If I am going to use a recordset, I at least understand this idea, but 
> can I (for example) build a function that returns an ADO recordset, 
> then set the rowsource of the form / combo to "=MyADORs()"?  Do I need 
> to set a "form global" recordset object, get that set, then poke that 
> RS object into the form/combo's property?
>

If you are using ADO, you don't need to use a passthrough query, you use an
ADODB.Command:

Function GetDataADO() As Boolean
Dim cmd As ADODB.Command
Dim prm As ADODB.Parameter
Dim rs As ADODB.Recordset
    
cmd.CommandType = adCmdStoredProc
cmd.CommandText = "sp_MyStoredProcedure"
'....
Set prm = cmd.CreateParameter("myParam", adInteger, adParamInput, 4,
cboIDSelector)
cmd.Parameters.Append prm
Set rs = cmd.Execute
....
End Function

--
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 Jan 26 01:27:28 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Thu, 26 Jan 2006 02:27:28 -0500
Subject: [dba-SQLServer] SPs are read-only
Message-ID: <005001c62249$f6a82710$6f00a8c0@ColbyM6805>

Is there a magic incantation to make my SP editable?  My tables are
read/write but a simple SP that pulls the same data (filtered on a couple of
ID fields) is read-only.  Any thoughts on why this is?

TIA,

John W. Colby
www.ColbyConsulting.com 




From fhtapia at gmail.com  Thu Jan 26 01:32:39 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Wed, 25 Jan 2006 23:32:39 -0800
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <004201c62221$eb0a1710$6f00a8c0@ColbyM6805>
References: <b874372a0601251639i391e9a7dr11b775dafd5699e8@mail.gmail.com>
	<004201c62221$eb0a1710$6f00a8c0@ColbyM6805>
Message-ID: <b874372a0601252332jb4d62cav2cac35b02fb70caa@mail.gmail.com>

I refrained from using ADPs as a development tool for SQL BEs, it appears
that ADPs will continue being supported in the sense that you can use OLEDB
connections directly to SQL Server.  nothing on the way I currently
develop... which is actually quite nice, I hope to have the sproc screen
clear of just all the sprocs as it is now,  it in reality should have only
displayed sprocs that the user had rights to...



On 1/25/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> >do you have a link?... as for the inline editing of the SPs, that does
> not
> affect me on my platform as I prefer QA than the ADP as sql dev tool.
>
> http://www.databaseadvisors.com/gazette/sqlexpress.htm
>
> Thinking about Access and SQL Server 2005
> Might I suggest: Plan to plan and test carefully too.
> http://lab.msdn.microsoft.com/express/sql/
> http://www.tegels.org/qara/
>
> There's been an interesting thread on the SQL Server Newsgroups about this
> topic. A developer was trying to create an ADP to work against express and
> got this message:
>
> You have connected to a version of SQL Server later than SQL Server 2000.
> The version of Visual Studio or Access that you are using was released
> before the version of SQL Server to which you are connected. For this
> reason, you might encounter problems.
>
> Mary Chipman from Microsoft posted this response:Andy Baron and Mary
> Chipman
>
> You will not be able to use any of the designers with SQLS 2005 databases,
> whether it's SQL Express or the Developer edition. IOW, you won't be able
> to
> create databases, tables, views or any other database objects from an ADP.
> The only support that is envisioned is that you will be able to connect an
> Access front-end to a SQLS 2005 back end if it is running in SQLS 2000
> compatibility mode, so your forms, reports and other local Access objects
> should still run. There is no service pack or quick fix being planned as
> far
> as I know because of the amount of work it would entail. If you stop to
> think about it, it's pretty hard to see how accomodating new Yukon
> features
> like CLR assemblies and complex data types in the ADP designers could be
> achieved without a complete rewrite.
>
> That said, with Access 2003, I was able to connect up to an instance of
> SQL
> 2005 (not in 2000 compatibility mode) and work with data with SQL2000
> compatible data types. I was also able to stick XML into an XML-typed (but
> not strongly-typed) column and have it work as expected.
>
> The bottom line here seems to be that ADPs aren't worth investing new work
> into today if you plan to go to SQL Server 2005 with them. However, my
> limited testing of Access 2003 as the Frontend and SQL Server 2005 as
> backend using linked tables seems to be okay. Time will tell, of course.
>
> microsoft.private.sqlserver2005.dataaccess
> http://communities.microsoft.com/newsgroups/default.asp
>
> To amplify what Kent said, there are no plans for supporting designing SQL
> Server objects using Access ADPs either now or in the future. You can use
> Access to connect to a SQL Server 2005 database in 2000 compatibility
> mode,
> but there is no support for new 2005 functionality being planned. It is
> recommended that you use the client tools in SQL Server for creating new
> SQL
> Server objects. There is also support in Whidbey for creating SQL Server
> objects.
>
> posted on Friday, August 20, 2004 2:03 PM
>
>
> John W. Colby
> 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: Wednesday, January 25, 2006 7:39 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] Upsize wizard and named queries
>
> do you have a link?... as for the inline editing of the SPs, that does not
> affect me on my platform as I prefer QA than the ADP as sql dev tool.
>
>
>
> On 1/25/06, John Colby <jwcolby at colbyconsulting.com> wrote:
> >
> > MS has plainly stated that ADPs will not be supported (at least in the
> > same
> > way) in future versions of Access.  They don't break but the inbuilt
> > editing of SPs etc go away.
> >
> >
> > John W. Colby
> > www.ColbyConsulting.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 Jan 26 01:36:20 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Wed, 25 Jan 2006 23:36:20 -0800
Subject: [dba-SQLServer] SPs are read-only
In-Reply-To: <005001c62249$f6a82710$6f00a8c0@ColbyM6805>
References: <005001c62249$f6a82710$6f00a8c0@ColbyM6805>
Message-ID: <b874372a0601252336g150da4fveabcd778e27a566a@mail.gmail.com>

what options do you have for the ODBC passthrough query?... i'm a bit foggy
on these details but I think you need to have them set to dynamic snapshot.

if you're using an ADP, then you need to refernce the updateable table in
the form's property.

On 1/25/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> Is there a magic incantation to make my SP editable?  My tables are
> read/write but a simple SP that pulls the same data (filtered on a couple
> of
> ID fields) is read-only.  Any thoughts on why this is?
>
> TIA,
>
> John W. Colby
> www.ColbyConsulting.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 paul.hartland at fsmail.net  Thu Jan 26 01:39:32 2006
From: paul.hartland at fsmail.net (paul.hartland at fsmail.net)
Date: Thu, 26 Jan 2006 08:39:32 +0100 (CET)
Subject: [dba-SQLServer] SPs are read-only
Message-ID: <27386106.1138261172275.JavaMail.www@wwinf3002>

John,

As far as I am aware when you pull back data into an appliication using an SP it is read only, if you want to pull back data and make it editible then I have found you have to use a view (do as much filtering as possible here (well I do anyway)) and then use some code with a select statement to bring it into an editible recordset.
If anyone knows different about SP's then please tell me as well cause OH how I would love to have an editible store procedure.
Paul



Message Received: Jan 26 2006, 07:28 AM
From: "John Colby" 
To: dba-sqlserver at databaseadvisors.com
Cc: 
Subject: [dba-SQLServer] SPs are read-only

Is there a magic incantation to make my SP editable? My tables are
read/write but a simple SP that pulls the same data (filtered on a couple of
ID fields) is read-only. Any thoughts on why this is?

TIA,

John W. Colby
www.ColbyConsulting.com 


_______________________________________________
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  Thu Jan 26 02:06:37 2006
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Thu, 26 Jan 2006 18:06:37 +1000
Subject: [dba-SQLServer] SPs are read-only
In-Reply-To: <005001c62249$f6a82710$6f00a8c0@ColbyM6805>
Message-ID: <43D90FAD.14137.B450109@stuart.lexacorp.com.pg>

On 26 Jan 2006 at 2:27, John Colby wrote:

> Is there a magic incantation to make my SP editable?  My tables are
> read/write but a simple SP that pulls the same data (filtered on a couple of
> ID fields) is read-only.  Any thoughts on why this is?
> 

Make sure that  your recordset include the primary from every referenced 
table.





-- 
Stuart




From mikedorism at verizon.net  Thu Jan 26 07:09:11 2006
From: mikedorism at verizon.net (Mike & Doris Manning)
Date: Thu, 26 Jan 2006 08:09:11 -0500
Subject: [dba-SQLServer] Building a pass through query
In-Reply-To: <004f01c62242$039fad60$6f00a8c0@ColbyM6805>
Message-ID: <000001c62279$b44b2a90$2f01a8c0@dorismanning>

A couple of things come to mind...

1)  Do your tables have Primary Keys?  If not, they won't be updatable
outside of SQL.

2)  Did you give your SQL Login "dbo" permissions to the database so it
could execute stored procedures and views?

Doris Manning
mikedorism at verizon.net





From mikedorism at verizon.net  Thu Jan 26 07:36:29 2006
From: mikedorism at verizon.net (Mike & Doris Manning)
Date: Thu, 26 Jan 2006 08:36:29 -0500
Subject: [dba-SQLServer] SPs are read-only
In-Reply-To: <27386106.1138261172275.JavaMail.www@wwinf3002>
Message-ID: <000101c6227d$84372260$2f01a8c0@dorismanning>

John,

I'm amazed at the amount of "going around the bush to get to the barn"
information that you are getting from this list.  So far, the responses are
far more complicated than they need to be.

When I was first starting out, I found an ADO Primer website
(http://authors.aspalliance.com/aspxtreme/ado/index.aspx) that really helped
me understand the basics behind what I was trying to do.

There are also several really good books out there for working with SQL
Server within Access.  My favorite is "Professional SQL Server Development
with Access 2000" by Rick Dobson (ISBN 1861004834).

Filling a combo box or listbox is as simple as creating a stored procedure
or view and putting the name of that stored procedure or view in the row
source property of the control.  It gets little bit more complicated when
you need to pass a parameter through but not as hard as you guys make it
out.

Here is the function I use to fill the work order listbox on my ADP's
startup screen.  I have four different stored procedures based on the sort
the user chose.  I pass in the division code and filtering parameters based
on textboxes the users enter data into.

*****************

Public Function GetWOList(intSort As Integer, _
        strDivision As String, strShow As String, _
        strClient As String, strWO As String, _
        strProj As String)
                        
    On Error GoTo ErrorHandler
    
    Dim strSproc As String
    
    Select Case intSort
        Case Is = 1 'Work Order Number
            strSproc = "ap_WOS_StartupWONum"
        Case Is = 2 'Project Name
            strSproc = "ap_WOS_StartupWOProj"
        Case Is = 3 'Show Name
            strSproc = "ap_WOS_StartupWOShow"
        Case Is = 4 'Client Name
            strSproc = "ap_WOS_StartupWOClient"
    End Select
    
    Set cmd = New ADODB.Command
    With cmd
        .CommandType = adCmdStoredProc
        .CommandText = strSproc
        .Parameters.Append .CreateParameter("@Division", adVarChar,
adParamInput, 50)
        .Parameters.Append .CreateParameter("@Status", adBoolean,
adParamInput, 1)
        .Parameters.Append .CreateParameter("@Show", adVarChar,
adParamInput, 50)
        .Parameters.Append .CreateParameter("@Client", adVarChar,
adParamInput, 75)
        .Parameters.Append .CreateParameter("@WO", adVarChar, adParamInput,
5)
        .Parameters.Append .CreateParameter("@Proj", adVarChar,
adParamInput, 50)
        .ActiveConnection = CurrentProject.Connection
        
        .Parameters("@Division") = strDivision
        If bolArch = True Then
            .Parameters("@Status") = 1
        Else
            .Parameters("@Status") = 0
        End If
        
        If Len(strShow) > 0 Then .Parameters("@Show") = "%" & strShow & "%"
        If Len(strClient) > 0 Then .Parameters("@Client") = "%" & strClient
& "%"
        If Len(strWO) > 0 Then
            If Len(strWO) = 5 Then
                .Parameters("@WO") = strWO
            Else
                .Parameters("@WO") = strWO & "%"
            End If
        End If
        If Len(strProj) > 0 Then .Parameters("@Proj") = "%" & strProj & "%"
        
        Set Forms!frmStartup!lstWO.Recordset = .Execute
        .ActiveConnection = Nothing
    End With
    Set cmd = Nothing

    Exit Function
    
ErrorHandler:
    If Err = 3421 Then
        MsgBox "Work Order Number filter can only be 5 characters!",
vbOKOnly, "Filter Too Long"
    Else
        Call HandleErrors(Err, "basStartup", "GetWOList")
    End If

End Function


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
paul.hartland at fsmail.net
Sent: Thursday, January 26, 2006 2:40 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SPs are read-only

John,

As far as I am aware when you pull back data into an appliication using an
SP it is read only, if you want to pull back data and make it editible then
I have found you have to use a view (do as much filtering as possible here
(well I do anyway)) and then use some code with a select statement to bring
it into an editible recordset.
If anyone knows different about SP's then please tell me as well cause OH
how I would love to have an editible store procedure.
Paul



Message Received: Jan 26 2006, 07:28 AM
From: "John Colby" 
To: dba-sqlserver at databaseadvisors.com
Cc: 
Subject: [dba-SQLServer] SPs are read-only

Is there a magic incantation to make my SP editable? My tables are
read/write but a simple SP that pulls the same data (filtered on a couple of
ID fields) is read-only. Any thoughts on why this is?

TIA,

John W. Colby
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 jwcolby at ColbyConsulting.com  Thu Jan 26 09:50:16 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Thu, 26 Jan 2006 10:50:16 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
Message-ID: <006901c62290$34914b10$6f00a8c0@ColbyM6805>

I am having a "conceptual issue" using the SMS.  I create a stored procedure
and it saves to a directory out on the hard disk.  Somehow I managed to get
a couple of them showing in the stored procedure window but I don't know how
so I am not seeing the rest of the SPs I am adding.  Additionally, if I
click one that does show in the SP window in the database in SMS, and say
"modify" it opens it in the edit window as a new query with just SPnn as the
name, where NN is a number.  Then when I try to save it it asks where I want
to save it.  So I am not "editing" the original, but creating a copy and
editing that.

Is anyone out there using this thing and if so how do I save (and see)
stored procedures in a given database, and ten edit that SP directly later?

John W. Colby
www.ColbyConsulting.com 




From DavidL at sierranevada.com  Thu Jan 26 10:50:36 2006
From: DavidL at sierranevada.com (David Lewis)
Date: Thu, 26 Jan 2006 08:50:36 -0800
Subject: [dba-SQLServer] Moving some object's recordsource to SQL Server
Message-ID: <00101736F13D774F88C54058CB2663C825DB25@celebration.sierranevada.corp>


Here is a code snippet that will connect you to sql server and run a
sproc using a parameter that is fed in from a control on the form.  HTH.
D. Lewis


Dim intBrewid  As Integer
Dim cmd As ADODB.Command
Dim rst As ADODB.Recordset
Set rst = New ADODB.Recordset
Dim rstHop As ADODB.Recordset
Set rstHop = New ADODB.Recordset
Set cmd = New ADODB.Command
Set cmd.ActiveConnection = CurrentProject.Connection
cmd.CommandType = adCmdStoredProc
cmd.CommandText = "dbo.spBrewMaltValues"
intBrewid = lstBrews.Value

Dim prm As ADODB.Parameter
Set prm = cmd.CreateParameter("Brewid", adInteger, adParamInput, ,
intBrewid)
cmd.Parameters.Append prm
DoCmd.Hourglass True

Set rst = cmd.Execute
cmd.CommandText = "dbo.spBrewHopValues"
Set rstHop = cmd.Execute 
DoCmd.Hourglass False


At 11:09 PM 1/24/2006, you wrote:
>Date: Wed, 25 Jan 2006 00:09:47 -0500
>From: "John Colby" <jwcolby at ColbyConsulting.com>
>Subject: [dba-SQLServer] Moving some object's recordsource to SQL
>         Server
>To: "'Access Developers discussion and problem solving'"
>         <accessd at databaseadvisors.com>, 
><dba-sqlserver at databaseadvisors.com>
>Message-ID: <00b201c6216d$9085fd90$647aa8c0 at ColbyM6805>
>Content-Type: text/plain;       charset="us-ascii"
>
>I need a "step by step" if you will of moving some object to SQL Server

>- combo or form - where the Access query was filtered and the filter 
>won't work in SQL Server.  For example a reference to a control on a
form.
>
>I know that I have to create a SP in SQL Server that accepts a
parameter.
>How do I "connect" to that query from Access?  Is it a n ODBC (or 
>other?) link, just like a table?  Then how do I feed the parameters to 
>the SP out in SQL server.
>
>I am getting ready to do this and am way under prepared for this.
>
>Environment:
>
>SQL Server Express 2005
>Access (Office) XP or 2003
>Fes now talking to the SQL Server BE using the standard (ODBC I think) 
>"links" that the upsize wizard created when it moved the tables.
>
>The FE seems to work as it did before except slower.  Now if I can 
>start replacing the slow "Access Queries over ODBC" with "SQL Server 
>SPs with passed params????" I might be able to see what this is capable

>of.  I just haven't a clue how to move to that "SP with Params".
>
>John W. Colby




From rl_stewart at highstream.net  Thu Jan 26 11:18:11 2006
From: rl_stewart at highstream.net (Robert L. Stewart)
Date: Thu, 26 Jan 2006 11:18:11 -0600
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <mailman.1840.1138294604.18500.dba-sqlserver@databaseadviso
	rs.com>
References: <mailman.1840.1138294604.18500.dba-sqlserver@databaseadvisors.com>
Message-ID: <6.2.3.4.2.20060126110600.02fdd9f0@pop3.highstream.net>

John,

When you right click on a stored procedure, and select modify, it 
comes up in an ALTER format.  If you save them to the hard drive, 
they are NOT in the database. You have to edit and save them in the 
database itself.

Robert

At 10:56 AM 1/26/2006, you wrote:
>Date: Thu, 26 Jan 2006 10:50:16 -0500
>From: "John Colby" <jwcolby at ColbyConsulting.com>
>Subject: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <006901c62290$34914b10$6f00a8c0 at ColbyM6805>
>Content-Type: text/plain;       charset="us-ascii"
>
>I am having a "conceptual issue" using the SMS.  I create a stored procedure
>and it saves to a directory out on the hard disk.  Somehow I managed to get
>a couple of them showing in the stored procedure window but I don't know how
>so I am not seeing the rest of the SPs I am adding.  Additionally, if I
>click one that does show in the SP window in the database in SMS, and say
>"modify" it opens it in the edit window as a new query with just SPnn as the
>name, where NN is a number.  Then when I try to save it it asks where I want
>to save it.  So I am not "editing" the original, but creating a copy and
>editing that.
>
>Is anyone out there using this thing and if so how do I save (and see)
>stored procedures in a given database, and ten edit that SP directly later?
>
>John W. Colby




From jwcolby at ColbyConsulting.com  Thu Jan 26 12:18:23 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Thu, 26 Jan 2006 13:18:23 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <6.2.3.4.2.20060126110600.02fdd9f0@pop3.highstream.net>
Message-ID: <008301c622a4$e5665e30$6f00a8c0@ColbyM6805>

>You have to edit and save them in the database itself.

And you do that by.....

Part of the problem here I suspect is that I am out on the bleeding edge
trying to use SQL Server 2005 which has a brand new widget for management
called Microsoft SQL Server Management Studio Express.  The old tools don't
work with 2005.  And (apparently) no one on this group is using this thing.

And then of course I am clueless to start with, never having done any of
this before.  I really don't want to spend my time learning the tools for
SQL Server 2000 (I have actually used them a fair amount) because I am
"selling" 2005 Express (can you say FREE?  An easy sell!) to my clients.  As
such I need to learn the tools for 2005 Express.

John W. Colby
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: Thursday, January 26, 2006 12:18 PM
To: dba-sqlserver at databaseadvisors.com
Cc: jwcolby at colbyconsulting.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

John,

When you right click on a stored procedure, and select modify, it comes up
in an ALTER format.  If you save them to the hard drive, they are NOT in the
database. You have to edit and save them in the database itself.

Robert

At 10:56 AM 1/26/2006, you wrote:
>Date: Thu, 26 Jan 2006 10:50:16 -0500
>From: "John Colby" <jwcolby at ColbyConsulting.com>
>Subject: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <006901c62290$34914b10$6f00a8c0 at ColbyM6805>
>Content-Type: text/plain;       charset="us-ascii"
>
>I am having a "conceptual issue" using the SMS.  I create a stored 
>procedure and it saves to a directory out on the hard disk.  Somehow I 
>managed to get a couple of them showing in the stored procedure window 
>but I don't know how so I am not seeing the rest of the SPs I am 
>adding.  Additionally, if I click one that does show in the SP window 
>in the database in SMS, and say "modify" it opens it in the edit window 
>as a new query with just SPnn as the name, where NN is a number.  Then 
>when I try to save it it asks where I want to save it.  So I am not 
>"editing" the original, but creating a copy and editing that.
>
>Is anyone out there using this thing and if so how do I save (and see) 
>stored procedures in a given database, and ten edit that SP directly later?
>
>John W. Colby


_______________________________________________
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  Thu Jan 26 13:17:31 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Thu, 26 Jan 2006 11:17:31 -0800
Subject: [dba-SQLServer] SPs are read-only
In-Reply-To: <000101c6227d$84372260$2f01a8c0@dorismanning>
Message-ID: <001701c622ad$27e76300$017ba8c0@xpserver>

Hi Doris:

I thought the whole idea was to get away from ADP, which is basically dead.
The only trouble was ADP's passing is that there has to be another way to
connect recordsets to the data objects. Hence the much more complex set of
coding.   

Nice coding!!... too bad about ADP :-(.

Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mike &
Doris Manning
Sent: January 26, 2006 5:36 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SPs are read-only

John,

I'm amazed at the amount of "going around the bush to get to the barn"
information that you are getting from this list.  So far, the responses are
far more complicated than they need to be.

When I was first starting out, I found an ADO Primer website
(http://authors.aspalliance.com/aspxtreme/ado/index.aspx) that really helped
me understand the basics behind what I was trying to do.

There are also several really good books out there for working with SQL
Server within Access.  My favorite is "Professional SQL Server Development
with Access 2000" by Rick Dobson (ISBN 1861004834).

Filling a combo box or listbox is as simple as creating a stored procedure
or view and putting the name of that stored procedure or view in the row
source property of the control.  It gets little bit more complicated when
you need to pass a parameter through but not as hard as you guys make it
out.

Here is the function I use to fill the work order listbox on my ADP's
startup screen.  I have four different stored procedures based on the sort
the user chose.  I pass in the division code and filtering parameters based
on textboxes the users enter data into.

*****************

Public Function GetWOList(intSort As Integer, _
        strDivision As String, strShow As String, _
        strClient As String, strWO As String, _
        strProj As String)
                        
    On Error GoTo ErrorHandler
    
    Dim strSproc As String
    
    Select Case intSort
        Case Is = 1 'Work Order Number
            strSproc = "ap_WOS_StartupWONum"
        Case Is = 2 'Project Name
            strSproc = "ap_WOS_StartupWOProj"
        Case Is = 3 'Show Name
            strSproc = "ap_WOS_StartupWOShow"
        Case Is = 4 'Client Name
            strSproc = "ap_WOS_StartupWOClient"
    End Select
    
    Set cmd = New ADODB.Command
    With cmd
        .CommandType = adCmdStoredProc
        .CommandText = strSproc
        .Parameters.Append .CreateParameter("@Division", adVarChar,
adParamInput, 50)
        .Parameters.Append .CreateParameter("@Status", adBoolean,
adParamInput, 1)
        .Parameters.Append .CreateParameter("@Show", adVarChar,
adParamInput, 50)
        .Parameters.Append .CreateParameter("@Client", adVarChar,
adParamInput, 75)
        .Parameters.Append .CreateParameter("@WO", adVarChar, adParamInput,
5)
        .Parameters.Append .CreateParameter("@Proj", adVarChar,
adParamInput, 50)
        .ActiveConnection = CurrentProject.Connection
        
        .Parameters("@Division") = strDivision
        If bolArch = True Then
            .Parameters("@Status") = 1
        Else
            .Parameters("@Status") = 0
        End If
        
        If Len(strShow) > 0 Then .Parameters("@Show") = "%" & strShow & "%"
        If Len(strClient) > 0 Then .Parameters("@Client") = "%" & strClient
& "%"
        If Len(strWO) > 0 Then
            If Len(strWO) = 5 Then
                .Parameters("@WO") = strWO
            Else
                .Parameters("@WO") = strWO & "%"
            End If
        End If
        If Len(strProj) > 0 Then .Parameters("@Proj") = "%" & strProj & "%"
        
        Set Forms!frmStartup!lstWO.Recordset = .Execute
        .ActiveConnection = Nothing
    End With
    Set cmd = Nothing

    Exit Function
    
ErrorHandler:
    If Err = 3421 Then
        MsgBox "Work Order Number filter can only be 5 characters!",
vbOKOnly, "Filter Too Long"
    Else
        Call HandleErrors(Err, "basStartup", "GetWOList")
    End If

End Function


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
paul.hartland at fsmail.net
Sent: Thursday, January 26, 2006 2:40 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SPs are read-only

John,

As far as I am aware when you pull back data into an appliication using an
SP it is read only, if you want to pull back data and make it editible then
I have found you have to use a view (do as much filtering as possible here
(well I do anyway)) and then use some code with a select statement to bring
it into an editible recordset.
If anyone knows different about SP's then please tell me as well cause OH
how I would love to have an editible store procedure.
Paul



Message Received: Jan 26 2006, 07:28 AM
From: "John Colby" 
To: dba-sqlserver at databaseadvisors.com
Cc: 
Subject: [dba-SQLServer] SPs are read-only

Is there a magic incantation to make my SP editable? My tables are
read/write but a simple SP that pulls the same data (filtered on a couple of
ID fields) is read-only. Any thoughts on why this is?

TIA,

John W. Colby
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



From mwp.reid at qub.ac.uk  Thu Jan 26 13:39:10 2006
From: mwp.reid at qub.ac.uk (Martin Reid)
Date: Thu, 26 Jan 2006 19:39:10 -0000
Subject: [dba-SQLServer]  SPs are read-only
References: <001701c622ad$27e76300$017ba8c0@xpserver>
	<D0BF9C78D1C45C418541C852C8944FE2025E65@qub-xchange-01.ads.qub.ac.uk>
Message-ID: <D0BF9C78D1C45C418541C852C8944FE2025E66@qub-xchange-01.ads.qub.ac.uk>

The next version of Access contains full ADP functionality using SQL Server 2000. SQL Server 2005 no because thats not the direction they are taking Access from what I am seeing. Think SharePoint in a big way.
 
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: Thu 26/01/2006 19:17
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SPs are read-only



Hi Doris:

I thought the whole idea was to get away from ADP, which is basically dead.
The only trouble was ADP's passing is that there has to be another way to
connect recordsets to the data objects. Hence the much more complex set of
coding.  

Nice coding!!... too bad about ADP :-(.

Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mike &
Doris Manning
Sent: January 26, 2006 5:36 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SPs are read-only

John,

I'm amazed at the amount of "going around the bush to get to the barn"
information that you are getting from this list.  So far, the responses are
far more complicated than they need to be.

When I was first starting out, I found an ADO Primer website
(http://authors.aspalliance.com/aspxtreme/ado/index.aspx) that really helped
me understand the basics behind what I was trying to do.

There are also several really good books out there for working with SQL
Server within Access.  My favorite is "Professional SQL Server Development
with Access 2000" by Rick Dobson (ISBN 1861004834).

Filling a combo box or listbox is as simple as creating a stored procedure
or view and putting the name of that stored procedure or view in the row
source property of the control.  It gets little bit more complicated when
you need to pass a parameter through but not as hard as you guys make it
out.

Here is the function I use to fill the work order listbox on my ADP's
startup screen.  I have four different stored procedures based on the sort
the user chose.  I pass in the division code and filtering parameters based
on textboxes the users enter data into.

*****************

Public Function GetWOList(intSort As Integer, _
        strDivision As String, strShow As String, _
        strClient As String, strWO As String, _
        strProj As String)
                       
    On Error GoTo ErrorHandler
   
    Dim strSproc As String
   
    Select Case intSort
        Case Is = 1 'Work Order Number
            strSproc = "ap_WOS_StartupWONum"
        Case Is = 2 'Project Name
            strSproc = "ap_WOS_StartupWOProj"
        Case Is = 3 'Show Name
            strSproc = "ap_WOS_StartupWOShow"
        Case Is = 4 'Client Name
            strSproc = "ap_WOS_StartupWOClient"
    End Select
   
    Set cmd = New ADODB.Command
    With cmd
        .CommandType = adCmdStoredProc
        .CommandText = strSproc
        .Parameters.Append .CreateParameter("@Division", adVarChar,
adParamInput, 50)
        .Parameters.Append .CreateParameter("@Status", adBoolean,
adParamInput, 1)
        .Parameters.Append .CreateParameter("@Show", adVarChar,
adParamInput, 50)
        .Parameters.Append .CreateParameter("@Client", adVarChar,
adParamInput, 75)
        .Parameters.Append .CreateParameter("@WO", adVarChar, adParamInput,
5)
        .Parameters.Append .CreateParameter("@Proj", adVarChar,
adParamInput, 50)
        .ActiveConnection = CurrentProject.Connection
       
        .Parameters("@Division") = strDivision
        If bolArch = True Then
            .Parameters("@Status") = 1
        Else
            .Parameters("@Status") = 0
        End If
       
        If Len(strShow) > 0 Then .Parameters("@Show") = "%" & strShow & "%"
        If Len(strClient) > 0 Then .Parameters("@Client") = "%" & strClient
& "%"
        If Len(strWO) > 0 Then
            If Len(strWO) = 5 Then
                .Parameters("@WO") = strWO
            Else
                .Parameters("@WO") = strWO & "%"
            End If
        End If
        If Len(strProj) > 0 Then .Parameters("@Proj") = "%" & strProj & "%"
       
        Set Forms!frmStartup!lstWO.Recordset = .Execute
        .ActiveConnection = Nothing
    End With
    Set cmd = Nothing

    Exit Function
   
ErrorHandler:
    If Err = 3421 Then
        MsgBox "Work Order Number filter can only be 5 characters!",
vbOKOnly, "Filter Too Long"
    Else
        Call HandleErrors(Err, "basStartup", "GetWOList")
    End If

End Function


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
paul.hartland at fsmail.net
Sent: Thursday, January 26, 2006 2:40 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SPs are read-only

John,

As far as I am aware when you pull back data into an appliication using an
SP it is read only, if you want to pull back data and make it editible then
I have found you have to use a view (do as much filtering as possible here
(well I do anyway)) and then use some code with a select statement to bring
it into an editible recordset.
If anyone knows different about SP's then please tell me as well cause OH
how I would love to have an editible store procedure.
Paul



Message Received: Jan 26 2006, 07:28 AM
From: "John Colby"
To: dba-sqlserver at databaseadvisors.com
Cc:
Subject: [dba-SQLServer] SPs are read-only

Is there a magic incantation to make my SP editable? My tables are
read/write but a simple SP that pulls the same data (filtered on a couple of
ID fields) is read-only. Any thoughts on why this is?

TIA,

John W. Colby
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

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com





From harkinsss at bellsouth.net  Thu Jan 26 13:56:38 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Thu, 26 Jan 2006 14:56:38 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <008301c622a4$e5665e30$6f00a8c0@ColbyM6805>
Message-ID: <000301c622b2$9f5049c0$8fb3d6d1@SUSANONE>

I'm using MS with Express. Use a CREATE PROCEDURE statement and execute it
-- that will save it in the db. I know MS isn't complete for Express, so it
might not be complete for 2005 either. 

And you do that by.....

Part of the problem here I suspect is that I am out on the bleeding edge
trying to use SQL Server 2005 which has a brand new widget for management
called Microsoft SQL Server Management Studio Express.  The old tools don't
work with 2005.  And (apparently) no one on this group is using this thing.

And then of course I am clueless to start with, never having done any of
this before.  I really don't want to spend my time learning the tools for
SQL Server 2000 (I have actually used them a fair amount) because I am
"selling" 2005 Express (can you say FREE?  An easy sell!) to my clients.  As
such I need to learn the tools for 2005 Express.




From maillist at kkendrick.net  Thu Jan 26 14:08:23 2006
From: maillist at kkendrick.net (maillist at kkendrick.net)
Date: Thu, 26 Jan 2006 14:08:23 -0600
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <008301c622a4$e5665e30$6f00a8c0@ColbyM6805>
Message-ID: <000401c622b4$42b650e0$030aa8c0@dragon>

John,

When you create the stored procedure with the CREATE PROCEDURE syntax, then
execute it, it is saved to SQL Server 2005.

When you modify the stored procedure with the ALTER PROCEDURE syntax, then
execute it, it is again saved to SQL Server -- with the modifications.

You also have the option of saving it to disk. If you don't want to save it,
then you just close it.

HTH.

Kay Kendrick
 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: Thursday, January 26, 2006 12:18 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

>You have to edit and save them in the database itself.

And you do that by.....

Part of the problem here I suspect is that I am out on the bleeding edge
trying to use SQL Server 2005 which has a brand new widget for management
called Microsoft SQL Server Management Studio Express.  The old tools don't
work with 2005.  And (apparently) no one on this group is using this thing.

And then of course I am clueless to start with, never having done any of
this before.  I really don't want to spend my time learning the tools for
SQL Server 2000 (I have actually used them a fair amount) because I am
"selling" 2005 Express (can you say FREE?  An easy sell!) to my clients.  As
such I need to learn the tools for 2005 Express.

John W. Colby
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: Thursday, January 26, 2006 12:18 PM
To: dba-sqlserver at databaseadvisors.com
Cc: jwcolby at colbyconsulting.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

John,

When you right click on a stored procedure, and select modify, it comes up
in an ALTER format.  If you save them to the hard drive, they are NOT in the
database. You have to edit and save them in the database itself.

Robert

At 10:56 AM 1/26/2006, you wrote:
>Date: Thu, 26 Jan 2006 10:50:16 -0500
>From: "John Colby" <jwcolby at ColbyConsulting.com>
>Subject: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <006901c62290$34914b10$6f00a8c0 at ColbyM6805>
>Content-Type: text/plain;       charset="us-ascii"
>
>I am having a "conceptual issue" using the SMS.  I create a stored 
>procedure and it saves to a directory out on the hard disk.  Somehow I 
>managed to get a couple of them showing in the stored procedure window 
>but I don't know how so I am not seeing the rest of the SPs I am 
>adding.  Additionally, if I click one that does show in the SP window 
>in the database in SMS, and say "modify" it opens it in the edit window 
>as a new query with just SPnn as the name, where NN is a number.  Then 
>when I try to save it it asks where I want to save it.  So I am not 
>"editing" the original, but creating a copy and editing that.
>
>Is anyone out there using this thing and if so how do I save (and see) 
>stored procedures in a given database, and ten edit that SP directly later?
>
>John W. Colby


_______________________________________________
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 Jan 26 14:15:17 2006
From: mwp.reid at qub.ac.uk (Martin Reid)
Date: Thu, 26 Jan 2006 20:15:17 -0000
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
References: <000401c622b4$42b650e0$030aa8c0@dragon>
Message-ID: <D0BF9C78D1C45C418541C852C8944FE2025E6A@qub-xchange-01.ads.qub.ac.uk>

John
 
Is it possible to downlaod a full version of SQL Server 2005 Evual. Then use the "proper" management tools to get used to the database before the evual expires?
 
Maritn
 
Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast
 
tel: 02890 974477
 

________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of maillist at kkendrick.net
Sent: Thu 26/01/2006 20:08
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio



John,

When you create the stored procedure with the CREATE PROCEDURE syntax, then
execute it, it is saved to SQL Server 2005.

When you modify the stored procedure with the ALTER PROCEDURE syntax, then
execute it, it is again saved to SQL Server -- with the modifications.

You also have the option of saving it to disk. If you don't want to save it,
then you just close it.

HTH.

Kay Kendrick


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: Thursday, January 26, 2006 12:18 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

>You have to edit and save them in the database itself.

And you do that by.....

Part of the problem here I suspect is that I am out on the bleeding edge
trying to use SQL Server 2005 which has a brand new widget for management
called Microsoft SQL Server Management Studio Express.  The old tools don't
work with 2005.  And (apparently) no one on this group is using this thing.

And then of course I am clueless to start with, never having done any of
this before.  I really don't want to spend my time learning the tools for
SQL Server 2000 (I have actually used them a fair amount) because I am
"selling" 2005 Express (can you say FREE?  An easy sell!) to my clients.  As
such I need to learn the tools for 2005 Express.

John W. Colby
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: Thursday, January 26, 2006 12:18 PM
To: dba-sqlserver at databaseadvisors.com
Cc: jwcolby at colbyconsulting.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

John,

When you right click on a stored procedure, and select modify, it comes up
in an ALTER format.  If you save them to the hard drive, they are NOT in the
database. You have to edit and save them in the database itself.

Robert

At 10:56 AM 1/26/2006, you wrote:
>Date: Thu, 26 Jan 2006 10:50:16 -0500
>From: "John Colby" <jwcolby at ColbyConsulting.com>
>Subject: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <006901c62290$34914b10$6f00a8c0 at ColbyM6805>
>Content-Type: text/plain;       charset="us-ascii"
>
>I am having a "conceptual issue" using the SMS.  I create a stored
>procedure and it saves to a directory out on the hard disk.  Somehow I
>managed to get a couple of them showing in the stored procedure window
>but I don't know how so I am not seeing the rest of the SPs I am
>adding.  Additionally, if I click one that does show in the SP window
>in the database in SMS, and say "modify" it opens it in the edit window
>as a new query with just SPnn as the name, where NN is a number.  Then
>when I try to save it it asks where I want to save it.  So I am not
>"editing" the original, but creating a copy and editing that.
>
>Is anyone out there using this thing and if so how do I save (and see)
>stored procedures in a given database, and ten edit that SP directly later?
>
>John W. Colby


_______________________________________________
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 rl_stewart at highstream.net  Thu Jan 26 14:29:42 2006
From: rl_stewart at highstream.net (Robert L. Stewart)
Date: Thu, 26 Jan 2006 14:29:42 -0600
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <mailman.1925.1138306556.18500.dba-sqlserver@databaseadviso
	rs.com>
References: <mailman.1925.1138306556.18500.dba-sqlserver@databaseadvisors.com>
Message-ID: <6.2.3.4.2.20060126142609.02fca9a8@pop3.highstream.net>

John,

Open The database.
Open Programmability
Right Click on Stored Procedures
Select Create New Stored Procedure

You are presented with a template for one.  If you have one from a 
file, open it in note pad and paste it in over the template.  Close 
it and save it.

Also, if you can get ahold of the developers version of SQL 2005, you 
can get the full version of SMS.

Robert

At 02:15 PM 1/26/2006, you wrote:
>Date: Thu, 26 Jan 2006 13:18:23 -0500
>From: "John Colby" <jwcolby at ColbyConsulting.com>
>Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <008301c622a4$e5665e30$6f00a8c0 at ColbyM6805>
>Content-Type: text/plain;       charset="us-ascii"
>
> >You have to edit and save them in the database itself.
>
>And you do that by.....
>
>Part of the problem here I suspect is that I am out on the bleeding edge
>trying to use SQL Server 2005 which has a brand new widget for management
>called Microsoft SQL Server Management Studio Express.  The old tools don't
>work with 2005.  And (apparently) no one on this group is using this thing.
>
>And then of course I am clueless to start with, never having done any of
>this before.  I really don't want to spend my time learning the tools for
>SQL Server 2000 (I have actually used them a fair amount) because I am
>"selling" 2005 Express (can you say FREE?  An easy sell!) to my clients.  As
>such I need to learn the tools for 2005 Express.
>
>John W. Colby
>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: Thursday, January 26, 2006 12:18 PM
>To: dba-sqlserver at databaseadvisors.com
>Cc: jwcolby at colbyconsulting.com
>Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio
>
>John,
>
>When you right click on a stored procedure, and select modify, it comes up
>in an ALTER format.  If you save them to the hard drive, they are NOT in the
>database. You have to edit and save them in the database itself.
>
>Robert




From jwcolby at ColbyConsulting.com  Thu Jan 26 14:59:27 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Thu, 26 Jan 2006 15:59:27 -0500
Subject: [dba-SQLServer] SP read only
Message-ID: <009501c622bb$65765380$6f00a8c0@ColbyM6805>

Folks,

I have the following SP.  It selects data from a single table, filtered on
two fields.  Pretty simple.  It is also read-only inside the SMS Express
tool.  The table itself is editable, i.e. if I just open the table I can
modify values.  Does anyone know if parameterized SPs are supposed to be
editable?  
If so, what can cause the SP result set to be Read Only?

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author:		<Author,,Name>
-- Create date: <Create Date,,>
-- Description:	<Description,,>
-- =============================================
CREATE PROCEDURE usp_FrmCallListFiltered
	-- Add the parameters for the stored procedure here
	@STID int,
	@DIID int
AS
BEGIN
	-- SET NOCOUNT ON added to prevent extra result sets from
	-- interfering with SELECT statements.
	SET NOCOUNT ON;

    -- Insert statements for procedure here
	SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, tblPeople.PE_Specialty,
tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
tblPeople.PE_Contact1, tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo,
tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
tblPeople.PE_Certification, tblPeople.PE_LIC_Licno,
tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress,
tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, tblPeople.PE_IDDNC,
tblPeople.PE_IDIWH, tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate,
tblPeople.PE_HotLead, tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive,
tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
tblPeople.PE_LIC_IDDI
	FROM tblPeople
	WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
((tblPeople.PE_LIC_IDDI)=@DIID))
	ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;

END
GO

John W. Colby
www.ColbyConsulting.com 




From mwp.reid at qub.ac.uk  Thu Jan 26 15:18:00 2006
From: mwp.reid at qub.ac.uk (Martin Reid)
Date: Thu, 26 Jan 2006 21:18:00 -0000
Subject: [dba-SQLServer] SP read only
References: <009501c622bb$65765380$6f00a8c0@ColbyM6805>
Message-ID: <D0BF9C78D1C45C418541C852C8944FE2025E6B@qub-xchange-01.ads.qub.ac.uk>

John
 
Remove the OrderBY and try it
 
Martin
 
Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast
 
tel: 02890 974477
 

________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
Sent: Thu 26/01/2006 20:59
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] SP read only



Folks,

I have the following SP.  It selects data from a single table, filtered on
two fields.  Pretty simple.  It is also read-only inside the SMS Express
tool.  The table itself is editable, i.e. if I just open the table I can
modify values.  Does anyone know if parameterized SPs are supposed to be
editable? 
If so, what can cause the SP result set to be Read Only?

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author:              <Author,,Name>
-- Create date: <Create Date,,>
-- Description: <Description,,>
-- =============================================
CREATE PROCEDURE usp_FrmCallListFiltered
        -- Add the parameters for the stored procedure here
        @STID int,
        @DIID int
AS
BEGIN
        -- SET NOCOUNT ON added to prevent extra result sets from
        -- interfering with SELECT statements.
        SET NOCOUNT ON;

    -- Insert statements for procedure here
        SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, tblPeople.PE_Specialty,
tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
tblPeople.PE_Contact1, tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo,
tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
tblPeople.PE_Certification, tblPeople.PE_LIC_Licno,
tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress,
tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, tblPeople.PE_IDDNC,
tblPeople.PE_IDIWH, tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate,
tblPeople.PE_HotLead, tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive,
tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
tblPeople.PE_LIC_IDDI
        FROM tblPeople
        WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
((tblPeople.PE_LIC_IDDI)=@DIID))
        ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;

END
GO

John W. Colby
www.ColbyConsulting.com


_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com




From word_diva at hotmail.com  Thu Jan 26 15:37:26 2006
From: word_diva at hotmail.com (Nancy Lytle)
Date: Thu, 26 Jan 2006 16:37:26 -0500
Subject: [dba-SQLServer] Best way to do a large delete
In-Reply-To: <D0BF9C78D1C45C418541C852C8944FE2025E6B@qub-xchange-01.ads.qub.ac.uk>
Message-ID: <BAY106-DAV8DD1A68946E8D3B0C49BA84150@phx.gbl>

 
I have to do a delete from a table with about 25 million rows.  I need to
delete about 4 million rows, based on the date in another table

Table Session

SessionID	SessionDate
1		1/25/2004
2		7/25/2001
I have created a view (SessionView) containing all sessionid's where the
sessiondate less than 3 years old.

(Create view SessionView
As
Select SessionID
>From Session
Where
Session.sessiondate >= getdate() - 1095)


Table Claims

ClaimID	SessionID		etc	etc			etc
24578		1			15	HealthPractice	5554441234
6548975	2			52	ChirocPract		5551234567

What I need is to delete all rows from Table Claims that have sessionids in
SessionView.

Delete
>From Claims
Where Claims.sessionID In (Select SessionID from SessionView)

-In this case ClaimID 6548975 would be deleted but ClaimID 24578 would not.

But I must be doing something wrong (I am very new at SQL Server, and have
never done a large scale delete that wasn't just straight forward), because
the delete seems to take forever.  Last time I had to stop it at just over 5
hours because the network admin needed to do some work on the server and
reboot it.

I have set the recovery to simple, and the server has no other active
databases or other applications running on it.

Any assistance appreciated.

Nancy Lytle
N_Lytle at terplaum.umd.edu

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.14.22/239 - Release Date: 1/24/2006
 


From jwcolby at ColbyConsulting.com  Thu Jan 26 15:47:47 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Thu, 26 Jan 2006 16:47:47 -0500
Subject: [dba-SQLServer] SP read only
In-Reply-To: <D0BF9C78D1C45C418541C852C8944FE2025E6B@qub-xchange-01.ads.qub.ac.uk>
Message-ID: <009f01c622c2$2620a030$6f00a8c0@ColbyM6805>

Nope, didn't help


John W. Colby
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, January 26, 2006 4:18 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only

John
 
Remove the OrderBY and try it
 
Martin
 
Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast
 
tel: 02890 974477
 

________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
Sent: Thu 26/01/2006 20:59
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] SP read only



Folks,

I have the following SP.  It selects data from a single table, filtered on
two fields.  Pretty simple.  It is also read-only inside the SMS Express
tool.  The table itself is editable, i.e. if I just open the table I can
modify values.  Does anyone know if parameterized SPs are supposed to be
editable? 
If so, what can cause the SP result set to be Read Only?

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author:              <Author,,Name>
-- Create date: <Create Date,,>
-- Description: <Description,,>
-- =============================================
CREATE PROCEDURE usp_FrmCallListFiltered
        -- Add the parameters for the stored procedure here
        @STID int,
        @DIID int
AS
BEGIN
        -- SET NOCOUNT ON added to prevent extra result sets from
        -- interfering with SELECT statements.
        SET NOCOUNT ON;

    -- Insert statements for procedure here
        SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, tblPeople.PE_Specialty,
tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
tblPeople.PE_Contact1, tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo,
tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
tblPeople.PE_Certification, tblPeople.PE_LIC_Licno,
tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress,
tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, tblPeople.PE_IDDNC,
tblPeople.PE_IDIWH, tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate,
tblPeople.PE_HotLead, tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive,
tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
tblPeople.PE_LIC_IDDI
        FROM tblPeople
        WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
((tblPeople.PE_LIC_IDDI)=@DIID))
        ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;

END
GO

John W. Colby
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 Jan 26 15:58:18 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Thu, 26 Jan 2006 16:58:18 -0500
Subject: [dba-SQLServer] SP read only
In-Reply-To: <D0BF9C78D1C45C418541C852C8944FE2025E6B@qub-xchange-01.ads.qub.ac.uk>
Message-ID: <00a001c622c3$9e6b3130$6f00a8c0@ColbyM6805>

If I execute the following SP it is also read-only.  This is just a select
*.  This doesn't bode well for updating a select sp

set ANSI_NULLS ON
set QUOTED_IDENTIFIER ON
go

-- =============================================
-- Author:		<Author,,Name>
-- Create date: <Create Date,,>
-- Description:	<Description,,>
-- =============================================
ALTER PROCEDURE [dbo].[spPeople]
	-- Add the parameters for the stored procedure here
	--<@Param1, sysname, @p1> <Datatype_For_Param1, , int> =
<Default_Value_For_Param1, , 0>, 
	--<@Param2, sysname, @p2> <Datatype_For_Param2, , int> =
<Default_Value_For_Param2, , 0>
AS
BEGIN
	-- SET NOCOUNT ON added to prevent extra result sets from
	-- interfering with SELECT statements.
	SET NOCOUNT ON;

    -- Insert statements for procedure here
	SELECT * from tblPeople
END 


John W. Colby
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, January 26, 2006 4:18 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only

John
 
Remove the OrderBY and try it
 
Martin
 
Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast
 
tel: 02890 974477
 

________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
Sent: Thu 26/01/2006 20:59
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] SP read only



Folks,

I have the following SP.  It selects data from a single table, filtered on
two fields.  Pretty simple.  It is also read-only inside the SMS Express
tool.  The table itself is editable, i.e. if I just open the table I can
modify values.  Does anyone know if parameterized SPs are supposed to be
editable? 
If so, what can cause the SP result set to be Read Only?

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author:              <Author,,Name>
-- Create date: <Create Date,,>
-- Description: <Description,,>
-- =============================================
CREATE PROCEDURE usp_FrmCallListFiltered
        -- Add the parameters for the stored procedure here
        @STID int,
        @DIID int
AS
BEGIN
        -- SET NOCOUNT ON added to prevent extra result sets from
        -- interfering with SELECT statements.
        SET NOCOUNT ON;

    -- Insert statements for procedure here
        SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, tblPeople.PE_Specialty,
tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
tblPeople.PE_Contact1, tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo,
tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
tblPeople.PE_Certification, tblPeople.PE_LIC_Licno,
tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress,
tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, tblPeople.PE_IDDNC,
tblPeople.PE_IDIWH, tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate,
tblPeople.PE_HotLead, tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive,
tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
tblPeople.PE_LIC_IDDI
        FROM tblPeople
        WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
((tblPeople.PE_LIC_IDDI)=@DIID))
        ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;

END
GO

John W. Colby
www.ColbyConsulting.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 Jan 26 16:03:28 2006
From: mwp.reid at qub.ac.uk (Martin Reid)
Date: Thu, 26 Jan 2006 22:03:28 -0000
Subject: [dba-SQLServer] SP read only
References: <009f01c622c2$2620a030$6f00a8c0@ColbyM6805>
Message-ID: <D0BF9C78D1C45C418541C852C8944FE2025E6C@qub-xchange-01.ads.qub.ac.uk>

John
 
How do you execute the SP from Access?
 
Martin
 
 
Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast
 
tel: 02890 974477
 

________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
Sent: Thu 26/01/2006 21:47
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only



Nope, didn't help


John W. Colby
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, January 26, 2006 4:18 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only

John

Remove the OrderBY and try it

Martin

Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast

tel: 02890 974477


________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
Sent: Thu 26/01/2006 20:59
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] SP read only



Folks,

I have the following SP.  It selects data from a single table, filtered on
two fields.  Pretty simple.  It is also read-only inside the SMS Express
tool.  The table itself is editable, i.e. if I just open the table I can
modify values.  Does anyone know if parameterized SPs are supposed to be
editable?
If so, what can cause the SP result set to be Read Only?

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author:              <Author,,Name>
-- Create date: <Create Date,,>
-- Description: <Description,,>
-- =============================================
CREATE PROCEDURE usp_FrmCallListFiltered
        -- Add the parameters for the stored procedure here
        @STID int,
        @DIID int
AS
BEGIN
        -- SET NOCOUNT ON added to prevent extra result sets from
        -- interfering with SELECT statements.
        SET NOCOUNT ON;

    -- Insert statements for procedure here
        SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, tblPeople.PE_Specialty,
tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
tblPeople.PE_Contact1, tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo,
tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
tblPeople.PE_Certification, tblPeople.PE_LIC_Licno,
tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress,
tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, tblPeople.PE_IDDNC,
tblPeople.PE_IDIWH, tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate,
tblPeople.PE_HotLead, tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive,
tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
tblPeople.PE_LIC_IDDI
        FROM tblPeople
        WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
((tblPeople.PE_LIC_IDDI)=@DIID))
        ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;

END
GO

John W. Colby
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 mwp.reid at qub.ac.uk  Thu Jan 26 16:35:30 2006
From: mwp.reid at qub.ac.uk (Martin Reid)
Date: Thu, 26 Jan 2006 22:35:30 -0000
Subject: [dba-SQLServer] SP read only
References: <009f01c622c2$2620a030$6f00a8c0@ColbyM6805>
	<D0BF9C78D1C45C418541C852C8944FE2025E6C@qub-xchange-01.ads.qub.ac.uk>
Message-ID: <D0BF9C78D1C45C418541C852C8944FE2025E6D@qub-xchange-01.ads.qub.ac.uk>

John
 
Very simple example I just ran and it recordset was updateable. I just added several records via the results window in Access.
 
SET QUOTED_IDENTIFIER ON 
GO
SET ANSI_NULLS ON 
GO
CREATE PROCEDURE dbo.StoredProcedure2(@ID int)
AS SELECT      fldAssetTypeID, fldAssetTypeDescription, fldAssetTypeRecordStatus
FROM          dbo.tblAssetType
WHERE      (fldAssetTypeID = @ID)
GO
SET QUOTED_IDENTIFIER OFF 
GO
SET ANSI_NULLS ON 
GO

 
 
 
 
Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast
 
tel: 02890 974477
 

________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of Martin Reid
Sent: Thu 26/01/2006 22:03
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only



John

How do you execute the SP from Access?

Martin


Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast

tel: 02890 974477


________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
Sent: Thu 26/01/2006 21:47
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only



Nope, didn't help


John W. Colby
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, January 26, 2006 4:18 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only

John

Remove the OrderBY and try it

Martin

Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast

tel: 02890 974477


________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
Sent: Thu 26/01/2006 20:59
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] SP read only



Folks,

I have the following SP.  It selects data from a single table, filtered on
two fields.  Pretty simple.  It is also read-only inside the SMS Express
tool.  The table itself is editable, i.e. if I just open the table I can
modify values.  Does anyone know if parameterized SPs are supposed to be
editable?
If so, what can cause the SP result set to be Read Only?

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author:              <Author,,Name>
-- Create date: <Create Date,,>
-- Description: <Description,,>
-- =============================================
CREATE PROCEDURE usp_FrmCallListFiltered
        -- Add the parameters for the stored procedure here
        @STID int,
        @DIID int
AS
BEGIN
        -- SET NOCOUNT ON added to prevent extra result sets from
        -- interfering with SELECT statements.
        SET NOCOUNT ON;

    -- Insert statements for procedure here
        SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, tblPeople.PE_Specialty,
tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
tblPeople.PE_Contact1, tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo,
tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
tblPeople.PE_Certification, tblPeople.PE_LIC_Licno,
tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress,
tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, tblPeople.PE_IDDNC,
tblPeople.PE_IDIWH, tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate,
tblPeople.PE_HotLead, tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive,
tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
tblPeople.PE_LIC_IDDI
        FROM tblPeople
        WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
((tblPeople.PE_LIC_IDDI)=@DIID))
        ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;

END
GO

John W. Colby
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 jwcolby at ColbyConsulting.com  Thu Jan 26 19:14:09 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Thu, 26 Jan 2006 20:14:09 -0500
Subject: [dba-SQLServer] SP read only
In-Reply-To: <D0BF9C78D1C45C418541C852C8944FE2025E6C@qub-xchange-01.ads.qub.ac.uk>
Message-ID: <00b101c622de$fa1852e0$6f00a8c0@ColbyM6805>

I ran the SP from inside of Server Management Studio express.  I am using
2005.  I am not using ADPs so there is no way to directly open a SP from
Access.  You have to either do an ado recordset or a pass through query.  I
had the pass through working but that was RO.  I have yet to get the
Recordset working, at least to the point of setting an access object's
Recordset property (I get an "invalid object").

I am using Microsoft SQL Server Management Studio Express.  I build the SPs
in SMSE and I execute the SP there as well.  I can "open" a table and the
table is RW, but apparently all (even simple) SPs are RO.  The SPs are RO
when used via a pass through out in Access.  At this point I have to wonder
if SQL Server 2005 Express has a setting or an intentional limitation
causing this behavior.

I have built two SPs in SMSE:

SELECT * FROM tlkpState

As well as 

SELECT ST_ID, ST_Code FROM tlkpState

This is the smallest, simplest table in the database.  Both of these SPs are
RO.

Going to the db and opening the linked (ODBC) table it is r/w.  Opening the
table directly in SMSE the table is r/w.  It has to do with being a SP.
What a waste of time.  8(

John W. Colby
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, January 26, 2006 5:03 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only

John
 
How do you execute the SP from Access?
 
Martin
 
 
Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast
 
tel: 02890 974477
 

________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
Sent: Thu 26/01/2006 21:47
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only



Nope, didn't help


John W. Colby
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, January 26, 2006 4:18 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only

John

Remove the OrderBY and try it

Martin

Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast

tel: 02890 974477


________________________________

From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
Sent: Thu 26/01/2006 20:59
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] SP read only



Folks,

I have the following SP.  It selects data from a single table, filtered on
two fields.  Pretty simple.  It is also read-only inside the SMS Express
tool.  The table itself is editable, i.e. if I just open the table I can
modify values.  Does anyone know if parameterized SPs are supposed to be
editable?
If so, what can cause the SP result set to be Read Only?

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author:              <Author,,Name>
-- Create date: <Create Date,,>
-- Description: <Description,,>
-- =============================================
CREATE PROCEDURE usp_FrmCallListFiltered
        -- Add the parameters for the stored procedure here
        @STID int,
        @DIID int
AS
BEGIN
        -- SET NOCOUNT ON added to prevent extra result sets from
        -- interfering with SELECT statements.
        SET NOCOUNT ON;

    -- Insert statements for procedure here
        SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, tblPeople.PE_Specialty,
tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
tblPeople.PE_Contact1, tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo,
tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
tblPeople.PE_Certification, tblPeople.PE_LIC_Licno,
tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress,
tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, tblPeople.PE_IDDNC,
tblPeople.PE_IDIWH, tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate,
tblPeople.PE_HotLead, tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive,
tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
tblPeople.PE_LIC_IDDI
        FROM tblPeople
        WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
((tblPeople.PE_LIC_IDDI)=@DIID))
        ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;

END
GO

John W. Colby
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 Jan 26 20:57:03 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Thu, 26 Jan 2006 18:57:03 -0800
Subject: [dba-SQLServer] SP read only
In-Reply-To: <009f01c622c2$2620a030$6f00a8c0@ColbyM6805>
References: <D0BF9C78D1C45C418541C852C8944FE2025E6B@qub-xchange-01.ads.qub.ac.uk>
	<009f01c622c2$2620a030$6f00a8c0@ColbyM6805>
Message-ID: <b874372a0601261857r44c31ab9xa901c7c77798423a@mail.gmail.com>

Do you have this set as the record source for your ADP?, if so can you check
that you have the uniquetable property set?, or do you have this as an ODBC
pass through query?

On 1/26/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> Nope, didn't help
>
>
> John W. Colby
> 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, January 26, 2006 4:18 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] SP read only
>
> John
>
> Remove the OrderBY and try it
>
> Martin
>
> Martin WP Reid
> Training and Assessment Unit
> Riddle Hall
> Belfast
>
> tel: 02890 974477
>
>
> ________________________________
>
> From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
> Sent: Thu 26/01/2006 20:59
> To: dba-sqlserver at databaseadvisors.com
> Subject: [dba-SQLServer] SP read only
>
>
>
> Folks,
>
> I have the following SP.  It selects data from a single table, filtered on
> two fields.  Pretty simple.  It is also read-only inside the SMS Express
> tool.  The table itself is editable, i.e. if I just open the table I can
> modify values.  Does anyone know if parameterized SPs are supposed to be
> editable?
> If so, what can cause the SP result set to be Read Only?
>
> SET ANSI_NULLS ON
> GO
> SET QUOTED_IDENTIFIER ON
> GO
> -- =============================================
> -- Author:              <Author,,Name>
> -- Create date: <Create Date,,>
> -- Description: <Description,,>
> -- =============================================
> CREATE PROCEDURE usp_FrmCallListFiltered
>         -- Add the parameters for the stored procedure here
>         @STID int,
>         @DIID int
> AS
> BEGIN
>         -- SET NOCOUNT ON added to prevent extra result sets from
>         -- interfering with SELECT statements.
>         SET NOCOUNT ON;
>
>     -- Insert statements for procedure here
>         SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, tblPeople.PE_Specialty
> ,
> tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
> tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
> tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
> tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
> tblPeople.PE_Contact1, tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo,
> tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
> tblPeople.PE_Certification, tblPeople.PE_LIC_Licno,
> tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress,
> tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, tblPeople.PE_IDDNC,
> tblPeople.PE_IDIWH, tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate,
> tblPeople.PE_HotLead, tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive,
> tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
> tblPeople.PE_LIC_IDDI
>         FROM tblPeople
>         WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
> ((tblPeople.PE_LIC_IDDI)=@DIID))
>         ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;
>
> END
> GO
>
> John W. Colby
> 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
>
>


--
-Francisco
http://pcthis.blogspot.com |PC news with out the jargon!
http://sqlthis.blogspot.com | Tsql and More...


From fhtapia at gmail.com  Thu Jan 26 20:57:57 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Thu, 26 Jan 2006 18:57:57 -0800
Subject: [dba-SQLServer] SP read only
In-Reply-To: <00b101c622de$fa1852e0$6f00a8c0@ColbyM6805>
References: <D0BF9C78D1C45C418541C852C8944FE2025E6C@qub-xchange-01.ads.qub.ac.uk>
	<00b101c622de$fa1852e0$6f00a8c0@ColbyM6805>
Message-ID: <b874372a0601261857l1dceab75o3764168c3db2f6e7@mail.gmail.com>

have you tested an ADO recordset to see if it is editable...?

On 1/26/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> I ran the SP from inside of Server Management Studio express.  I am using
> 2005.  I am not using ADPs so there is no way to directly open a SP from
> Access.  You have to either do an ado recordset or a pass through
> query.  I
> had the pass through working but that was RO.  I have yet to get the
> Recordset working, at least to the point of setting an access object's
> Recordset property (I get an "invalid object").
>
> I am using Microsoft SQL Server Management Studio Express.  I build the
> SPs
> in SMSE and I execute the SP there as well.  I can "open" a table and the
> table is RW, but apparently all (even simple) SPs are RO.  The SPs are RO
> when used via a pass through out in Access.  At this point I have to
> wonder
> if SQL Server 2005 Express has a setting or an intentional limitation
> causing this behavior.
>
> I have built two SPs in SMSE:
>
> SELECT * FROM tlkpState
>
> As well as
>
> SELECT ST_ID, ST_Code FROM tlkpState
>
> This is the smallest, simplest table in the database.  Both of these SPs
> are
> RO.
>
> Going to the db and opening the linked (ODBC) table it is r/w.  Opening
> the
> table directly in SMSE the table is r/w.  It has to do with being a SP.
> What a waste of time.  8(
>
> John W. Colby
> 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, January 26, 2006 5:03 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] SP read only
>
> John
>
> How do you execute the SP from Access?
>
> Martin
>
>
> Martin WP Reid
> Training and Assessment Unit
> Riddle Hall
> Belfast
>
> tel: 02890 974477
>
>
> ________________________________
>
> From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
> Sent: Thu 26/01/2006 21:47
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] SP read only
>
>
>
> Nope, didn't help
>
>
> John W. Colby
> 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, January 26, 2006 4:18 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] SP read only
>
> John
>
> Remove the OrderBY and try it
>
> Martin
>
> Martin WP Reid
> Training and Assessment Unit
> Riddle Hall
> Belfast
>
> tel: 02890 974477
>
>
> ________________________________
>
> From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
> Sent: Thu 26/01/2006 20:59
> To: dba-sqlserver at databaseadvisors.com
> Subject: [dba-SQLServer] SP read only
>
>
>
> Folks,
>
> I have the following SP.  It selects data from a single table, filtered on
> two fields.  Pretty simple.  It is also read-only inside the SMS Express
> tool.  The table itself is editable, i.e. if I just open the table I can
> modify values.  Does anyone know if parameterized SPs are supposed to be
> editable?
> If so, what can cause the SP result set to be Read Only?
>
> SET ANSI_NULLS ON
> GO
> SET QUOTED_IDENTIFIER ON
> GO
> -- =============================================
> -- Author:              <Author,,Name>
> -- Create date: <Create Date,,>
> -- Description: <Description,,>
> -- =============================================
> CREATE PROCEDURE usp_FrmCallListFiltered
>         -- Add the parameters for the stored procedure here
>         @STID int,
>         @DIID int
> AS
> BEGIN
>         -- SET NOCOUNT ON added to prevent extra result sets from
>         -- interfering with SELECT statements.
>         SET NOCOUNT ON;
>
>     -- Insert statements for procedure here
>         SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, tblPeople.PE_Specialty
> ,
> tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
> tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
> tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
> tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
> tblPeople.PE_Contact1, tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo,
> tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
> tblPeople.PE_Certification, tblPeople.PE_LIC_Licno,
> tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress,
> tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, tblPeople.PE_IDDNC,
> tblPeople.PE_IDIWH, tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate,
> tblPeople.PE_HotLead, tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive,
> tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
> tblPeople.PE_LIC_IDDI
>         FROM tblPeople
>         WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
> ((tblPeople.PE_LIC_IDDI)=@DIID))
>         ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;
>
> END
> GO
>
> John W. Colby
> 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 Jan 26 20:58:13 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Thu, 26 Jan 2006 18:58:13 -0800
Subject: [dba-SQLServer] SP read only
In-Reply-To: <b874372a0601261857r44c31ab9xa901c7c77798423a@mail.gmail.com>
References: <D0BF9C78D1C45C418541C852C8944FE2025E6B@qub-xchange-01.ads.qub.ac.uk>
	<009f01c622c2$2620a030$6f00a8c0@ColbyM6805>
	<b874372a0601261857r44c31ab9xa901c7c77798423a@mail.gmail.com>
Message-ID: <b874372a0601261858n42ac7b37r9cc90e6348fe8496@mail.gmail.com>

nevermind, just read your post on it not being adp

On 1/26/06, Francisco Tapia <fhtapia at gmail.com> wrote:
>
> Do you have this set as the record source for your ADP?, if so can you
> check that you have the uniquetable property set?, or do you have this as an
> ODBC pass through query?
>
> On 1/26/06, John Colby <jwcolby at colbyconsulting.com> wrote:
> >
> > Nope, didn't help
> >
> >
> > John W. Colby
> > 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, January 26, 2006 4:18 PM
> > To: dba-sqlserver at databaseadvisors.com
> > Subject: Re: [dba-SQLServer] SP read only
> >
> > John
> >
> > Remove the OrderBY and try it
> >
> > Martin
> >
> > Martin WP Reid
> > Training and Assessment Unit
> > Riddle Hall
> > Belfast
> >
> > tel: 02890 974477
> >
> >
> > ________________________________
> >
> > From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John Colby
> > Sent: Thu 26/01/2006 20:59
> > To: dba-sqlserver at databaseadvisors.com
> > Subject: [dba-SQLServer] SP read only
> >
> >
> >
> > Folks,
> >
> > I have the following SP.  It selects data from a single table, filtered
> > on
> > two fields.  Pretty simple.  It is also read-only inside the SMS Express
> > tool.  The table itself is editable, i.e. if I just open the table I can
> >
> > modify values.  Does anyone know if parameterized SPs are supposed to be
> > editable?
> > If so, what can cause the SP result set to be Read Only?
> >
> > SET ANSI_NULLS ON
> > GO
> > SET QUOTED_IDENTIFIER ON
> > GO
> > -- =============================================
> > -- Author:              <Author,,Name>
> > -- Create date: <Create Date,,>
> > -- Description: <Description,,>
> > -- =============================================
> > CREATE PROCEDURE usp_FrmCallListFiltered
> >         -- Add the parameters for the stored procedure here
> >         @STID int,
> >         @DIID int
> > AS
> > BEGIN
> >         -- SET NOCOUNT ON added to prevent extra result sets from
> >         -- interfering with SELECT statements.
> >         SET NOCOUNT ON;
> >
> >     -- Insert statements for procedure here
> >         SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF,
> > tblPeople.PE_Specialty,
> > tblPeople.PE_LName, tblPeople.PE_FName, tblPeople.PE_MName,
> > tblPeople.PE_Addr1, tblPeople.PE_Addr2, tblPeople.PE_City,
> > tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, tblPeople.PE_IDST,
> > tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, tblPeople.PE_Currempl,
> > tblPeople.PE_Contact1, tblPeople.PE_Licotherstates,
> > tblPeople.PE_RateInfo,
> > tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress,
> > tblPeople.PE_Certification, tblPeople.PE_LIC_Licno,
> > tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress ,
> > tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, tblPeople.PE_IDDNC
> > ,
> > tblPeople.PE_IDIWH, tblPeople.PE_MBIF, tblPeople.PE_MBIFFollowUpDate,
> > tblPeople.PE_HotLead, tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive ,
> > tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
> > tblPeople.PE_LIC_IDDI
> >         FROM tblPeople
> >         WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
> > ((tblPeople.PE_LIC_IDDI)=@DIID))
> >         ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;
> >
> > END
> > GO
> >
> > John W. Colby
> > 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
> >
> >
>
>
> --
> -Francisco
> http://pcthis.blogspot.com |PC news with out the jargon!
> http://sqlthis.blogspot.com | Tsql and More...
>



--
-Francisco
http://pcthis.blogspot.com |PC news with out the jargon!
http://sqlthis.blogspot.com | Tsql and More...


From accessd at shaw.ca  Fri Jan 27 00:08:43 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Thu, 26 Jan 2006 22:08:43 -0800
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <000301c622b2$9f5049c0$8fb3d6d1@SUSANONE>
Message-ID: <002001c62308$20a17300$017ba8c0@xpserver>

Hi Susan:

I have been playing with and have the base for a new application on the new
MS SQL 2005... not the Express version, (Last time the Express version
corrupted things so badly that a full re-install was required) and it runs
excellently and is very stable. There is now too many features on it and MS
SQL is becoming a huge data management pig with so many different modules. I
am sure I am sure I will master it.... 5 years after MS has introduced
another version.

I feel the Express is just 'cripple-ware' and would recommend MySQL for
small low cost jobs.

Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: January 26, 2006 11:57 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

I'm using MS with Express. Use a CREATE PROCEDURE statement and execute it
-- that will save it in the db. I know MS isn't complete for Express, so it
might not be complete for 2005 either. 

And you do that by.....

Part of the problem here I suspect is that I am out on the bleeding edge
trying to use SQL Server 2005 which has a brand new widget for management
called Microsoft SQL Server Management Studio Express.  The old tools don't
work with 2005.  And (apparently) no one on this group is using this thing.

And then of course I am clueless to start with, never having done any of
this before.  I really don't want to spend my time learning the tools for
SQL Server 2000 (I have actually used them a fair amount) because I am
"selling" 2005 Express (can you say FREE?  An easy sell!) to my clients.  As
such I need to learn the tools for 2005 Express.


_______________________________________________
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 Jan 27 06:30:00 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Fri, 27 Jan 2006 07:30:00 -0500
Subject: [dba-SQLServer] SP read only
In-Reply-To: <b874372a0601261857l1dceab75o3764168c3db2f6e7@mail.gmail.com>
Message-ID: <00e401c6233d$64ac2ba0$6f00a8c0@ColbyM6805>

>have you tested an ADO recordset to see if it is editable...?

Nope. 


John W. Colby
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: Thursday, January 26, 2006 9:58 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only

have you tested an ADO recordset to see if it is editable...?

On 1/26/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> I ran the SP from inside of Server Management Studio express.  I am 
> using 2005.  I am not using ADPs so there is no way to directly open a 
> SP from Access.  You have to either do an ado recordset or a pass 
> through query.  I had the pass through working but that was RO.  I 
> have yet to get the Recordset working, at least to the point of 
> setting an access object's Recordset property (I get an "invalid 
> object").
>
> I am using Microsoft SQL Server Management Studio Express.  I build 
> the SPs in SMSE and I execute the SP there as well.  I can "open" a 
> table and the table is RW, but apparently all (even simple) SPs are 
> RO.  The SPs are RO when used via a pass through out in Access.  At 
> this point I have to wonder if SQL Server 2005 Express has a setting 
> or an intentional limitation causing this behavior.
>
> I have built two SPs in SMSE:
>
> SELECT * FROM tlkpState
>
> As well as
>
> SELECT ST_ID, ST_Code FROM tlkpState
>
> This is the smallest, simplest table in the database.  Both of these 
> SPs are RO.
>
> Going to the db and opening the linked (ODBC) table it is r/w.  
> Opening the table directly in SMSE the table is r/w.  It has to do 
> with being a SP.
> What a waste of time.  8(
>
> John W. Colby
> 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, January 26, 2006 5:03 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] SP read only
>
> John
>
> How do you execute the SP from Access?
>
> Martin
>
>
> Martin WP Reid
> Training and Assessment Unit
> Riddle Hall
> Belfast
>
> tel: 02890 974477
>
>
> ________________________________
>
> From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John 
> Colby
> Sent: Thu 26/01/2006 21:47
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] SP read only
>
>
>
> Nope, didn't help
>
>
> John W. Colby
> 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, January 26, 2006 4:18 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] SP read only
>
> John
>
> Remove the OrderBY and try it
>
> Martin
>
> Martin WP Reid
> Training and Assessment Unit
> Riddle Hall
> Belfast
>
> tel: 02890 974477
>
>
> ________________________________
>
> From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John 
> Colby
> Sent: Thu 26/01/2006 20:59
> To: dba-sqlserver at databaseadvisors.com
> Subject: [dba-SQLServer] SP read only
>
>
>
> Folks,
>
> I have the following SP.  It selects data from a single table, 
> filtered on two fields.  Pretty simple.  It is also read-only inside 
> the SMS Express tool.  The table itself is editable, i.e. if I just 
> open the table I can modify values.  Does anyone know if parameterized 
> SPs are supposed to be editable?
> If so, what can cause the SP result set to be Read Only?
>
> SET ANSI_NULLS ON
> GO
> SET QUOTED_IDENTIFIER ON
> GO
> -- =============================================
> -- Author:              <Author,,Name>
> -- Create date: <Create Date,,>
> -- Description: <Description,,>
> -- =============================================
> CREATE PROCEDURE usp_FrmCallListFiltered
>         -- Add the parameters for the stored procedure here
>         @STID int,
>         @DIID int
> AS
> BEGIN
>         -- SET NOCOUNT ON added to prevent extra result sets from
>         -- interfering with SELECT statements.
>         SET NOCOUNT ON;
>
>     -- Insert statements for procedure here
>         SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, 
> tblPeople.PE_Specialty , tblPeople.PE_LName, tblPeople.PE_FName, 
> tblPeople.PE_MName, tblPeople.PE_Addr1, tblPeople.PE_Addr2, 
> tblPeople.PE_City, tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, 
> tblPeople.PE_IDST, tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, 
> tblPeople.PE_Currempl, tblPeople.PE_Contact1, 
> tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo, 
> tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress, 
> tblPeople.PE_Certification, tblPeople.PE_LIC_Licno, 
> tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress, 
> tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, 
> tblPeople.PE_IDDNC, tblPeople.PE_IDIWH, tblPeople.PE_MBIF, 
> tblPeople.PE_MBIFFollowUpDate, tblPeople.PE_HotLead, 
> tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive, 
> tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
tblPeople.PE_LIC_IDDI
>         FROM tblPeople
>         WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
> ((tblPeople.PE_LIC_IDDI)=@DIID))
>         ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;
>
> END
> GO
>
> John W. Colby
> 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 Paul.Hartland at orridge.co.uk  Fri Jan 27 06:38:27 2006
From: Paul.Hartland at orridge.co.uk (Paul Hartland)
Date: Fri, 27 Jan 2006 12:38:27 -0000
Subject: [dba-SQLServer] SP read only
Message-ID: <14A7AB003EFD444BBB193A23128DA20EC033E9@AL-PRI.Aldridge.local>

Just a sideline to this discussion about read only stored procedures, is
it possible to have an updateable stored procedure recordset in visual
basic ?

If so, anyone know how I go about doing this ?

Thanks in advance for any help on this. 


PAUL HARTLAND
Database Designer/Programmer
paul.hartland at orridge.co.uk
DDI - 01922 472031
Mobile - 07730 523179


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John
Colby
Sent: 27 January 2006 12:30
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only

>have you tested an ADO recordset to see if it is editable...?

Nope. 


John W. Colby
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: Thursday, January 26, 2006 9:58 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SP read only

have you tested an ADO recordset to see if it is editable...?

On 1/26/06, John Colby <jwcolby at colbyconsulting.com> wrote:
>
> I ran the SP from inside of Server Management Studio express.  I am 
> using 2005.  I am not using ADPs so there is no way to directly open a

> SP from Access.  You have to either do an ado recordset or a pass 
> through query.  I had the pass through working but that was RO.  I 
> have yet to get the Recordset working, at least to the point of 
> setting an access object's Recordset property (I get an "invalid 
> object").
>
> I am using Microsoft SQL Server Management Studio Express.  I build 
> the SPs in SMSE and I execute the SP there as well.  I can "open" a 
> table and the table is RW, but apparently all (even simple) SPs are 
> RO.  The SPs are RO when used via a pass through out in Access.  At 
> this point I have to wonder if SQL Server 2005 Express has a setting 
> or an intentional limitation causing this behavior.
>
> I have built two SPs in SMSE:
>
> SELECT * FROM tlkpState
>
> As well as
>
> SELECT ST_ID, ST_Code FROM tlkpState
>
> This is the smallest, simplest table in the database.  Both of these 
> SPs are RO.
>
> Going to the db and opening the linked (ODBC) table it is r/w.  
> Opening the table directly in SMSE the table is r/w.  It has to do 
> with being a SP.
> What a waste of time.  8(
>
> John W. Colby
> 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, January 26, 2006 5:03 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] SP read only
>
> John
>
> How do you execute the SP from Access?
>
> Martin
>
>
> Martin WP Reid
> Training and Assessment Unit
> Riddle Hall
> Belfast
>
> tel: 02890 974477
>
>
> ________________________________
>
> From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John 
> Colby
> Sent: Thu 26/01/2006 21:47
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] SP read only
>
>
>
> Nope, didn't help
>
>
> John W. Colby
> 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, January 26, 2006 4:18 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] SP read only
>
> John
>
> Remove the OrderBY and try it
>
> Martin
>
> Martin WP Reid
> Training and Assessment Unit
> Riddle Hall
> Belfast
>
> tel: 02890 974477
>
>
> ________________________________
>
> From: dba-sqlserver-bounces at databaseadvisors.com on behalf of John 
> Colby
> Sent: Thu 26/01/2006 20:59
> To: dba-sqlserver at databaseadvisors.com
> Subject: [dba-SQLServer] SP read only
>
>
>
> Folks,
>
> I have the following SP.  It selects data from a single table, 
> filtered on two fields.  Pretty simple.  It is also read-only inside 
> the SMS Express tool.  The table itself is editable, i.e. if I just 
> open the table I can modify values.  Does anyone know if parameterized

> SPs are supposed to be editable?
> If so, what can cause the SP result set to be Read Only?
>
> SET ANSI_NULLS ON
> GO
> SET QUOTED_IDENTIFIER ON
> GO
> -- =============================================
> -- Author:              <Author,,Name>
> -- Create date: <Create Date,,>
> -- Description: <Description,,>
> -- =============================================
> CREATE PROCEDURE usp_FrmCallListFiltered
>         -- Add the parameters for the stored procedure here
>         @STID int,
>         @DIID int
> AS
> BEGIN
>         -- SET NOCOUNT ON added to prevent extra result sets from
>         -- interfering with SELECT statements.
>         SET NOCOUNT ON;
>
>     -- Insert statements for procedure here
>         SELECT tblPeople.PE_ID, tblPeople.PE_IDCRF, 
> tblPeople.PE_Specialty , tblPeople.PE_LName, tblPeople.PE_FName, 
> tblPeople.PE_MName, tblPeople.PE_Addr1, tblPeople.PE_Addr2, 
> tblPeople.PE_City, tblPeople.PE_Zipcode1, tblPeople.PE_Zipcode2, 
> tblPeople.PE_IDST, tblPeople.PE_PhoneH, tblPeople.PE_PhoneW, 
> tblPeople.PE_Currempl, tblPeople.PE_Contact1, 
> tblPeople.PE_Licotherstates, tblPeople.PE_RateInfo, 
> tblPeople.PE_Worktime, tblPeople.PE_Email, tblPeople.PE_BusAddress, 
> tblPeople.PE_Certification, tblPeople.PE_LIC_Licno, 
> tblPeople.PE_DateStampName, tblPeople.PE_DateStampAddress, 
> tblPeople.PE_DateStampPhoneH, tblPeople.PE_PhoneCell, 
> tblPeople.PE_IDDNC, tblPeople.PE_IDIWH, tblPeople.PE_MBIF, 
> tblPeople.PE_MBIFFollowUpDate, tblPeople.PE_HotLead, 
> tblPeople.PE_HotLeadNotes, tblPeople.PE_Inactive, 
> tblPeople.PE_NoHomePhoneInfo, tblPeople.PE_FOE, tblPeople.PE_LIC_IDST,
tblPeople.PE_LIC_IDDI
>         FROM tblPeople
>         WHERE (((tblPeople.PE_LIC_IDST)=@STID) AND
> ((tblPeople.PE_LIC_IDDI)=@DIID))
>         ORDER BY tblPeople.PE_LName, tblPeople.PE_FName;
>
> END
> GO
>
> John W. Colby
> 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

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


_______________________________________________

*  This message is confidential.
*  This email, its content and any files transmitted with it are intended solely for the addressee and may be legally privileged and/or confidential.
*  Access by any other party is unauthorised without the express written permission of the sender.
*  If you have received this email in error you may not copy or use the contents, attachments or information in any way and any review, use, dissemination, forwarding, disclosure, alteration, printing of this information is strictly prohibited. Please destroy it and notify the sender via return e-mail.
*  This email has been prepared using information believed by Paul Hartland to be reliable and accurate, but the company makes no warranty as to accuracy or completeness. In particular the author does not accept responsibility for changes made to this email after it was sent.
*  Any opinions expressed in this document are those of the author and do not necessarily reflect the opinions of the company or its affiliates.

The Orridge web site can be found at:
http://www.orridge.co.uk




From harkinsss at bellsouth.net  Fri Jan 27 07:56:01 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Fri, 27 Jan 2006 08:56:01 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <002001c62308$20a17300$017ba8c0@xpserver>
Message-ID: <001801c62349$b7ef35d0$aeb3d6d1@SUSANONE>

I feel the Express is just 'cripple-ware' and would recommend MySQL for
small low cost jobs.

===I had to reformat to get Management Studio to work, but now that I have
all the pieces working, including VB Express, I have to tell you -- it is
working great and I love it. The entire package brings a level of
development to the little guy that I've never seen before. They can do a
whole lot and never write a line of code -- VB Express does it all for them.


I have to say I disagree unless MySQL has changed a lot. I haven't looked at
it in a long time, so that's possible, but it was terribly difficult to use,
just a few years ago. 

Management Studio makes Express easy to manage. VB Express makes it easy to
develop. 

It's a winner even though I'm still mad at MS for putting us all through so
much installation crap to get here. 

Susan H. 



From harkinsss at bellsouth.net  Fri Jan 27 08:07:20 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Fri, 27 Jan 2006 09:07:20 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <002001c62308$20a17300$017ba8c0@xpserver>
Message-ID: <000801c6234b$0315af70$aeb3d6d1@SUSANONE>

I feel the Express is just 'cripple-ware' and would recommend MySQL for
small low cost jobs.

===I had to reformat to get Management Studio to work, but now that I have
all the pieces working, including VB Express, I have to tell you -- it is
working great and I love it. The entire package brings a level of
development to the little guy that I've never seen before. They can do a
whole lot and never write a line of code -- VB Express does it all for them.


I have to say I disagree unless MySQL has changed a lot. I haven't looked at
it in a long time, so that's possible, but it was terribly difficult to use,
just a few years ago. 

Management Studio makes Express easy to manage. VB Express makes it easy to
develop. 

It's a winner even though I'm still mad at MS for putting us all through so
much installation crap to get here. 

Susan H. 



From jwcolby at ColbyConsulting.com  Fri Jan 27 09:43:49 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Fri, 27 Jan 2006 10:43:49 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <001801c62349$b7ef35d0$aeb3d6d1@SUSANONE>
Message-ID: <00ed01c62358$784d3da0$6f00a8c0@ColbyM6805>

I have to say, overall, I agree.

SQL Server 2005 is FREE!  It is SQL Server with a few insignificant (for the
intended market) limitations.  It won't use more than one processor, nor
more than 1 gb of ram for it's buffers, and of course it has a max FILE SIZE
of 4gb, although you can have databases in different files, each 4 GB max.
For small databases it is an extremely powerful Server.

Management Studio is FREE!  

VB Express is FREE.  It integrates seamlessly with SQL Server Express,
including the ability to build tables out in SQL Server right inside of
VB.Net Express.

My understanding is that SQL Server uses VB.NET as it's internal scripting
language which opens up what you can do with Stored procedures.

This is an awesome combination of FREE stuff.  

To be honest, once I get over the learning curve I am leaning towards
abandoning the MDB as a BE.  Do everything from the ground up in SQL Server
Express and if the time ever comes where the client needs the power of the
full on version, they just go there.  No migration, no headaches.  You have
the ability to develop Access apps that talk to it for quick internal stuff,
VB.NET and ASP.NET for Internet apps if you need them.

This assumes of course that I get the "SPs are read-only" issue cleared up.

John W. Colby
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: Friday, January 27, 2006 8:56 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

I feel the Express is just 'cripple-ware' and would recommend MySQL for
small low cost jobs.

===I had to reformat to get Management Studio to work, but now that I have
all the pieces working, including VB Express, I have to tell you -- it is
working great and I love it. The entire package brings a level of
development to the little guy that I've never seen before. They can do a
whole lot and never write a line of code -- VB Express does it all for them.


I have to say I disagree unless MySQL has changed a lot. I haven't looked at
it in a long time, so that's possible, but it was terribly difficult to use,
just a few years ago. 

Management Studio makes Express easy to manage. VB Express makes it easy to
develop. 

It's a winner even though I'm still mad at MS for putting us all through so
much installation crap to get here. 

Susan H. 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From cfoust at infostatsystems.com  Fri Jan 27 10:25:48 2006
From: cfoust at infostatsystems.com (Charlotte Foust)
Date: Fri, 27 Jan 2006 08:25:48 -0800
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
Message-ID: <F55048AF7E974F429BB24597D7355EEABF67@INFOSERVER04.infostat.local>

Lovely!  So now that development is so easy, we can expect to see
horrible database design in VBExpress and not just in Access. :o{

Charlotte Foust


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: Friday, January 27, 2006 5:56 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio


I feel the Express is just 'cripple-ware' and would recommend MySQL for
small low cost jobs.

===I had to reformat to get Management Studio to work, but now that I
have all the pieces working, including VB Express, I have to tell you --
it is working great and I love it. The entire package brings a level of
development to the little guy that I've never seen before. They can do a
whole lot and never write a line of code -- VB Express does it all for
them.


I have to say I disagree unless MySQL has changed a lot. I haven't
looked at it in a long time, so that's possible, but it was terribly
difficult to use, just a few years ago. 

Management Studio makes Express easy to manage. VB Express makes it easy
to develop. 

It's a winner even though I'm still mad at MS for putting us all through
so much installation crap to get here. 

Susan H. 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From cfoust at infostatsystems.com  Fri Jan 27 10:27:13 2006
From: cfoust at infostatsystems.com (Charlotte Foust)
Date: Fri, 27 Jan 2006 08:27:13 -0800
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
Message-ID: <F55048AF7E974F429BB24597D7355EEABF68@INFOSERVER04.infostat.local>

By Office 12, you're pretty much going to have to abandon the mdb
anyhow, John.  Might as well start early!

Charlotte Foust


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John
Colby
Sent: Friday, January 27, 2006 7:44 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio


I have to say, overall, I agree.

SQL Server 2005 is FREE!  It is SQL Server with a few insignificant (for
the intended market) limitations.  It won't use more than one processor,
nor more than 1 gb of ram for it's buffers, and of course it has a max
FILE SIZE of 4gb, although you can have databases in different files,
each 4 GB max. For small databases it is an extremely powerful Server.

Management Studio is FREE!  

VB Express is FREE.  It integrates seamlessly with SQL Server Express,
including the ability to build tables out in SQL Server right inside of
VB.Net Express.

My understanding is that SQL Server uses VB.NET as it's internal
scripting language which opens up what you can do with Stored
procedures.

This is an awesome combination of FREE stuff.  

To be honest, once I get over the learning curve I am leaning towards
abandoning the MDB as a BE.  Do everything from the ground up in SQL
Server Express and if the time ever comes where the client needs the
power of the full on version, they just go there.  No migration, no
headaches.  You have the ability to develop Access apps that talk to it
for quick internal stuff, VB.NET and ASP.NET for Internet apps if you
need them.

This assumes of course that I get the "SPs are read-only" issue cleared
up.

John W. Colby
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: Friday, January 27, 2006 8:56 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

I feel the Express is just 'cripple-ware' and would recommend MySQL for
small low cost jobs.

===I had to reformat to get Management Studio to work, but now that I
have all the pieces working, including VB Express, I have to tell you --
it is working great and I love it. The entire package brings a level of
development to the little guy that I've never seen before. They can do a
whole lot and never write a line of code -- VB Express does it all for
them.


I have to say I disagree unless MySQL has changed a lot. I haven't
looked at it in a long time, so that's possible, but it was terribly
difficult to use, just a few years ago. 

Management Studio makes Express easy to manage. VB Express makes it easy
to develop. 

It's a winner even though I'm still mad at MS for putting us all through
so much installation crap to get here. 

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



From artful at rogers.com  Fri Jan 27 10:36:24 2006
From: artful at rogers.com (Arthur Fuller)
Date: Fri, 27 Jan 2006 11:36:24 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <00ed01c62358$784d3da0$6f00a8c0@ColbyM6805>
Message-ID: <001801c6235f$d03b72a0$8e01a8c0@rock>

>> My understanding is that SQL Server uses VB.NET as it's internal
scripting language which opens up what you can do with Stored procedures.
Not quite true. SQL 2005 includes the .NET framework in its installation and
permits you to use either VB.NET and C#.NET in stored procedures. But MS
itself says the new languages are not intended to replace TSQL, which
remains the principal language for sprocs and UDFs. It is emphatically not
recommended to rewrite all your stored procedures using these languages.
These language extenstions are intended for special-case situations, in
particular when working with row-by-row logic, and when writing to multiple
target tables from within a sproc, where the concept of a recordset may be
useful. TSQL can do these sorts of things but the syntax is clumsy. Note
also that the .NET languages impose a performance penalty. Equivalent TSQL
will run more quickly.
Finally, I think that the presence of .NET languages in SQL Server will
probably result in a bunch of .NET developers thinking that they know how to
manipulate a SQL Server. In other words, there will be a LOT of work
available in a year or so for TSQL experts, increasing the performance of
code written in .NET.
Arthur



From artful at rogers.com  Fri Jan 27 10:41:59 2006
From: artful at rogers.com (Arthur Fuller)
Date: Fri, 27 Jan 2006 11:41:59 -0500
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <b874372a0601251639i391e9a7dr11b775dafd5699e8@mail.gmail.com>
Message-ID: <001901c62360$980c18c0$8e01a8c0@rock>

You will forget all about EM and QA in the first 10 minutes after running
SQL 2005 Studio! And you are quite right -- the loss of being able to create
and edit sprocs and UDFs within Access means nothing, now that Studio is
here. It is pretty much everything I ever wanted, except that it doesn't
automatically invoice my clients LOL.

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco
Tapia
Sent: January 25, 2006 7:39 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Upsize wizard and named queries

do you have a link?... as for the inline editing of the SPs, that does not
affect me on my platform as I prefer QA than the ADP as sql dev tool.



From fhtapia at gmail.com  Fri Jan 27 10:53:41 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Fri, 27 Jan 2006 08:53:41 -0800
Subject: [dba-SQLServer] Remote Servers...
Message-ID: <b874372a0601270853m4586ff4n725fd490830ae32f@mail.gmail.com>

We have a remote server wich hosts our website, it also contains a sql
server and data we collect for our users filling out surveys.  I have a job
initiates a DTS job and collects the new data and transfers it inhouse (this
is initiated from an inhouse sql server).  I also have a report off an
in-house reporting services box that runs reports on the collected data, the
data is comming from 2 sources, the survey is from the remote sql server,
while the remaining data is from an internal sql server.  The issue we're
running into is that customers will fill out their survey and want to
instantly see the results.  Additionally they'll affect the other sources of
data run the report and are spoiled that the data is live.  MGMT likes the
data live, and thus I'm wondering how to approach the 1hr pull from the
remote sql server.

I'm considering adding a linked server and then when the report is ran, just
pull over the new data, but keep the 1hr snapshot... this way the data is
always current.  Anythoughts on this?

Thanks,

--
-Francisco
http://pcthis.blogspot.com |PC news with out the jargon!
http://sqlthis.blogspot.com | Tsql and More...


From fhtapia at gmail.com  Fri Jan 27 10:54:41 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Fri, 27 Jan 2006 08:54:41 -0800
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <001901c62360$980c18c0$8e01a8c0@rock>
References: <b874372a0601251639i391e9a7dr11b775dafd5699e8@mail.gmail.com>
	<001901c62360$980c18c0$8e01a8c0@rock>
Message-ID: <b874372a0601270854t15e9091fsee360de48b19a392@mail.gmail.com>

nice review... i created a VM w/ Sql2005, i've yet to play with it :(

On 1/27/06, Arthur Fuller <artful at rogers.com> wrote:
>
> You will forget all about EM and QA in the first 10 minutes after running
> SQL 2005 Studio! And you are quite right -- the loss of being able to
> create
> and edit sprocs and UDFs within Access means nothing, now that Studio is
> here. It is pretty much everything I ever wanted, except that it doesn't
> automatically invoice my clients LOL.
>
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco
> Tapia
> Sent: January 25, 2006 7:39 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] Upsize wizard and named queries
>
> do you have a link?... as for the inline editing of the SPs, that does not
> affect me on my platform as I prefer QA than the ADP as sql dev tool.
>
> _______________________________________________
> 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  Fri Jan 27 11:14:58 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Fri, 27 Jan 2006 12:14:58 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <F55048AF7E974F429BB24597D7355EEABF67@INFOSERVER04.infostat.local>
Message-ID: <000001c62365$33b75600$657aa8c0@ColbyM6805>

Uhhh yep.  Perhaps to a smaller extent though since VB.Net itself is a bitch
to learn, whereas Access is easy to learn. 


John W. Colby
www.ColbyConsulting.com 


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Friday, January 27, 2006 11:26 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

Lovely!  So now that development is so easy, we can expect to see horrible
database design in VBExpress and not just in Access. :o{

Charlotte Foust


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: Friday, January 27, 2006 5:56 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio


I feel the Express is just 'cripple-ware' and would recommend MySQL for
small low cost jobs.

===I had to reformat to get Management Studio to work, but now that I have
all the pieces working, including VB Express, I have to tell you -- it is
working great and I love it. The entire package brings a level of
development to the little guy that I've never seen before. They can do a
whole lot and never write a line of code -- VB Express does it all for them.


I have to say I disagree unless MySQL has changed a lot. I haven't looked at
it in a long time, so that's possible, but it was terribly difficult to use,
just a few years ago. 

Management Studio makes Express easy to manage. VB Express makes it easy to
develop. 

It's a winner even though I'm still mad at MS for putting us all through so
much installation crap to get here. 

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



From harkinsss at bellsouth.net  Fri Jan 27 11:19:34 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Fri, 27 Jan 2006 12:19:34 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <F55048AF7E974F429BB24597D7355EEABF67@INFOSERVER04.infostat.local>
Message-ID: <002801c62365$d8720d20$aeb3d6d1@SUSANONE>

More work for you Charlotte. :) 

Susan H. 

Lovely!  So now that development is so easy, we can expect to see horrible
database design in VBExpress and not just in Access. :o{



From harkinsss at bellsouth.net  Fri Jan 27 11:19:34 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Fri, 27 Jan 2006 12:19:34 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <00ed01c62358$784d3da0$6f00a8c0@ColbyM6805>
Message-ID: <002a01c62365$e41183e0$aeb3d6d1@SUSANONE>


To be honest, once I get over the learning curve I am leaning towards
abandoning the MDB as a BE.  

========John, if I stay in this market, I am seriously considering the same
thing. 

Susan H. 



From accessd at shaw.ca  Fri Jan 27 12:39:52 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Fri, 27 Jan 2006 10:39:52 -0800
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <001801c62349$b7ef35d0$aeb3d6d1@SUSANONE>
Message-ID: <004801c62371$0f8ccc40$017ba8c0@xpserver>

Hi Susan:

I am glad to hear you have it all working. I feel that you can not have SQL
Express and a full version MS SQL version running on the same machine unless
it is through Virtual Server.

Like MS SQL, MySQL is an awkward package to work with unless you have a
decent management interface. (You have to have 'PHP' and 'PhpMyAdmin'
installed on your station.)

When you get all the bugs out would you be up to answering some question on
your process. A third re-install is not in my immediate future and I hate
tempting fate especially if an upgrade may extend to a client or two.

Jim    

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan
Harkins
Sent: January 27, 2006 5:56 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

I feel the Express is just 'cripple-ware' and would recommend MySQL for
small low cost jobs.

===I had to reformat to get Management Studio to work, but now that I have
all the pieces working, including VB Express, I have to tell you -- it is
working great and I love it. The entire package brings a level of
development to the little guy that I've never seen before. They can do a
whole lot and never write a line of code -- VB Express does it all for them.


I have to say I disagree unless MySQL has changed a lot. I haven't looked at
it in a long time, so that's possible, but it was terribly difficult to use,
just a few years ago. 

Management Studio makes Express easy to manage. VB Express makes it easy to
develop. 

It's a winner even though I'm still mad at MS for putting us all through so
much installation crap to get here. 

Susan H. 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From accessd at shaw.ca  Fri Jan 27 12:51:52 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Fri, 27 Jan 2006 10:51:52 -0800
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <00ed01c62358$784d3da0$6f00a8c0@ColbyM6805>
Message-ID: <004901c62372$bc951a90$017ba8c0@xpserver>

Well, it looks like a very promising future in application design... I am
still a little gun shy after having to re-install my OS 2x (possible because
of beta versions). Any recommendations, process steps, things-to-avoid,
potential conflicts would be greatly appreciated.

Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: January 27, 2006 7:44 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

I have to say, overall, I agree.

SQL Server 2005 is FREE!  It is SQL Server with a few insignificant (for the
intended market) limitations.  It won't use more than one processor, nor
more than 1 gb of ram for it's buffers, and of course it has a max FILE SIZE
of 4gb, although you can have databases in different files, each 4 GB max.
For small databases it is an extremely powerful Server.

Management Studio is FREE!  

VB Express is FREE.  It integrates seamlessly with SQL Server Express,
including the ability to build tables out in SQL Server right inside of
VB.Net Express.

My understanding is that SQL Server uses VB.NET as it's internal scripting
language which opens up what you can do with Stored procedures.

This is an awesome combination of FREE stuff.  

To be honest, once I get over the learning curve I am leaning towards
abandoning the MDB as a BE.  Do everything from the ground up in SQL Server
Express and if the time ever comes where the client needs the power of the
full on version, they just go there.  No migration, no headaches.  You have
the ability to develop Access apps that talk to it for quick internal stuff,
VB.NET and ASP.NET for Internet apps if you need them.

This assumes of course that I get the "SPs are read-only" issue cleared up.

John W. Colby
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: Friday, January 27, 2006 8:56 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

I feel the Express is just 'cripple-ware' and would recommend MySQL for
small low cost jobs.

===I had to reformat to get Management Studio to work, but now that I have
all the pieces working, including VB Express, I have to tell you -- it is
working great and I love it. The entire package brings a level of
development to the little guy that I've never seen before. They can do a
whole lot and never write a line of code -- VB Express does it all for them.


I have to say I disagree unless MySQL has changed a lot. I haven't looked at
it in a long time, so that's possible, but it was terribly difficult to use,
just a few years ago. 

Management Studio makes Express easy to manage. VB Express makes it easy to
develop. 

It's a winner even though I'm still mad at MS for putting us all through so
much installation crap to get here. 

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



From accessd at shaw.ca  Fri Jan 27 12:56:58 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Fri, 27 Jan 2006 10:56:58 -0800
Subject: [dba-SQLServer] Upsize wizard and named queries
In-Reply-To: <001901c62360$980c18c0$8e01a8c0@rock>
Message-ID: <004a01c62373$731cb430$017ba8c0@xpserver>

This all sounds extremely promising. The probelm of automatically invoicing
the clients is where you the programmer come in.

Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Arthur
Fuller
Sent: January 27, 2006 8:42 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Upsize wizard and named queries

You will forget all about EM and QA in the first 10 minutes after running
SQL 2005 Studio! And you are quite right -- the loss of being able to create
and edit sprocs and UDFs within Access means nothing, now that Studio is
here. It is pretty much everything I ever wanted, except that it doesn't
automatically invoice my clients LOL.

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco
Tapia
Sent: January 25, 2006 7:39 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Upsize wizard and named queries

do you have a link?... as for the inline editing of the SPs, that does not
affect me on my platform as I prefer QA than the ADP as sql dev tool.

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From dwaters at usinternet.com  Fri Jan 27 13:44:32 2006
From: dwaters at usinternet.com (Dan Waters)
Date: Fri, 27 Jan 2006 13:44:32 -0600
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <8806641.1138379373118.JavaMail.root@sniper39>
Message-ID: <001c01c6237a$18edd5a0$0200a8c0@danwaters>

Charlotte - MS has said that development capability will continue with
Access 12.  Why to you say we'll have to abandon the .mdb anyhow?

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Friday, January 27, 2006 10:27 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

By Office 12, you're pretty much going to have to abandon the mdb
anyhow, John.  Might as well start early!

Charlotte Foust



From harkinsss at bellsouth.net  Fri Jan 27 14:36:58 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Fri, 27 Jan 2006 15:36:58 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <004901c62372$bc951a90$017ba8c0@xpserver>
Message-ID: <000901c62381$74bca030$e1b3d6d1@SUSANONE>

The only real advice there is Jim -- don't install betas. :) 

As for MS, SS Express, and VB Express, the kinks finally seem to be worked
out. 

Susan H. 

Well, it looks like a very promising future in application design... I am
still a little gun shy after having to re-install my OS 2x (possible because
of beta versions). Any recommendations, process steps, things-to-avoid,
potential conflicts would be greatly appreciated.



From rl_stewart at highstream.net  Sat Jan 28 08:37:18 2006
From: rl_stewart at highstream.net (Robert L. Stewart)
Date: Sat, 28 Jan 2006 08:37:18 -0600
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <mailman.5.1138384804.26249.dba-sqlserver@databaseadvisors. com>
References: <mailman.5.1138384804.26249.dba-sqlserver@databaseadvisors.com>
Message-ID: <6.2.3.4.2.20060128081313.0328d848@pop3.highstream.net>

I am already going that way and have been for over a year.  The 
problem is that I essentially have wasted the last year because the 
difference between VS 2003 and 2005 is so radical.  Now I am relearning.

John,

What is the SPs read-only problem?  Can you explain what you are 
trying to do again?

Robert

At 12:00 PM 1/27/2006, you wrote:
>Date: Fri, 27 Jan 2006 12:19:34 -0500
>From: "Susan Harkins" <harkinsss at bellsouth.net>
>Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <002a01c62365$e41183e0$aeb3d6d1 at SUSANONE>
>Content-Type: text/plain;       charset="us-ascii"
>
>
>To be honest, once I get over the learning curve I am leaning towards
>abandoning the MDB as a BE.
>
>========John, if I stay in this market, I am seriously considering the same
>thing.
>
>Susan H.




From jwcolby at ColbyConsulting.com  Sat Jan 28 09:16:23 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Sat, 28 Jan 2006 10:16:23 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <6.2.3.4.2.20060128081313.0328d848@pop3.highstream.net>
Message-ID: <002601c6241d$cd9ce1a0$657aa8c0@ColbyM6805>

Build a SP in 2005 (express for me).  It is read-only, regardless of whether
I try and edit the data it inside of SMSE or in a pass-through out in
Access.

I am trying to bind a form to a SP recordset.


John W. Colby
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: Saturday, January 28, 2006 9:37 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

I am already going that way and have been for over a year.  The problem is
that I essentially have wasted the last year because the difference between
VS 2003 and 2005 is so radical.  Now I am relearning.

John,

What is the SPs read-only problem?  Can you explain what you are trying to
do again?

Robert

At 12:00 PM 1/27/2006, you wrote:
>Date: Fri, 27 Jan 2006 12:19:34 -0500
>From: "Susan Harkins" <harkinsss at bellsouth.net>
>Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <002a01c62365$e41183e0$aeb3d6d1 at SUSANONE>
>Content-Type: text/plain;       charset="us-ascii"
>
>
>To be honest, once I get over the learning curve I am leaning towards 
>abandoning the MDB as a BE.
>
>========John, if I stay in this market, I am seriously considering the 
>same thing.
>
>Susan H.


_______________________________________________
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  Sat Jan 28 09:37:54 2006
From: mwp.reid at qub.ac.uk (Martin Reid)
Date: Sat, 28 Jan 2006 15:37:54 -0000
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
Message-ID: <200601281537.k0SFbr109544@databaseadvisors.com>

john

pt will return ready only. 
try open ur sp and assigning it using command object. dont use set rst=cnmd.execute.

use

rst.open cnmd

-----Original Message-----
From:	"dba-sqlserver-bounces at databaseadvisors.com" <dba-sqlserver-bounces at databaseadvisors.com> on behalf of	"John Colby" <jwcolby at colbyconsulting.com>
Sent:	28 January 2006 15:16
To:	"dba-sqlserver at databaseadvisors.com" <dba-sqlserver at databaseadvisors.com>
Subject:	Re: [dba-SQLServer] SQL 2005 Server Management Studio

Build a SP in 2005 (express for me).  It is read-only, regardless of whether
I try and edit the data it inside of SMSE or in a pass-through out in
Access.

I am trying to bind a form to a SP recordset.


John W. Colby
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: Saturday, January 28, 2006 9:37 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

I am already going that way and have been for over a year.  The problem is
that I essentially have wasted the last year because the difference between
VS 2003 and 2005 is so radical.  Now I am relearning.

John,

What is the SPs read-only problem?  Can you explain what you are trying to
do again?

Robert

At 12:00 PM 1/27/2006, you wrote:
>Date: Fri, 27 Jan 2006 12:19:34 -0500
>From: "Susan Harkins" <harkinsss at bellsouth.net>
>Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <002a01c62365$e41183e0$aeb3d6d1 at SUSANONE>
>Content-Type: text/plain;       charset="us-ascii"
>
>
>To be honest, once I get over the learning curve I am leaning towards 
>abandoning the MDB as a BE.
>
>========John, if I stay in this market, I am seriously considering the 
>same thing.
>
>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



From jwcolby at ColbyConsulting.com  Sat Jan 28 10:09:13 2006
From: jwcolby at ColbyConsulting.com (John Colby)
Date: Sat, 28 Jan 2006 11:09:13 -0500
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <200601281537.k0SFbr109544@databaseadvisors.com>
Message-ID: <002701c62425$2e9ae1d0$657aa8c0@ColbyM6805>

Ohhhh... Thanks for that.  I'll try it and get back.

The strange part is I would expect it to be R/W directly in SMSE. 


John W. Colby
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: Saturday, January 28, 2006 10:38 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

john

pt will return ready only. 
try open ur sp and assigning it using command object. dont use set
rst=cnmd.execute.

use

rst.open cnmd

-----Original Message-----
From:	"dba-sqlserver-bounces at databaseadvisors.com"
<dba-sqlserver-bounces at databaseadvisors.com> on behalf of	"John Colby"
<jwcolby at colbyconsulting.com>
Sent:	28 January 2006 15:16
To:	"dba-sqlserver at databaseadvisors.com"
<dba-sqlserver at databaseadvisors.com>
Subject:	Re: [dba-SQLServer] SQL 2005 Server Management Studio

Build a SP in 2005 (express for me).  It is read-only, regardless of whether
I try and edit the data it inside of SMSE or in a pass-through out in
Access.

I am trying to bind a form to a SP recordset.


John W. Colby
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: Saturday, January 28, 2006 9:37 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

I am already going that way and have been for over a year.  The problem is
that I essentially have wasted the last year because the difference between
VS 2003 and 2005 is so radical.  Now I am relearning.

John,

What is the SPs read-only problem?  Can you explain what you are trying to
do again?

Robert

At 12:00 PM 1/27/2006, you wrote:
>Date: Fri, 27 Jan 2006 12:19:34 -0500
>From: "Susan Harkins" <harkinsss at bellsouth.net>
>Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <002a01c62365$e41183e0$aeb3d6d1 at SUSANONE>
>Content-Type: text/plain;       charset="us-ascii"
>
>
>To be honest, once I get over the learning curve I am leaning towards 
>abandoning the MDB as a BE.
>
>========John, if I stay in this market, I am seriously considering the 
>same thing.
>
>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

_______________________________________________
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 Jan 28 14:46:01 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Sat, 28 Jan 2006 12:46:01 -0800
Subject: [dba-SQLServer] SQL 2005 Server Management Studio
In-Reply-To: <002601c6241d$cd9ce1a0$657aa8c0@ColbyM6805>
Message-ID: <001201c6244b$d97294b0$017ba8c0@xpserver>

Hi John:

I am not sure what your problem could be with 2005 Express. Sorry I can not
help you with that.

For binding a SP recordset to a form check out this link:
http://support.microsoft.com/kb/281998

HTH
Jim

 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: January 28, 2006 7:16 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

Build a SP in 2005 (express for me).  It is read-only, regardless of whether
I try and edit the data it inside of SMSE or in a pass-through out in
Access.

I am trying to bind a form to a SP recordset.


John W. Colby
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: Saturday, January 28, 2006 9:37 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio

I am already going that way and have been for over a year.  The problem is
that I essentially have wasted the last year because the difference between
VS 2003 and 2005 is so radical.  Now I am relearning.

John,

What is the SPs read-only problem?  Can you explain what you are trying to
do again?

Robert

At 12:00 PM 1/27/2006, you wrote:
>Date: Fri, 27 Jan 2006 12:19:34 -0500
>From: "Susan Harkins" <harkinsss at bellsouth.net>
>Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <002a01c62365$e41183e0$aeb3d6d1 at SUSANONE>
>Content-Type: text/plain;       charset="us-ascii"
>
>
>To be honest, once I get over the learning curve I am leaning towards 
>abandoning the MDB as a BE.
>
>========John, if I stay in this market, I am seriously considering the 
>same thing.
>
>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



From martyconnelly at shaw.ca  Sun Jan 29 14:42:45 2006
From: martyconnelly at shaw.ca (MartyConnelly)
Date: Sun, 29 Jan 2006 12:42:45 -0800
Subject: [dba-SQLServer] Determine status or start SQL Express
References: <001201c6244b$d97294b0$017ba8c0@xpserver>
Message-ID: <43DD28C5.10202@shaw.ca>

Useful piece of vb.net code, I wonder if I can rewrite into VBA.


  How to detect the status of the SQL Server Express service or start
  the SQL Server Express service by using Visual Basic

http://support.microsoft.com/kb/912426/en-us?spid=2855

-- 
Marty Connelly
Victoria, B.C.
Canada





From rl_stewart at highstream.net  Mon Jan 30 14:25:43 2006
From: rl_stewart at highstream.net (Robert L. Stewart)
Date: Mon, 30 Jan 2006 14:25:43 -0600
Subject: [dba-SQLServer] dba-SQLServer Digest, Vol 35, Issue 29
In-Reply-To: <mailman.2652.1138464557.18500.dba-sqlserver@databaseadviso
	rs.com>
References: <mailman.2652.1138464557.18500.dba-sqlserver@databaseadvisors.com>
Message-ID: <6.2.3.4.2.20060130135538.03048618@pop3.highstream.net>

John,

Now I see.  The trick is that you cannot bind the form to the 
SP.  You are going to have to do it as an unbound form.  Then use 
additional SPs to do the updates and deletes.

Robert

At 10:09 AM 1/28/2006, you wrote:
>Date: Sat, 28 Jan 2006 10:16:23 -0500
>From: "John Colby" <jwcolby at ColbyConsulting.com>
>Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <002601c6241d$cd9ce1a0$657aa8c0 at ColbyM6805>
>Content-Type: text/plain;       charset="us-ascii"
>
>Build a SP in 2005 (express for me).  It is read-only, regardless of whether
>I try and edit the data it inside of SMSE or in a pass-through out in
>Access.
>
>I am trying to bind a form to a SP recordset.
>
>
>John W. Colby




From accessd at shaw.ca  Mon Jan 30 15:07:51 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Mon, 30 Jan 2006 13:07:51 -0800
Subject: [dba-SQLServer] dba-SQLServer Digest, Vol 35, Issue 29
In-Reply-To: <6.2.3.4.2.20060130135538.03048618@pop3.highstream.net>
Message-ID: <002101c625e1$3b2dbb80$017ba8c0@xpserver>

I concur. There is third-party software that can emulate a bound connection,
at a cost of course and then there is always a .Net solution.

Jim 

PS I have been discussing this point for almost 10 years, Bound versus
Unbound and that you just can not get here from there. The old ways die
hard.

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L.
Stewart
Sent: January 30, 2006 12:26 PM
To: dba-sqlserver at databaseadvisors.com
Cc: jwcolby at ColbyConsulting.com
Subject: Re: [dba-SQLServer] dba-SQLServer Digest, Vol 35, Issue 29

John,

Now I see.  The trick is that you cannot bind the form to the 
SP.  You are going to have to do it as an unbound form.  Then use 
additional SPs to do the updates and deletes.

Robert

At 10:09 AM 1/28/2006, you wrote:
>Date: Sat, 28 Jan 2006 10:16:23 -0500
>From: "John Colby" <jwcolby at ColbyConsulting.com>
>Subject: Re: [dba-SQLServer] SQL 2005 Server Management Studio
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <002601c6241d$cd9ce1a0$657aa8c0 at ColbyM6805>
>Content-Type: text/plain;       charset="us-ascii"
>
>Build a SP in 2005 (express for me).  It is read-only, regardless of
whether
>I try and edit the data it inside of SMSE or in a pass-through out in
>Access.
>
>I am trying to bind a form to a SP recordset.
>
>
>John W. Colby


_______________________________________________
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  Mon Jan 30 16:33:58 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Mon, 30 Jan 2006 14:33:58 -0800
Subject: [dba-SQLServer] Best way to do a large delete
In-Reply-To: <BAY106-DAV8DD1A68946E8D3B0C49BA84150@phx.gbl>
References: <D0BF9C78D1C45C418541C852C8944FE2025E6B@qub-xchange-01.ads.qub.ac.uk>
	<BAY106-DAV8DD1A68946E8D3B0C49BA84150@phx.gbl>
Message-ID: <b874372a0601301433p3cff896bjc93330880b86bc07@mail.gmail.com>

That's a whole lotta deletes :)  setting the database to simple recovery
will aid you in not logging each record.  You may even get some performance
help if you set your view to a WITH(NOLOCK) option.  That way it doesn't
bother to lock any records while reading the view.  I'm going to just guess
that these 25million records are backed up.

one thing you might want to do is JOIN on the VIEW and run you delete in the
following way

Delete
>From Claims
         INNER JOIN SessionView WITH(NOLOCK)
ON Claims.SessionID = SessionView.SessionID

Joins are FASTER than IN where clauses and thus you should yeild much better
performance. (and yes you're deleting from the claims table.)

On 1/26/06, Nancy Lytle <word_diva at hotmail.com> wrote:
>
>
> I have to do a delete from a table with about 25 million rows.  I need to
> delete about 4 million rows, based on the date in another table
>
> Table Session
>
> SessionID       SessionDate
> 1               1/25/2004
> 2               7/25/2001
> I have created a view (SessionView) containing all sessionid's where the
> sessiondate less than 3 years old.
>
> (Create view SessionView
> As
> Select SessionID
> >From Session
> Where
> Session.sessiondate >= getdate() - 1095)
>
>
> Table Claims
>
> ClaimID SessionID               etc     etc                     etc
> 24578           1                       15      HealthPractice  5554441234
> 6548975 2                       52      ChirocPract             5551234567
>
> What I need is to delete all rows from Table Claims that have sessionids
> in
> SessionView.
>
> Delete
> >From Claims
> Where Claims.sessionID In (Select SessionID from SessionView)
>
> -In this case ClaimID 6548975 would be deleted but ClaimID 24578 would
> not.
>
> But I must be doing something wrong (I am very new at SQL Server, and have
> never done a large scale delete that wasn't just straight forward),
> because
> the delete seems to take forever.  Last time I had to stop it at just over
> 5
> hours because the network admin needed to do some work on the server and
> reboot it.
>
> I have set the recovery to simple, and the server has no other active
> databases or other applications running on it.
>
> Any assistance appreciated.
>
> Nancy Lytle
> N_Lytle at terplaum.umd.edu
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 267.14.22/239 - Release Date: 1/24/2006
>
> _______________________________________________
> 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 darrend at nimble.com.au  Mon Jan 30 18:04:26 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Tue, 31 Jan 2006 11:04:26 +1100
Subject: [dba-SQLServer] BIT OT:Report Services User Group
Message-ID: <20060131000437.NKWX15112.omta03ps.mx.bigpond.com@DENZILLAP>

Hi All - Cross Posted to AccessD
Bit OT
Anyone know a good Reporting Services user group?
 
Many thanks
 
Darren

-----------------------------



From fhtapia at gmail.com  Mon Jan 30 18:41:36 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Mon, 30 Jan 2006 16:41:36 -0800
Subject: [dba-SQLServer] BIT OT:Report Services User Group
In-Reply-To: <20060131000437.NKWX15112.omta03ps.mx.bigpond.com@DENZILLAP>
References: <20060131000437.NKWX15112.omta03ps.mx.bigpond.com@DENZILLAP>
Message-ID: <b874372a0601301641k76b0c9e1hf00e900f3410fdad@mail.gmail.com>

nope :(, I do as much research on it as I can on google groups :(, nothing
really great is available... I think mostly cuz Sql2000 ver was beta... I
expect to see much more documentation for it now that they have a version 2
(sqlserver2005)

On 1/30/06, Darren DICK <darrend at nimble.com.au> wrote:
>
> Hi All - Cross Posted to AccessD
> Bit OT
> Anyone know a good Reporting Services user group?
>
> Many thanks
>
> Darren
>
> -----------------------------
>
> _______________________________________________
> 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 darrend at nimble.com.au  Mon Jan 30 19:08:05 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Tue, 31 Jan 2006 12:08:05 +1100
Subject: [dba-SQLServer] Include data in Generate SQL Script
Message-ID: <20060131010816.JOHD19070.omta01ps.mx.bigpond.com@DENZILLAP>

Hi all
When I use "Generate SQL script" to create a 'blank' dB of tables etc,
is there an option, a tool (even 3rd party tool) that will allow me to say...
Select certain tables in the original dB and to to have the data in those tables
included in the "Generate SQL script"?
 
Make sense?
 
Many thanks
 
Darren

-----------------------------




From darrend at nimble.com.au  Mon Jan 30 19:10:12 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Tue, 31 Jan 2006 12:10:12 +1100
Subject: [dba-SQLServer] BIT OT:Report Services User Group
In-Reply-To: <b874372a0601301641k76b0c9e1hf00e900f3410fdad@mail.gmail.com>
Message-ID: <20060131011023.NONO17345.omta04ps.mx.bigpond.com@DENZILLAP>

Thanks Francisco
I do agree - it does look dire - Slim Pickins indeed
<sigh>

I'll post my Q to this list - maybe you guys can help :-)) 


Darren
------------------------------
 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia
Sent: Tuesday, 31 January 2006 11:42 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] BIT OT:Report Services User Group

nope :(, I do as much research on it as I can on google groups :(, nothing
really great is available... I think mostly cuz Sql2000 ver was beta... I expect
to see much more documentation for it now that they have a version 2
(sqlserver2005)

On 1/30/06, Darren DICK <darrend at nimble.com.au> wrote:
>
> Hi All - Cross Posted to AccessD
> Bit OT
> Anyone know a good Reporting Services user group?
>
> Many thanks
>
> Darren
>
> -----------------------------
>
> _______________________________________________
> 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 darrend at nimble.com.au  Mon Jan 30 20:45:38 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Tue, 31 Jan 2006 13:45:38 +1100
Subject: [dba-SQLServer] Reporting Services Q
Message-ID: <20060131024555.RWOB17345.omta04ps.mx.bigpond.com@DENZILLAP>

Hello all
I have a nice function that finds the file name from a given path
Function is called f_GetPath - Picked it up from the AccessD Archives - See foot
of this email
 
To call it in access I would do something like...
Private Sub txtSomeTextField_AfterUpdate()
    debug.print f_GetPath(me.txtSomeTextField) 
End Sub
 
So if the original value passed was C:\Program Files\Some Folder\coolfile.txt
the result in the debug window would be coolfile.txt
 
 
In Reporting Services I have a text Box
With a value of Fields!FileName.Value
It shows values similar to w:\Operations\Data Files\ImportedData\WW23879.A23
All I want to show is the actual file name bit not the full path - EG
WW23879.A23
 
SO I set the value of the text box to  f_GetPath(Fields!Filename.Value)
And placed the f_GetPath function inside the MacroExplorer Under MyMacros
 
But now when I preview the report I get...
The value expression for the textbox 'txtFileName' contains an error: [BC30451]
Name 'f_GetPath' is not declared.

So...How do I declare f_GetPath
 
Many thanks in advance
 
Darren

-----------------------------

Function f_GetPath(ByVal aPath) As String

' Strips the path name from the supplied file and path name

' leaves the trailing slash on there

Dim foo As Integer, aSlash As Integer

aSlash = 0

foo = InStr(aPath, "\")

While (foo > 0)

aSlash = foo

foo = InStr(aSlash + 1, aPath, "\")

End While

If aSlash > 0 Then

f_GetPath = Left$(aPath, aSlash)

Else

f_GetPath = aPath

End If

End Function



From accessd at shaw.ca  Tue Jan 31 00:54:32 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Mon, 30 Jan 2006 22:54:32 -0800
Subject: [dba-SQLServer] Include data in Generate SQL Script
In-Reply-To: <20060131010816.JOHD19070.omta01ps.mx.bigpond.com@DENZILLAP>
Message-ID: <000601c62633$305bada0$017ba8c0@xpserver>

Darren:

I am not sure what you mean but you can transfer data by simply exporting it
from one set of tables and importing it into another set of tables in the
current db. 

...or have you looked at the 'INTO' like: "SELECT * INTO MyRemoteTableName
IN '\\server\databse\LocationOfMyRemoteMDB' from MyLocalTable;" Using this
select in conjunction with an 'INSERT' sql can extract data from one MDB and
place it into another.

Syntax

SELECT column_name(s) INTO newtable [IN externaldatabase] FROM source 

HTH
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: January 30, 2006 5:08 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Include data in Generate SQL Script

Hi all
When I use "Generate SQL script" to create a 'blank' dB of tables etc,
is there an option, a tool (even 3rd party tool) that will allow me to
say...
Select certain tables in the original dB and to to have the data in those
tables
included in the "Generate SQL script"?
 
Make sense?
 
Many thanks
 
Darren

-----------------------------


_______________________________________________
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 Jan 31 01:50:56 2006
From: fhtapia at gmail.com (Francisco Tapia)
Date: Mon, 30 Jan 2006 23:50:56 -0800
Subject: [dba-SQLServer] BIT OT:Report Services User Group
In-Reply-To: <20060131011023.NONO17345.omta04ps.mx.bigpond.com@DENZILLAP>
References: <b874372a0601301641k76b0c9e1hf00e900f3410fdad@mail.gmail.com>
	<20060131011023.NONO17345.omta04ps.mx.bigpond.com@DENZILLAP>
Message-ID: <b874372a0601302350l57cdd4d9l68efea7960c4c0ae@mail.gmail.com>

i'll answer what I can... one thing I found out that unlike access where you
can take the already available textboxes and reference them, you can't do
that in reporting services... that is.. if you have textbox1 w/ sums and
textbox2 w/ sums you can't have textbox3 = textbox 1+2, ou have to do the
sums in textbox3 all over again... :(



On 1/30/06, Darren DICK <darrend at nimble.com.au> wrote:
>
> Thanks Francisco
> I do agree - it does look dire - Slim Pickins indeed
> <sigh>
>
> I'll post my Q to this list - maybe you guys can help :-))
>
>
> Darren
> ------------------------------
>
>
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco
> Tapia
> Sent: Tuesday, 31 January 2006 11:42 AM
> To: dba-sqlserver at databaseadvisors.com
> Subject: Re: [dba-SQLServer] BIT OT:Report Services User Group
>
> nope :(, I do as much research on it as I can on google groups :(, nothing
> really great is available... I think mostly cuz Sql2000 ver was beta... I
> expect
> to see much more documentation for it now that they have a version 2
> (sqlserver2005)
>
> On 1/30/06, Darren DICK <darrend at nimble.com.au> wrote:
> >
> > Hi All - Cross Posted to AccessD
> > Bit OT
> > Anyone know a good Reporting Services user group?
> >
> > Many thanks
> >
> > Darren
> >
> > -----------------------------
> >
> > _______________________________________________
> > 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 Robin at rolledgold.net  Tue Jan 31 04:07:04 2006
From: Robin at rolledgold.net (Robin )
Date: Tue, 31 Jan 2006 10:07:04 -0000
Subject: [dba-SQLServer] BIT OT:Report Services User Group
Message-ID: <560E2B80EC8F624B93A87B943B7A9CD542F8DC@rgiserv.rg.local>

Darren,
Came across this book on Amazon - don't know the Author but might be
worth a look
http://www.amazon.com/gp/product/0072232161/103-2241368-7005434?v=glance
&n=283155
Rgds
Robin Lawrence


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren
DICK
Sent: 31 January 2006 00:04
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] BIT OT:Report Services User Group


Hi All - Cross Posted to AccessD
Bit OT
Anyone know a good Reporting Services user group?
 
Many thanks
 
Darren

-----------------------------

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From Paul.Hartland at orridge.co.uk  Tue Jan 31 06:06:57 2006
From: Paul.Hartland at orridge.co.uk (Paul Hartland)
Date: Tue, 31 Jan 2006 12:06:57 -0000
Subject: [dba-SQLServer] SQL Server Database Replication Between Two Servers
Message-ID: <14A7AB003EFD444BBB193A23128DA20EC035A1@AL-PRI.Aldridge.local>

To all,

We have two servers (for the purpose of security lets call them SRV_1
and SRV_2) which both have a copy of SQL Server 2000 on them, onto which
I have placed a test database (Dbase_Rep).  When a user updates the
database on SRV_1 I need the changes to also be made on SRV_2 either
instantly or at a desired time interval.  I know this can be done and
have had a quick play and almost got it there.

Does anyone have an idiot proof step by step guide starting from scratch
or know where I can get one from.

Thanks in advance for any help on this. 


PAUL HARTLAND
Database Designer/Programmer
paul.hartland at orridge.co.uk
DDI - 01922 472031
Mobile - 07730 523179

_______________________________________________

*  This message is confidential.
*  This email, its content and any files transmitted with it are intended solely for the addressee and may be legally privileged and/or confidential.
*  Access by any other party is unauthorised without the express written permission of the sender.
*  If you have received this email in error you may not copy or use the contents, attachments or information in any way and any review, use, dissemination, forwarding, disclosure, alteration, printing of this information is strictly prohibited. Please destroy it and notify the sender via return e-mail.
*  This email has been prepared using information believed by Paul Hartland to be reliable and accurate, but the company makes no warranty as to accuracy or completeness. In particular the author does not accept responsibility for changes made to this email after it was sent.
*  Any opinions expressed in this document are those of the author and do not necessarily reflect the opinions of the company or its affiliates.

The Orridge web site can be found at:
http://www.orridge.co.uk




From darrend at nimble.com.au  Tue Jan 31 06:18:32 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Tue, 31 Jan 2006 23:18:32 +1100
Subject: [dba-SQLServer] Include data in Generate SQL Script
In-Reply-To: <000601c62633$305bada0$017ba8c0@xpserver>
Message-ID: <20060131121853.LBRI18661.omta02sl.mx.bigpond.com@DENZILLAP>

Hi Jim et al

I like your Select * INTO business
Does it work with SQL?

Anyway...

I found a brilliant - and free
SPROC to do it for us

We wanted to create several new 'blank' SQL dbs using scripts from Original dB
with about 450 tables
The majority of the tables we only wanted the table structure so the standard
EntManager script feature was fine
BUT
We wanted to populate our destination new 'blank' dB with data from a few tables
from our Original as we went
Not all - just a few - Because they are needed tables in each and every new
'blank' db but they
have thousands of rows of data in 'em

Didn't want to write Insert Field, field WITH value, value for each ROW of the
needed tables 

This SPROC saved the day and is brilliantly easy to use

No affiliation at all - here's the link - heaps of other stuff there as well 

http://vyaskn.tripod.com/code.htm#inserts

Darren
------------------------------
T: 0424 696 433
 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Tuesday, 31 January 2006 5:55 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Include data in Generate SQL Script

Darren:

I am not sure what you mean but you can transfer data by simply exporting it
from one set of tables and importing it into another set of tables in the
current db. 

...or have you looked at the 'INTO' like: "SELECT * INTO MyRemoteTableName IN
'\\server\databse\LocationOfMyRemoteMDB' from MyLocalTable;" Using this select
in conjunction with an 'INSERT' sql can extract data from one MDB and place it
into another.

Syntax

SELECT column_name(s) INTO newtable [IN externaldatabase] FROM source 

HTH
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: January 30, 2006 5:08 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Include data in Generate SQL Script

Hi all
When I use "Generate SQL script" to create a 'blank' dB of tables etc, is there
an option, a tool (even 3rd party tool) that will allow me to say...
Select certain tables in the original dB and to to have the data in those tables
included in the "Generate SQL script"?
 
Make sense?
 
Many thanks
 
Darren

-----------------------------


_______________________________________________
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  Tue Jan 31 06:19:52 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Tue, 31 Jan 2006 23:19:52 +1100
Subject: [dba-SQLServer] BIT OT:Report Services User Group
In-Reply-To: <560E2B80EC8F624B93A87B943B7A9CD542F8DC@rgiserv.rg.local>
Message-ID: <20060131122013.QNVT1358.omta03sl.mx.bigpond.com@DENZILLAP>

Thanks Robin

Will look at it

Thanks Francisco
Yes I am finding out that despite the rhetoric it is not very similar to Access
report designing 


Darren
------------------------------
T: 0424 696 433
 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robin 
Sent: Tuesday, 31 January 2006 9:07 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] BIT OT:Report Services User Group

Darren,
Came across this book on Amazon - don't know the Author but might be worth a
look http://www.amazon.com/gp/product/0072232161/103-2241368-7005434?v=glance
&n=283155
Rgds
Robin Lawrence


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: 31 January 2006 00:04
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] BIT OT:Report Services User Group


Hi All - Cross Posted to AccessD
Bit OT
Anyone know a good Reporting Services user group?
 
Many thanks
 
Darren

-----------------------------

_______________________________________________
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  Tue Jan 31 08:15:22 2006
From: accessd at shaw.ca (Jim Lawrence)
Date: Tue, 31 Jan 2006 06:15:22 -0800
Subject: [dba-SQLServer] Include data in Generate SQL Script
In-Reply-To: <20060131121853.LBRI18661.omta02sl.mx.bigpond.com@DENZILLAP>
Message-ID: <000501c62670$c60e81f0$017ba8c0@xpserver>

Hi Darren:

I have used in Access and it is a standard method but I have never tried in
MS SQL as there are so many other ways of building your own import and
export scripts.

Looks like a good site.

Jim 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: January 31, 2006 4:19 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Include data in Generate SQL Script

Hi Jim et al

I like your Select * INTO business
Does it work with SQL?

Anyway...

I found a brilliant - and free
SPROC to do it for us

We wanted to create several new 'blank' SQL dbs using scripts from Original
dB
with about 450 tables
The majority of the tables we only wanted the table structure so the
standard
EntManager script feature was fine
BUT
We wanted to populate our destination new 'blank' dB with data from a few
tables
from our Original as we went
Not all - just a few - Because they are needed tables in each and every new
'blank' db but they
have thousands of rows of data in 'em

Didn't want to write Insert Field, field WITH value, value for each ROW of
the
needed tables 

This SPROC saved the day and is brilliantly easy to use

No affiliation at all - here's the link - heaps of other stuff there as well


http://vyaskn.tripod.com/code.htm#inserts

Darren
------------------------------
T: 0424 696 433
 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim
Lawrence
Sent: Tuesday, 31 January 2006 5:55 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Include data in Generate SQL Script

Darren:

I am not sure what you mean but you can transfer data by simply exporting it
from one set of tables and importing it into another set of tables in the
current db. 

...or have you looked at the 'INTO' like: "SELECT * INTO MyRemoteTableName
IN
'\\server\databse\LocationOfMyRemoteMDB' from MyLocalTable;" Using this
select
in conjunction with an 'INSERT' sql can extract data from one MDB and place
it
into another.

Syntax

SELECT column_name(s) INTO newtable [IN externaldatabase] FROM source 

HTH
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: January 30, 2006 5:08 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Include data in Generate SQL Script

Hi all
When I use "Generate SQL script" to create a 'blank' dB of tables etc, is
there
an option, a tool (even 3rd party tool) that will allow me to say...
Select certain tables in the original dB and to to have the data in those
tables
included in the "Generate SQL script"?
 
Make sense?
 
Many thanks
 
Darren

-----------------------------


_______________________________________________
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 darrend at nimble.com.au  Tue Jan 31 08:18:41 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Wed, 1 Feb 2006 01:18:41 +1100
Subject: [dba-SQLServer] Include data in Generate SQL Script
In-Reply-To: <000501c62670$c60e81f0$017ba8c0@xpserver>
Message-ID: <20060131141913.RXOF1358.omta03sl.mx.bigpond.com@DENZILLAP>

Thanks Jim
 


Darren
------------------------------
T: 0424 696 433
 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Wednesday, 1 February 2006 1:15 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Include data in Generate SQL Script

Hi Darren:

I have used in Access and it is a standard method but I have never tried in MS
SQL as there are so many other ways of building your own import and export
scripts.

Looks like a good site.

Jim 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: January 31, 2006 4:19 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Include data in Generate SQL Script

Hi Jim et al

I like your Select * INTO business
Does it work with SQL?

Anyway...

I found a brilliant - and free
SPROC to do it for us

We wanted to create several new 'blank' SQL dbs using scripts from Original dB
with about 450 tables The majority of the tables we only wanted the table
structure so the standard EntManager script feature was fine BUT We wanted to
populate our destination new 'blank' dB with data from a few tables from our
Original as we went Not all - just a few - Because they are needed tables in
each and every new 'blank' db but they have thousands of rows of data in 'em

Didn't want to write Insert Field, field WITH value, value for each ROW of the
needed tables 

This SPROC saved the day and is brilliantly easy to use

No affiliation at all - here's the link - heaps of other stuff there as well


http://vyaskn.tripod.com/code.htm#inserts

Darren
------------------------------
T: 0424 696 433
 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Tuesday, 31 January 2006 5:55 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Include data in Generate SQL Script

Darren:

I am not sure what you mean but you can transfer data by simply exporting it
from one set of tables and importing it into another set of tables in the
current db. 

...or have you looked at the 'INTO' like: "SELECT * INTO MyRemoteTableName IN
'\\server\databse\LocationOfMyRemoteMDB' from MyLocalTable;" Using this select
in conjunction with an 'INSERT' sql can extract data from one MDB and place it
into another.

Syntax

SELECT column_name(s) INTO newtable [IN externaldatabase] FROM source 

HTH
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Darren DICK
Sent: January 30, 2006 5:08 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Include data in Generate SQL Script

Hi all
When I use "Generate SQL script" to create a 'blank' dB of tables etc, is there
an option, a tool (even 3rd party tool) that will allow me to say...
Select certain tables in the original dB and to to have the data in those tables
included in the "Generate SQL script"?
 
Make sense?
 
Many thanks
 
Darren

-----------------------------


_______________________________________________
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 rl_stewart at highstream.net  Tue Jan 31 09:09:15 2006
From: rl_stewart at highstream.net (Robert L. Stewart)
Date: Tue, 31 Jan 2006 09:09:15 -0600
Subject: [dba-SQLServer] Include data in Generate SQL Script
In-Reply-To: <mailman.801.1138693844.7309.dba-sqlserver@databaseadvisors .com>
References: <mailman.801.1138693844.7309.dba-sqlserver@databaseadvisors.com>
Message-ID: <6.2.3.4.2.20060131090835.03033c20@pop3.highstream.net>

It is the DTS Create Server Objects object.  Check it out.

At 01:50 AM 1/31/2006, you wrote:
>Date: Tue, 31 Jan 2006 12:08:05 +1100
>From: "Darren DICK" <darrend at nimble.com.au>
>Subject: [dba-SQLServer] Include data in Generate SQL Script
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID:
>         <20060131010816.JOHD19070.omta01ps.mx.bigpond.com at DENZILLAP>
>Content-Type: text/plain;       charset="us-ascii"
>
>Hi all
>When I use "Generate SQL script" to create a 'blank' dB of tables etc,
>is there an option, a tool (even 3rd party tool) that will allow me to say...
>Select certain tables in the original dB and to to have the data in 
>those tables
>included in the "Generate SQL script"?
>
>Make sense?
>
>Many thanks
>
>Darren




From darrend at nimble.com.au  Tue Jan 31 09:21:16 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Wed, 1 Feb 2006 02:21:16 +1100
Subject: [dba-SQLServer] Include data in Generate SQL Script
In-Reply-To: <6.2.3.4.2.20060131090835.03033c20@pop3.highstream.net>
Message-ID: <20060131152145.SGZZ1358.omta03sl.mx.bigpond.com@DENZILLAP>

Hi Robert
Where is that in EntManager? 


Darren
------------------------------

 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L.
Stewart
Sent: Wednesday, 1 February 2006 2:09 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Include data in Generate SQL Script

It is the DTS Create Server Objects object.  Check it out.

At 01:50 AM 1/31/2006, you wrote:
>Date: Tue, 31 Jan 2006 12:08:05 +1100
>From: "Darren DICK" <darrend at nimble.com.au>
>Subject: [dba-SQLServer] Include data in Generate SQL Script
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID:
>         <20060131010816.JOHD19070.omta01ps.mx.bigpond.com at DENZILLAP>
>Content-Type: text/plain;       charset="us-ascii"
>
>Hi all
>When I use "Generate SQL script" to create a 'blank' dB of tables etc, 
>is there an option, a tool (even 3rd party tool) that will allow me to say...
>Select certain tables in the original dB and to to have the data in 
>those tables included in the "Generate SQL script"?
>
>Make sense?
>
>Many thanks
>
>Darren


_______________________________________________
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 Jan 31 09:29:37 2006
From: rl_stewart at highstream.net (Robert L. Stewart)
Date: Tue, 31 Jan 2006 09:29:37 -0600
Subject: [dba-SQLServer] Include data in Generate SQL Script
In-Reply-To: <mailman.935.1138720909.7309.dba-sqlserver@databaseadvisors .com>
References: <mailman.935.1138720909.7309.dba-sqlserver@databaseadvisors.com>
Message-ID: <6.2.3.4.2.20060131092807.0309c678@pop3.highstream.net>

It is in Data Transformation Services.
There is an object in the tools pallet that is the copy database objects.
You can configure it to copy all of the objects and to copy data also.

At 09:21 AM 1/31/2006, you wrote:
>Date: Wed, 1 Feb 2006 02:21:16 +1100
>From: "Darren DICK" <darrend at nimble.com.au>
>Subject: Re: [dba-SQLServer] Include data in Generate SQL Script
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID:
>         <20060131152145.SGZZ1358.omta03sl.mx.bigpond.com at DENZILLAP>
>Content-Type: text/plain;       charset="us-ascii"
>
>Hi Robert
>Where is that in EntManager?




From darrend at nimble.com.au  Tue Jan 31 09:31:41 2006
From: darrend at nimble.com.au (Darren DICK)
Date: Wed, 1 Feb 2006 02:31:41 +1100
Subject: [dba-SQLServer] Include data in Generate SQL Script
In-Reply-To: <6.2.3.4.2.20060131092807.0309c678@pop3.highstream.net>
Message-ID: <20060131153209.SINZ1358.omta03sl.mx.bigpond.com@DENZILLAP>

Sorry
When I am in EntManager
I select my dB then
Select Tools|Data Transformation Services
I only See...
Export Data or
Import Data
 


Darren
------------------------------
T: 0424 696 433
 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L.
Stewart
Sent: Wednesday, 1 February 2006 2:30 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Include data in Generate SQL Script

It is in Data Transformation Services.
There is an object in the tools pallet that is the copy database objects.
You can configure it to copy all of the objects and to copy data also.

At 09:21 AM 1/31/2006, you wrote:
>Date: Wed, 1 Feb 2006 02:21:16 +1100
>From: "Darren DICK" <darrend at nimble.com.au>
>Subject: Re: [dba-SQLServer] Include data in Generate SQL Script
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID:
>         <20060131152145.SGZZ1358.omta03sl.mx.bigpond.com at DENZILLAP>
>Content-Type: text/plain;       charset="us-ascii"
>
>Hi Robert
>Where is that in EntManager?


_______________________________________________
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 Jan 31 12:26:48 2006
From: rl_stewart at highstream.net (Robert L. Stewart)
Date: Tue, 31 Jan 2006 12:26:48 -0600
Subject: [dba-SQLServer] Include data in Generate SQL Script
In-Reply-To: <mailman.5.1138730404.17837.dba-sqlserver@databaseadvisors. com>
References: <mailman.5.1138730404.17837.dba-sqlserver@databaseadvisors.com>
Message-ID: <6.2.3.4.2.20060131122609.030cbee8@pop3.highstream.net>

You have to create a local package and then you get the full 
capabilities of DTS.

At 12:00 PM 1/31/2006, you wrote:
>Date: Wed, 1 Feb 2006 02:31:41 +1100
>From: "Darren DICK" <darrend at nimble.com.au>
>Subject: Re: [dba-SQLServer] Include data in Generate SQL Script
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID:
>         <20060131153209.SINZ1358.omta03sl.mx.bigpond.com at DENZILLAP>
>Content-Type: text/plain;       charset="us-ascii"
>
>Sorry
>When I am in EntManager
>I select my dB then
>Select Tools|Data Transformation Services
>I only See...
>Export Data or
>Import Data
>
>
>
>Darren




From KP at sdsonline.net  Tue Jan 31 18:30:46 2006
From: KP at sdsonline.net (Kath Pelletti)
Date: Wed, 1 Feb 2006 11:30:46 +1100
Subject: [dba-SQLServer] For Susan / Martin
Message-ID: <001101c626c6$bef27a60$6501a8c0@user>

Susan / Martin

Just wondering whether you have a new version of your access to sql book for Sql Server 2005?

rgds
Kath


From harkinsss at bellsouth.net  Tue Jan 31 21:10:25 2006
From: harkinsss at bellsouth.net (Susan Harkins)
Date: Tue, 31 Jan 2006 22:10:25 -0500
Subject: [dba-SQLServer] For Susan / Martin
In-Reply-To: <001101c626c6$bef27a60$6501a8c0@user>
Message-ID: <001a01c626dd$151a4970$b5b3d6d1@SUSANONE>

No, I think most of the information -- if going from Access to SQL Server
2000 is probably still the same -- Martin? 

There may be subtle changes between Jet SQL and T-SQL that I don't know
about, but I wouldn't expect much. Martin will know better than me -- I
haven't done much with 2005 -- been busy with SQL Server Express, but
they're still just as similar as they always have been. 

Susan H. 

Just wondering whether you have a new version of your access to sql book for
Sql Server 2005?